If you want to change the color of the lighting in the interior and control when the spoiler comes up, I recommend you try out Enhanced Vehicle System by hgyi56! Update ver. 1.1:Improved the damaged appearance of the car New Update ver. 1.2:Fixed the annoying camera auto centering
It's the best vehicle mode ever. I made it perfect in everything, including vehicle speed, handling, design, lighting, etc. I wonder if it is possible to provide a version of the camera setup that is set like the existing vehicles
*EDIT: You can now download the vanilla Camera version in the optional files to have the default camera.
If you go into Cyperpunk 2077/r6/tweaks/lotus_evija/lotus_evija.yaml and open the yaml file, you can delete 'tppCameraPresets' and then you will have the vanilla/original camera presets.
You can also delete 'tppCameraParams' to make the TPP camera fov the same as in vanilla cars
Just make sure you keep the syntax of everything else the same as it was when you delete something or else the car wont spawn in game
The vehicle's tpp seems new and unique, almost like a cinematic point of view combined. However, the y point of view is slightly lower, so the front seems to be slightly obscured by the vehicle. Other than that, your work looks great.
I changed the camera position in TPP through the yaml because I want everyone to experience the car like I see it in my game.
However, you can change the camera position to your liking. If you go into Cyperpunk 2077/r6/tweaks/lotus_evija/lotus_evija.yaml you can open the yaml file and increase the y value in the evija camera presets which are located at the top of the file under the gear_inline 7 !
Hey, just wanna say this is probably one of the best car mods for Cyberpunk 2077 out there! outstanding job
I have to ask tho, in your lotus_evija.yaml file, vehEngineData is not put under Vehicle.lotus_evija which might cause the gearing not to work?
I tried to make the car gearless by editing said file and putting vehEngineData under Vehicle.lotus_evija and removing the gear, but I haven't had any luck.
Would you mind giving some clarity on this?
I have minimal experience in modding, so please forgive me if there's a misunderstanding
You are correct, I did make a mistake there but it's fine since the car is just using the caliburn gears and VehEngineData. I really like the handling and don't want to ruin it so I will leave this as it is but thanks for letting me know, this clears up the confusion I had.
1. Put "vehEngineData" under "Vehicle.lotus_evija"
2. In "gears" list (under "vehEngineData") replace "- !remove Vehicle.VehicleEngineData_4_SportPlus_inline0....7" to "- !remove Vehicle.VehicleEngineData_4_SuperSport_inline0....7"
3. At the top gears ("lotus_evija_gear_inline0....7") set "$base: Vehicle.v_sport1_quadra_turbo_r_inline10...17" instead "$base: Vehicle.VehicleEngineData_4_SportPlus_inline0...7 "
I'm using Dreampunk and everything's good here. Gotta say, this car is one of the best for cyberpunk 2077 XD https://www.youtube.com/watch?v=Uozg_-rEkPA
This mod looks awesome & I'm looking forward to driving around Night City xx How do I get the car without having to install the dealer? I haven't booted up the game yet cos I'll be recording & don't wanna be running around trying to find the car xx
In the Description of the mod, scroll down and copy that whole code into the CET command console inside the game and press enter. Then call the car like any other car through the call menu
Your mod is technically very impressive — I want to emphasize that right from the start. Still, there’s one aspect I view critically: you're modifying global settings, particularly the fov, which really shouldn't be treated as a vehicle-specific parameter. The FOV affects the entire game world and shouldn't be changed by a single vehicle mod.
Additionally, your fix for auto-centering (lockedCamera) alters another global behavior. By default, this value is set to False, which is the correct setting for the vast majority of players. You’ve set it to True, presumably because a single user reported that their custom camera behavior stopped working with your mod. While that’s a kind and well-meant response, it ultimately causes problems for 99% of other users, for whom it previously worked fine.
The reason this issue exists at all has to do with how TweakXL processes overrides like Camera.VehicleTPP_DefaultParams. As soon as your mod sets fov through this record, the entire record gets copied to something like Camera.VehicleTPP_DefaultParams$SOMETHING and is then used for your vehicle. As a result, lockedCamera is reset to its default value (False), regardless of what the user might have customized elsewhere. Any changes users made — either through the game or other mods — are ignored, because your vehicle ends up using its own private copy of the parameter set.
This means: anyone who has customized their camera behavior loses those settings when using your vehicle. On the other hand, your new “fix” now forces all other users to have a freely rotating camera, even if they never asked for it.
Unfortunately, TweakXL doesn’t offer an elegant solution to this problem, since tweaks are applied before the game even starts, and can only work with the values available at that point. The most reasonable approach would probably be to offer multiple versions of your mod: a main file that avoids any global interference, and optional versions with customized Tweak YAMLs for those who explicitly want that behavior.
I'm not saying any of this to tear down your work — quite the opposite. I find your approach and effort genuinely interesting. My goal is simply to highlight the technical implications behind the scenes, and why your well-intentioned fix unintentionally creates new issues.
If any of this sounds harsh, that’s not my intention. I truly hope this feedback is helpful to you.
I’ve created a mod to optimize vehicle camera settings. What you’ve done here actually had a positive side effect for me — it helped me account for issues like this in my own mod, making it more solid and reliable. So I don’t really need to point these things out, because my mod already handles them and they’re no longer a problem on my end. So, thanks for that, in any case. That said, I'd recommend addressing it soon, since most users won’t leave feedback — they’ll just uninstall if something doesn’t work as expected.
The fov and camera position change that is defined in the evija yaml ONLY applies to my car and not to any other car in the game since these changes are made under my car's vehicle record. My intention was to override users' camera settings with the yaml because I want everyone to experience the car and view it how I think is best. All other cars are unaffected by the evija yaml.
The lockedCamera change to disable the camera auto centering was NOT made to accomodate the very few people that have a custom camera mod. By default, the camera reset time is at like 2 seconds which meant that every 2 secs the camera reset to where you couldn't see the road with my car specifically. I didn't experience this in my game because I had the reset time at 10 seconds and since I move the camera often when driving to look around, the camera never reset for me which is why I wasn't aware of this problem many people had.
Here's 2 screenshots with the close camera on the evija and vanilla quadra turbo. The custom fov in the evija yaml only applies to my car as the image is more zoomed out in the quadra. Same with the custom camera position which only applies to the evija.
Thank you for your response and explanations. I’m well aware that the settings apply exclusively to your vehicle — in fact, I even pointed that out myself and explained in detail how it works, why that happens, and why I personally think it's a bad idea to offer it as the only version. That's all. It's entirely up to you what you do with this information.
Morpheus9436 I don't know how it behaves in your game, but here it is behaving like this! It really sucks to drive the car with the camera so low! That's why everyone complains, and the camera doesn't stay fixed using the Better Camera Auto Mod! I made a video to show how it is here for me and I believe that whoever is complaining is facing the same thing!
50 comments
Update ver. 1.1: Improved the damaged appearance of the car
New Update ver. 1.2: Fixed the annoying camera auto centering
If you go into Cyperpunk 2077/r6/tweaks/lotus_evija/lotus_evija.yaml and open the yaml file, you can delete 'tppCameraPresets' and then you will have the vanilla/original camera presets.
You can also delete 'tppCameraParams' to make the TPP camera fov the same as in vanilla cars
Just make sure you keep the syntax of everything else the same as it was when you delete something or else the car wont spawn in game
Other than that, your work looks great.
However, you can change the camera position to your liking. If you go into Cyperpunk 2077/r6/tweaks/lotus_evija/lotus_evija.yaml you can open the yaml file and increase the y value in the evija camera presets which are located at the top of the file under the gear_inline 7 !
I have to ask tho, in your lotus_evija.yaml file, vehEngineData is not put under Vehicle.lotus_evija which might cause the gearing not to work?
I tried to make the car gearless by editing said file and putting vehEngineData under Vehicle.lotus_evija and removing the gear, but I haven't had any luck.
Would you mind giving some clarity on this?
I have minimal experience in modding, so please forgive me if there's a misunderstanding
2. In "gears" list (under "vehEngineData") replace "- !remove Vehicle.VehicleEngineData_4_SportPlus_inline0....7" to "- !remove Vehicle.VehicleEngineData_4_SuperSport_inline0....7"
3. At the top gears ("lotus_evija_gear_inline0....7") set "$base: Vehicle.v_sport1_quadra_turbo_r_inline10...17" instead "$base: Vehicle.VehicleEngineData_4_SportPlus_inline0...7 "
Then gears works.
Additionally, your fix for auto-centering (lockedCamera) alters another global behavior. By default, this value is set to False, which is the correct setting for the vast majority of players. You’ve set it to True, presumably because a single user reported that their custom camera behavior stopped working with your mod. While that’s a kind and well-meant response, it ultimately causes problems for 99% of other users, for whom it previously worked fine.
The reason this issue exists at all has to do with how TweakXL processes overrides like Camera.VehicleTPP_DefaultParams. As soon as your mod sets fov through this record, the entire record gets copied to something like Camera.VehicleTPP_DefaultParams$SOMETHING and is then used for your vehicle. As a result, lockedCamera is reset to its default value (False), regardless of what the user might have customized elsewhere. Any changes users made — either through the game or other mods — are ignored, because your vehicle ends up using its own private copy of the parameter set.
This means: anyone who has customized their camera behavior loses those settings when using your vehicle. On the other hand, your new “fix” now forces all other users to have a freely rotating camera, even if they never asked for it.
Unfortunately, TweakXL doesn’t offer an elegant solution to this problem, since tweaks are applied before the game even starts, and can only work with the values available at that point. The most reasonable approach would probably be to offer multiple versions of your mod: a main file that avoids any global interference, and optional versions with customized Tweak YAMLs for those who explicitly want that behavior.
I'm not saying any of this to tear down your work — quite the opposite. I find your approach and effort genuinely interesting. My goal is simply to highlight the technical implications behind the scenes, and why your well-intentioned fix unintentionally creates new issues.
If any of this sounds harsh, that’s not my intention. I truly hope this feedback is helpful to you.
I’ve created a mod to optimize vehicle camera settings. What you’ve done here actually had a positive side effect for me — it helped me account for issues like this in my own mod, making it more solid and reliable. So I don’t really need to point these things out, because my mod already handles them and they’re no longer a problem on my end. So, thanks for that, in any case. That said, I'd recommend addressing it soon, since most users won’t leave feedback — they’ll just uninstall if something doesn’t work as expected.
The fov and camera position change that is defined in the evija yaml ONLY applies to my car and not to any other car in the game since these changes are made under my car's vehicle record. My intention was to override users' camera settings with the yaml because I want everyone to experience the car and view it how I think is best. All other cars are unaffected by the evija yaml.
The lockedCamera change to disable the camera auto centering was NOT made to accomodate the very few people that have a custom camera mod. By default, the camera reset time is at like 2 seconds which meant that every 2 secs the camera reset to where you couldn't see the road with my car specifically. I didn't experience this in my game because I had the reset time at 10 seconds and since I move the camera often when driving to look around, the camera never reset for me which is why I wasn't aware of this problem many people had.
Here's 2 screenshots with the close camera on the evija and vanilla quadra turbo. The custom fov in the evija yaml only applies to my car as the image is more zoomed out in the quadra. Same with the custom camera position which only applies to the evija.
I made a video to show how it is here for me and I believe that whoever is complaining is facing the same thing!
Sample Video