Most likely my last mod version i will make for awhile for various reasons, the game being underwhelming for one. The game just doesn't interest me as much lately.
I'm also expecting Turn 10 to disable using modified zip files in the future or at least disabling certain files from being modified via encryption, this is just speculation, as you might know, they hate any mods that improve enjoyment. So if for any reason the mod stops working or crashes your game after an update, it's because they updated the zip file and my mod will not work.
Thanks to everyone for trying out/being interested in using the mod and your comments.
Hi Wonder2k19, thank you for the great mod and the update!
I was wondering, would it technically be possible to (re-)enable motion blur in dashboard / cockpit cam? (T10 could have at least made it optional...)
Also, how difficult would it be to create a near chase cam similar to the one of Driveclub, i.e. lower and closer to car (with normal fov and everything else unchanged)?
1. Open the renderscenarios folder in media/pcfamily/renderscenarios/ 2. Depending on your graphic settings being Ultra, High or Medium, open the corresponding folder then open global.xml. 3. Add these lines to the file
e.g <DynamicRenderSettings> <MotionBlurSamples value="3"/> <MotionBlurExposureFraction value="0"/> <MotionBlurInCockpit value="1"/> 4. Save and test.
As far as Driveclub, yes that is possible with the proper research although having not played the game it would require more effort on my part but i'll keep your suggestion in mind if i ever update this mod.
Wow, thank you so much for your great comment and the detailed description! :)
Motion blur in cockpit view(s) works like a charm with your lines, and (for me) it adds so much sense of speed and immersion!
Browsing the global.xml file, I discovered some more interesting settings, like High Definition Wheel Blur (set <HighDefAIWheelBlur value="0"/> to 1 - works great in conjunction with the 2D Wheel Fix mod), tweaks to LODs and shadows and more (still needs testing)
Concerning Driveclub, I would greatly appreciate your help in figuring out the necessary changes. Apparently, there appears to have been a mod for FH3 (also perhaps FM7 judging by the image enclosed?) which basically translated the chase cam of Driveclub (low height, close to the car) to Forza: Lower chase camera angle.
Yes, any useful lines found in global.xml need proper documentation at least somewhere for the public to hopefully be of use. Doing these camera changes is trivial and presents more complications, here is just some thoughts so far.
- Some cars do not rely on the camera.zip file instead(maybe) on the gamedb.slt file that is encrypted. I said this before, one car might look fine then another car might be unusable(where the camera values are placed) so without access to that file we are limited in that way to changes/values made. - OpusRelease (FH3 Developer Build) camera values might not translate properly to FM 2023. It's a useful tool but still has it's limitations for being of use.
- Any change in values made in the camera.ini file, i have to re-pack the entire zip file, wait for the game to load then see any changes. We need better tools to test camera values, being an online service game, again we are limited to any sort of real-time tools, if at all possible. - Math formulas, camera physics and algorithms, just lol. Whoever is the engineer at Turn10 must think the camera is fine which is why we haven't seen any major changes for years now. It's getting old now....
- If you want to do these changes like I've done, use Quickbms(altervista) with the zip script (method 21 encryption is used) to extract the camera.zip file, edit the xml and ini files with a text editor (notepad++), re-pack all files as a zip file with windows zip compression(select all files in a folder, right-click, send to zip). I've done the QuickBms part already so you only need to re-pack any of my versions albeit with some changes already made.
TL;DR Made a version loosely based on Driveclub, used my own values. It will never be perfect to the game but it's the best i can do for now.
Wow, I'm absolutely speechless and blown away, this is pretty much spot on and way better than I could have ever hoped for, thank you so much!!
While I will try to fiddle with the camera settings a little bit more myself (in this regard, again, thank you very much for the detailed how-to), I think the far chase camera is already almost perfect and my favorite combined with a FoV between 42-48. The near chase cam is also great on its own, perhaps just a tiny bit too low, but still far better than the default ones - I'll try and see if I can tweak it a bit. I also added a few images with different car/track combos to showcase the difference and the look of the cameras in general!
Yes, it would be awesome, if, we had more control over these settings ingame, ranging from basic things like seat position/heigt adjustment in cockpit view to perhaps even creating and saving custom cameras.
Speaking of cockpit view, do you happen to know if/how the exposure could be adjusted? Maybe it's just me, but sometimes I find it very dark inside a car (also a reason I prefer 3rd person cam) to the point where almost everything is a shade of black or darkish grey.
Again, thank you for your efforts, it made FM so much more fun for me!
"Speaking of cockpit view, do you happen to know if/how the exposure could be adjusted?"
Maybe in base/tracks/basetracksettings.xml would be my best guess, though not entirely sure and you will have to experiment. "<ToneMapCockpitExposure.." specifically the exposure values being negative values. Always make a backup of the file before changing values. I was thinking about <CockpitFilmicTone......exposure not tonemap.
Also about the global.xml file <TilingScenario value="3"/> is the value for Anti-aliasing, setting this value to 0 removes TAA. I would change these myself but the game is getting monthly updates and they (devs) may decide to change these values in the future.
I did try to change the 'tilingscenarios' option to '0' as you said, but it appears it stops the game from loading, as you get a perpetual loading screen before the game goes to the Turn10 intro. It's a shame I can't turn TAA off...
Yep as expected, probably fixed/patched. That's how Turn 10 roll, fix things that don't need fixing, forget about all the other bullshit that need to be fixed. I didn't expect they would care about anyone disabling Anti-Aliasing, not that i cared too much about it anyway.
Extract entire zip to a folder, open camerasettings.ini file with notepad, find "FollowHighCam\HeightMaxAboveGround" and "FollowLowCam\HeightMaxAboveGround", change both Min and Max heights values simultaneously, re-pack all files into a zip called 'camera.zip' with windows compression.
Added 2 new camera versions - (Traditional GT) and (Default with just effects removed)
- FOV settings are "50 degrees" for the first chase camera and "40 degrees" for the high chase camera. - Refer to screenshot, which has slightly different values but everything else like cockpit can be whatever value you want.
Haven't played the game in awhile so i thought give y'all something to play around with.
great mod. is there any way to make the camera follow the rotation/direction of the car? because then it would be a perfect replica of the GT7 feel which i absoltely love
I have updated to Version 0.2, check the optional download on the files page. The zip file just needs to be directly renamed and placed in game folder as "camera.zip".
32 comments
Comments locked
The author has locked this comment topic for the time beingMost likely my last mod version i will make for awhile for various reasons, the game being underwhelming for one.
The game just doesn't interest me as much lately.
I'm also expecting Turn 10 to disable using modified zip files in the future or at least disabling certain files from being modified via encryption, this is just speculation, as you might know, they hate any mods that improve enjoyment.
So if for any reason the mod stops working or crashes your game after an update, it's because they updated the zip file and my mod will not work.
Thanks to everyone for trying out/being interested in using the mod and your comments.
I was wondering, would it technically be possible to (re-)enable motion blur in dashboard / cockpit cam? (T10 could have at least made it optional...)
Also, how difficult would it be to create a near chase cam similar to the one of Driveclub, i.e. lower and closer to car (with normal fov and everything else unchanged)?
Cheers!
1. Open the renderscenarios folder in media/pcfamily/renderscenarios/
2. Depending on your graphic settings being Ultra, High or Medium, open the corresponding folder then open global.xml.
3. Add these lines to the file
e.g <DynamicRenderSettings>
<MotionBlurSamples value="3"/>
<MotionBlurExposureFraction value="0"/>
<MotionBlurInCockpit value="1"/>
4. Save and test.
As far as Driveclub, yes that is possible with the proper research although having not played the game it would require more effort on my part but i'll keep your suggestion in mind if i ever update this mod.
Motion blur in cockpit view(s) works like a charm with your lines, and (for me) it adds so much sense of speed and immersion!
Browsing the global.xml file, I discovered some more interesting settings, like High Definition Wheel Blur (set <HighDefAIWheelBlur value="0"/> to 1 - works great in conjunction with the 2D Wheel Fix mod), tweaks to LODs and shadows and more (still needs testing)
Concerning Driveclub, I would greatly appreciate your help in figuring out the necessary changes. Apparently, there appears to have been a mod for FH3 (also perhaps FM7 judging by the image enclosed?) which basically translated the chase cam of Driveclub (low height, close to the car) to Forza: Lower chase camera angle.
FM23 (default / mockup photomode):
Doing these camera changes is trivial and presents more complications, here is just some thoughts so far.
- Some cars do not rely on the camera.zip file instead(maybe) on the gamedb.slt file that is encrypted.
I said this before, one car might look fine then another car might be unusable(where the camera values are placed) so without access to that file we are limited in that way to changes/values made.
- OpusRelease (FH3 Developer Build) camera values might not translate properly to FM 2023.
It's a useful tool but still has it's limitations for being of use.
- Any change in values made in the camera.ini file, i have to re-pack the entire zip file, wait for the game to load then see any changes.
We need better tools to test camera values, being an online service game, again we are limited to any sort of real-time tools, if at all possible.
- Math formulas, camera physics and algorithms, just lol.
Whoever is the engineer at Turn10 must think the camera is fine which is why we haven't seen any major changes for years now. It's getting old now....
- If you want to do these changes like I've done, use Quickbms(altervista) with the zip script (method 21 encryption is used) to extract the camera.zip file, edit the xml and ini files with a text editor (notepad++), re-pack all files as a zip file with windows zip compression(select all files in a folder, right-click, send to zip).
I've done the QuickBms part already so you only need to re-pack any of my versions albeit with some changes already made.
TL;DR Made a version loosely based on Driveclub, used my own values. It will never be perfect to the game but it's the best i can do for now.
While I will try to fiddle with the camera settings a little bit more myself (in this regard, again, thank you very much for the detailed how-to), I think the far chase camera is already almost perfect and my favorite combined with a FoV between 42-48. The near chase cam is also great on its own, perhaps just a tiny bit too low, but still far better than the default ones - I'll try and see if I can tweak it a bit. I also added a few images with different car/track combos to showcase the difference and the look of the cameras in general!
Yes, it would be awesome, if, we had more control over these settings ingame, ranging from basic things like seat position/heigt adjustment in cockpit view to perhaps even creating and saving custom cameras.
Speaking of cockpit view, do you happen to know if/how the exposure could be adjusted? Maybe it's just me, but sometimes I find it very dark inside a car (also a reason I prefer 3rd person cam) to the point where almost everything is a shade of black or darkish grey.
Again, thank you for your efforts, it made FM so much more fun for me!
Maybe in base/tracks/basetracksettings.xml would be my best guess, though not entirely sure and you will have to experiment.
I was thinking about <CockpitFilmicTone......exposure not tonemap."<ToneMapCockpitExposure.." specifically the exposure values being negative values.
Always make a backup of the file before changing values.
Also about the global.xml file
<TilingScenario value="3"/> is the value for Anti-aliasing, setting this value to 0 removes TAA.
I would change these myself but the game is getting monthly updates and they (devs) may decide to change these values in the future.
Glad you like the mod, thanks!
- FOV settings are "50 degrees" for the first chase camera and "40 degrees" for the high chase camera.
- Refer to screenshot, which has slightly different values but everything else like cockpit can be whatever value you want.
Haven't played the game in awhile so i thought give y'all something to play around with.
Will be neatly packed into a 7-zip archive.
Files verified, thank you Eric :)
All other versions will be archived.
I will be uploading a non-modded version with just driving effects removed soon as an optional file.