Fallout 4

Fallout 4

View Stats:
hoe to fix weapon debris with the RTX card?
i kept getting crashes when i enable weapon debris, i heard its due to the RTX 2080ti, is there a way around this to enable the weapon debris with the RTX 2080ti i own?
< >
Showing 1-15 of 75 comments
Lucifer69 Mar 25, 2019 @ 6:32pm 
Why do you need it on? It allows you to see some rocks flying when shooting walls, and what not, so what?

Weapon debris tends to cause grief with all cards, not just the RTX series. It's just like Godrays. Either disable them or set them to low as they don't much for the cost.

Edit: As to why weapon debris is an issue is because it causes a memory leak, I believe. Testing it shouldn't be too hard if you could monitor usage. There's no fix if it's true so trying to figure out why is beyond pointless.
Last edited by Lucifer69; Aug 5, 2019 @ 7:18am
Spec_Ops_Ape Mar 25, 2019 @ 9:42pm 
Petition Bethesda to update Nvidia's Flex software to the latest version.
Originally posted by Saif:
i kept getting crashes when i enable weapon debris, i heard its due to the RTX 2080ti, is there a way around this to enable the weapon debris with the RTX 2080ti i own?
Swapping to a GTX is the only way.
hawkeye Mar 26, 2019 @ 12:26am 
My rtx2070 is now in my word processing pc.
lambo4debo2 Aug 4, 2019 @ 11:38pm 
I have a nvidia gtx 1650, it can run everything in ultra but I do keep the shadow quality lower for performance purposes. Anyhow what I want to get at is it's more than capable of weapon debris ultra, yet here I am stating if I do so much as turn it on... it ♥♥♥♥♥♥♥ crashes... severely disappointed. I've checked into this problem for days now and the only thing I can come up with is the physx driver has an issue and I'm not the only one... I really hope this gets fixed or somebody finds a way around it.. hopefully the physx driver will have an update that fixes it. (HIGHLY UNLIKELY)
It's possible they will update it. I went through the same thing with my GeForce 1070. Instead of a crash some of us got fps in the teens.

They (nvidia??) did end up fixing it somehow and after a couple years I had a fully functional weapon debris.
Jush Aug 11, 2019 @ 4:48am 
No. The only solution is to keep complaining until it is fixed.

And people like you are disgusting for enabling lazy devs.

Username checks out.
Originally posted by Lucifer69:
It's been an issue since day one Mr. Snowflakes. NvFlex is not provided by the PhysX runtime, it is stand alone. Nvidia can not update a library somewhere and make FO4 work with Turing. The only solution is to stop posting on old threads [that are asking for help] complaining about it, and just deal with it.

You'll also see threads claiming running an older card as the PhysX slave will fix crashes. Flex doesn't follow the PhysX setting, it gets disabled when you choose an alternate chip; however, the implementation of Flex by Bethesda is hardware dependent - the API supports hardware agnostic code, but Bethesda didn't use it.

Only Bethesda can fix it. They have a website, might I direct your complaints there.

lol if you're that guy from the damn Nvidia forums. This is clearly a solution to be solved by Nvidia, not Bethesda. New cards, drivers, and architecture should be able to work with 4 year-old games.

As for your attitude, you're really coming across like you have Asperger's. Go for a run outside or something, kid.
Lucifer69 Sep 6, 2019 @ 4:38pm 
Should be able to is irrelevant. Again, this has nothing to do with Nvidia. Crying about it on a forum that they don't care about won't do anything.
It actually has everything to do with NVidia since they developed Flex and the cards that are having problems with this four-year-old game. Unless you not only work for Nvidia but also developed the ♥♥♥♥♥♥♥ software that is ♥♥♥♥♥♥♥♥ the bed, you should have no reason to be so obsessed with denying reality. It is a simple fact that Nvidia needs to address this problem.
tulle040657 Sep 8, 2019 @ 10:43am 
Originally posted by Lucifer69:
Should be able to is irrelevant. Again, this has nothing to do with Nvidia. Crying about it on a forum that they don't care about won't do anything.
So it worked fine until the release of the 16xx and 20xx cards and somehow it is the fault of a game written before they were made?

You do know it still works fine on their older cards, right?
Lucifer69 Sep 8, 2019 @ 2:28pm 
It's never worked. Not perfectly. Pascal is a very close refresh of Maxwell. Close enough that no update was really needed to Flex to keep it fairly stable. Turing is a totally different kind of monster. Bethesda must update Flex.

Nvidia cannot magically update a library somewhere and fix it. They can release an updated Flex, and Bethesda can upload it, if they wanted to. This would cost money, and dev time. This is money spent on fewer than 1% of the game population. This would also force another .exe update which would break F4SE, until it's updated.

Too many arm chair experts.
tulle040657 Sep 8, 2019 @ 2:42pm 
Originally posted by Lucifer69:
It's never worked. Not perfectly. Pascal is a very close refresh of Maxwell. Close enough that no update was really needed to Flex to keep it fairly stable. Turing is a totally different kind of monster. Bethesda must update Flex.

Nvidia cannot magically update a library somewhere and fix it. They can release an updated Flex, and Bethesda can upload it, if they wanted to. This would cost money, and dev time. This is money spent on fewer than 1% of the game population. This would also force another .exe update which would break F4SE, until it's updated.

Too many arm chair experts.
Not providing backward compatibility is bad design, sorry

-- from an armchair expert with 35 years embedded software experience
Last edited by tulle040657; Sep 8, 2019 @ 2:43pm
Lucifer69 Sep 8, 2019 @ 2:50pm 
I'd like the hear your thoughts on DirectX then. It's no different in that regard, except it's hard locked.

For a so called embedded software engineer, you sure don't know your stuff. I'd trust Best Buy Geek Squad before you. Lmao.
Last edited by Lucifer69; Sep 8, 2019 @ 2:50pm
tulle040657 Sep 8, 2019 @ 3:01pm 
Originally posted by Lucifer69:
I'd like the hear your thoughts on DirectX then. It's no different in that regard, except it's hard locked.

For a so called embedded software engineer, you sure don't know your stuff. I'd trust Best Buy Geek Squad before you. Lmao.

An app developer should never have to recompile their app because you made hardware changes (i.e. dirextx9 works fine for all video cards my directx 9 app needs no changes to work)

There is a reason that the concept of drivers and dlls were developed, so new features could be added without breaking older programs
< >
Showing 1-15 of 75 comments
Per page: 1530 50

Date Posted: Mar 25, 2019 @ 6:06pm
Posts: 75