I'm using Unity 2017.2.
I have strange problem. When i run my game into the editor it drops the FPS to very low like 5 - 7 FPS. However if i make a build and run the game it runs perfectly without any problems with 150 - 200 FPS.
Here is my profiler:
All is runing fine without any errors. Can you give me any suggestion where the problem can be. I hope somebody faced similar problem before and i'll be able to resolve this.
Taken from this unity forum post, it seems this is a known issue with the editor itself. You can either roll back to the last version, or wait for a bugfix to come out... Although the fix for this has been "expected soon" for awhile now. It is possible that 2017.3 fixed this issue, though. I haven't updated Unity since it came out so I cannot confirm.
Related
I have developed a Unity3d Mac standalone app, which crashed after a while with the above mentioned error - the whole app gets frozen.
I have pages with a video, which I load and un-load dynamically when entering/exit the page. Most of the time the app crashed when I leave the page with the video to the menu. Anyone any idea, I did find anything valuable answer to this matter :(
----- Tests -----
After a few test runs, I narrowed it down to the video. Not sure what exactly the issue is, but when I played a video and leave the page the app freezes...sometimes immediately, sometimes after a while.
Unity 2018.1f
Tested on : Mac OSX 10.12.6 & OSX 10.11.6
After long tests and try-outs, we found a general problem with Unity and continues playing videos. After updating everything, as well as to the latest Unity2018.2 version - it finally was working well. As per Unity changelog, they did some fixes on the VideoPlayer.
Good luck.
so my Unity worked fine until now, last time I built the game was yesterday and everything worked fine. Since yesterday the only thing that I did is that I changed some colliders and removed facebook gamecenter plugin. Now, when I try to play the game, everything is fine, but when I try to build it, it starts giving me 250 errors in total.
The last error always says :
"Error building Player because scripts had compiler errors"
Others error are connected to the standard assets.
Screenshots:
For some reason this happens. There a few options of fixing it, but the easiest one to simply re-install Unity.
PS: You wont lose any data.
About a month ago, I loaded the Android emulator "Andy" on my windows 8 laptop and it seemed to work fine (except it kept kicking me out of Clash of Clans after a couple minutes, but the emulator kept running).
Yesterday, something happened. While in Clash of Clans, the background turned all black and just the small images were visible. This has happened before and I would kill Andy using the X in the upper right corner. I would then restart Andy and things worked OK again.
However, yesterday when this happened, I killed Andy in the same way, but when I tried to restart Andy the frame would display for a second or two and then go away.
I figured that a bit got twisted somewhere, so I uninstalled that version of Andy and downloaded and installed a newer version, but I get the same results.
I checked the web and the closest I came was "Andy won't launch on windows 8". The suggested solution was to roll back the display driver. I did that with the same results.
I figure that there may be a flag somewhere that thinks Andy is running, so it shuts down any new version, but that is just a guess.
Has anyone else run into this problem?
If so what was the solution?
Try to change the compatibility setting to windows 7/8
I was propted by apple to upgrade my debugger settings yesterday, In doing so I have some how broken xcode.
When ever I now try to load an application (dosn't matter what version of the simulator I am using) Xcode and my simulator both freeze up. then the rainbow loader just sits their constantly turning over.
Is there any way to fix this? I'm really stuck and don't know what to do as it dose not seem like a very common problem from all the research I have done to fix this.
I am running the latest version of xcode 4.3.2 (4E2002) and using 5.1 simulator.. and have tried 4.2 simulator to the same effect.
any help in getting my xcode back up and running would be massively appreciated.
Okay so I figured out what the problem is but not a real solution...
Basically the error started happening when I was prompted by xcode to update my debugger to the LLDB version. this is what cause my simulator to keep crashing xcode.. or vice versa honastly I still dont know why this is happening but yea...
so.. what I did to get this simulator working again was go to Product>edit scheme> debugger then changed from LLDB back to GDB.. this solved my issue for now... however I need to figure out why LLDB is not working and what I should do leading into the future. hope this helps someone else.
I have facing this problem too but I got a solution either you said its temporary ... some time ios 5.1 simulator hangs when I shifted to the ios 4.1 sdk its a common practice for the developer to check it I have simply first close the simulator and again start it and then reset all the content in the preference area that its resolved my issue .. check it might be you also got resolve for apply this trick or technique.
Thanks
In my case, was too many old breakpoints tracks (788), even to deleted files, I just clean it and now it runs perfect, I hope it helps.
A picture to illustrate:
the ABPersonCopyImageData function in iOS4 SDK 4.0->4.02 seems to return uncropped image
and leads to terrible performance and crashing due to running out of memory. It used
to work fine on OC versions 3.0->3.1.3. I've tried upgrading to 4.02 but still same issues
Is there a workaround for this?
Well now there is ABPersonCopyImageDataWithFormat in the SDK 4.1 which returns either thumbnails or the full image
Thanks for this post. I had a major surprise bug due to this issue in a release and this post helped save the day with rapid bug fix.
Everything had previously worked fine but suddenly went all wrong with users who had contact images of a certain types. Setting the format to kABPersonImageFormatThumbnail completely solved the issue.