LOD Problems

[dubiousintent]

If you say it isn't the same issue, then we need to start from a known staring point: vanilla, without any mods or INI tweaks. Then confirm if you still have the "blurry" view in the distance. That will tell us if it is basic to the game or something being added causing it.

 

Given your problem describing this issue, I'd like to see at least a screenshot of that "blurry" distance, and preferably something that indicates where something starts to "pop-in" (marking the beginning of "foreground"), so we both know what we are talking about.

 

I know it's boring debugging. But continuing to play a game you are trying to debug just adds confusion to the issue. Focus on one problem at a time. You should consider copying your "Data" folder, so you have one for "Data-Play" and "Data-Test". Then rename whichever to just "Data" for the appropriate purpose.

 

Quickly: Your MMR problem sounds like a conflict with another "radio" mod.

 

The "hands" glitch was known to happen with FO3 also; cause unknown. Switching weapons or 1st/3rd "person view" would fix them. Don't know if the console command "player.setscale 1" will have any effect but can't hurt to try.

 

If you are going to play modded games on the PC, then you need to get over your "technophobia". It's mostly a matter of learning terminology. Everyone starts out knowing nothing. Specific terms convey specific meanings which are often more complex ideas. If you don't understand what some instructions are trying to convey, then you have to take the time to lookup the terms you don't understand or ask someone about it. It's all out there on the web. If you can't follow instructions (either written or visual; and there is a role for both, often complimentary), then you are only going to create more of a mess instead of cleaning one up. It's an investment in enjoying games. It will become easier over time. If you can't make that investment, then stick to console games or vanilla and enjoy them for what they are.

 

Edit: Did you follow the STEP Guide ENBoost instructions? What confused you?

 

-Dubious-

Edited March 4, 2017 by dubiousintent

[Dubik123]

So today, I took another crack at installing ENBoost and actually done it correctly. However, my game now looks as if anisotropic filtering was off, even when it is on. In my terms, objects in the distance now have these sharp thin black lines around them. Taking a screenshot of the distance would be pointless, you would not see anything because everything looks so "sharp". As for the LOD generating slowly, it did not help.

 

However, it seems that ENBoost has completely messed up my game. After installation, I noticed a potentially game-breaking bug. I tried to take at least 5 screenshots but Steam did not save them. Argh... Let me try to explain it.

 

I could see objects like grass or palm trees through rocks. Also, the small radioactive pools littered across the ground were now covered with a green box until I stood on them. If this explanation is terribly unclear, I will try to launch the game, not through the 4GB Enabler, but through the default lancher and then take a screenshot.

 

Yes, the hands glitch also happens to me in Fallout 3 from time to time. Only reloading a save helps.

 

The MMR bug is 100% not caused by a mod. It has been happening since I bought the game about 3 years ago. I had absolutely no mods installed back then. I tried to install an expander for the station to see if it stabilizes the thing - no such luck. After the current installation, I, again, have no radio mods installed. This is also a purely vanilla thing.

 

If screenshots are really necessary, I will most likely have to reinstall the game again and wipe the slate clean, given how it is now all messed up with ENBoost and that I have the texture pack installed.

[dubiousintent]

The MMR problem has to be mod related as it is not occurring with other stations. If it was an underlying problem with your sound drivers it would affect all stations. Music normally starts a track and runs through the entire recording unless something interrupts it. The switching from a given sound track after ten seconds indicates a script is acting upon it. The vanilla script doesn't do that.

 

The transparency problem ("objects like grass or palm trees through rocks") is known to occur with ENB for some people. If you installed the full ENB Series (instead of just the ENBoost component), then the fix for that is simple: see the "Issue: ENB Transparency/Translucency problem" entry in "Troubleshooting". Note the settings for both the game and the video card required by ENB.

 

ENBoost "messed up" your game how? All it does is allocate some additional system memory to video rendering. That is all once the game has sent the meshes and textures to the video system. It's used for "overflow" that the card can't handle, but it is slower. But by all means remove it if it isn't helping.

 

Every time you respond you are reporting different symptoms. It's all very confusing as they are not consistent with any particular problem. Which is why I want to get to a known starting point (vanilla) and work through one problem at a time.

 

I want a screenshot because you can't have it both ways: the distance is "too blurry" or it's "too sharp". Again, we need to get a baseline of vanilla in order to identify what is going wrong by adding one thing at a time. If you can't get a decent "vanilla" then you certainly aren't going to have a decent modded game.

 

-Dubious-

[Dubik123]

So I reinstalled the game again to have a completely vanilla experience. The LOD issue still persists but I managed to record a short video of it. I don't think you will see what I mean, but it is worth a try.

 

 

I tried to aim the gun towards the road which was not yet generated, in case you're wondering.

 

