Hello. Trying to get Adventure Creator to work with UFPS. I am new to both systems. To the best of my knowledge, I am using the latest versions of both assets (AC 1.48b & UFPS 1.5.1) I am using Unity 5.2.1p4. Here are the issues:
1. Errors
Error: (Hero AC(Clone) (vp_FPWeaponHandler)) Hierarchy error. This component must be added to a gameobject with vp_Weapon components in child gameobjects.
From my searching, I have seen that a whole lot of people have this problem, but have yet to see a solution that works. In fact, has anyone actually ever gotten AC to work with UFPS without errors?
In any case, if I add my "Hero AC" prefab to the scene before the game starts and retag the FPSCamera to MainCamera and retag MainCamera to untagged, I get the following error: MainCamera has no MainCamera component.
I'm not including the full text of these errors simply because I'm sure you're already familiar with them. In both cases, the game appears to still work, although in the first case, the animations for shooting in UFPS's third person view is screwed up, but this doesn't happen in the second case. I have read in another thread that it is pretty safe to just ignore "the MainCamera has no MainCamera component" error, but I am posting this to make sure there haven't been any development s since that thread. If the solution is still to ignore this error, then so be it for now. If there is a fix now known, I'd like to know it just because I hate errors :-)
2. No sound until the menu is brought up.
When the game starts, there is no sound. There continues to be no sound until I bring up the esc menu and then choose resume. Upon choosing resume to dismiss the menu, the sounds that were supposed to have played before play at that time. From that point on, all sounds play as they are supposed to.
I have found no info on how to fix this one.
Both of these issues also arise when using the "Advanced Player" AC prefab that is provided by Adventure Creator.
Thanks,
vance
Comments
1) I believe you have the MainCamera tagging the wrong way around. If the prefab is in the scene before the game starts, then the player camera must be untagged.
If the prefab is loaded in at runtime, then the player camera should be tagged as "MainCamera". In both cases, AC's MainCamera should remain tagged as "MainCamera".
2) I have the same issue, but it's not clear to me why this is the case. However, I do find that the issue does not occur if the player prefab is in the scene before the game runs. Try tagging the components as suggested above, and see if things improve.
The ideal workflow would be that you can have both the MainCameraVR and the UFPS camera in the scene together, so that you can either give the player full control, or cut to other cameras, without having to change the core setup of the scene.