Gran Turismo 4: Difference between revisions
No edit summary |
(merged issues) |
||
Line 697: | Line 697: | ||
|Description=Red and green garbage from the depth buffer renders through to the screen. | |Description=Red and green garbage from the depth buffer renders through to the screen. | ||
|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. | ||
}} | }} | ||
Line 731: | Line 723: | ||
|Description=Car headlights, smoke and dust effects are seen through objects. | |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". | |Workaround=Go to Config -> Video (GS) -> Plugin Settings, and set renderer to "OpenGL (Hardware)". Then set Blending Unity Accuracy to at least "High". | ||
**'''Alternate workaround''': Use software rendering. | |||
}} | }} | ||
Revision as of 11:04, 26 January 2022
Developer(s): Polyphony Digital
Publisher(s): SCEI (JP, AS, KO), SCEA (US), SCEE (EU)
Genre: Racing
Wikipedia: Link
Game review links: IGN: 9.5/10, Metacritic: 89/100, GameSpot: 8.9/10, Eurogamer: 8/10
Game description: With authentic cars, courses, and car physics, Gran Turismo 4 adds an even more realistic racing simulation to the series. The characteristics of each car take into account weight, speed, friction, and more to deliver realistic handling. Test-drive new vehicles in courses located in various sites, such as Nurburgring Nordschleife, New York City, the Grand Canyon, and Tsukuba Circuit. Along with Career mode, Gran Turismo 4 highlights the new GT Photo mode and GT Online mode, which lets players around the world compete over the Internet.
Gran Turismo 4 is the fourth game in the Gran Turismo series. It features over 700 vehicles, 51 tracks, B-Spec mode, Photo mode, and 1080i support. This game was released on February 22, 2005 to critical acclaim.
Test configurations on Windows:
Environment | Configurations | Comments | Tester | ||||
---|---|---|---|---|---|---|---|
Region | OS | CPU/GPU | Revision | Graphics | Sound/Pad | ||
NTSC-U | Windows 7 |
|
0.9.9 (r4878)
|
GSdx (r4873) |
|
• 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. • EE Cyclerate can give speedup during the races, but may also cause slowdown to the track-selection screens where videos are shown at the background. • 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. |
Machina |
NTSC-U | Windows |
|
1.1.0 (r5480) | GSdx SSE4 (r5442) |
|
Runs near full speed. | |
NTSC-J | Windows |
|
1.1.0 (svn r5832) | GSdx |
|
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. | |
NTSC-U | Windows 7 x64 |
|
1.2.1 r5875 | GSdx 0.1.16 (r5875)
|
|
BIOS v2.00, Game runs fine at 5x Native resolution. Some slight hiccups/slowdown in the menus. One weird glitch I saw was on dirt tracks, the plumes of dirt seem to be transparent and can be seen through hills and can be seen coming out of the middle of the back of the car. Still use recommended hacks for maximum performance. | Zrooney |
NTSC-U | Windows 7 |
|
1.2.1 (2014-02-02)
|
GSdx 0.1.16
|
|
Great FPS at the menus, bad FPS at races or showing cars. Slowmotion FPS at the races, almost unplayable. | Berto |
PAL | Windows 7 |
|
1.2.1.(r5873)
|
GSdx SSE4 (r5875) |
|
60+ FPS in menus but drops below 45~50 in races or licence tests. With speedhacks the frame rates are pretty stable, 55~60 FPS in races with multiple cars. | KX64 |
NTSC-U | Windows 8.1 |
|
1.3.0
|
GSdx
|
|
Ran with 60 FPS | Apihl1000 |
PAL | Windows |
|
1.3.1 (svn 2015-06-18) | GSdx32 SSE4 |
|
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. | |
NTSC-U | Windows 7 |
|
1.4.0 | GSdx32 SSE4
|
|
All other graphic options are default. Game runs smoother than on the real PS2. Besides problem with licence test crashing everything works perfect. I did notice licence test uses way more RAM than actual races, and I crashed when I ran out of RAM in certain tests. Other than that it's perfect. (at 4x native with MSAA and AF enabled, I'm peaking at 10+ GB of RAM usage) | Infini |
PAL | Windows XP (SP3) |
|
v1.5.0 (dev-2016-01-26)
|
GSdx SSE4 (2016-01-26)
|
|
On some menus, a minor slowdown occurs (ca. 2–4 FPS). On normal racetracks, FPS stays around 50 (PAL), but on more graphically-intensive tracks like street circuits, slowdowns can be slight (ca. 5–18 FPS) on Single Race / 2-players mode. On Time-trials, minor slowdown may occur on tracks like that (ca. 2–5 FPS). On Software-mode: Usually about 10 FPS slower than hardware-rendering (with 4 threads). Other bugs: a red flash occur at every race start, but shade boost tones it down. Lower edges on menus may have white lines. | Titus03 |
NTSC-U | Windows 10 x64 |
|
v1.5.0 (dev-2017-09-17)
|
GSdx SSE4.1 (2017-09-17)
|
|
Game starts fine. Menus run well save for some choppiness, especially during transitions and when loading car models. License tests require more cycles & RAM usage than regular races, seeming to cause upwards of 10 FPS slowdown in some cases. Would probably get better/more stable performance with further tweaks. Interestingly having 12 cores seems to make little difference to performance from a threading standpoint. | starkeysuper64 |
NTSC-U | Windows 10 64-bit (build 16299) |
|
1.5.0 (dev 2017-12-08)
|
GSdx AVX2 (2017-12-28)
|
|
Runs perfectly well, albeit with a lag spike of 10-15 FPS at about the end of some tracks. Menu-wise, every time a menu changes, the screen fades and goes down with an angle. The car models are blurry, though that might be because of random tweaking. Tested on the most intensive track I could find, Las Vegas Drag Strip, in a BMW M3 GTR Race Car and it stayed at 60 FPS. Photo mode works but its a blur when taking pictures and the photo looks lifeless due to color degradation. | ZestoOnyx |
NTSC-U | Windows 8.1 |
|
1.5.0
|
GSdx 1.1.0 AVX
|
|
Runs at full speed. Using above 3X native gives weird stuttering issues. Using 480p mode with Shadeboost enabled to compensate. At these settings the game is absolutely stable: Renderer: Direct3D11 (Hardware), Interlacing (F5): Bob tff, Texture Filtering: Bilinear (PS2), Internal Resolution: 3x Native, Anisotropic Filtering: 16x, Mipmapping: Basic (Fast), CRC Hack Level: Automatic (Default), (✓) Allow 8-Bit Textures. EE/IOP: Clamping Mode "Full", VU: Clamping mode "Extra". License tests require these two to be at their stock settings. | lolled132 |
NTSC-U | Windows 10 |
|
1.6.0
|
GSdx 1.2.0 AVX2
|
|
Runs at full speed. Using 480p. render scaling is at 3x and it very rarely stutters for a second or two, VRAM usage goes up to 3.5GB. License tests and everything works perfectly in version 1.6.0. | TurboSonic |
NTSC-U | Windows 10 LTSC 1809 (17763) |
|
1.6.0
|
GSdx32-AVX2 1.2.0
|
|
BIOS: USA v01.60 (07/02/2002). 60 FPS 100% of the time for both menus and sim; tracked using RTSS. Runs smooth without any issues. No drops in FPS, stutters, etc. anywhere. Any settings I didn't note to the left are at default/recommended. Game works perfectly with a Microsoft Xbox 360 Wireless Controller for Windows. | Strayborne |
NTSC-J | Windows 10 |
|
1.7.0 beta 32-bit | GSdx32-AVX2 1.2.0 |
|
Runs at full speed, both software and hardware mode. Note that GSDX hardware mode had a graphical bug where the wheel rims are being offset, resulting a shaky wheel when viewed under replay, software mode are unaffected. Meanwhile, software mode requires a strong CPU with at least 6 core and above to emulate properly, CPU usage on all cores are at about 50%-60%. License test bug happens on license iB-5 where you may require to disable automatic gamefixes first. Also, be warned that continuous loading savestate will causing the game unable to perform save, citing the game save is corrupt. You can only fix this issue by deleting GT4 game save from memcard browser and load the savestate and save the game, but you will lose all cars except the current one that you had drive. | amirzaim |
NTSC-U | Windows 10 |
|
1.7.0 (dev-1545)
|
GSdx
|
SPU2-X | Completed a large chunk of the game. Good emulation these days, game ran mostly full speed at 6x native resolution with no speedhacks, but a handful of tracks needed the resolution to be reduced to 4x. Run the game in OpenGL mode for proper brightness. Ensure Blending Accuracy is set to at least Basic, and Conservative Buffer Allocation is checked. In Emulation Settings > GS Window, change Zoom to 100.20 to remove some garbage from the edges of the screen. Special Stage Route 5 and George V Paris are the most intensive tracks to run at full speed, and you'll get your lowest framerates here, so they're good benchmarks. A few minor visual bugs remain. "Get ready to drive" will be stuck on the screen even once you gain control of the car. This can be fixed by just pressing Select (to change view). The NTSC version of the game is preferable due to its 480p mode, and the game is hideously interlaced without 480p enabled. Final note: be very careful using savestates in this game, if you overuse them you can corrupt the memory card. Not just the GT4 save, but the entire memory card. To prevent this, ensure you never load a state from before the memory card was last saved to. | CynicMimic |
Environment | Configurations | Comments | Tester | ||||
---|---|---|---|---|---|---|---|
Region | OS | CPU/GPU | Revision | Graphics | Sound/Pad | ||
? | Kubuntu 12.04 x64 |
|
1.0.0 | GSdx 0.1.16 |
|
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. | T-dome |
NTSC-U | Fedora 22 x64 |
|
1.4.0 | GSdx 1.0.0 |
|
50% speed with hardware accel. 25% with software. playable otherwise. | kerpal |
NTSC-U | Debian 9.3 x64 |
|
1.4.0 | GSdx 1.0.0 |
|
mostly 100% speed with hardware acceleration at native resolution. some occasional slowdowns but not often. very playable but the audio buzzes a bit. | kerpal |
PAL | Ubuntu 17.04 x64 |
|
1.5.0~git201708311541 | GSdx (GCC 6.3.0, SSE2) 1.0.0 | SPU2-X 2.0.0 | Full speed at native resolution. Black screen at higher resolution. | Marc |
NTSC-U | Debian 9.3 x64 |
|
1.5.0-git20171209-2234 | GSdx 1.1.0 |
|
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. | kerpal |
NTSC-U | Arch Linux |
|
1.7.0 (dev-13 g8bf6ba144)
|
GSdx 1.2.0 AVX2
|
|
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. | Bizlab |
NTSC-J | Arch Linux |
|
1.7.0 (dev-13 g8bf6ba144)
|
GSdx 1.2.0 AVX2
|
|
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. | Bizlab |
NTSC-U | KDE Neon (Ubuntu 20.04) |
|
1.5.0
|
GSdx 1.1.0 AVX
|
|
Mostly stays at a steady 60 fps during the races. The odd drop will occur. George V Paris (which seems to be one of the hardest to emulate) race track works fine at full 60 fps; but there will be the odd drop again to about 50 or even 47 fps. Otherwise, pretty playable. Funny how this is a CPU intensive game. But apparently the lower EE Cycle rate, higher the EE Skipping rate and without MTVU enabled, the better the game performs (At least in my case). However, there will be screen shaking. To reduce that, go in the game options and under "Screen," change the screen to "HDTV 1080i." That should reduce the screen shaking during a race. But when going through some menus like selecting a race course, there will be screen shaking. Otherwise, the game works decently enough to play. | Dreaper |
Trivia
- Original names: グランツーリスモ4 (SCPS-17001) & (SCPS-19252), 跑車浪漫旅4 (SCAJ-30007), 跑车浪漫旅 4 (SCCS-60002), 그란 투리스모 4 (SCKA-30001)
- Information and reports of demo versions of this game can be found here.
Known Issues
Out of VRAM crashes
- Status: Active
- Type: Major
- 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:
- PCSX2 versions released later than May 7th, 2016 should have much smaller VRAM spikes.
- Make sure Large Framebuffer is disabled.
- 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. Note in 1.7.0 dev builds Sparse Texture may be broken and cause problems.
Missing/flickering textures
- Status: Active
- Type: Minor
- 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.
Garbage on bottom and right screen edges
- Status: Active
- Type: Minor
- Description: Red and green garbage from the depth buffer renders through to the screen.
- Workaround: Go to Config -> Emulation Settings -> GS Window and set Zoom to 100.20.
Shaky wheel rims seen during replay
- Status: Active
- Type: Minor
- Description: Wheel rims are being offset during upscaling, resulting the wheel rims are out of alignment and shaky when seen during replay
- Workaround: Enable GSDX HW hacks by enabling Merge Sprite and Wild Arms Offset, set Half Pixel Offset to Special (Texture-Aggressive), set Round Sprite to Full and set Texture Offset to X:60 Y:0. Alternatively, you can use software mode but isn't ideal at all or just stick to PS2 native display but less ideal for bigger screens.
Fixed Issues
Demo races do not work
- Status: Fixed
- Type: Minor
- Description: Demonstrations return back to the menu as soon as they start.
- Workaround: Go to Config -> Emulation Settings -> EE/IOP and set Clamping Mode to "Full". However, this will make other events fail to load, requiring it to be set back to Normal after the Demonstration.
Effects visible through objects
- Status: Fixed
- Type: Minor
- 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".
- Alternate workaround: Use software rendering.
Game doesn't load past copyright screen.
- Status: Fixed
- Type: Major
- Description: Due to dual layer issues the game might not load past the copyright screen.
- Workaround:
- As of March 2016 this issue has been fixed on the latest v1.5.0 development builds.
- For older versions use patch supplied at the compatibility list on the forums (see bottom of the page for links). Though this will disable all in game videos (including the background of the main menu).
Improper interlacing
- Type: Note (not an issue)
- Description: The interlacing in-game is improper and "shakes".
- Workaround: Change the interlacing mode in GSdx to "Bob tff" to correct improper interlacing.
Garbage photos
- Status: Fixed
- Type: Serious
- Description: Garbage replaces the area in which the photo should be displayed.
- Workaround: As of May 2016 this issue has been fixed on the latest v1.5.0 development builds.
Whole screen garbage
- Status: Fixed
- Type: Serious
- Description: During events, the 3D area of the screen is obscured by garbage graphics.
- Workaround:
- This issue can been fixed in the latest v1.5.0 development builds as of May 2016 (see issue below).
- For older versions: In-game during an event press the start button, go to Screen and set Brightness to 0. Or from the main menu of the game, go to Options -> Picture Quality, and set Brightness to 0.
- For older NTSC versions: Change the display in game config to "Normal", then you can set the brightness to 5 without the broken graphics and also have a correct image.
Broken in-game screen options
- Status: Fixed
- Type: Minor
- Description: In-game brightness or contrast values do not work properly in-game.
- 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.
Gameplay Screenshots
|
![]() |
---|
- Games rated A in Japan
- Games rated E in North America
- Games rated 3+ in Europe
- Games rated G in Australia
- Games rated ALL in Korea
- Games support steering wheel
- Games with special controllers
- Games with widescreen support
- Games with progressive support
- GPU intensive games
- CPU intensive games
- Multiplayer games
- Games with English language
- Games with Japanese language
- Games with German language
- Games with French language
- Games with Spanish language
- Games with Italian language
- Games with Simplified Chinese language
- Games with Traditional Chinese language
- Games with Korean language
- Games
- Playable games
- Racing
- Games by Polyphony Digital
- Games with major issues
- Games with minor issues