Why are my physics different in the editor and deployment at same framerate? [closed]

Question

Closed. This question needs details or clarity. It is not currently accepting answers.

---

Want to improve this question? Add details and clarify the problem by editing this post.

Closed 9 years ago.

Improve this question

So I'm making a 2D tile map test project, and it runs perfectly* in the editor, but once I get it to a windows .exe it runs like crap for no reason**. I didn't touch one character of code, and the deployment settings are default, so I have no idea whats going on. Can anyone give me any ideas?

*You can move about and jump on the level ground and slopes without getting stuck at all

**You get stuck on every tiles corner, and can't go up slopes at all.

Test case - https://dl.dropboxusercontent.com/u/28109593/unity/MapTest2D.zip

Answer 1

Actually it seems (and it is logic) that the Unity engine is faster as standalone than in the editor (of course when you don't have to run all the editor around, and i dont even speak about the profiler...) so knowing that :

Physics will be able to happen more often and it will make more precise calculations, so small details which are not spotted in Editor will be in the build version like small tile differences, and also forces may be applied more accurately and/or more often which could prevent slopes limits to work proerly...

That's not all though you should take a look at your project properties, in player and check if you are running the Editor in Standalone mode and if your selected quality setting is the same.