Windows 7 64. I’ve tried opening different projects, restarting my computer, creating a new project, uninstalling unity, checked firewall exceptions, ran as administrator, and after a good bit of googling i didn’t find anyone else with the same issue.
6 Answers
6I know this sounds weird, but restart your computer and before you open unity turn off your internet. After you’ve done that open unity and open your project. Once the project is loaded you can turn you internet back on. This worked for me.
Well, turning off my internet for some reason stops my projects from loading in at the project select window. Or anything else for that matter. I tried to just straight up open up a scene from my project instead and that resulted in the same issue of only the process starting.
– GeorgeBGreenOkay nevermind that, i got it to work after one more restart, even though it took about 45 seconds from clicking the project to the editor actually launching. This is a really annoying issue and it seems multiple people are having it. Really hope it's fixed in the near future.
– GeorgeBGreenDoing that it seems to register the platform continually even after walking far away from it. That does explain the problem as it never seems to stop registering the platform.
– nilserlinghAs I recall it’s the server (or proxy) problem on a forum somewhere. My solution is to access Unity directly without the editor. Locate your asset, find your scenes, and double click on one of em.
It works for me at least 
I’ve been experiencing the same issue and it seems others are experiencing this as well. At first I thought it was just me! (had already reinstalled, deleted Library folder, deleted .meta files, etc)
Edit: I followed NSFS’s instructions and now it works. Thanks!
Just to clarify, it is missing one frame where it reaches the right edge correct? It would be best to place a separate debug.log for when the condition is met that says changing direction or something. I assume it has to be called at least once if it reaches the right edge and turns around. At this point I'd take a shot in the dark by changing the check from if the groundInfo.collider == false, to if groundInfo.collider == null; It's possible that there's something wonky happening there that I'm not familiar with. Personally, I always check to see if its null, not false.
– Chimer0sDone this similar to the answers above:
Restarted pc,
deleted these 3 folders:
Library,
Temp,
and the Custom GI Cache
Turned off internet, started unity launcher.
Exit unity launcher, re-enabled internet, started unity launcher and selected folder with my project
I changed it to null, and added the debug.log inside the if(groundCollider) condition. It registers the platform like it should to begin with, then it registers the platform is missing, and flips. The it walks towards the left, and when it stop registering the platform, nothing happens. It just keeps registering the platform not existing, but does nothing apart from continuing into the air. I also added a log after both the change euler angles parts. And when running it now, all the logs trigger continualy once it walks of the platform.
– nilserlinghI finally figured it out! Turns out all I had to do was change the secound transform.eulerAngles = new Vector2(0, 360) instead of transform.eulerAngles = new Vector2(0, -180). Dont know why, but that fixed the problem. Thanks for the help though! Wouldent have figured it out without you I think! @Chimer0s
– nilserlinghI had this issue when using Multiple Monitors.
Sometimes I would even unplug my second monitor and my Unity projects would load faster.
With my secondary monitor plugged in, it loads really slow sometimes. Very odd…
Do you have multiple monitors?
LOL I THOUGHT ITS A PROBLEM WITH THE VERSION SO I DOWNLOADED THREE MODULES JUST FOR THAT
Wow lol. Well live and learn. I guess it makes sense when you think about it since 180 and -180 are actually the same amount of rotation from 0. We're a bit slow lol. Glad you figured it out eventually. :P
– Chimer0s
The next step for me would be to add
– Chimer0selse debug.Log(groundInfo.collider.name);after your groundInfo collider check then watch the console to see if it continues to report a collision while walking off the edge(easiest to do if you have the console set to collapse), because it seems to me that the code should work correctly and that the only reason it wouldn't is if it isn't being called because the condition is never met.