Im working on my first project in unity and I am running into a problem where the camera is not turning properly, i cannot look up or down only left and right and even then it does not turn the camera but the angle of the environment here are some screenshots of the setup of the project.[
Related
I am currently writing a 2D game in unity and whenever I build the actual game, the sprites all disappear, the player is the only thing that remains.
However, the sprites are still there, just invisible. It's not an issue of order of layer and am having trouble fixing it.
I am using SpriteShapeController.
SpriteShapeController auto shows as it having a sprite so it made me think I had a sprite already
I just made Custom Square Sprites and added them in.
When using the unity editor all animations tied to the camera work, but when build and deployed onto the hololens the animation wont process(being overridden by real life coordinates), the way to get around this is by attaching it to a random gameObject. My issue is giving the user the ability to roam around space whilst tying animations and force movements to the cameras parent(empty gameObject).
I have tried making the gameobject stay where the camera is but obviously this just makes for constant motion.
Is there any way to keep the cameras parent exactly where the camera is in order to stop the animations going glitchy?
So initially I had trouble with my character's left arm and gun clipping through objects(not entirely though) and I followed the instructions in this unity3D post to fix this issue(Read through the top answer so you know what I did).
Solution for FPS gun clipping through walls
Now I'm having trouble figuring out how to stop my player left arm and gun from rendering twice when he starts running fast(Doesn't occur when I'm just walking or slightly running). I know it has something to do with there being two cameras but I need an additional camera to stop the gun and the player's arm from clipping through objects.
Here is a picture that shows what I mean.
IF you look closely, you can see that the AK-47's magazine is being rendered twice(there is very small gap there) as well as the left arm. I've fiddled with both camera settings and could not figure out a way to stop this from happening. How do I go about fixing this issue?
You need to disable the gun layer from rendering with the first camera. The gun layer should only render on the second camera.
Everyone.
Vuforia Camera does not work, but only black screen on Android 6.0+ versions.
Vuforia Version is 6.2.2 and Unity version is 5.4.4
But vuforia camera works on less than android 5.0
How can I fix this issues?
I hope you to teach me about this.
This is an interesting problem I have and there is an unacceptable temporary fix I am using while testing this system out. For the iPhone 7, to get past this suspend the app and then return to it. After about 2 seconds the camera will work. I am guessing it will work similar for android. I will update with a better fix if I come by a real fix after my testing if I decide to use this system.
Edit:
Short answer:
Delete the meta data for any pre-existing custom camera controller script. If you are using your own camera controller you need to disable the vuforia one and delete the meta for that. You are basically hijacking the camera feed after it starts.
long: I began this application by building out my own system and to test vuforia I disabled these items (like the camera feed). I went through the logs and saw that even with these items disabled the camera feed was still running and this feed started AFTER the vuforia camera so basically my own start() methods (even though they were disabled) were hijacking the camera from vuforia. It turns out that my meta data for my camera controller script was still poised to run the script even though everything was disabled. After deleting my camera controller script meta data it worked fine. You can also just delete the camera controller and it will delete the meta. By camera controller I mean my custom written camera controller that was built before I added in vuforia. This is a hard to find fix because it works fine in unity, but not when you build out to a device. The meta doesn't seem to update for the device, just the unity engine.
If you are using the vuforia camera make sure you either use the vuforia plane that comes as a child of the camera or delete the meta data to whatever camera script you wrote. You should get camera feed in a new empty project just by dropping in the vuforia camera, there is no need to build your own script and if you do, make sure one isn't overriding the other like mine was.
If you want to simply test to make sure it isn't your device or code create a NEW empty unity project, import vuforia (no need to import the database, just the sdk) and then drop the vuforia camera into the project and test it. Don't add anything extra or do any image recognition. If this works, it's your code somewhere.
I am using Vuforia 6.2.10, Unity 5.4.4.f(64 bit) and a Nexus 7 Android 6. I had the same issue where the camera was black. I started over, adding one component at a time. The AR Camera alone worked fine. Adding a Target Image also worked. I added a plane and image to the TI and the camera failed to work. Setting the image texture type to Sprite 2d and ui seemed to help.
I discovered that by deleting the app from the device and creating a apk file each time it worked.
I am not sure I'd count on Vuforia in the near term.
I am trying to create a 2d platformer game in Unity 5 following these tutorials: https://www.3dbuzz.com/training/view/creating-2d-games-in-unity-45
I am however running into a problem where when I hit the play button in Unity my character simply does not appear inside the game. I made sure he is on the right layer and has all of the required scrips associated to him and still no dice...
Here is a copy of my source code: https://mega.co.nz/#!4YFAVLxA!8UZieNrqI3F1--4HsaLPPfw_ICbCkG7uGZVuWAfmSyY
In the end the issue was that my main camera was not far enough on the Z axis and unity was rendering my player behind the camera!
I fixed it by setting the camera's Z coordinate to -100 instead on -10.