So many crashes...

[Icebot]

Lately I've been experiencing an increase in the number of game crashes. Unfortunately, I tried updating the Intel® Extreme Tuning Utility but without success. Is anyone else having this problem?

* I tried searching for this problem here on the forum and couldn't find it. I apologize if there is already a thread about this issue.

 

[Winterfire]

You should provide more details... A crash like this: https://f95zone.to/threads/the-ranpy-crash-or-not-loud-and-get-en-error.276385/ or a crash with no message at all? Does it generate a log? and will you provide said log? What platform are you playing on? It's hard to help if we don't know what's going on.

 

[Icebot]

You should provide more details... A crash like this: https://f95zone.to/threads/the-ranpy-crash-or-not-loud-and-get-en-error.276385/ or a crash with no message at all? Does it generate a log? and will you provide said log? What platform are you playing on? It's hard to help if we don't know what's going on.

Thanks for replying! Some crashers do generate logs. When that happens, I'll post them here without any problem.

 

[Icebot]

You should provide more details... A crash like this: https://f95zone.to/threads/the-ranpy-crash-or-not-loud-and-get-en-error.276385/ or a crash with no message at all? Does it generate a log? and will you provide said log? What platform are you playing on? It's hard to help if we don't know what's going on.

An example:

 

[Winterfire]

That's an error of the game, it's not something you can fix. The dev has to fix it.

-edit-
Or rather, you can fix it if you edit the script and fix the game yourself, but it's a bug, rather than an issue with your pc.

 

[Icebot]

That's an error of the game, it's not something you can fix. The dev has to fix it.

-edit-
Or rather, you can fix it if you edit the script and fix the game yourself, but it's a bug, rather than an issue with your pc.

Here is other exemple for another game:

 

[Winterfire]

Here is other exemple for another game:
View attachment 5425105

That looks like a dev mistake as well (unless you messed up with game files trying to mod, patch, or whatever).

Since I am not french and therefore I can be wrong, let me conjure anne O'nymous to make sure

 

[peterppp]

Lately I've been experiencing an increase in the number of game crashes. Unfortunately, I tried updating the Intel® Extreme Tuning Utility but without success. Is anyone else having this problem?

looks like the cpu thing with intel 13900 and 14900 (and maybe others). there's been many threads about it, but no specific answer that always works.

here's one of the threads about it
https://f95zone.to/threads/all-renpy-games-either-crashing-or-fail-to-launch.169143/
you were on the right track with the tuning utility.

 

[anne O'nymous]

That looks like a dev mistake as well [...]

No, it's peterppp who's right here, it looks like the Python Vs Intel issue. When they works at too high frequency, some series of Intel processors make Python hallucinate. And I mean seriously hallucinate.

Take the first traceback by example:

if renpy.display.draw.update(force=self.display_reset):

The bool that is supposed to not be callable is the result of the call to renpy.[...].update, but Intel CPU prediction was a bit too fast for Python... Instead of the "if" as it is wrote, Python tried to proceed if RESULT_OF[renpy.display.draw.update(force=self.display_reset)](force=self.display_reset):, what led to the error displayed.
So far, slowing a bit the CPU frequency always solved the issue.

 

[peterppp]

So far, slowing a bit the CPU frequency always solved the issue.

if that's true, that's good to know. i just remember that there's been several ways people have fixed it, but those ways didnt work for everyone who tried them (or so they said)

 

[anne O'nymous]

if that's true, that's good to know. i just remember that there's been several ways people have fixed it, but those ways didnt work for everyone (or so they said)

Well, I can have missed the case where it wasn't enough, it's still a possibility.

But seen the issue, I guess that if it failed to solve the issue, it's because the frequency was still a bit too high; it's always a conflict between the CPU prediction and actual code.
I already explained the first case, the second is near to this. The code point to renpy.display.render.redraw_time(), but Python end trying to access renpy.display.display; therefore RESULT_OF[renpy.display].display.render.redraw_time().

So, slowing down enough the CPU will also slow down the predictions, and should systematically solve the issues.