Gran Turismo 4: Difference between revisions

Jump to navigation Jump to search
m (Marked NTSC-J as playable on Linux)
(2 intermediate revisions by 2 users not shown)
Line 524: Line 524:
* OnePAD 1.3.0
* OnePAD 1.3.0
|Comments=
|Comments=
No slowdowns, audio sounds fine, no bugs that can't be fixed.
Some Licence Center tests (B-3 being the first) will crash if you don't set both Clamping Mode settings to "Normal". Unfortunately using "Normal" causes some graphical issues so you'll have to change the settings for your Driver's Licence tests and then swap back to "Full" and "Extra" for the rest of the game (see my settings). Other than that, I haven't found any issues.
|Tester=Bizlab
|Tester=Bizlab
}}
}}
Line 556: Line 556:
* OnePAD 1.3.0
* OnePAD 1.3.0
|Comments=
|Comments=
Same setup as the NTSC-U test. Didn't test the game that much, but I'm assuming there are no region specific issues. Will edit if I find something.
Some Licence Center tests (B-3 being the first) will crash if you don't set both Clamping Mode settings to "Normal". Unfortunately using "Normal" causes some graphical issues so you'll have to change the settings for your Driver's Licence tests and then swap back to "Full" and "Extra" for the rest of the game (see my settings). Same setup as the NTSC-U test. Didn't test the game that much, but I'm assuming there are no region specific issues.
|Tester=Bizlab
|Tester=Bizlab
}}
}}
Line 569: Line 569:
== Known Issues ==
== Known Issues ==
{{Issue
{{Issue
|IssueName=Heavy crashing
|IssueName=Out of VRAM crashes
|IsFixed=0
|IsFixed=0
|IssueLevel=2
|IssueLevel=2
|Description=PCSX2 crashes during or at the start of a race, often with GSdx Out of memory warnings in the log.
|Description=When launching the first race of a play session, VRAM usage jumps significantly just before the race preview screen starts. After the first race, this problem does not happen again until the next time you boot the game. The game will also have occasional VRAM spikes as it continues to run. Either of these can potentially cause a crash if they cause your system to run out of VRAM.
|Workaround=<br>
|Workaround=<br>
# In recent PCSX2 GIT revisions as of May 7th, 2016, VRAM spikes have been greatly reduced.
# PCSX2 versions released later than May 7th, 2016 should have much smaller VRAM spikes.
# Make sure you have "Large Framebuffer" disabled on the recent GIT revisions as it can amplify the VRAM spikes when enabled.
# Make sure Large Framebuffer is disabled.
# To avoid crashes at the start of an event, hit F9 to toggle between hardware and software rendering, then hit F9 again to return to your desired renderer. This refreshes the emulation state of GSdx and clears the bad VRAM.
# To avoid crashes at the start of the first race of a play session, when on the loading screen with your car's name and tire types, wait for the loading circle to abruptly stop; this is a sign that you have run out of VRAM. Hit F9 to toggle between hardware and software rendering and wait a moment for it to respond. Once it changes renderers, wait for it go go around a few more times, then hit F9 again to return to your desired renderer. This refreshes the emulation state of GSdx and clears the bad VRAM. If you notice that it never actually stalls out at all, you may still need to clear the VRAM and should hit F9 twice to do so before starting the race.
# To reduce VRAM spikes further, Nvidia users can Force Enable Sparse Texture in GSdx Advanced settings & hacks. OpenGL only.
# To reduce VRAM spikes further, Nvidia users can Force Enable Sparse Texture in GSdx Advanced settings & hacks. OpenGL only.
}}
}}
ninja
54

edits

Navigation menu