Cheeky Foveated DLSS 5 Neural Rendering with eye tracking now.

[Koziolek]

On 10/13/2026 at 4:32 PM, Dash,Polder said:

VectorXR layer should always be above Cheeky or you may experience some issues with some features, you can use VectorXR itself to arrange the layer order, another one of it's great features.  Use the arrows circled in red to set the order.

it's completely oposite for me. With cheeky below vectorXR I was not able to run any game. Korea, DCS, MSFS2024 all crashed on start. I stopped using Vector and went back to Necksafer and Cheeky only, then I satrted experimenting and found out that Vector has to be on the very bottom

[Panzerlang]

Just now, Koziolek said:

it's completely oposite for me. With cheeky below vectorXR I was not able to run any game. Korea, DCS, MSFS2024 all crashed on start. I stopped using Vector and went back to Necksafer and Cheeky only, then I satrted experimenting and found out that Vector has to be on the very bottom

Same, and it broke a bunch of stuff too.

[YoYo]

I had a similar experience. The vector had to be underneath.

[pepper9881]

04.10.2026 в 22:29, pepper9881 сказал:

Не дождавшись исправления трекинга глаз от автора программы, я исправил его сам. 

Ссылка на мой форк с исправлениями версии 0.5.4

добавил выбор пресетов А или B для nvngx_dlssnr.dll версии 310.9.16 в меню DLSS-NR

[Husar]

9 hours ago, pepper9881 said:

Added a choice of presets A or B for  nvngx_dlssnr.dllversion 310.9.16 in the DLSS-NR menu

So DLSS5 has styles (standard, normal, cinematic) and presets A and B .I have to check the difference. Before this fix there was only A as default?

There is also preset C for DLSS NR , this one they said is for performance and best to use with  frame generation?

Edited October 19 by Husar

[pepper9881]

10 часов назад, Husar сказал:

So DLSS5 has styles (standard, normal, cinematic) and presets A and B .I have to check the difference. Before this fix there was only A as default?

There is also preset C for DLSS NR , this one they said is for performance and best to use with  frame generation?

Preset C is only for frame generation (nvngx_dlssg.dll). Cheeky works only with the nvngx_dlss.dll and nvngx_dlssnr.dll libraries. In the new nvngx_dlssnr.dll version 310.9.16, only presets A and B are available. If you copy the nvngx_dlssnr.dll version 310.9.16 into the game folder and don’t force any preset for Korea, for example, via Nvidia Profile Inspector, then the faster preset B will be used automatically. I added the preset selection so that you can simply compare the performance directly during the game by switching presets on the fly. And I must say, I’m impressed. Preset B, with the Rendering Order: Before Upscaling option also selected,  results in a performance drop of only 15% on my system  when working together with the usual DLSS presets J or M in quality mode. I can no longer play in my headset with a 90 Hz refresh rate, but everything works fine in 72 Hz mode. I like the aircraft cockpits with neural processing enabled more than the original ones.

[Husar]

32 minutes ago, pepper9881 said:

Preset C is only for frame generation (nvngx_dlssg.dll). Cheeky works only with the nvngx_dlss.dll and nvngx_dlssnr.dll libraries. In the new nvngx_dlssnr.dll version 310.9.16, only presets A and B are available. If you copy the nvngx_dlssnr.dll version 310.9.16 into the game folder and don’t force any preset for Korea, for example, via Nvidia Profile Inspector, then the faster preset B will be used automatically. I added the preset selection so that you can simply compare the performance directly during the game by switching presets on the fly. And I must say, I’m impressed. Preset B, with the Rendering Order: Before Upscaling option also selected,  results in a performance drop of only 15% on my system  when working together with the usual DLSS presets J or M in quality mode. I can no longer play in my headset with a 90 Hz refresh rate, but everything works fine in 72 Hz mode. I like the aircraft cockpits with neural processing enabled more than the original ones.

I'm using new  DLSS NR , DLSS quality M and with a new  DLSS NR before upscaling I lost 40 fps "only" on whole screen in 2D . Good enough playable fps around 140.

Edited October 19 by Husar

[pepper9881]

On a headset with eye tracking, the central zone where DLSS (including NR) is applied can be made quite small—mine is 0.48x0.40. This helps reduce the performance cost. Of course, a lot also depends on your specific hardware configuration.

[Husar]

16 minutes ago, pepper9881 said:

On a headset with eye tracking, the central zone where DLSS (including NR) is applied can be made quite small—mine is 0.48x0.40. This helps reduce the performance cost. Of course, a lot also depends on your specific hardware configuration.

While I was using Quest Pro I had that size fovea area and performance was great.

[Dash,Polder]

https://github.com/ClarkCheekyKent/CheekyFoveatedDLSS/releases/tag/v0.6.0

He's added frame generation, may be worth checking out, so far none of the versions out there beat the turbo mode of vectorXR on my hardware set up, although they are starting to getting close.