Gran Turismo 4: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 43: Line 43:
|Region=NTSC-U
|Region=NTSC-U
|OS=Windows 7
|OS=Windows 7
|CPU=Intel C2D e8400 OC 3.6Ghz
|CPU=Intel Core 2 Duo E8400 OC @ 3.6 GHz
|GPU=nVidia GeForce 260GTX
|GPU=nVidia GeForce GTX 260
|Revision=0.9.9 r4878
|Revision=0.9.9 r4878
|Graphics=GSdx r4873
|Graphics=GSdx r4873
Line 57: Line 57:
|Region=NTSC-U
|Region=NTSC-U
|OS=Windows
|OS=Windows
|CPU=Intel Core i7 @ 3.4Ghz
|CPU=Intel Core i7 @ 3.4 GHz
|GPU=Nvidia GTX 285 768MB
|GPU=Nvidia GTX 285 768MB
|Revision=1.1.0 r5480
|Revision=1.1.0 r5480
Line 71: Line 71:
|Region=NTSC-J
|Region=NTSC-J
|OS=Windows
|OS=Windows
|CPU=I5 3330
|CPU=Intel Core i5-3330 @ 3.0 GHz
|GPU=HD radeon 6850
|GPU=HD Radeon 6850
|Revision=1.1.svn5832
|Revision=1.1.svn5832
|Graphics=GSdx
|Graphics=GSdx
Line 78: Line 78:
*SPU2-X
*SPU2-X
*?
*?
|Comments=USA v02.20(10/02/2006), Can be hard agressive for cpu and gpu., Can appear some glitchs in hardware mode in the races,but software mode its fine,even hardware mode its fine also.
|Comments=USA v02.20(10/02/2006), Can be hard for CPU and GPU. Can have some glitches in hardware mode in the races, but software mode is fine.
|Tester={{ForumUser|DESTRUIDOR}}
|Tester={{ForumUser|DESTRUIDOR}}
}}
}}
Line 85: Line 85:
|Region=NTSC-U
|Region=NTSC-U
|OS=Windows 7 64-Bit
|OS=Windows 7 64-Bit
|CPU=Intel i7 @ 3.4Ghz
|CPU=Intel Core i7 @ 3.4 GHz
|GPU=Sapphire R9 290X 4GB
|GPU=Sapphire R9 290X 4GB
|Revision=1.2.1 r5875
|Revision=1.2.1 r5875
|Graphics=GSdx 10 (Hardware) 0.1.16 r5875  
|Graphics=GSdx 0.1.16 r5875  
*D3D10 (Hardware)
|Sound=
|Sound=
*SPU2-X r5875
*SPU2-X r5875
Line 99: Line 100:
|Region=NTSC-U
|Region=NTSC-U
|OS=Windows 7
|OS=Windows 7
|CPU=C2D E7500 2.93Ghz
|CPU=Intel Core 2 Duo E7500 @ 2.93 GHz
|GPU=GeForce GT630 128-BIT 1GB
|GPU=GeForce GT630 128-bit 1GB
|Revision=1.2.1 2014-02-02
|Revision=1.2.1 2014-02-02
|Graphics=*GSdx10 0.1.16 (Hardware)
|Graphics=*GSdx 0.1.16
|Sound=SPU2-X 2014-07-14
*D3D10 (Hardware)
|Comments=Great FPS at the menus, badly FPS at races or showing cars. Slow-Motion FPS at the races, almost unplayable. (EE 3, VU 0, INTC, Wait Loop and MVU)
|Sound=
*SPU2-X 2014-07-14
*?
|Comments=Great FPS at the menus, bad FPS at races or showing cars. Slow-Motion FPS at the races, almost unplayable. (EE 3, VU 0, INTC, Wait Loop and MVU)
|Tester=Berto
|Tester=Berto
}}
}}
Line 111: Line 115:
|Region=NTSC-U
|Region=NTSC-U
|OS=Windows 8.1
|OS=Windows 8.1
|CPU=AMD A8-6600K @ 4.4Ghz
|CPU=AMD A8-6600K @ 4.4 GHz
|GPU=AMD Sapphire r9-270x
|GPU=AMD Sapphire R9 270X
|Revision=1.3.0
|Revision=1.3.0
|Graphics=GSdx
|Graphics=GSdx
|Sound=SPU2-X
|Sound=
*SPU2-X
*?
|Comments=Extra rendering threads set to 2, Direct3D11 (Software), (EE 1, VU 1, INTC, Wait Loop, MVU and MTVU) ran with 60 FPS
|Comments=Extra rendering threads set to 2, Direct3D11 (Software), (EE 1, VU 1, INTC, Wait Loop, MVU and MTVU) ran with 60 FPS
|Tester=Apihl1000
|Tester=Apihl1000
Line 123: Line 129:
|Region=PAL
|Region=PAL
|OS=Windows
|OS=Windows
|CPU=i5 4690 3.5 ghz
|CPU=Intel Core i5-4690 @ 3.5 GHz
|GPU=msi 750ti 2gd5/ovcv1
|GPU=MSI GTX 750 Ti 2gd5/ovcv1
|Revision=PCSX2 1.3.1-20150618094926
|Revision=PCSX2 1.3.1-20150618094926
|Graphics=GSdx32-SSE4.1
|Graphics=GSdx32-SSE4.1
|Sound=SPU2-X
|Sound=
|Comments=Runs above full speed. needed to set ee clamping mode manually to full so the text that says the time between you and the first car to display correct. looks like the this is needs to add to game fixes GameIndex.dbf so it can auto change the ee clamping mode to full. some rare random slowdowns that happened randomly in the races no specific reason but in last lees than a secont other than that the game works perfect.
*SPU2-X
*?
|Comments=Runs above full speed. Needed to set EE clamping mode manually to full so the text that says the time between you and the first car to display correctly. Looks like this needs to be added to game fixes GameIndex.dbf so it can auto change the EE clamping mode to full. Some rare random slowdowns that happened randomly in the races, no specific reason but in last less than a second. Other than that the game works perfect.
|Tester={{ForumUser|truemaster}}
|Tester={{ForumUser|truemaster}}
}}
}}
Line 138: Line 146:
|Region=?
|Region=?
|OS=Kubuntu 12.04 64 bit
|OS=Kubuntu 12.04 64 bit
|CPU=Core i3-2100 3.1 GHz dual core+HT
|CPU=Intel Core i3-2100 @ 3.1 GHz
|GPU=Nvidia 8800GT with proprietary 295.40 driver
|GPU=Nvidia 8800GT with proprietary 295.40 driver
|Revision=1.0.0
|Revision=1.0.0
|Graphics=GSdx 0.1.16
|Graphics=GSdx 0.1.16
|Sound=SPU2-X 2.0.0
|Sound=
*SPU2-X 2.0.0
*?
|Comments=Only problem is that in a race it is too slow (20-30 fps) and the game doesn't work with frame skipping. With hardware video acceleration enabled in GSdx, it is twice as slow. The problem seems to be the CPU.
|Comments=Only problem is that in a race it is too slow (20-30 fps) and the game doesn't work with frame skipping. With hardware video acceleration enabled in GSdx, it is twice as slow. The problem seems to be the CPU.
|Tester=T-dome
|Tester=T-dome
Line 151: Line 161:
*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.
*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 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.
*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.
*The "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.
*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.


Line 160: Line 170:
|IsFixed=0
|IsFixed=0
|IssueLevel=2
|IssueLevel=2
|Description=Crashes pretty often. This 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 ZeroGS or ZZOgl.
# 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 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 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 do not 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 205: Line 215:
|IsFixed=0
|IsFixed=0
|IssueLevel=-1
|IssueLevel=-1
|Description=The interlacing ingame is improper and "shakes".
|Description=The interlacing in-game is improper and "shakes".
|Workaround=Change the interlacing mode in GSdx to "Bob tff" to correct improper interlacing.
|Workaround=Change the interlacing mode in GSdx to "Bob tff" to correct improper interlacing.
}}
}}
ninja
485

edits