Ren'Py All Ren'Py games are crashing constantly

[peterppp]

One other note: Since this thread deals primarily with Windows (PC) based technology, I have discovered that when starting the exe file using the "Run as Administrator" and then holding "Shift+G" until the screen with the options to change the graphics options displays, the only area I have to make any changes are the "Gamepad" area and I just select "Disable" and then quit. I am then able to start the game as usual. So, unless you are using a Gamepad, I would start with disabling that function first then see if you need to make other adjustments.


View attachment 4089100

do you have a gamepad connected? then just disconnecting that would probably fix it also

 

[SISIMEN]

do you have a gamepad connected? then just disconnecting that would probably fix it also

No gamepad. I never use one so I found it odd that disabling that function allowed me to start up Ren'py games.

 

[anne O'nymous]

No gamepad. I never use one so I found it odd that disabling that function allowed me to start up Ren'py games.

Yet there's something that interfere.

Strangely the gamepad is enabled by default, but it's just an input source like any other. Therefore, the game will not react if you don't use the gamepad, like it don't react if you don't use the keyboard. What also mean that obviously it will not react if there's no gamepad.
And like it's enabled by default, if it was due to the way Ren'Py handle the gamepad, or how a given version of Windows handle it, there would be millions people who complain about that issue.

My guess is that something (I have no clue what) lead Ren'Py to believe that there's really a gamepad, and when it try to configure it, or address it, like it's not a gamepad-like device, boom.

 

[SISIMEN]

Yet there's something that interfere.

Strangely the gamepad is enabled by default, but it's just an input source like any other. Therefore, the game will not react if you don't use the gamepad, like it don't react if you don't use the keyboard. What also mean that obviously it will not react if there's no gamepad.
And like it's enabled by default, if it was due to the way Ren'Py handle the gamepad, or how a given version of Windows handle it, there would be millions people who complain about that issue.

My guess is that something (I have no clue what) lead Ren'Py to believe that there's really a gamepad, and when it try to configure it, or address it, like it's not a gamepad-like device, boom.

That was what I thought as well. I suspect it has something to do with my secondary keypad I use for gaming. The odd thing was this just started happening recently and made no changes to my hardware configuration. It isn't a big deal just a minor inconvenience when the occasional Ren'py game requires an administrator start with the Gamepad settings change.

 

[anne O'nymous]

That was what I thought as well. I suspect it has something to do with my secondary keypad I use for gaming. The odd thing was this just started happening recently and made no changes to my hardware configuration.

The fact that it's a recent issue can come from Ren'Py.
With the 8.x branch and Python 3.x port, a part of the code have been refactored, then ported to the 7.x branch. Gamepad detection/handling can be a part of it.
Then, your secondary keypad is recognized as input, but wrongly interpreted as a gamepad; or not discriminated as not a gamepad, it depend how Ren'Py is coded.

It's totally up to you if you do it or not, but it probably worth trying to unplug the secondary keypad (unless it's a pain in the ass due to configuration issue) next time you face this, just to see if it's actually the cause.
And if it is, perhaps a report to Ren'Py team, on

You must be registered to see the links

,

You must be registered to see the links

or

You must be registered to see the links

.