This mod is now in its final form, unless some bug is discovered.
This mod DOES NOT work correctly with Kill Cams. They are poorly implemented in the base game and also cause you to be killed because of loss of control and no way to abort them. I HIGHLY suggest disabling them. In Fallout 3 you had 90% damage resistance while in VATS/Kill Cams, you DO NOT in New Vegas. This was just another poorly thought out change by Obsidian that wasn't tested properly.
It does everything I would like it to do, and I will probably not add any new features to it from this point forward.
Thanks to everyone who tested it and made suggestions.
If the mod does not show up in MCM, you need to update MCM to bugfix 2. It does NOT work with the MCM that comes with PN either.
If you have an issue with things returning to default or an FOV of 0, do not edit your game ini files and make sure the game has sufficient permissions to write to the ini file MCM creates for the mod. IE, don't install your game in protected folders like Program Files. If you did you can run your game as admin to get around it at your own risk.
I had the same issue with the FOV resetting and after suffering for 1 hour, I found the culprit. It was the "Disable zooming while holstered" in lStewieAl's Tweaks. Hope this helps someone, back to shooting Fiend for me.
had high hopes for this mod, been following everyone's solutions in the comments. but having way too much trouble with fov resetting back to 0 over and over again. ended up uninstalling so i could just go back to playing the game at least
I disabled the fov slider in mod manager and went back to the .ini s#*! that wasn't working for me in the first place (change fov to to 90 and add a line saying fDefaultWorldFOV=85.0000 under [Display]). Did this to the ini in documents and the ini in the steam directory. This time though, I changed both files to not be read only. Booted game back up, fov still like 65. Closed game again, renabled this mod in mod manager thinking "f it, vats is for the weak." Lo and behold, my vats is currently working right. maybe it was the ini's being read only that messed it up? Maybe it was the line I added?
Does anyone know why anytime I exit vats or dialogue that it zooms back into my FOV very slowly? It didn't do that for so long and now I can't find a fix.
Having an issue where upon death the bNoWeaponZoom will change from 0 to 1. Resetting it in MCM will allowing zooming until switching the 3rd person or changing weapons. Restarting the game is the only way to fix it until the issue repeats itself upon death. Setting FOV slider to Read-Only dosen't help. Read on here the kill cams don't work with this mod so I disabled those. Does the player death cam cause an issue?
Encountering this as well. Disabled all other mods apart from this and MCM, dying and reloading a save causes the ironsight zoom to not work properly. The camera just snaps back and forth instead of the actual zoom effect, and this sometimes results in ironsights not zooming in at all. Rebooting the game is required to fix it.
Holy f*#@, that took so long to figure out. Thank you. So basically just set world fov 5 higher than whatever you want the player fov to be. For example, I made world fov 95 and player fov 90. What a strange bug...
Then what's the point of having the option to set player fov if setting it more than 5 apart from world fov is going to broke the game? It kind of defeats the purpose.
Try using the missile launcher with a world FOV 90 and player FOV 85...
Yup this fixed the issue for me too. Must be some weird quirk of the game itself or something. Either way you are a God for this one. The cinematic cameras work perfectly fine as long as the first person FOV is exactly 5 less than the third person FOV.
Just wanted to confirm that this finally fixed the FOV resetting after a cinematic killcam. I had none of the tweaks activated that everyone blamed as the culprits so I was chasing this down for a long time. I have my World FOV at 90 and my 1st person FOV at 85.
If you have weapon clipping issues at a higher FOV like with the missile launcher, I highly recommend using the mod Weapon Based Hands Clip Distance.
I had the same issue with the FOV resetting and after suffering for 1 hour, I found the culprit. It was the "Disable zooming while holstered" in lStewieAl's Tweaks. Hope this helps someone, back to shooting Fiend for me.
;disables zooming when aiming with a weapon holstered bDisableHolsteredWeaponFOVZoom = 1
No need to change the previous value, is the same.
BUT make sure your values in falloutcustom.ini match your values in FOVSlider.ini. This is what matters.
I was stuck with a strange textures or bodies stretched out in the map when i set the FOV every time i start a game. This .ini changes solve my problem!
I confirm this works for me too. After a cinematic shot/kill in VATS, my screen turned black and my fov slider values became zero. Same values in fov slider and falloutcustom solve this (only fDefaultWorldFOV и fDefault1stPersonFOV), in my case 90/70 - perfect for NVAO.
I built a new computer, installed windows 11, fresh installed NV and most of the other mods I use, it still works flawlessly for me.
There is an unknown conflict with someone else's mod and I couldn't tell you which. No one EVER posts their load order, so I can't even try to find it.
I wonder if there's a way to set near distance clipping for individual weapons. I need high distance for most of the melee animations but anything higher than 5 makes the 2 handed weapon animations clipped.
Using this mod does somehow cause my LOD to flicker more. Don't ask me how. Increasing FOV through the console does not cause the increase in Z-Fighting. This game never fails to surprise me. Edit: It's Near Distance Flickering, which I adjusted to help with first person clipping. It affects LOD apparently.
1055 comments
This mod DOES NOT work correctly with Kill Cams. They are poorly implemented in the base game and also cause you to be killed because of loss of control and no way to abort them. I HIGHLY suggest disabling them. In Fallout 3 you had 90% damage resistance while in VATS/Kill Cams, you DO NOT in New Vegas. This was just another poorly thought out change by Obsidian that wasn't tested properly.
It does everything I would like it to do, and I will probably not add any new features to it from this point forward.
Thanks to everyone who tested it and made suggestions.
If the mod does not show up in MCM, you need to update MCM to bugfix 2. It does NOT work with the MCM that comes with PN either.
If you have an issue with things returning to default or an FOV of 0, do not edit your game ini files and make sure the game has sufficient permissions to write to the ini file MCM creates for the mod. IE, don't install your game in protected folders like Program Files. If you did you can run your game as admin to get around it at your own risk.
EDIT: SO the cause of this issue was with Stewie's Tweaks. bVATSHipFire = 0 has fixed the issue for me :)
I disabled the fov slider in mod manager and went back to the .ini s#*! that wasn't working for me in the first place (change fov to to 90 and add a line saying fDefaultWorldFOV=85.0000 under [Display]). Did this to the ini in documents and the ini in the steam directory. This time though, I changed both files to not be read only. Booted game back up, fov still like 65. Closed game again, renabled this mod in mod manager thinking "f it, vats is for the weak." Lo and behold, my vats is currently working right. maybe it was the ini's being read only that messed it up? Maybe it was the line I added?
Try using the missile launcher with a world FOV 90 and player FOV 85...
For clarification; "FOV" in the ini settings refers to fDefaultWorldFOV and "player FOV" is fDefault1stPersonFOV.
Really weird but this was the solution for me.
Thank you Gamebryo, very cool.
If you have weapon clipping issues at a higher FOV like with the missile launcher, I highly recommend using the mod Weapon Based Hands Clip Distance.
;disables zooming when aiming with a weapon holstered
bDisableHolsteredWeaponFOVZoom = 1
No need to change the previous value, is the same.
BUT make sure your values in falloutcustom.ini match your values in FOVSlider.ini. This is what matters.
FOVSlider.ini:
[Display]
fDefaultWorldFOV=90.0000
fDefault1stPersonFOV=65.0000
fPipboy1stPersonFOV=40.0000
falloutcustom.ini:
[Display]
fDefaultFOV=90.0000
fDefaultWorldFOV=90.0000
fDefault1stPersonFOV=65.0000
fPipboy1stPersonFOV=40.0000
These are the settings that work for me.
This .ini changes solve my problem!
Thank you so much for sharing!
There is an unknown conflict with someone else's mod and I couldn't tell you which. No one EVER posts their load order, so I can't even try to find it.
Have fun.
Edit: It's Near Distance Flickering, which I adjusted to help with first person clipping. It affects LOD apparently.