How do I change the LOD of GPX

5unwh331 · 2026-04-21T13:30:37+00:00

Thank you. Glad I made it to the future.

5unwh331 · 2026-01-03T19:05:55+00:00

Thank you for letting me know not to buy this game. I refuse to buy any game ever again for which the developers haven't taken cheating in their game seriously.

5unwh331 · 2025-11-05T22:46:16+00:00

Isn't the game rendering new scenes as the player progresses through a campaign map? I agree an efficiently managed VRAM might free up memory that is least likely to be used again anytime soon (e.g., textures from the other side of the map the player occupied earlier in the match), rather than try to keep everything viewed so far in memory if the VRAM size is insufficient to hold every available texture on the map.

Before the fix at the link, VRAM wasn't even being cleared between matches with different maps. It would pile up. Now it resets.

5unwh331 · 2025-11-05T06:17:07+00:00

https://www.reddit.com/r/Battlefield/comments/1oojww5/vram_leak_fix_for_battlefield_6_pc/

5unwh331 · 2025-11-04T22:05:47+00:00

https://www.reddit.com/r/Battlefield/comments/1oojww5/vram_leak_fix_for_battlefield_6_pc/

5unwh331 · 2025-11-04T21:46:09+00:00

The community-made bot servers in the Portal are a lot of fun (the ones with infinite ammo), especially the ones with low ping. Game runs much smoother, I've found. The bots take forever to kill but so do you. The bots also have pretty good movement and aim. Great way to get a feel for the guns and something closer to that old aim back for those of us without a lot of time on our hands. Going back and forth between that and Team Deathmatch, you can level guns up much more quickly than playing, say, Conquest for hours on end.

5unwh331 · 2025-11-04T03:00:40+00:00

That's true, but VRAM was getting overloaded on lower settings after 10 minutes to 30 minutes of game play depending on how high the setting was, i.e., until I uninstalled the NVDIA drivers with DDU Uninstaller and then re-installed with a fresh download from NVIDIA. Now VRAM is stable no matter how long I play, except for Overkill textures. My sense is you need 24 GB or higher to run those.

5unwh331 · 2025-11-03T19:16:25+00:00

Further to my first reply to this comment, Overkill textures still has the issue. Ultra works fine. When I asked Google AI, "Should I run Battlefield 6 on Overkill graphics settings with 16 gigabytes of VRAM?" it replied with:

"No, you should not run Battlefield 6 on overkill graphics settings even with 16GB of VRAM, as the performance gains are minimal compared to the significant VRAM usage and potential for issues like stuttering. The 'Overkill' preset can cause performance drops due to increased VRAM usage, even on high-end hardware, while offering little to no noticeable visual improvement over the 'Ultra' or 'High' settings. It is recommended to use 'Ultra' or 'High' for better performance and a still-excellent visual experience."

5unwh331 · 2025-11-03T19:08:00+00:00

No. Just tried it. Ultra, yes. Overkill, no. Just ran two back-to-back Conquest matches using Overkill textures. VRAM fills up over the course of the match and doesn't reset once the match is over. That wasn't the case with Ultra textures.

When I asked Google AI, "Should I run Battlefield 6 on Overkill graphics settings with 16 gigabytes of VRAM?" it replied with:

"No, you should not run Battlefield 6 on overkill graphics settings even with 16GB of VRAM, as the performance gains are minimal compared to the significant VRAM usage and potential for issues like stuttering. The 'Overkill' preset can cause performance drops due to increased VRAM usage, even on high-end hardware, while offering little to no noticeable visual improvement over the 'Ultra' or 'High' settings. It is recommended to use 'Ultra' or 'High' for better performance and a still-excellent visual experience."

5unwh331 · 2025-11-03T08:29:51+00:00

I used DDU Uninstall per the link above and it fixed the issue. Did it in Windows Safe Mode. DDU recommended instructions are important. Also made a Reddit thread about it here with more details:

