Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags
(1 edit)

Dug up a log from one of the crashes:

While running game code:
  File "game/900_GAME.rpy", line 31, in script call
    call navigate() from _call_navigate
  File "game/400_interaction/410_navigator.rpy", line 178, in script
    call screen navigate()
  File "renpy/common/000statements.rpy", line 569, in execute_call_screen
    store._return = renpy.call_screen(name, *args, **kwargs)
  File "game/screens.rpy", line 243, in execute
    screen quick_menu():
  File "game/screens.rpy", line 243, in execute
    screen quick_menu():
  File "game/screens.rpy", line 248, in execute
    if quick_menu:
  File "game/screens.rpy", line 248, in <module>
    if quick_menu:
NameError: name 'quick_menu' is not defined

The performance hits probably occurred at the boardgame  (running pathfinding, etc not ideally)

Yeah, that could use caching and similar optimization techniques and that's a kind of thing where you would really like to use  godot or unity which come with set of already predefined functions for this and are better suited for the type of games you make and could speed up development significantly, however either requires some time to learn, but that's up to you; Anyways keep up the good work

That looks like a weird renpy timing issue (not part of my game code). No idea what could cause it...

In my next game I will definitely have performance in the back of my head when coding. 

I usually code on my mac and test the windows version in parallels/virtual machine, so the win code runs in an awfully slow environment. Haven't seen above issue there, though. But some timing issues with screen.rpy have occurred (especially tooltip features)