mirror of
https://github.com/gopher64/gopher64.git
synced 2026-04-25 15:06:00 +03:00
[GH-ISSUE #663] Issues with Turok 2 (possibly others) and Resolution #120
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/gopher64#120
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jammize-debug on GitHub (Jan 26, 2026).
Original GitHub issue: https://github.com/gopher64/gopher64/issues/663
I am not sure if this is a new version issue or not, I recently updated (on Windows 11) and am using the portable version so I can move the emulator freely between PCs (via an external drive) without having to worry about Documents folders and so forth.
So I only just started Turok 2 after the update. I've been playing other games such as Banjo, Jet Force Gemini, Bomberman, Paper Mario and a few others just fine. I've been using 4X Resolution with Integer Scaling and nothing else changed.
After starting Turok 2, there are certain parts (such as immediately upon climbing the ladder leading up to one of the 2 boats in the area after the second Beacon is lit, around the middle of the level - it's always the same ladder and happens every time) where upon climbing, the game freezes for a few seconds and then continues to play behind the now frozen screen (I can move around etc) and clicking on the Gopher64 UI afterwards just crashes and closes the emulator. About 50% of the time when this happens, upon reopening Gopher64, all of the settings are back to default, and it even deletes my controller profiles.
I played the same area with default resolution (1X) and it worked fine. Playing in any other resolution, regardless of integer scaling (tried 8X, tried 2X, both with and without Integer Scaling) causes the freeze and crash to happen. So this issue seems related specifically to the Resolution being above default.
Ryzen 5600X
RTX 3060 TI
16GB memory
8GB Vram
@loganmc10 commented on GitHub (Jan 26, 2026):
Are you able to share a save state just before the area where it happens?
@jammize-debug commented on GitHub (Jan 26, 2026):
It won't let me drop it here, says the file type (.state0) is not supported.
Edit::
Don't know if it worked but I compressed a copy of it into a .zip archive below.
@jammize-debug commented on GitHub (Jan 27, 2026):
Turok 2 Seeds of Ev-CB62DF8E8085FC1828B943723B2CD164AEABBE53B2940314189D4133233DFB86.zip
@loganmc10 commented on GitHub (Jan 27, 2026):
Unfortunately, I can't reproduce the problem. I loaded that save state and climbed up the ladder right in front of me, and nothing happened, even at 8x resolution.
@jammize-debug commented on GitHub (Jan 27, 2026):
Very odd. I wonder if it's my Rom version. I have the 1.1 (Rev1) version. Might try getting a different one and replacing and trying again. Will update.
@jammize-debug commented on GitHub (Jan 27, 2026):
So yeah even with the original (non revision 1) version, it still crashes on the same ladder. I don't get it. I assume you have the revision version same as I do since the savestate worked for you - sigh. I have no idea where to even begin with this, then. Something about my PC build maybe? Or playing it on an external drive? I play all my emus on an external and I've only had this issue with this particular game across all platforms. =(
When updating Gopher I only have to download the new version exe and replace the old one right? No other folders or files needed?
EDIT ::: Tested it by copying the N64 folder with the rom and file structure onto my C: Drive and launched it from there, to see if maybe running it from my SSD rather than an External would solve the issue. Still happens on the same ladder.
Pulling my hair out over this lol.
@loganmc10 commented on GitHub (Jan 28, 2026):
Yes, gopher64 is just 1 exe. I'm not sure what it could be. I know that upscaling uses a lot of VRAM, but usually people only run into problems around 8x.
@jammize-debug commented on GitHub (Jan 28, 2026):
Yeah only thing Ive ever gotten on 8x was a bit of lag on rare occasions, mostly cutscenes on some games with lots going on. I just switched to 4x to avoid that.
I tried it on another Emulator and it works without issue so I don't know, something about my setup seemingly doesn't agree with Gopher. So I had to switch over.
Thank you for your help regardless.