Very weird behaviour with built game and editor play mode

Hi guys,

I’m currently working on a (simple) game that utilizes physics.
When I’m testing it (in the editor play mode) it works perfectly fine.
But when I build it, strange things happen: It feels like the game suddenly uses another physics engine. Certain mechanics, like basic movement, suddenly don’t work anymore. It feels like the player character does not have enough “force” to move its body.
BUT! Even this only happens SOMETIMES, on RANDOM occassions.
I already checked several possible causes - there are no physics materials loaded dynamically, actually none are even used at all. The Input used it the exact same.

I’m struggling with this problem for over a week now, and loosing my trust in Unity as this problem seems unsolveable for me.
My final attempt is to try and ask here now, hoping that someone had a similar problem too already.

Thanks for ANY kind of help.

Okay, replying to myself for now - I could find out that it has something to do with the Time Singleton, and its fixed update iteration. When I set the fixed update step to 0.01, I could achieve a consistently broken behaviour. Which means, it now always works in Editor Play Mode, and never works inside the built Game. Maybe that’s some useful information. It is also very dependant on which machine the built game is running - for some of my friends it works, for some it doesn’t. And no, it has nothing to do with the graphics. Even in windowed 1024x768 & Potato-Mode, we get the same behaviour. I am close to done with Unity now. Why should I be paying half a grand per YEAR for a software that behaves randomly inconsistent? I know that this is not a place to rant, but I have had similar problems with Unity before and seeing that 150+ people follow this question without anyone having an answer, my problem seems not unheard of. At least if I interpret that correctly. Thank you.