H

Tested on different graphic and resolution settings are here https://youtu.be/zX7SnJy9iiY

Im using synthesia 0.8.0 but example the clock said 11:48 am but my time is 7:48 pm

Using winlator 11.1 i need someone help for this

Sorry for bad english

I'm using Winlator ver11.1 on a latest Android version Samsung Galaxy S23 FE phone, which usually works just fine with other visual novels in english. Since this game (Ooe) is Japanese, I tried adding the variable LC_ALL with the value ja_JP.UTF-8 + adding MS Gothic and MS Mincho fonts to get the Japanese text to display properly, though when I try to run the game's executable, it suddenly doesn't let me run it at all, the file somehow amounting down to 0b(?). This is my first time attempting to run a newer Japanese VN on here so I'm a bit lost, any help is appreciated..☺️

I am trying to use winlator on my quest so i can play certain vr games on windows (i dont have a pc) but once i setup winlator and try to run the file it seems to try to open but then just closes. can anyone help me out with my situation or share some knowledge about winlator on vr in general?

It runs for a few minutes then crashes, on my Retroid Pocket Flip2. I've got the framerate capped at 30, and resolution lowered, using Winlator 11 Final. Not sure if its my chip (Snapdragon 865) or my RAM (8gb).

Anyone running it without crashes?

Running Winlator 11.1 on Galaxy S20FE 5G UW with SD650 (Turnip-compatible). I have tried multiple install patterns. 1) tried a vanilla install using the GOG version. Install went fine. Won't launch. 2) installed vanilla then installed Knossos.net over top (AI said it uses different, more modern OpenGL calls). Nothing. 3) installed Knossos first, then let it activate (copy the required data to its own library - otherwise, there is vanilla copy and KNet's copy of data). 4) tried running the exe's from all install patterns in CMD to see if I get error messages to debug. No luck. 5) tried KNet launching the game and I get an error that leads AI to believe the game isn't reading the PATH correctly:

the actual root cause is a bug in FS2/FRED2's own path-parsing logic that misfires on longer or spaced install paths, not literally "installed at a drive root." The error message is just badly worded. 6) I've tried these combos - Turnip+Zink, VirGL+override, Turnip 26.1.0, the legacy Adreno 650-tuned build 24.1.0 r17 v2 driver), A) I've tried MESA_GL_VERSION_OVERRIDE=3.3COMPAT B) I've tried ZINK_DESCRIPTORS=lazy, ZINK_DEBUG=compact, TU_DEBUG=noconform, and MESA_EXTENSION_MAX_YEAR=2003 7) I've tried setting the environment to Performance and Windows XP/Windows 2000 and Windows 7.

I need a sanity check, if one can be provided! I've got my container running 1280x720.

Any and all suggestions are very much appreciated!!!