On my computer everything looks fine, but on my laptop specific materials are all black. I've made sure i'm on the same version of the project. It is also black in the build.
I am using the customizableGrid from the asset store.
I have had this problem before, and for me it was related to lighting. It's a bit difficult to know if you're in the same position based on just the screenshot, but try - on your laptop - going into Window -> Lighting -> Settings and press "Generate Lighting" again. Could be worth a shot.
I have no idea why this works, but I'll post it anyway. For anyone else having the same issue this might work. Upload it to the collab cloud. Delete from disk, redownload from cloud. I've had the issue three times now, and everytime i redownload it from the cloud the textures are back. It is a weird glitch indeed, but at least I have a workaround.
Related
I created a Third Person project in Unreal engine. Everything was working fine for a while. Meaning, I was able to control the player when I previewed the game (play). Due to something I probably did, at one point I could no longer control the player in the preview mode. Instead, it seems that I am controlling the default player -- sort of a camera that hangs up in the sky. I checked all the settings Including the "Default Pawn Class" in the project settings, as well as in the world settings.
Not sure what I did wrong or what settings do I need to change. I would love to get some help.
Thanks.
By mistake, I was running in the simulate mode. I change back to the "Selected Viewport" mode and everything is back to normal.
Unity won't let me select objects on my scene without first selecting the object in the Hierarchy. This was all I could find on the issue.
However, it seems that they decided that closing and opening the scene window fixed the bug, but not so with me. Also note that I am on a blank project. Its been really difficult to work around this bug.
Edit:
I have even uninstalled Unity and reinstalled with the hopes that this would solve the problem, but unfortunately it did not. Thanks for any help ahead of time.
Honestly this is such an odd problem that I'm having difficulty knowing how to try and fix the problem. I also reported the bug as recommended below by NoëlWidmer, but even the staff who was very kind had no idea how to deal with the problem, and the advice he gave also didn't change a thing. Truly, I don't even know what more information I can give you guys because as I said I literally opened a new Unity project for the first time after reinstalling and was unable to select without first clicking on the hierarchy. Is this just a special freak case that landed with me or has this happened to anyone else?? Also I'm using a two year old Windows 8 Laptop with literally nothing installed on it but the Adobe suite and a few other game developer necessities, so my computer most likely is not the source of the problem.
Edit: a Clue??
Well I was messing around with the scene and hierarchy view in full screen, and I noticed something interesting after clicking on the object in the hierarchy and moving the object in the scene view:
Unfortunately my PrintScreen doesnt show the actual mouse, but as you can see the scene view acts as though I'm clicking on the object, but here at the same time I saw my real mouse off down to the right! Also while I've selected an object on the scene editor and I move my mouse off the scene window things get a bit off and the mouse will pop up on other sides of the window and so on. I don't know if that's normal and its that way for everyone or if it's just me and it might help figure out what's going on.
Man I've really been liking Unity but if this keeps up I think I'll have to drop it and find another software, because I certainly will never be able to design anything worth while if I have to select the object on the hierarchy every time for every single object.
Some bug for me on Mac platform. I resolve just entering and exit from fullscreen mode.
Probably may also work change layout with top-right combo.
I had similar issue while using older versions of unity (in addition inspector window lost the focus repeatedly). In my case rearraging editor windows and saving custom window layout solved it. As far as I remember, I just moved scene view outside Unity window (on the second screen) as well as hierarchy view, and saved resulting position as a new window layout.
Not sure if there is anything else I can tell about it, it's pretty mysterious problem.
I'm overwhelmed with joy right now!! The problem was indeed a bug. I was working on a project and moving objects around (still using the hierarchy to select objects) and then a split second later for absolutely no reason Unity decided to start working the way it should've!!! I guess its just one of those issues where you just have to cross your fingers and hope it'll resolve itself. I'm so glad this dumb issue resolved itself because I was about to tear my hair out and succumb to using another computer for my unity design, or even worse another software. Thank you to everyone who helped!
This is super strange. This simple button is not clickable at all. But when I close the Unity and Mono editors and fire it up again, it will work - only once. I mean, the second time you hit the play button, the button will not work anymore. I didn't change settings of the button or the canvas. I just put them in the scene and click play button. I think this is a bug? But there's no log i can see. This is bugging me for good 30 mins. I even restarted my PC and still working only on the first hit of play button. Thanks
EDIT: just found the problem. This problem occurs when you use the Unity Remote app on Android. It will work first. But when you try it the second time, buttons are not responding anymore. The only solution I found for this is to reinstall the Unity. Tried restarting PC but didn't work. Soo, peace out. Thanks
Try to turn on the Force Module Active property on inspector in EventSystem. I had the same problem on Version 5.3.1 on my machine (macbook pro mid 2010 on OSX El Capitan). Deleted the Unity, rolled back to 5.2.2, upgrade to 5.3.3, the problem is still there. Did that and somehow it works, but I don't know the reason why
I'm new to augmented reality, and I'm using vuforia 4.2.3 and unity 5, I followed all the steps trying to make a test run and whenever the camera detects the target the whole screen turn white, I've tried many thing but none of them worked, can someone help me?
I had a problem that sounds similar.
There is a known bug that causes white screen, could be related to that? See here for more info.
What worked for me was to change the VideoBackground.shader code, as described on that thread.
Go to Project>>Qualcomm Augmented reality>>Shaders
Double-click VideoBackground. This opens up Mono.
In the code, change where it says:
"queue"="geometry-11"
to this:
"queue"="Geometry"
Save, rebuild etc.
Worked for me.
I've got a mysterious problem with images and caching. In my project I've got 20 photos that elegantly fade in and out with a random function that changes up the order a bit.
I found that I didn't like one image in particular, image_1.png and wanted to push it back in the rotation (each time the app starts the images start with image_1.png). So, I swapped the name of image_1.png with that of image_16.png. When I look at image in the project folder and in Resources indeed the images are as they should be but when I run the app its the same old image that starts things out.
I have reset the sim, deleted the app from my iPhone, removed the images from the project and reimported them and still the same image.
Even odder.. I have an image_0.png that is no longer in the project file at all ... its not even on my hard drive.... but it shows up as well.
Do I have a ghost in my Mac or is this just seriously persistent cache?
Clean All Targets
Sounds like a persistent cache.
Let me guess: you have your images in a directory that you add to your project as a reference?
Yeah, that stuff's weird and buggy. Even in the latest xcode. I find it helps to recreate the folder with the new contents in a different place, then remove the old one from the project and add the new one. Perhaps even closing the project before re-adding.
XCode sucks.