Gran Turismo 4: Difference between revisions
Right, Impact of EE also explained.
Karasuhebi (talk | contribs) m (I think you meant Q9650) |
(Right, Impact of EE also explained.) |
||
| Line 194: | Line 194: | ||
|Graphics=GSDx32-SSE4 20160126 | |Graphics=GSDx32-SSE4 20160126 | ||
|Sound=SPU2-X 20150912 | |Sound=SPU2-X 20150912 | ||
|Comments=On some menus, a minor slowdown occurs (ca. | |Comments=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). Settings: EE/IOP: Clamping Mode=Full / VUI: Clamping Mode=Extra. Speedhacks: EE=0 & VU=2, INTC, Idle loop, mVU & MTVU ON. Graphics: Interlacing=Bob tff, Resolution: 2x Native (Required for smooth replays, otherwise Custom resolution: 1920x1080 doesn't give any extra slowdowns.), 8-bit=ON, BF=Forced, CRC=Full, HW-hacks: ON (Half-pixel Offset, & Align Sprite ON), Logarithmic Z=ON, AC=ON, Shader: Shade Boost: 40, 100 & 65. Other bugs: a red flash occur at every race start, but shade boost tones it down. Lower edges on menus may have white lines. | ||
|Tester=Titus03 | |Tester=Titus03 | ||
}} | }} | ||
| Line 220: | Line 220: | ||
*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. | ||
*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. | *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. | ||