AmbrosiusGrimm

New Member
Jan 24, 2018
3
0
I'm having a issue with the game, it launches fine but when I start pressing buttons. I get various 'bool' object is not callable errors. They come from different lines in different rpy files but always crash the game.
 

WadeWilsoon

Active Member
Oct 1, 2019
513
652
It looks like there aren't gonna be a Lacey or Yumiko sex scenes anytime soon. I have been waiting for a long time.
 

Bantry

Forum Fanatic
Oct 24, 2017
5,237
12,903
I'm having a issue with the game, it launches fine but when I start pressing buttons. I get various 'bool' object is not callable errors. They come from different lines in different rpy files but always crash the game.
What kind of system/device are you playing on? What buttons are you pressing? Do you have a traceback report?
 

AmbrosiusGrimm

New Member
Jan 24, 2018
3
0
What kind of system/device are you playing on? What buttons are you pressing? Do you have a traceback report?
I'm playing on a windows 11 pc. The error is caused by pressing any buttons on the menu or even just advancing dialogue when I do manage to get past the menu. this is one of the tracebacks I have.

I'm sorry, but an uncaught exception occurred.

While running game code:
File "renpy/common/000statements.rpy", line 570, in execute_call_screen
store._return = renpy.call_screen(name, *args, **kwargs)
TypeError: 'bool' object is not callable

-- Full Traceback ------------------------------------------------------------

Full traceback:
File "renpy/bootstrap.py", line 326, in bootstrap
renpy.main.main()
File "renpy/main.py", line 617, in main
run(restart)
File "renpy/main.py", line 148, in run
renpy.execution.run_context(True)
File "renpy/execution.py", line 922, in run_context
context.run()
File "script.rpyc", line 448, in script
File "script.rpyc", line 448, in script
File "renpy/ast.py", line 1969, in execute
self.call("execute")
File "renpy/ast.py", line 1957, in call
return renpy.statements.call(method, parsed, *args, **kwargs)
File "renpy/statements.py", line 278, in call
return method(parsed, *args, **kwargs)
File "renpy/common/000statements.rpy", line 570, in execute_call_screen
store._return = renpy.call_screen(name, *args, **kwargs)
File "renpy/exports.py", line 2983, in call_screen
rv = renpy.ui.interact(mouse="screen", type="screen", roll_forward=roll_forward)
File "renpy/ui.py", line 298, in interact
rv = renpy.game.interface.interact(roll_forward=roll_forward, **kwargs)
File "renpy/display/core.py", line 3101, in interact
repeat, rv = self.interact_core(preloads=preloads, trans_pause=trans_pause, pause=pause, pause_start=pause_start, **kwargs)
File "renpy/display/core.py", line 3586, in interact_core
if renpy.display.draw.update(force=self.display_reset):
TypeError: 'bool' object is not callable

Windows-10-10.0.22621
Ren'Py 7.4.4.1439
Holiday Island 0.4.1.0
Sun Feb 25 14:33:19 2024
 

zapallbugs

Engaged Member
Jul 10, 2018
2,227
2,507
I'm playing on a windows 11 pc. The error is caused by pressing any buttons on the menu or even just advancing dialogue when I do manage to get past the menu. this is one of the tracebacks I have.

I'm sorry, but an uncaught exception occurred.

While running game code:
File "renpy/common/000statements.rpy", line 570, in execute_call_screen
store._return = renpy.call_screen(name, *args, **kwargs)
TypeError: 'bool' object is not callable

-- Full Traceback ------------------------------------------------------------

Full traceback:
File "renpy/bootstrap.py", line 326, in bootstrap
renpy.main.main()
File "renpy/main.py", line 617, in main
run(restart)
File "renpy/main.py", line 148, in run
renpy.execution.run_context(True)
File "renpy/execution.py", line 922, in run_context
context.run()
File "script.rpyc", line 448, in script
File "script.rpyc", line 448, in script
File "renpy/ast.py", line 1969, in execute
self.call("execute")
File "renpy/ast.py", line 1957, in call
return renpy.statements.call(method, parsed, *args, **kwargs)
File "renpy/statements.py", line 278, in call
return method(parsed, *args, **kwargs)
File "renpy/common/000statements.rpy", line 570, in execute_call_screen
store._return = renpy.call_screen(name, *args, **kwargs)
File "renpy/exports.py", line 2983, in call_screen
rv = renpy.ui.interact(mouse="screen", type="screen", roll_forward=roll_forward)
File "renpy/ui.py", line 298, in interact
rv = renpy.game.interface.interact(roll_forward=roll_forward, **kwargs)
File "renpy/display/core.py", line 3101, in interact
repeat, rv = self.interact_core(preloads=preloads, trans_pause=trans_pause, pause=pause, pause_start=pause_start, **kwargs)
File "renpy/display/core.py", line 3586, in interact_core
if renpy.display.draw.update(force=self.display_reset):
TypeError: 'bool' object is not callable

Windows-10-10.0.22621
Ren'Py 7.4.4.1439
Holiday Island 0.4.1.0
Sun Feb 25 14:33:19 2024
Let me guess, Renpy 7.4.4 is from march 2021. Win11 didn't exist yet at that time. Is this Renpy even supported on win11?
Edit: the basic Renpy is probably not the problem, but the drivers shipped with it likely are not compatible with win11.
 
Last edited:
  • Like
Reactions: Bantry

darkhound1

Well-Known Member
Game Developer
Aug 8, 2017
1,810
8,499
Let me guess, Renpy 7.4.4 is from march 2021. Win11 didn't exist yet at that time. Is this Renpy even supported on win11?
Edit: the basic Renpy is probably not the problem, but the drivers shipped with it likely are not compatible with win11.
I can't say what's causing it. But I can't believe it is a general win11 problem. If that was the case, there would be a ton of people reporting problems by now.
Maybe there is someone using win11 who can confirm that the game generally works.
 

zapallbugs

Engaged Member
Jul 10, 2018
2,227
2,507
I can't say what's causing it. But I can't believe it is a general win11 problem. If that was the case, there would be a ton of people reporting problems by now.
Maybe there is someone using win11 who can confirm that the game generally works.
There are tons of people reporting problems with Renpy games on win11. A simple Google search will turn up thousands. The problem is most of those reports are not specific to any Renpy version. And after reading quite a number of those reports my estimate too was that there is no general Renpy problem. It all comes down to drivers shipped with a specific version, the hardware people are running on etc. What the reporter here faces looks like driver hell too. The error is somewhere in the lower layers, not in the HI code. But I can't find any lists of what drivers are included with what version of Renpy. Not even on the Renpy site.
 
  • Like
Reactions: Bantry
4.10 star(s) 219 Votes