NotITG v4 is a version which introduced many new features and quality of life improvements.
It was used in the UKSRTX competition.
Most of what would be needed for a typical player is working well.
What does not
Self-explanatory. No idea why this happens, but if you kill the process or the game crashes, the closing monitor flash does not happen. This reportedly doesn't happen on much older versions (<5.2-ish) but I can't confirm this claim.
I'm not sure if it's just Wine's terminal color support being buggy, but colors like to act really weirdly. Bleeding onto other lines, being sometimes invisible, it's a whole mess and you'd much rather actually want there to be no colors at all if you want to read through the logs for anything meaningful.
I'm not sure if I can really point this one out, as it's more PulseAudio's fault? I'd recommend reopening PulseAudio before launching NITG for more consistent sync results each game with killall pulseaudio; pulseaudio -D
When using GLSL shaders, GPU memory can leak over in certain spots. One example I've noted is if a shader is referencing a point on the screen that is out-of-bounds, that point will be blank, or rarely parts of GPU memory. Most of the time leaked GPU memory is just Japanese, Korean and Chinese characters due to the theme loading lots of these types of fonts to memory, but if you use a different theme or remove them from the theme, it starts using banner art, seemingly random patterns and often parts of your desktop.
One good example of a file that produces this is NULCTRL:
There aren't any good examples of this I could find, but sometimes shaders produce behaviour unseen on Windows.
Also, you're unlikely to experience this, but I've had less luck with shaders on an older NVIDIA laptop running Nouvaeu. I've once had an issue where the default note vertex shader somehow corrupted itself and started breaking every file:
There was a bug with the key names where all non-special key names would change to Key_, and because of this theme-defined shortcuts like the console didnt work. However, there is a patch for this (provided by one of the lead devs, ArcticFqx):
Extract this into Program/ and run the Wine version each time instead of the regular version. This'll fix the Key_ bug present without it.
What was not tested
You may need to pay attention to how much shaders are used in files you play if you're streaming or recording them, as leaked GPU memory can rarely include parts of your open applications and even closed applications (!!!) This is explained more in the "What does not" section.
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Current||Solus 4.2 Fortitude||Mar 06 2021||6.3||Yes||Yes||Yes||Silver||oatmealine|
|Show||Solus 4.1||Oct 22 2020||5.19||N/A||Yes||No||Garbage||oatmealine|
|Show||Solus 4.1||Apr 15 2020||5.5||N/A||Yes||Yes||Silver||oatmealine|
|Show||Solus 4.1||Mar 27 2020||5.4||N/A||Yes||No||Silver||oatmealine|