Flickering/missing geometry in RE engine games

[runar-work]

NVIDIA Open GPU Kernel Modules Version

590.48.01

Please confirm this issue does not happen with the proprietary driver (of the same version). This issue tracker is only for bugs specific to the open kernel driver.

• I confirm that this does not happen with the proprietary driver package.

Operating System and Version

Arch Linux

Kernel Release

6.18.9-arch1-2 #1 SMP PREEMPT_DYNAMIC Mon, 09 Feb 2026 17:16:33 +0000 x86_64 GNU/Linux

Please confirm you are running a stable release kernel (e.g. not a -rc). We do not accept bug reports for unreleased kernels.

• I am running on a stable kernel release.

Hardware: GPU

GPU 0: NVIDIA GeForce GTX 1660 Ti (UUID: GPU-a8fb3a3a-9dd5-b430-1b78-cb1f1ecd6079)

Describe the bug

As first reported in this issue on the Proton tracker with RTX 5000, there's a problem with missing or flickering geometry in the Monster Hunter Stories 3 demo. I could reproduce the same issue on RTX 3070 in MHS3 and also with GTX 1660 Ti in MHS3, the Pragmata demo and Resident Evil Requiem.

On RTX 3070 I tested both 590.48.01 and 580.94.17 with the open kernel module in MHS3. On GTX 1660 Ti I could only test the 590 driver with the open module. I have not been able to reproduce this issue on GTX 1660 Ti with the proprietary module.

To Reproduce

I've been most easily able to reproduce this on the GTX 1660 Ti on the title screen in the Pragmata demo. In MHS3 it happens most quickly inside Azuria castle a few minutes into the demo. In Resident Evil Requiem it also happens within a few minutes after starting the game.

The common factor seems to be vsync disabled, low preset and 1080p to get a high framerate. On the RTX 3070 it's been more difficult to reproduce, so I haven't been able to reproduce the issue on the title screen in Pragmata there, but it still happens occasionally in MHS3.

Bug Incidence

Often

nvidia-bug-report.log.gz

nvidia-bug-report.log.gz

More Info

I haven't been able to capture this issue in RenderDoc, as any capture will replay normally afterwards. Adding extra barriers (graphics, pre-raster, pre-compute, post-compute) in vkd3d-proton also had no effect. VKD3D_CONFIG=breadcrumbs_sync also had no effect.

[ryzendew]

nvidia-bug-report.log.gz

same issue

you can watch here the entire game

[cameronbosch]

Hi, I'm the one of the people who originally reported this issue in Monster Hunter Stories 3 Twisted Reflection on the Proton GitHub, and I was the first (as far as I know) to get a good recording of the issue happening.

Here is a recording of the issue happening in the game. (Unfortunately, I couldn't use OBS Studio to do a screen capture because as soon as I entered the game, the frame rate and especially 1% lows were completely unusable, making the screen capturing method impossible, and this was despite using NVENC. This is why I did a free hand recording of my laptop's screen.)

Monster.Hunter.Stories.3.Twisted.Reflection.-.Serious.Graphical.Issues.mp4

[runar-work]

To clarify, this issue is not about vertex explosions. I've not seen any vertex explosions on the two GPUs I've tested on in any of the three games I mentioned. This is about geometry getting culled when it shouldn't be.

[alcortazzo]

nvidia-bug-report.log.gz

[inittux111]

nvidia-bug-report.log.gz

[ptr1337]

Think this should be maybe reported to the forum, since its likely an issue in the userspace utils and not the kernel module :)

[inittux111]

Think this should be maybe reported to the forum, since its likely an issue in the userspace utils and not the kernel module :)

It is my first time reporting something for Nvidia :) this seemed like the most logical place to do it was someone else had already. I also posted my bug report on the Nvidia forums in the topic about the 590 driver release but it was automatically hidden so I guess I have to wait until a mod approves my post.

[runar-work]

Yes, that other glitch is a known driver issue that should be fixed in the upcoming 595 release.

Since the missing geometry issue was initially reported on a laptop setup and I also tend to use a Raphael iGPU to drive the display, I also tested without it, but I could still reproduce the issue in MHS3 while using only the GTX 1660 Ti. For some reason I couldn't reproduce it on my initial attempt, but disabling shader caches (__GL_SHADER_DISK_CACHE=0 VKD3D_SHADER_CACHE_PATH=0) had no effect.