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.
This mod is completely broken. It's beyond me why everyone uses this, and why it's even included in Wabbajacks in the first place.
Cinematic kill cams trigger, this mod glitches out and resets FOV. After VATS, at random times, you are stuck in a grey void until you restart the game (reloading a save doesn't work).
At completely random times, zooming in and out will be broken too: for some reason, the weapon itself doesn't do the iron sights animation, and zooming itself will be instant, instead of the slow zoom in. I have had Scope Scissoring get enabled for no reason as well, despite me setting it to zero.
Before anyone claims it's my load order being messed up: all those bugs happened in multiple load orders I've had, also after following Viva New Vegas to the letter, AND in popular Wabbajacks that otherwise work perfectly. I'm currently running Begin Again Wabbajack, and every glitch I've mentioned happened, in an hour of playtime. And YES, I have tried the Stewie Tweaks "Disable zooming while holstered" fix and setting "bVATSHipFire = 0". It's a fix for one problem, but the others remain.
It's much more reliable to simply edit world FOV, weapon FOV and Pip-boy FOV by changing those in "FalloutCustom.ini". Not to mention this will take up an ESP slot as well, which is starting to get out of fashion nowadays with ESPless this, ESPless that. There's even HUD mods that are completely ESPless, yet this mod only messes with FOV and still takes an ESP? Plus, changing FOV is a one time thing, it's not like I need an MCM menu for "convenience", since I'm not gonna dynamically change FOV or whatever. I change it once, done. Rather do INI edits than have this cluttering the load order. I'm salty because EVERYONE recommends this, when it's clearly useless, and keeps appearing in Wabbajacks.
Your broken load order is not the fault of this mod. It's been here for getting on 10 years and has never failed to work properly for me or thousands of other users.
If it's not compatible with the set of mods or whatever badly curated mod pack you use, that's YOUR problem not this mods problem.
It's clearly stated the mod does NOT work properly with kill cams and it never did. I never intended it to, because they are awful and poorly implemented in the base game.
Bitching about stuff is useless, so why bother. No one MAKES you use any mod. IF they don't work for you, MOVE ALONG.
Dude, its people like you that make modders pissed off. I've been using this mod with multiple setups running 400+ mod load orders and never once had an issue with it. If your trying to help address potential bugs, try wording it a little more friendly next time. You sound like a total ass. Thank you for the hard work RoyBatterian.
This mod straight up stopped working for me upon using VATS and I cannot for the life of me get it working again. It was working perfectly fine until I used VATS, and everything I've tried (reinstalling, changing Stewie's Tweaks settings, etc.) didn't work.
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.
1036 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 :)
Cinematic kill cams trigger, this mod glitches out and resets FOV. After VATS, at random times, you are stuck in a grey void until you restart the game (reloading a save doesn't work).
At completely random times, zooming in and out will be broken too: for some reason, the weapon itself doesn't do the iron sights animation, and zooming itself will be instant, instead of the slow zoom in. I have had Scope Scissoring get enabled for no reason as well, despite me setting it to zero.
Before anyone claims it's my load order being messed up: all those bugs happened in multiple load orders I've had, also after following Viva New Vegas to the letter, AND in popular Wabbajacks that otherwise work perfectly. I'm currently running Begin Again Wabbajack, and every glitch I've mentioned happened, in an hour of playtime. And YES, I have tried the Stewie Tweaks "Disable zooming while holstered" fix and setting "bVATSHipFire = 0". It's a fix for one problem, but the others remain.
It's much more reliable to simply edit world FOV, weapon FOV and Pip-boy FOV by changing those in "FalloutCustom.ini". Not to mention this will take up an ESP slot as well, which is starting to get out of fashion nowadays with ESPless this, ESPless that. There's even HUD mods that are completely ESPless, yet this mod only messes with FOV and still takes an ESP? Plus, changing FOV is a one time thing, it's not like I need an MCM menu for "convenience", since I'm not gonna dynamically change FOV or whatever. I change it once, done. Rather do INI edits than have this cluttering the load order. I'm salty because EVERYONE recommends this, when it's clearly useless, and keeps appearing in Wabbajacks.
Don't use this.
If it's not compatible with the set of mods or whatever badly curated mod pack you use, that's YOUR problem not this mods problem.
It's clearly stated the mod does NOT work properly with kill cams and it never did. I never intended it to, because they are awful and poorly implemented in the base game.
Bitching about stuff is useless, so why bother. No one MAKES you use any mod. IF they don't work for you, MOVE ALONG.
It was working perfectly fine until I used VATS, and everything I've tried (reinstalling, changing Stewie's Tweaks settings, etc.) didn't work.
Edit: It's Near Distance Flickering, which I adjusted to help with first person clipping. It affects LOD apparently.
EDIT: This stopped happening and now it works fine, no idea what happened.