Gran Turismo 4: Difference between revisions

Jump to navigation Jump to search

Gran Turismo 4 (view source)

Revision as of 15:51, 29 January 2020

736 bytes removed ,  29 January 2020
no edit summary
mNo edit summary
No edit summary
(3 intermediate revisions by the same user not shown)
Line 478: Line 478:
# Make sure you have "Large Framebuffer" disabled on the recent GIT revisions as it can amplify the VRAM spikes when enabled.
# Make sure you have "Large Framebuffer" disabled on the recent GIT revisions as it can amplify the VRAM spikes when enabled.
# 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 an event, temporarily switch to the Sofware Renderer by pressing F9.
# If you get lots of crashes during license tests go to Config > Video (GS) > Plugin Settings, and set Internal Resolution to (1x) Native, or set Renderer to any of the "(Software)" options.
# To reduce VRAM spikes further, Nvidia users can Force Enable Sparse Texture in GSdx Advanced settings & hacks. OpenGL only.
# Multisample anti-aliasing(MSAA) can cause the game to crash a lot. Make sure the MSAA level is set to 0 in the GSdx Configure Hacks menu(MSAA is only avaialble for the Direct3D Hardware renderers).
# In Windows XP, even in native resolution, you may get instant crashes when starting races if you do not have enough VRAM. Using a custom resolution lower than 512x512 seems to help.
}}
}}


Line 489: Line 487:
|Description=Missing ground textures and/or textures in the distance flicker.
|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.
|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
|IssueName=Effects visible through objects
|IsFixed=0
|IssueLevel=0
|Description=Car headlights, smoke and dust effects are seen through objects.
|Workaround=Go to Config -> Video (GS) -> Plugin Settings, and set renderer to "OpenGL (Hardware)". Then set Blending Unity Accuracy to at least "High".
}}
}}


Line 509: Line 499:


== Fixed Issues ==
== Fixed Issues ==
{{Issue
|IssueName=Effects visible through objects
|IsFixed=1
|IssueLevel=0
|Description=Car headlights, smoke and dust effects are seen through objects.
|Workaround=Go to Config -> Video (GS) -> Plugin Settings, and set renderer to "OpenGL (Hardware)". Then set Blending Unity Accuracy to at least "High".
}}
{{Issue
{{Issue
|IssueName=Game doesn't load past copyright screen.
|IssueName=Game doesn't load past copyright screen.
Line 556: Line 555:
|IssueLevel=0
|IssueLevel=0
|Description=In-game brightness or contrast values do not work properly in-game.
|Description=In-game brightness or contrast values do not work properly in-game.
|Workaround=This issue can been fixed in the latest v1.5.0 development builds as of May 2016. Go to Config -> Video (GS) -> Plugin Settings, set Renderer to "OpenGL (Hardware)", set CRC Hack Level to Automatic(or Partial is automatic is not available). For older versions or the Direct3D Hardware renderers, press the start button in-game, go to Screen(or from the main menu of the game, go to Options -> Picture Quality) and set Brightness to 0 to avoid the problems mentioned in the issue above.
|Workaround=This has been resolved in recent v1.5.0 git builds. CRC hack level should be left on Automatic. For older versions set in game brightness/contrast to 0 or alternatively switch to software rendering.
}}
}}


Retrieved from "https://wiki.pcsx2.net/Special:MobileDiff/92853...94448"

Navigation menu