Ssato243
Engaged Member
- Feb 2, 2021
- 2,975
- 1,790
- 306
Code:
2025-11-06 18:05:55 UTC
Windows-10-10.0.26200
Ren'Py 8.3.4.24120703
Myth of Slayer
Ch.9
Built at 2025-10-23 09:18:06 UTC
Early init took 0.06s
Loading error handling took 0.04s
Loading script took 0.91s
Loading save slot metadata took 0.09s
Loading persistent took 0.01s
Set script version to: (8, 3, 4)
Running init code took 0.33s
Loading analysis data took 0.13s
Analyze and compile ATL took 0.00s
Reloading save slot metadata took 0.05s
Index archives took 0.00s
Dump and make backups took 0.00s
Cleaning cache took 0.00s
Making clean stores took 0.00s
Initial gc took 0.10s
DPI scale factor: 1.000000
nvdrs: Loaded, about to disable thread optimizations.
nvdrs: b"Couldn't load nvlib." (can be ignored)
Creating interface object took 0.00s
Cleaning stores took 0.00s
Init translation took 0.10s
Build styles took 0.00s
Load screen analysis took 0.04s
Analyze screens took 0.00s
Save screen analysis took 0.00s
Prepare screens took 0.08s
Save pyanalysis. took 0.02s
Save bytecode. took 0.04s
Running _start took 0.00s
Interface start took 0.15s
Initializing gl2 renderer:
primary display bounds: (0, 0, 2560, 1440)
swap interval: 1 frames
Windowed mode.Ssato243
Engaged Member
- Feb 2, 2021
- 2,975
- 1,790
- 306
Ssato243
Engaged Member
- Feb 2, 2021
- 2,975
- 1,790
- 306
TRIED THREE TIME, STILL GET THIS ERROR. IT WAS AFTER I UPDATED THE DRIVER FROM AMD
Goeffel
Active Member
- Sep 10, 2022
- 886
- 624
- 193
well, would your AMD tools not let you downgrade the driver ?
else maybe windows made a system restore point before updating the driver.
whowhawhy
Active Member
- Jan 19, 2023
- 935
- 1,494
- 202
it's hebrew not unsupported characters, and they eventually admitted it started with a driver update, with the error message coincidentally being attributed to issues with graphics card drivers.
there are many different suggestions in google results (i don't mean the pinned ai answer) that don't involve rolling back on the update if it's not corrupted and the op needs it for a different reason, and i'm not sure if they've tried all of them yet.
It's not the first time I encounter someone having issues due to special symbols (usually cyrilic), but if it's certain that it's not that, then yeah... Just rolling down the update should be enough. It's weird an update causes such an issue though, I feel like it could be something else, if he has a laptop, it could be a number of factors including the laptop not being plugged in (may default to low performance to save battery) or not running it with the dedicated GPU (could have been default before, but not now for some reason?)
Before rolling down an update, I think moving to C:/Games/GameName with no special characters is much quicker to test if that's truly the issue or not. He could also try to hold Shift while opening the game, and see if the menu even opens, and the game works with different settings, in that case it'd be nearly guaranteed that it's a driver issue.
- Jun 10, 2017
- 12,722
- 20,865
- 1,026
Thought about it at first, but the error come from LoadLibrary, the Windows DLL linker. I can be wrong (Ren'Py changed a lot its internal process) but normally this mean that Windows was able to find the Python interpreter, and therefore had no problem to understand the path.
This being said, I'm not sure that it's actually a question of driver. Ren'Py itself rely on 7 dynamic libraries, it can also be anyone of those.
Ssato243
Engaged Member
- Feb 2, 2021
- 2,975
- 1,790
- 306
i tried that already, also got the error 87, the same error
Ssato243
Engaged Member
- Feb 2, 2021
- 2,975
- 1,790
- 306
Try one of the solutions written in this reddit thread then:
You must be registered to see the links
But I think the best option (which is also suggested there) is to rollback your update to the previous one.
- Jun 10, 2017
- 12,722
- 20,865
- 1,026
After looking at his log.txt file, I agree with this. It end right before Ren'Py log the GPU information, so it's the drivers that Windows can't load. Not because it's corrupted, but apparently because it, hmm, lets say, refuse to be dynamically linked to a third party application, at least not the way Ren'Py usually do it.
I didn't even look at the log (probably obvious at this point), but it's simple enough that you can go by exclusion...
Try a simple path, try holding shift to change renderer, and if none of those options work, simply revert the latest changes
It's a shame that lately updates seem to break more than they fix. At least it's not just Windows screwing up with their new updates, they really need to hire a frenchman to test everything before releasing to the public.
- Jun 10, 2017
- 12,722
- 20,865
- 1,026
Well, for once it's not Ren'Py the culprit, a ton of software seem to have the same issue with AMD GPU drivers. And like it's recurring, while the last drivers update also lead to the same error with AutoCAD, I'm almost sure that it's AMD that do stupid things.
Testing would, alas, not be enough.
PyTom and the team are not bad when it come to coding, but they lack the foundation, in terms of hardware and inter-dependencies, needed for a multi-OS software.
There's two 6.99.x versions of Ren'Py where the console can't be fully used with non QWERTY keyboards, because PyTom didn't know that the
ALT GR key is in fact the ALT + [/icode]SHIFT[/icode] combination. And on non QWERTY keyboards this key is needed for characters like "[", "]", "{", "}", as well as, accessorily, "\" and "#"...It's probably because I'm old, but knowing how keyboards works, and acknowledging that not all of them are QWERTY, seem a basic when you develop something like Ren'Py.
Oh I mean Windows (and in this case AMD), I am aware that's not a Ren'Py issue