FOV adjustment and misc CWCheat codes

10
United States
United States
Here are some FOV adjustment and misc CWCheat codes for
  • EU v2.00 (UCES01245 2.00)
  • US v2.00 (UCUS98632 2.00)
  • JP v1.01 (UCJS10100 1.01)
  • ASIA v1.00 (UCAS40265 1.00)

The codes do not affect pruning so higher values would make pop out on the sides more visible

See https://forums.ppsspp.org/showthread.php?tid=3590 for how one can use the CWCheat codes on PPSSPP

On real devices, use a tool like https://github.com/DragonNeos/cwcheatdb and refer to your CWCheat plugin's documentation

Edit: for GTPSP on PPSSPP, one can remove pop outs on the sides by disabling culling in graphics settings
 
Last edited:
I found the Camera Angle & Damper UCUS-98632 [US]

_C0 Camera Angle
_L 0x004F3100 0xDDDDDDD
_C0 Camera Damper
_L 0x004F3108 0xDDDDDDD

Gran Turismo 4 aka Stiff Cam:
Angle - 42F00000 (Float value: 120)
Damper - 41700000 (Float value: 15)

Gran Turismo 3 Cam:
Angle - 41F00000 (Float value: 30)
Damper - 41200000 (Float value: 10)

Default Gran Turismo PSP Cam:
Angle - 42C80000 (Float value: 100)
Damper - 42200000 (Float value: 40)

Click here for your own custom angle & damper value
 
I found the Camera Angle & Damper UCUS-98632 [US]

_C0 Camera Angle
_L 0x004F3100 0xDDDDDDD
_C0 Camera Damper
_L 0x004F3108 0xDDDDDDD

Gran Turismo 4 aka Stiff Cam:
Angle - 42F00000 (Float value: 120)
Damper - 41700000 (Float value: 15)

Gran Turismo 3 Cam:
Angle - 41F00000 (Float value: 30)
Damper - 41200000 (Float value: 10)

Default Gran Turismo PSP Cam:
Angle - 42C80000 (Float value: 100)
Damper - 42200000 (Float value: 40)

Click here for your own custom angle & damper value
how to apply bro?
 
Greetings! Katie and Blitz. I want to ask something, is there a way to disable the HUD through these cwcheat codes?

I tried making the textures transparent and to some e extent it worked. But the map, rev, turbo gauge, still stays no matter what I do
 
Here are some FOV adjustment and misc CWCheat codes for
  • EU v2.00 (UCES01245 2.00)
  • US v2.00 (UCUS98632 2.00)
  • JP v1.01 (UCJS10100 1.01)
  • ASIA v1.00 (UCAS40265 1.00)

The codes do not affect pruning so higher values would make pop out on the sides more visible

See https://forums.ppsspp.org/showthread.php?tid=3590 for how one can use the CWCheat codes on PPSSPP

On real devices, use a tool like https://github.com/DragonNeos/cwcheatdb and refer to your CWCheat plugin's documentation

Edit: for GTPSP on PPSSPP, one can remove pop outs on the sides by disabling culling in graphics settings
Sorry to bother, but would you happen to have the memory address of the camera distance values? The fov ones work fine, but they make the car look all zoomed out and tiny the higher the value, which isn't optimal with such a small screen
 
Sorry to bother, but would you happen to have the memory address of the camera distance values? The fov ones work fine, but they make the car look all zoomed out and tiny the higher the value, which isn't optimal with such a small screen
The only values you need to edit are the marked ones - the smaller the hex values the smaller FOV (and bigger car ofc). 50 FOV is a little too high for me too. Start from changing these to 08, it will give you just a tiny bit bigger FOV than original. If it's too small change it to 10, than to 18, 20 and so on until you'll find the perfect one. Don't forget these are hex values. Tested, working.
 

Attachments

  • Opera Zrzut ekranu_2024-05-25_183457_github.com.png
    Opera Zrzut ekranu_2024-05-25_183457_github.com.png
    2.7 KB · Views: 1
Last edited:
The only values you need to edit are the marked ones - the smaller the hex values the smaller FOV (and bigger car ofc). 50 FOV is a little too high for me too. Start from changing these to 08, it will give you just a tiny bit bigger FOV than original. If it's too small change it to 10, than to 18, 20 and so on until you'll find the perfect one. Don't forget these are hex values. Tested, working.
Oh I'm aware of that, but the reason I'm asking it's because I know it's possible since there's an old PPSSPP fork called Canary that has the option to alter the CamZ values (among other things) which define the distance from the camera to the player entity, in this case the car.

This wouldn't be a problem, however, if it weren't for the fact that it utilizes an outdated version of PPSSPP (1.03 if I'm not mistaken), it's very unstable and also riddled with nasty visual glitches, that's why I asked for the memory address of the CamZ values on the game itself so the same outcome can be achieved with a simple cheat. That way, it could be used in virtually any version of PPSSPP, along with real hardware

Here's a gameplay from someone i suspect is using the same method I just described. (The messed up HUD is a dead giveaway). Notice how he's got an augmented FOV but his car isn't zoomed out.

I also attached some screenshots for comparison
 

Attachments

  • Screenshot_20240526-011518~2.png
    Screenshot_20240526-011518~2.png
    224.6 KB · Views: 1
  • Screenshot_20240526-011115~3.png
    Screenshot_20240526-011115~3.png
    284 KB · Views: 1
Last edited:
Back