FaR2sToNeD

Close to a year later it dawned on me while trying to fix a separate issue in FO3... The Z-fighting issue was addressed in Skyrim by Gopher in one of his . He mentions a lot of different things to tweak but the main thing that worked for me on the Fallout engine was 'fNearDistance='. I've been playing with the variable and anything above 10 seems to cause clipping with arms/weapons in first person mode but you can find a balance eventually with a few attempts. So I guess this is solved. Open FALLOUT.INI and search for 'fNearDistance=', change the value and test.

I only noticed this today, I really hope I'm not too late to apply. I've never seen a position so well suited to me in all honesty, it's more or less what I do now but comprised of something I actually love. Application sent. Good luck to everyone :)

That's a good point actually, could simply be faulty hardware. To me it looks like a draw distance glitch, or as RoyBatterian said, a faulty card. EDIT: Ah lol posted at the same time, well we can check your ini files and make sure you have all the tools required. Firstly, do you have/have you used... -NVSE -BOSS -FNVEdit -ArchiveInvalidation Invalidated Unfortunately if you don't already have FNVEdit, it's been taken down from the Nexus :/ Use those three tools if you haven't already (and run FNVEdit to check for errors if you have it) and if that doesn't work/you tried it before then post your ini files and I'll see if I can spot any errors.

Have you tried running FOMM/NMM as an administrator?

I think you'd have more luck asking this in the Feedback, suggestions and questions forum since it's probably not a problem specific to New Vegas. A lot more people check those forums too since they're about the Nexus sites in general and not one specific game.

Will need a little more information sorry. Do you have any graphical mods installed? Have you made any changes to the ini files? Does it happen everywhere or in a specific location? The more information the better :)

Strange, the standalone wont work without the binaries from the ENBdev website so I always assumed it was simply a way to get endorsements on here while visitors to his own site.

haha that was fun to read :P But for realsies, do you have any follower mods installed or is it a vanilla issue?

Haha yea tbh it's always hard for me to change from NMM when I go back for FO3/NV, perhaps the stability has improved since my last try. Regarding the screenshot, those elements will be controlled by your DarnUI so something must have overwritten it. Again, trying and testing is the best but if you can live with it I wouldn't bother lol. Plus, looks kinda cool, like an actual visor HUD. If you make it all activate at specific moments with iHUD it could be like a visor overlay or ocular implants ^^

Haha you're welcome, I've literally just got a PC good enough to mess with ugrids so it was a happy coincidence I noticed this thread. Glad everything's working, fingers crossed it continues! Kudos for letting me know it worked ^^

Ah, well I'm glad it kinda worked lol. What brackets do you mean btw? Can you post a screenshot? EDIT: I noticed you're also using NMM? I've heard a lot of issues surrounding that with FO3/NV. If you can be bothered, you might want to make the change to FOMM as it's designed solely for NV and FO3. To use, just download a mod manually, select "Package Manager" in FOMM then "Add FOMOD" then activate. Not as pretty as NMM but better for NV.

Haha yea tbh if in doubt, that's the best and easiest way :) Glad it's sorted for you.

Well first download the Ini File Editor so you can revert any changes you make (such an amazing tool, don't know why it's not more popular), just load the FalloutPrefs.ini in the editor and allow it to make a backup. Each change you make will be highlighted so you can 1 click restore after testing. Here's a screenshot of mine so you can see what I mean... I personally change both FalloutPrefs.ini and Fallout.ini to make sure there's no conflicts. To answer, from what I'm aware iPreloadSizeLimit is the amount of memory loaded at any one time, with higher ugrid values it requires higher amounts of memory to process the information, while uExterior Cell Buffer relates to how many cells are loaded into the available memory (the iPreLoadSizeLimit). The TweakGuide.com Fallout 3 section explains it well, just scroll down a little to find... A lot of people with a lot more knowledge than me have been tampering with ugrids and the related variables since Oblivion so I'm pretty sure they're correct. Not sure however if it will fix the deathclaw issue.

Yea that's what I meant, that was a much easier way of explaining it xD It could well be those variables, the reason behind is explained here but I'm not sure what problems are actually caused by not changing them. Perhaps deathclaws in Goodsprings is one of them? ^^

Well it appears to be an offical bug (scroll down to the bottom). Perhaps it's one of the many things fixed by the yukichiagi unofficial patch? EDIT: According to the changelog all they did with the forecaster was... Forecaster - You will always have the option to exit conversation with him via the "On second thought, maybe another time" option. Might not be a fix out there for this one sorry :/

Hmm ok lets try another approach... 1. Uninstall all hud mods (except darn, we can just overwrite that). 2. Delete aHUD and iHUD and install oHUD instead (it combines them all into one esp). 3. Install THIS version of DarnUI manually. 4. Re-install The Mod Configuration Menu. 5. Re-Install uHUD. Obviously overwrite everything each time, the key to making all the UI mods work together is the order they're installed in. From my memory that would be the best order to ensure the correct files are overwritten. Let me know :smile: EDIT: Forgot about this too, make sure bShowQuestMarkers=1 is in your FalloutPrefs.ini.

You're both lacking Unified HUD Project which I'd heavily recommend, you should try reinstalling darnui before installing the UHP but also there's some serious issues in your load orders too. @niciuffo You're missing compatibility patches for EVE/WMX and Project Nevada which can be found HERE. As for your radar, try UHP linked above and see if it helps, if not post back with your ini files. @Braveroli Below are conflicting mods which you have to correct, you only need the ones highlighted in green as you have all the DLC. Having all active will cause a lot of problems. Also, you have iHud installed which by default hides the compass. The default key is "i" to toggle it on and off, if you press ESC and go to the mod configuration menu however you can change the setting in iHud so the compass is always on.

Nobody? :(

The only other thing I can suggest is opening the cell in GECK and seeing if there's some kind of navmesh error or something causing it to happen. Sorry :/

Hmm, I remember an issue like this a while ago. Try editing the following values in the FalloutPrefs.ini file. Also unplug any controllers you might have attached.

Go to C:\Documents\My Games\FalloutNV, are there two ini files there? If not, I assume you installed all the mods before running the game? Deactivate ALL mods (except official DLC) and launch the game until the start menu then exit. This will create the needed ini files. Reload FOMM, activate the mods and try again.

Just to throw my 2p in the mix, have you calibrated the other variables to compensate the change in ugrids? Also, have you saved after changing the ugrid variable more than once? ie: Changed from 5 to 7, saved, changed again and saved again? This corrupts saves and probably won't be fixable. There are a number of variables to change the view distance without changing ugrids, however you can't change ugrids on that save now anyway as mentioned above so I'm not sure how that would help. If you reload a save that had the original 5 value then these ini commands are what you're looking for (my personal current settings)...

There is this on WineHQ but I'm not a member so have no idea how to download and can't verify it works.

You could try Xpadder however I don't use a game pad so have no idea if it will work sorry. Good luck ^^

Your best options really are the following... -NVSR -ENBoost ENBoost however might require you to not use an ENB, and in my experience actually caused me more issues than it fixed for NV however the NVSR is an amazing thing. Also have you tried messing with your ini files? There's a lot of possible performance tweaks to be had if not.