My Post processing worked when i started my project but now that i am several months into it, my scene view turns blank and gray when i check the post processing from the dropdown. I am using Unity 2019.4 Any ideas? My first posting was deleted because of clarity without notifying me, so I have been stuck on project for days waiting for an answer that was never going to come. I don't know how much more I can say. I you don't understand my post then don't just delete it, let me know what you don't understand.
It looks like i may have fixed it. I got an error message saying that it couldn't add another camera, so i looked at the FPS. I didn't see anything wrong so I just removed it and reinstalled the FPS controller. That seems to have fixed it. Thanks for the responses.
Related
Really really simply question.
In my own computer when I create a button with Xcode, I can see the blue outline.
But, in my office's computer I do the same thing I can't see the blue outline (and can't figure out how much bigger the button is).
What is happening?
I've recorded a video and uploaded to YouTube in order to be more clear — https://youtu.be/Bl_aOXxtIeA
PS: I've been trying to solve this thing on last 3 days, and no luck, even contacting a friend which is an iOS developer.
Folks, I just found the solution (trying by myself). Thanks for the replies too.
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!
I'm having a problem getting changes that I make to the state machine transitions to 'stick'. I will create a transition with the timings that I want, the click on another transition then click back... And the settings I"d created for the transition are no longer there.
I've included an huge png to try to try and illustrate my point... I don't know if anyone has had any similar issues, or can see quite what I'm doing wrong? It seems werid that the transitions kind of 'flick back' to another state. Almost like the state I'm trying to provide it isn't accepted...
Any help would be greatly appreciated, I've been confused about this for a long time.
Any further information required I'm happy to provide.
I am doing an IM application with the lwuit api, In my message form I have an issue, I can't view the last message when the message's contents fill the screen, I have to scroll manually and it is embarrassing.
I have tried everything by my side but still I didn't get the solution.
I hope someone will help me out
Thanks
I have tried to do the same thing as you long time ago but the scrolling of my app became crazy. In this video you can find a similar app and in the description you can find the links to the code. Take a look on them, please.
http://www.youtube.com/watch?v=LFClNS5vWQs
Good luck!
I have this map view with a bunch of overlays. When I hit the home button and re-open it, all the overlays disappear for a second and immediately re-appear. At first I thought it was my code that was doing it but I put breakpoints pretty much everywhere and none of my code seems to be triggering the "reset". Even mapView:viewForOverlay: doesn't get called before the overlays reappear.
I thought maybe this is an inevitable behavior of MKMapView, but it seems like Maps.app doesn't do it either — if you calculate a route and quit/re-open the app, the overlays stay there the whole time.
I'm thinking maybe MKMapView clears all of its annotations/overlays by default on quit so it takes less memory while staying backgrounded. Is there any way to avoid this? Kinda like Maps.app does?
EDIT: here's a small project I put together to demonstrate the problem. Just launch it in Simulator, click the home button, and re-open it. You'll see the map path overlay disappear for a moment.
This is more of a follow-up than an actual answer, but basically this issue has been flagged as a bug by Apple. I submitted this as a TSI to Apple a while ago and received the following answer:
Thanks for providing a sample project. I don't see any issues in your
code. At this point I recommend escalating the issue to engineering by
filing a bug about the "flicker" from the MKPolylineView being redrawn
at https://developer.apple.com/bugreporter/ and sending me the bug
number so I can use it to follow up.
I then submitted radar #11041378
Thanks again for your bug report. As it happens, I don't have a
workaround for you at this time. Engineering is still working on the
issue, but I don't have a timeline for a fix.
I'll go ahead and leave this incident open for you as long as bug
11041378 is open. If you have any questions about it's status in the future, or the status of a workaround, feel free to reply back and I
will check it for you.
If you have any comments for engineering, or want to tell the story of
why it's important to your situation, I'd actually encourage you to
put that directly in the bug. Since it's been assigned to engineering,
any comments will go directly to them.
I appended the following comment that describes why the issue is important to me:
This bug feels rather important to me as the user expects to find the
app in the exact state he left it when he quit the app. The flickering
overlays (sometimes disappearing for less than second, other times for
2-3s) may get the user confused about what is going on, when all he
really wants is to interact with the map/overlays right away.
Haven't heard back from Apple since. Hopefully this will get fixed in iOS 6?