As the title says, r_DisableRendering it not functional.
Using it on Release, Beta or Latest will cause FiveM to instantly crash when opening.
I’ve tested this across 3 different PC’s all with different GPU/Hardware setups.
Simply add +set r_disablerendering 1 to your startup options and this will occur.
Attached the crash dump/
CfxCrashDump_2023_05_07_02_47_14.zip (1.1 MB)
I’m going to guess it’s fixed by fix(conhost): crash with r_disableRendering · citizenfx/fivem@29b3f1c · GitHub - might be I had another change lying around too in this regard however.
Testing this again on Latest branch the original issues seems to be fixed but it’s now crashing at the same point with a rage graphics error.
Attached zip crash dump
CfxCrashDump_2023_05_07_18_51_57.zip (1.1 MB)
Right, some other code that got added since I last needed to use disable-rendering seems to break now.
I made some attempt to fix it locally but I still saw something try to render so this needs a more detailed look instead.
How often does the release branch get updated?
Two other related edge-cases to consider would be the
GetD3D11Device bits in
DrawPerf (if settings were saved from the previous session) and the
sharedD3D11 bits in
Has there been any update to this?