Gran Turismo 4: Difference between revisions

Jump to navigation Jump to search

Gran Turismo 4 (view source)

Revision as of 19:45, 1 November 2020

3,318 bytes added ,  1 November 2020
→‎Known Issues
No edit summary
(16 intermediate revisions by 6 users not shown)
Line 24: Line 24:
|japan_rating      = A
|japan_rating      = A
<!-- Language props -->
<!-- Language props -->
|chinese           = SCAJ-30007 & SCCS-60002
|simplified chinese = SCCS-60002
|traditional chinese = SCAJ-30007
|italian          = SCES-51719
|italian          = SCES-51719
|spanish          = SCES-51719
|spanish          = SCES-51719
Line 54: Line 55:
|releasedateNTSCJ  = December 28, 2004<br />March 10, 2005 <small>(Korea)</small><br />July 6, 2006 <small>(PlayStation 2 the Best)</small><br />September 21, 2006 <small>(BigHit Series, Korea)</small>
|releasedateNTSCJ  = December 28, 2004<br />March 10, 2005 <small>(Korea)</small><br />July 6, 2006 <small>(PlayStation 2 the Best)</small><br />September 21, 2006 <small>(BigHit Series, Korea)</small>
|statusNTSCJ      = 2
|statusNTSCJ      = 2
|linuxstatusNTSCJ  =
|linuxstatusNTSCJ  = 2
|macstatusNTSCJ    =
|macstatusNTSCJ    =
}}
}}
Line 393: Line 394:
|Region=NTSC-U
|Region=NTSC-U
|OS=Windows 10
|OS=Windows 10
|CPU=AMD Ryzen 3600 @ 3.9 GHz
|CPU=AMD Ryzen 5 3600 @ 3.9 GHz
|GPU=Nvidia GTX 1070
|GPU=Nvidia GeForce GTX 1070 @ 8 GB
|Revision=1.6.0
|Revision=1.6.0
<spoiler show="Settings" hide="Hide">
<spoiler show="Settings" hide="Hide">
* Speedhacks:
* Speedhacks:
** EE Cyclerate: 0
** EE Cyclerate: 0
** VU Cycle Stealing: 1
** VU Cycle Stealing: 0
** MTVU: ✓
** MTVU: ✓
** mVU Hack: ✓
** mVU Hack: ✓
Line 410: Line 411:
<spoiler show="Settings" hide="Hide">
<spoiler show="Settings" hide="Hide">
* Renderer: Direct3D11 (Hardware)
* Renderer: Direct3D11 (Hardware)
* Interlacing: Bob tff
* Internal resolution: 3x Native
* Texture Filtering: Bilinear (PS2)
* Allow 8-bit Textures
* CRC Hack Level: Full
* FXAA Shader
</spoiler>
</spoiler>
|Sound=
|Sound=
Line 488: Line 495:
|Comments=100% speed with hardware acceleration at native resolution. significantly less slowdowns than pcsx2 1.4.0. audio also renders much more cleanly with SDL/alsa. extremely playable.  
|Comments=100% speed with hardware acceleration at native resolution. significantly less slowdowns than pcsx2 1.4.0. audio also renders much more cleanly with SDL/alsa. extremely playable.  
|Tester=kerpal
|Tester=kerpal
}}
{{TestingEntry
|Status=2
|Region=NTSC-U
|OS=Arch Linux
|CPU=AMD Ryzen 5 3600
|GPU=AMD Radeon RX Vega 56
|Revision=1.7.0 (dev-13 g8bf6ba144)
<spoiler show="Settings" hide="Hide">
* '''EE/IOP:'''
** Clamping Mode: Full
* '''VUs:'''
** Clamping Mode: Extra
* '''Speedhacks:'''
** mVU Flag Hack: ✓
** MTVU: ✓
</spoiler>
|Graphics=GSdx 1.2.0 AVX2
<spoiler show="Settings" hide="Hide">
* Renderer: OpenGL (Hardware)
* Internal Resolution: 5x Native
* Interlacing: Bob tff
* Texture Filtering: Bilinear (PS2)
* Anisotropic Filtering: 4x
* CRC Hack Level: Partial
</spoiler>
|Sound=
* SPU2-X 2.0.0
* OnePAD 1.3.0
|Comments=
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
}}
{{TestingEntry
|Status=2
|Region=NTSC-J
|OS=Arch Linux
|CPU=AMD Ryzen 5 3600
|GPU=AMD Radeon RX Vega 56
|Revision=1.7.0 (dev-13 g8bf6ba144)
<spoiler show="Settings" hide="Hide">
* '''EE/IOP:'''
** Clamping Mode: Full
* '''VUs:'''
** Clamping Mode: Extra
* '''Speedhacks:'''
** mVU Flag Hack: ✓
** MTVU: ✓
</spoiler>
|Graphics=GSdx 1.2.0 AVX2
<spoiler show="Settings" hide="Hide">
* Renderer: OpenGL (Hardware)
* Internal Resolution: 5x Native
* Interlacing: Bob tff
* Texture Filtering: Bilinear (PS2)
* Anisotropic Filtering: 4x
* CRC Hack Level: Partial
</spoiler>
|Sound=
* SPU2-X 2.0.0
* OnePAD 1.3.0
|Comments=
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
}}
}}
{{TestingFooter}}
{{TestingFooter}}
Line 499: Line 570:
== 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, temporarily switch to the Sofware Renderer by pressing F9.
# 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 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. Note in 1.7.0 dev builds Sparse Texture may be broken and cause problems.
}}
}}


{{Issue
|IssueName=Missing/flickering textures
|IsFixed=0
|IssueLevel=0
|Description=Missing ground textures and/or textures in the distance flicker.
|Workaround=Go to Config -> Video (GS) -> Plugin Settings, and set Renderer to any of the "(Software)" options. Then Make sure the Mipmapping option is checked at Software Mode Settings.
}}


{{Issue
{{Issue
Line 518: Line 596:
|Workaround=Go to Config -> Emulation Settings -> GS Window and set Zoom to 100.20.
|Workaround=Go to Config -> Emulation Settings -> GS Window and set Zoom to 100.20.
}}
}}
== Fixed Issues ==


{{Issue
{{Issue
|IssueName=Missing/flickering textures
|IssueName=Effects visible through objects
|IsFixed=1
|IsFixed=0
|IssueLevel=0
|IssueLevel=0
|Description=Missing ground textures and/or textures in the distance flicker.
|Description=Car headlights, smoke and dust effects are seen through objects.
|Workaround=Go to Config -> Video (GS) -> Plugin Settings, and set Renderer to any of the "(Software)" options. Then Make sure the Mipmapping option is checked at Software Mode Settings.
|Workaround=Use software rendering.
}}
}}
== Fixed Issues ==


{{Issue
{{Issue
Pandubz
ninja
54

edits

Retrieved from "https://wiki.pcsx2.net/Special:MobileDiff/94800...96014"

Navigation menu