GTR2 Graphics Optimization

Scratchpad

===
241010

Testing Graphics Options at Jacarepaguá for effect on jittery frame times
- 2004 NGT Porsche GT3-RSRPrivate Practice, Clear, 1pm
- Max (Custom): 5ms - 17ms
- Max ~ -Compressed Textures (PLR)
	10-10-2024, 21:07:56 GTR2.exe benchmark completed, 7653 frames rendered in 85.032 s
                     Average framerate  :   90.0 FPS
                     Minimum framerate  :   88.2 FPS
                     Maximum framerate  :   90.9 FPS
                     1% low framerate   :   59.8 FPS
                     0.1% low framerate :   41.6 FPS
- Full: 8ms - 15ms
- High: 
- Medium: 8ms - 15ms1`
- Low: 
	10-10-2024, 20:45:47 GTR2.exe benchmark completed, 17811 frames rendered in 197.891 s
                     Average framerate  :   90.0 FPS
                     Minimum framerate  :   88.4 FPS
                     Maximum framerate  :   90.9 FPS
                     1% low framerate   :   62.4 FPS
                     0.1% low framerate :   43.9 FPS
- Low + Custom Low Video
	10-10-2024, 20:49:39 GTR2.exe benchmark completed, 7790 frames rendered in 86.547 s
                     Average framerate  :   90.0 FPS
                     Minimum framerate  :   88.5 FPS
                     Maximum framerate  :   90.8 FPS
                     1% low framerate   :   65.1 FPS
                     0.1% low framerate :   43.9 FPS
- Low ~ +Level of Detail Bias 75% -High Detail Wheels -Super Fidelity Replays -High Resolution Car Livery -High Resolution Cockpit 
	10-10-2024, 20:54:27 GTR2.exe benchmark completed, 8823 frames rendered in 98.031 s
                     Average framerate  :   90.0 FPS
                     Minimum framerate  :   88.5 FPS
                     Maximum framerate  :   90.8 FPS
                     1% low framerate   :   64.3 FPS
                     0.1% low framerate :   46.9 FPS
Low ~ -Replays -Record Best Lap -Timestamp Replays +Replay Fidelity Minimum 
	10-10-2024, 20:58:34 GTR2.exe benchmark completed, 7320 frames rendered in 81.328 s
                     Average framerate  :   90.0 FPS
                     Minimum framerate  :   88.8 FPS
                     Maximum framerate  :   90.9 FPS
                     1% low framerate   :   60.9 FPS
                     0.1% low framerate :   46.7 FPS
===
240616

Testing performance for FIA GT 2004 30 AI at Spa 2004
- Rearview Back Clip=5000 + LODMultiplier=1.0 + graphicsForceTrackLODOut=2500
- Seems normal enough

Might be seeing this problem: "this setting could cause visual weirdness where multiple instances of the same object, say tree, are visible simultaneously."
- Some trees are sort of flashing at Spa
- Nah, this problem seems to be about the angle you're looking at the tree at

Defviews.cam
- LODMultiplier=(1.00000)
  - 1.25: Same lod, draw distance, pop-in
  
===
240616

Testing performance for FIA GT 2004 30 AI at Donington GP 2004

Shovas.PLR
Rearview Back Clip="5000.00000"
- 0.00: +/- 0% FPS, no effect, so 5000 ok

Defviews.cam
- LODMultiplier=(8.00000)
  - 1.0: Double FPS ~100 to ~200 
  - 2.0: -12% FPS (~200 to ~175), fixes all pop-in issues
    - May be acceptable but try CrewChief.ini graphicsRearViewLODMultiplier first
- LODMultiplier=2.0 with default ClipPlanes and graphicsForceTrackLODOut=2500
  -  2.0: -20% FPS (~200 to ~160 lows), solved shadow pop-in though
  - 1.25: -10% FPS (~200 to 180 lows), shadow pop-in distance increased (good)
  -  1.5: -15% FPS (~200 to 170 lows), shadow pop-in distance increased (good)
  - 1.75: -20% FPS (~200 to 160 lows), shadow pop-in distance increased (good)
  - Conclusion: Not worth the FPS loss I guess and it was just the one front straight build as seen from the back straight at quite a distance so meh
  
- ClipPlanes=(0.17500, *100000.000000*)
  -    50000: Same lod, draw distance, and fps that I can see
  -    25000: +5% FPS maybe (~200 to ~210), same lod and draw distance
  -    12500: same lod and draw distance
  -     6250: same lod and draw distance
    ^ If this is meters then it makes sense why it's so much lower than 100000
  -     3125: same lod and draw distance
  -   1562.5: same lod and draw distance
  -   781.25: same lod and draw distance
  -  390.625: same lod and draw distance
    ^ CrewChief.ini graphicsForceTrackLODOut=2500 may be overriding this
  - 195.3125: same lod and draw distance
  -    10.00: same lod and draw distance
    ^ Again with graphicsForceTrackLODOut=0: Yes, same pop-in symptoms 
	^ ClipPlanes(..., 2500): Hm, no, same pop-in symptoms
	^ ClipPlanes(..., 5000): Same pop-in symptoms
	^ So ClipPlanes(.., N) is not the same as CrewChief.ini graphicsForceTrackLODOut
	  ^ I probably confused ClipPlanes behaviour when testing it alongside PLR LODMultiplier
    ^ graphicsForceTrackLODOut is still needed
	^ Is ClipPlanes(.., N) still needed? No, back to default (500) and graphicsForceTrackLODOut=2500, and everything's fine.
  - I may have been seeing effects with ClipPlanes on a drop without CCGEP
	
CrewChief.ini
- graphicsRearViewLODMultiplier = 8.000000
  - 1.0: No significant change +/- to FPS
- graphicsForceTrackLODOut = 0.0
  - =5000: -20% FPS (~200 to ~160), fixes pop-in objects, does not fix shadow pop-in 
  - =2500: +5% FPS maybe (~200 to ~210), fixes pop-in objects, does not fix shadow pop-in