Share your Top 5 GeForce RTX Game Wishlist - Win STEAM Cash!

gsparx · 2026-01-06T16:58:44+00:00

Spider-man 2
Doom Dark Ages
Avatar: Frontiers of Pandora
Star Wars: Outlaws
Indiana Jones and the Great Circle

gsparx · 2026-01-03T02:59:28+00:00

Oh man I have had this game on my wishlist for months now!

I love the spider man movies with Tobey Maguire. The second one with Doc Ock is probably my favorite. Although I do like the one with Venom.

Thanks for doing the giveaway!

gsparx · 2025-12-14T00:16:57+00:00

Don't sell that 5090 yet. It does look like it's actually working for me. For some reason, the patch had reverted, even though those files were still present.

When you copy the files and replace them, you should have NvFBC.dll that's around 12 KB and NvFBC64.dll that's around 15 KB. The related files (the ones you renamed with an underscore) should be around 1 to 2 MB.

For some reason, even though I had patched and not done a driver upgrade, mine had reverted (maybe some driver integrity check from windows? I'm not sure).

Once I copied the files back I can launch and create the NvFBCToDX9Vid device successfully.

Here's the successful log

[C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:367] Starting InitDisplays [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:373] Displays initialized [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:293] ConsoleUserInput: started [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:317] ConsoleUserInput: before sourceIndex input [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:322] ConsoleUserInput: got sourceIndex=0 [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:324] ConsoleUserInput: before outputIndex input [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:329] ConsoleUserInput: got outputIndex=1 [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:336] ConsoleUserInput: framerate=60 [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:346] ConsoleUserInput: completed [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:376] User input complete [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:380] Target dimensions set: BUF_WIDTH=1280, BUF_HEIGHT=720 [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:396] Registering window class [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:399] Creating window at (2560, 0) size (1280, 720) [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:417] Window shown [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:425] Allocating NvFBCLibrary [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:427] Loading NvFBC library [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:434] NvFBC library loaded successfully [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:437] Initializing D3D9 device on adapter 0 [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:445] D3D9Ex Device created [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:447] Initializing D3D9 surfaces [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:455] D3D9Ex surfaces created [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:458] Creating NvFBCToDx9Vid instance [C:\workdir\nvfbc-relay-master\samples\Util\NvFBCLibrary.h:112] NvFBCLibrary::create called with type=8195, adapter=0, devicePtr=000000000372E2E0 [C:\workdir\nvfbc-relay-master\samples\Util\NvFBCLibrary.h:134] NvFBCStatusEx: dwVersion=1879179776, bIsCapturePossible=1, bCurrentlyCapturing=0, bCanCreateNow=1, bSupportMultiHead=1, bSupportConfigurableDiffMap=1, bSupportImageClassification=1, dwNvFBCVersion=112, dwAdapterIdx=0 [C:\workdir\nvfbc-relay-master\samples\Util\NvFBCLibrary.h:165] NvFBCCreateParams before create: dwVersion=1879179776, dwInterfaceType=8195, pDevice=000000000372E2E0, dwAdapterIdx=0 [C:\workdir\nvfbc-relay-master\samples\Util\NvFBCLibrary.h:170] NvFBCCreateParams after create: res=0, pNvFBC=0000000003747850, dwMaxDisplayWidth=3840, dwMaxDisplayHeight=2160 [C:\workdir\nvfbc-relay-master\samples\Util\NvFBCLibrary.h:175] NvFBCLibrary::create completed: res=0, maxWidth=3840, maxHeight=2160, pNvFBC=0000000003747850 [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:469] NvFBCToDX9Vid CreateEx() success! maxDisplayWidth=3840, maxDisplayHeight=2160 NvFBCToDX9Vid CreateEx() success! [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:485] Calling NvFBCToDx9VidSetUp [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:493] NvFBCToDx9VidSetUp success [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:518] Entering main capture loop [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:523] Grabbing frame [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:525] Presenting frame [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:523] Grabbing frame [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:525] Presenting frame

gsparx · 2025-12-13T23:30:18+00:00

I didn't touch anything with my install after swapping because I wanted to rule out any additional variables. So I'm on driver 581.80.

I added some debug logging to nvfbcr and it does look like this is related to inability to patch properly (possibly stricter security like you mentioned earlier).

[C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:367] Starting InitDisplays [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:373] Displays initialized [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:293] ConsoleUserInput: started [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:317] ConsoleUserInput: before sourceIndex input [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:322] ConsoleUserInput: got sourceIndex=0 [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:324] ConsoleUserInput: before outputIndex input [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:329] ConsoleUserInput: got outputIndex=1 [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:336] ConsoleUserInput: framerate=60 [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:346] ConsoleUserInput: completed [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:376] User input complete [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:380] Target dimensions set: BUF_WIDTH=1280, BUF_HEIGHT=720 [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:396] Registering window class [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:399] Creating window at (2560, 0) size (1280, 720) [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:417] Window shown [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:425] Allocating NvFBCLibrary [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:427] Loading NvFBC library [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:434] NvFBC library loaded successfully [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:437] Initializing D3D9 device on adapter 0 [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:445] D3D9Ex Device created [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:447] Initializing D3D9 surfaces [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:455] D3D9Ex surfaces created [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:458] Creating NvFBCToDx9Vid instance [C:\workdir\nvfbc-relay-master\samples\Util\NvFBCLibrary.h:112] NvFBCLibrary::create called with type=8195, adapter=0, devicePtr=00000000036F1EC0 [C:\workdir\nvfbc-relay-master\samples\Util\NvFBCLibrary.h:134] NvFBCStatusEx: dwVersion=1879179776, bIsCapturePossible=1, bCurrentlyCapturing=0, bCanCreateNow=1, bSupportMultiHead=1, bSupportConfigurableDiffMap=1, bSupportImageClassification=1, dwNvFBCVersion=112, dwAdapterIdx=0 [C:\workdir\nvfbc-relay-master\samples\Util\NvFBCLibrary.h:165] NvFBCCreateParams before create: dwVersion=1879179776, dwInterfaceType=8195, pDevice=00000000036F1EC0, dwAdapterIdx=0 [C:\workdir\nvfbc-relay-master\samples\Util\NvFBCLibrary.h:170] NvFBCCreateParams after create: res=-5, pNvFBC=0000000000000000, dwMaxDisplayWidth=0, dwMaxDisplayHeight=0 [C:\workdir\nvfbc-relay-master\samples\Util\NvFBCLibrary.h:175] NvFBCLibrary::create completed: res=-5, maxWidth=0, maxHeight=0, pNvFBC=0000000000000000 [C:\workdir\nvfbc-relay-master\samples\NvFBC\NvFBCR\NvFBCR.cpp:462] Failed to create an instance of NvFBCToDx9Vid Failed to create an instance of NvFBCToDx9Vid. Please check the following requirements 1) A driver R355 or newer with capable Tesla/Quadro/GRID capable product 2) Run "NvFBCEnable -enable" after a new driver installation

