|
|
Are you able to give any more details or include the log.txt or traceback.txt from the game's directory that would help with debugging? As you're the first and only person I know of to report this there's very little to go on when it comes to investigating this issue.
|
|
|
|
where would i find that |
|
|
|
log.txt (1,489 bytes)
2025-06-07 20:15:50 UTC
Windows-10-10.0.19045
Ren'Py 8.3.4.24120703
Summertime Saga
21.0.0-wip.5791
Built at 2025-04-01 20:11:05 UTC
Early init took 0.14s
Loading error handling took 0.06s
Loading script took 1.10s
Loading save slot metadata took 0.13s
Loading persistent took 0.01s
Set script version to: (8, 3, 4)
Running init code took 1.01s
Loading analysis data took 0.08s
Analyze and compile ATL took 0.03s
Reloading save slot metadata took 0.07s
Index archives took 0.01s
Dump and make backups took 0.00s
Cleaning cache took 0.00s
Making clean stores took 0.00s
Initial gc took 0.14s
DPI scale factor: 3.000000
nvdrs: Loaded, about to disable thread optimizations.
nvdrs: b"Couldn't load nvlib." (can be ignored)
Creating interface object took 0.01s
Cleaning stores took 0.00s
Init translation took 0.14s
Build styles took 0.01s
Load screen analysis took 0.03s
Analyze screens took 0.01s
Save screen analysis took 0.00s
Prepare screens took 0.15s
Save pyanalysis. took 0.01s
Save bytecode. took 0.04s
Running _start took 0.01s
Interface start took 0.20s
Initializing gl2 renderer:
primary display bounds: (0, 0, 3840, 2160)
swap interval: 1 frames
Fullscreen mode.
Vendor: "b'Intel'"
Renderer: b'Intel(R) HD Graphics 4600'
Version: b'4.3.0 - Build 20.19.15.4835'
Display Info: None
Screen sizes: virtual=(1920, 1080) physical=(3840, 2160) drawable=(3840, 2160)
Could not open 'cache/shaders.txt':
Maximum texture size: 4096x4096
|
|
|
|
The only thing that stands out as a potential issue is your onboard graphics processor, but it does appear to meet the expected requirements. I have a few suggestions for things you can try but nothing guaranteed:
- Make sure that your graphics drivers are fully updated - the version you are running appears to be significantly outdated.
- When in-game hold down the Shift key and press G, this will bring up a debug menu. In the "Renderers" section switch to "ANGLE2", then close and restart your game.
- Trying running the game in windowed mode at or smaller than 1920x1080 during the problematic sequence and see it that helps matters. It's a computationally expensive sequence compared to the rest of the game, and it's possible that running it at much higher resolutions like yours could be over-stressing your relatively underpowered onboard GPU.
Hope that helps, let us know how it turns out. :)
|
|