Edit: This time, I reinstalled the game in English. Mojave Music Radio is now, for some reason, working properly. Perhaps a conflict with the Czech version?

Edited March 6, 2017 by Dubik123

[dubiousintent]

The video is a big help. I agree it is "blurry" even up close when you first start moving in the game. That is not normal for vanilla, so it appears to me to be an issue with your video card. (Which is why we needed to test in pure vanilla.) It seems to be rendering more slowly than expected. Certainly slower than my GTX 760, which also has only 4GB of VRAM. The road appearing as it does in the mid-ground is typical, though more noticeable due to the general slowness. It may be that you are not getting the full benefit of the onboard VRAM. If the card is still in warranty, I would speak with whomever sold it to you or contact the manufacturer and complain, providing the link to your video and explaining that is with an unmodded "vanilla" game. If you have any of the games used in "nVida's Benchmarks" a comparison test using the same benchmark program they use with those will help. The more games manifesting the same issue, the more it points to a card problem. Point out everything you see "wrong" with the rendering. "In-warranty" they will usually exchange it without problem but be sure you get them to issue an "RMA" (Return to Manufacturer Authorization") number first. The more detailed information you can provide, the easier it will be to get an RMA.

 

My initial suspicion is that it is clocked wrong, but I don't have that card and have never had occasion to dig into adjusting those settings for my own, and so have no idea what it should be. A Google search on "gtx 970 overclocking tutorial" turns up a number of articles and videos on how to do so safely. (The official GeForce forums says "Nvidia caps the amount you can adjust the voltage by a lot, so with a modern Nvidia it's not possible to kill it with adjusting voltage; even with 400 series cards (not sure how far back though).") As I know you are not "tech knowledgeable", this suggestion is really to find what the proper default values are, and determine if your card is not performing to spec. Those articles should tell you how to do that without risking damage to your card.

 

Otherwise, you need to find someone local who is familiar with hardware to help you.

 

The MMR issue does indeed appear to be a "regional language" implementation issue with Czech. You can raise the issue with your regional Steam support now that you can show it to be reproducible as both "vanilla" and language specific.

 

-Dubious-

[Dubik123]

I am stalling here. But for a reason.

I certainly am not going to mess around with clocking my GPU. I can barely install software - this is WAY out of my league.

My GPU is probably no longer in warranty...

 

However, what is worth noting is that the issue happened mid-playtrough back when I had my old AMD Radeon card... Switching the GPUs did not fix it. Does that somehow eliminate the possibility of the issue being tied to my current GPU?

[dubiousintent]

You are going to like the answer even less. That suggests the problem is with the motherboard's video subsystem. The only way to be sure (outside of a visit to a computer shop to run diagnostics) would be to try your GTX 970 card in another system (completely different hardware) and see if the same or similar symptoms carry over there.

 

-Dubious-

[Dubik123]

Great... That's another thing I probably won't be able to do...

 

If I do manage to take it to the shop, after they diagnose the problem, will they be able to fix it as well? And is it going to cost a fortune?

Can't really say I could do the other solutions either...

 

So... I guess that if I want to play New Vegas, I will have to live through these bugs, right?

[dubiousintent]

As for if you take it to a shop: no guarantees they can fix it. Motherboards are not something most shops can fix. (I don't know of any that even try.) They usually confirm and then offer to replace it because it's cheaper than the time it would take to chase down the fault before they can determine if it could be fixed. They may or may not be able to provide one that is compatible with the rest of your existing components. The closer your motherboard is to existing models, the more likely it is to be compatible. Old enough and you have to get a new CPU, CPU Cooler, RAM, and Power Supply as well. Hard drives and video card can usually transfer unless they are also too old for the current connection technologies.

 

Given we have already exhausted software tweaks, I'm afraid you are indeed stick with the problems, both in FNV and other games. At least, that is all the help I can give. Now you know you can't put off the need to start saving for a new system.

 

For future reference: business figures to replace a desktop computer every three years. A home owner needs to figure on every five years. Anything longer than that is a bonus. Unless you have money to throw away, buy the model just before this year's latest and greatest offering. It will be significantly discounted, and close enough in every respect you are unlikely to notice the difference. That will get you a significant upgrade in performance that will last until you are ready to replace it again.

 

Dust and heat are the enemies of electronics. Keep them in a stable temperature environment (as in "leave them running" with plenty of air circulation unless you are going to be away for a week or more; turning them off and then on over night causes heat stress which weakens soldered connections) and clear out the dust periodically.

 

-Dubious-

[Dubik123]

Alright well... I guess I will have to live with these bugs. On a brigher note, I can have an excuse for the rendering in NV and make up in my character's backstory that he is short-sighted :D

 

There are two things I don't understand from your reply. First off, why would the shop offer me a motherboard that is out of date with my current components? And what do you mean by "leave them running"? Should I not quit my PC?