I7-14700k RTX 3080 TI 64 GB Ram Windows 11. Tried with new Gpu Driver aswell, tried reseting my NVidia Settings and starting in admin. Other Unity VR Games work fine.
Tried it with 1.5 still the same.
Hey, guy here with completely different hardware but same problem, a semi-solution, a real solution and even more words.
You can do this: Go into the "/PhotoSession_Data" folder and delete the "Config.json" file. That will ""fix"" it...
HOWEVER, the crux is, that you have to always delete the Config.json before you start the game.
AND the game will only be usable for exactly 1 scene. So if you go into Free Mode after launch it's fine and you can do whatever in the default room.
BUT as soon as you switch to another scene (school, tutorial or whatever) the game will turn into seizure mode.
OR You can get rid of all these problems by setting your system region format to English, Japanese or whatever country that uses a point as decimal separator (System Control -> Region -> first tab -> first dropdown menu).
What follows is a technical explanation... feel free to ignore it:
Going on from the discovery that deleting the default Config.json does "something", I compared a Config.json state from launching the game successfully (first scene loading fine) with one from after a scene transition:
Float values get chopped off. Or rather: Float values get written with decimal comma instead of point. That's bad.
The Config.json the game ships with has them correctly written with decimal points.
The reason why the initial problem (weird hands glitch, big head girl) happens, is because the float values loose their decimal point after being initialized and rewritten to the Config.json (since the decimal point is handled as a number grouping separator in our respective countries, not as a decimal separator). So for example nipple size "1.5" will turn to "15". Girl head size will turn from 1.25 to 125... naturally, chaos ensues and the engine can't keep up.
I'm a bit mad about this behavior. I'm not a game dev but to me this seems like the developers made the conscious decision to pull the separator from the system (aka Russian roulette) instead of strictly adhering to language syntax. But fine... maybe they had to for some godforsaken reason or it's a default Unity thing and they didn't know.
But they also did not implement checks for values outside of the intended scope... that's just bonkers.
Anyway, question for you guys: Are there emulators that handle region format? "Locale Emulator 2.5.0.1" doesn't do the trick I suppose. Or should it work and mine is just not working correctly? It doesn't show up in the context menu for these install-less Unity engine executables at least (probably because there is no registry entry for these).
