ptitSeb
ptitSeb
> > > > It was immediate on my side but my test machine has 96GB of memory (I know, it's huge). > > > > Note that Steam alone...
Indeed. Thanks for the test & analysis. Don't you want to create a PR with the fixes?
Ok, I reproduce the issue on my side (just received a MilkV Pioneer, so I could test this with a proprer graphic card). I'll check dynarec_test on my side indeed,...
So, I pushed some fixes on the Dynarec. It helps, but doesn't fix completly the loading of Celeste...
Should be fixed now. You can update and try again.
Interesting. Give it a try with `BOX64_DYNAREC_NATIVEFLAGS=0` also. And maybe with `BOX64_DYNAREC_SAFEFLAG=2`, in case this is heavily encrypted.
It might be a "inverted carry" flags that doesn't propage correctly? You should generate a dump: use `BOX64_DYNAREC_DUMP=2` to generate a colorfull dump of the generated code, and also redirct...
You can trace only on an interval to limit the size of the trace (with `BOX4_TRACE=0x40000-0x41000`... But of course trace can rapidly be huge!
Did you tried to run VRChat with `BOX64_DYNAREC_NATIVEFLAGS=0`` ?
The error message you see are probably the cause of the bad lightnlng. It's a hardware limitation: RPi4 can only have 4 framebuffer binded to an fbo, but the game...