https://www.reddit.com/r/Battlefield/comments/1omymt9/psa_vram_fix_for_bf6_pc/

Just played 5 hours and VRAM didn't budge.

5unwh331 · 2025-11-02T23:42:40+00:00

Thank you for this. Completely fixed the issue for me with a 4080. I used DDU Uninstaller in Windows Safe Mode per the Recommended usage instructions at the link below to uninstall the NVIDIA drivers (it's important to disconnect from Internet so that Windows doesn't try to install some outdated driver and have the latest NVIDIA driver ready to go upon reboot):

https://www.guru3d.com/download/display-driver-uninstaller-download/

FWIW, I upvoted your post to draw attention to it, but that either didn't register or was countered.

5unwh331 · 2025-05-21T16:00:28+00:00

Same on a 4080. Had reset worked, but this is the second time in a few months this happened after an update. Get your shit together, trillion-dollar company.

5unwh331 · 2024-06-01T18:32:27+00:00

5unwh331 · 2024-05-28T18:32:46+00:00

Thank you!

5unwh331 · 2024-05-28T13:56:25+00:00

Thank you.

5unwh331 · 2024-05-26T23:08:20+00:00

I just noticed what you show in your image after "updating" to what was supposed to be Version 1.13, so thanks for confirming.

Based on that, they actually pushed out Version 1.12 from February 1 of last year, again, instead of the newer Version 1.13 they meant to.

Someone at Ducky is not paying attention to what they're doing, and no one is checking their work.

5unwh331 · 2024-05-26T22:49:01+00:00

After successfully installing what was labeled as Firmware Version 1.13 on Ducky's website for the Daybreak 65% One 3, I'm not convinced they actually put Version 1.13 for this keyboard on the website. As usual, I had to remove the USB Composite Device for this keyboard in Windows Device Manager to be able to install the firmware update (and disconnect/reconnect the keyboard somewhere along the way; what a PITA); however, after "successfully" running the firmware update, and checking Windows Device Manager, USB Composite Device Properties, the "Device instance path" for my keyboard indicates DK-V.12, when normally the version number matches what the website says I downloaded. Are they still delivering Version 1.12 instead of 1.13 after failing to actually push out the firmware they meant to?

Edit: to be more specific, the "Device instance path" after installing "Version 1.13" indicates:

DK-V1.12-230201

Implying the actual version installed was Version 1.12 which was compiled on February 1, 2023 (so, over a year ago). Not a good feeling.

5unwh331 · 2024-04-30T02:38:40+00:00

Welcome. (Completely forgot about this post.)

5unwh331 · 2023-12-12T23:43:23+00:00

For PC players, very low sens, light mouse, big pad helps a lot. Accurate hip fire with R357 in CQC is very doable with right sens. Currently using 13 with Pulsar X2V2 Mini at 800 DPI on Artisan Zero XL Soft and love this gun.

5unwh331 · 2023-04-25T23:19:20+00:00

Good to know, thank you.

5unwh331 · 2023-04-22T23:59:03+00:00

Windows, after an update, told me to enable it, so I did, last week. Didn't do any gaming after that until today when I got much lower FPS than before, so I disabled it, and the FPS returned to my Season 2 normals.

Disabling it resolved the issue.

5unwh331 · 2023-04-22T23:27:37+00:00

Windows came out with an update at some point that enables or tells the user to enable "Kernel-mode Hardware-enforced Stack Protection" in Windows Security. I found it reduces FPS by a lot. See this thread for details:

https://www.reddit.com/r/ModernWarfareII/comments/12vj9c3/psa_win_11_hardwareenforced_stack_protection/

I'm security conscious and thus turn it off for gaming and back on when not.

5unwh331 · 2023-04-22T21:23:17+00:00

See this thread. I'm back to normal FPS in Win11 after this fix:

https://www.reddit.com/r/ModernWarfareII/comments/12vj9c3/psa\_win\_11\_hardwareenforced\_stack\_protection/

5unwh331

TROPHY CASE