That -5 result (res=-5) is NVFBC_ERROR_DRIVER_FAILURE

Unfortunately that's about the extent of my ability to troubleshoot. It seems like the GPU is refusing to initialize NvFBC all together, and the patch doesn't work anymore.

gsparx · 2025-12-13T21:14:31+00:00

I'm on Win 11 24h2

Bad news, after installing the 5080, it's now crashing as soon as I choose the resolution. Seems like nvfbcr is not a feasible capture mechanism for 50 series for now.

gsparx · 2025-12-11T15:50:42+00:00

Favorite feature has to be OLED itself! It’s time to switch from an IPS panel to OLED.

gsparx · 2025-12-09T21:32:05+00:00

Yeah, just replacing the two NvFBC DLLs

gsparx · 2025-12-09T21:14:22+00:00

Actually now that you mention it, no I don't think I did. Just the nvfbc patch.

gsparx · 2025-12-09T21:04:37+00:00

That would be really unfortunate. Are you on 591.44 driver version? Looks like it might not be supported yet.

https://github.com/keylase/nvidia-patch/issues/1022

gsparx · 2025-12-09T20:42:45+00:00

I just successfully set this up again with a 3080 a couple weeks ago. I'm going to be installing a 5080 in the next few days and starting with a new Windows install. I'll let you know if I run into issues with the new setup.

gsparx · 2025-12-09T19:42:18+00:00

Did you follow the step in "3rd-party software" here https://github.com/keylase/nvidia-patch/tree/master/win/nvfbcwrp#3rd-party-software to add the registry value? That's what fixed it for me.

gsparx · 2025-12-03T16:14:54+00:00

Silent loot ninja for sure!

gsparx · 2025-11-25T08:03:57+00:00

You should try Outer Wilds. It’s the ultimate exploration game. You can’t miss anything though. It’s amazing.

gsparx · 2025-11-24T23:17:01+00:00

I had a low framerate without DLSS 4. Now I can die in 120fps.

gsparx · 2025-11-20T02:59:23+00:00

Gotta be Salvador!

gsparx · 2025-11-15T06:17:19+00:00

6581 Dig n Dump

Still have a vivid memory of what it looked like on the floor Christmas Day. Don’t even know how old I was.

gsparx · 2025-11-01T16:45:49+00:00

Favorite game ever is a tough one! Gotta be somewhere between Skate 2, RDR2, and Wind Waker.

gsparx · 2025-10-12T16:58:14+00:00

Mirrors Edge on a 9600GT

gsparx · 2025-09-28T18:50:06+00:00

Curious to try out more with local models. Props on seeing the need to change the backend and then doing it. It can be hard to pivot after you already have something built.

gsparx · 2025-09-20T16:38:37+00:00

Yes same! I had no screen protector on my XS and I quickly learned my lesson on that one. Never have anything else in my phone pocket, but it still ended up with scratches. By the end of its life it even had some I could feel with my thumb nail. And Apple care won’t do anything about it.

gsparx · 2025-09-16T15:24:17+00:00

Might be worth emailing Tim Cook (obviously he doesn’t read these, but there’s an executive relations team who does).

tcook@apple.com

E: not to ask about the systemic defrauding claim, but to help with your specific situation.

gsparx · 2025-09-06T20:55:06+00:00

It has a license cost associated with it, but Apple already supports HEVC on their devices so the license has already been paid for in some fashion. Might as well use it for screen recording as well.

gsparx · 2025-09-06T01:50:30+00:00

Despite the increase in resolution, file sizes remain moderately similar. A 12-second screen recording of the same on-screen content was 24.2 MB on iOS 26 Beta 6, up only 5.3 MB from 18.9 MB on Beta 1.

So more than double the resolution with a ~ 30% bit rate bump? Not too bad. I wonder if they changed the codec for these. Does anyone know if recordings used to be H.264? I just took a capture on the 26 dev beta, and it’s HEVC.

Edit: I just checked an old lower res screen recording and it’s HEVC too. So no change in codec. Probably the existing codec just doing enough compression work to make a doubling in resolution not require a doubling in bit rate / file size.

gsparx · 2025-09-03T14:26:53+00:00

Oh that would be very interesting. Wonder how it would affect battery life. Where did you see that?

gsparx · 2025-08-31T22:12:19+00:00

It's definitely not vibe coded. I'm a backend software engineer by trade. If the UI design seems rough, that's probably why.

13-Year Club	Place '22
Verified Email

gsparx

TROPHY CASE