Gran Turismo 4: Difference between revisions

Holy crap, more grammar fixing.
(Oh my god this needed a lot of correcting. Fixed various grammar issues in the "Known Issues" section.)
(Holy crap, more grammar fixing.)
Line 138: Line 138:


==Hacks and Performance==
==Hacks and Performance==
*MTVU may increase speed in quad cores, in dual-cores it increases depending on the race but may cause slowdown in others.
*The MTVU hack may increase speed in quad core CPUs. This varies in dual-core CPUs as it may increase depending on the race but may cause slowdown in others.
*Other hacks cause crashes or game won't boot., *This game requires a ton of personal tinkering to get it to run decent., *This game has very, VERY high requirements. Don't expect a smooth or stable game. Heavy slowdown often. Mostly depends on track, lights and the amount of cars on screen.
*Other hacks can cause crashes or the game won't boot. This game requires a ton of personal tinkering to get it to run decent.This game also has very, VERY high system requirements (expect to use at least an i5 or an FX 6300 above). Don't expect a smooth or stable game. Slowdowns are heavy and very prevalent. It mostly depends on track, the lighting and the amount of cars on screen.
*"Allow 8-bit textures" in GSdx may help with speed a bit more and maybe reduce the Vram slowdowns.
*The "Allow 8-bit textures" in GSdx may help with speed a bit more and maybe reduce the VRam slowdowns.
*If you are using software mode and have 4 cores or more (this includes hyperthreaded cores, as PCSX2 takes advantage of this), set the "extra software threads" to the amount of total threads in your CPU minus one (4 cores, threads to "3", 8 cores, threads to "7", etc.). This can provide a noticeable speedup in any game running in software mode, but beware that only native resolution can be used.


==Known Issues==
==Known Issues==
Line 148: Line 149:
|IsFixed=0
|IsFixed=0
|IssueLevel=2
|IssueLevel=2
|Description=Crashes pretty often. Happens because of spikes in VRam use.
|Description=Crashes pretty often. This happens because of spikes in VRam use.
|Workaround=<br>
|Workaround=<br>
# If you get lots of crashes during license tests use a lower internal resolution in GSdx or use ZeroGS or ZZOgl. expect much slower speeds from using the last two.
# If you get lots of crashes during license tests use a lower internal resolution in GSdx or use ZeroGS or ZZOgl. Expect much slower speeds from using ZeroGS or ZZOgl.
# In GSdx, Hardware AA causes the game to crash a lot. Set the AA level to 0. Running the game with native resolution seems to help as well.
# In GSdx, Hardware AA can cause the game to crash a lot. Set the AA level to 0. Running the game with native resolution seems to help as well.
# In Windows XP, even in native resolution, you may get instant crashes when starting races if you don't have enough VRam. Using a custom resolution lower than 512x512 seems to help.
# 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 174: Line 175:


{{Issue
{{Issue
|IssueName=Demo races not working
|IssueName=Demo races do not working
|IsFixed=0
|IsFixed=0
|IssueLevel=-1
|IssueLevel=-1
|Description=Demonstrations return back to menu as soon as they start.
|Description=Demonstrations return back to the menu as soon as they start.
|Workaround=Demonstration races only work with EE clamping set to full.
|Workaround=Demonstration races will only work with EE clamping set to full.
}}
}}


ninja
158

edits