Just restarted my pc, redownloaded the slipstreamed version, replaced my existing dlls and now I get: Failed to evaluate the script: Python exception: Unexpected behavior. Contact author. Traceback (most recent call last): File "src\cython\vapoursynth.pyx", line 1712, in vapoursynth.vpy_evaluateScri...

I will slipstream it later today.

Thanks!

Cu Selur

The test dll version works fine.

Cu Selur

No problem and no rush.
I'm happy your on it and the problem was easy traceable.

Thanks for looking into it.

Cu Selur

Using 64bit here.

Apparently Vapoursynth does not call CoInitialize() so my WMI calls fail.

And those were added with 2053, since 2052 does work fine.

Just wondering what the status of current Vapoursynth support is. Atm. I use 64bit DGSource as an AvisynthPlugin in Vapoursynth 64bit: # Imports import vapoursynth as vs core = vs.get_core() # Loading Avisynth Plugins core.avs.LoadPlugin(path="G:/Hybrid/vsfilters/SourceFilter/DGDecNV/DGDecodeNV.dll"...

Happy to help and really happy that all is working again.

Downloaded and installed the hotfix driver.
From the looks of it the issue is solved with that driver version.
(starting DGDecNV, loading a source die DGSource and NVEncC all work as they should)

Cu Selur

Just read the thread over inside the NVIDIA forum, seems like they are aware of the problem and working on it,.. so let's hope it doesn't take them too long to figure out how they broke it and how to repair it.

Cu Selur

NVCEnC also fails with that the 378.66 driver version,... (upgrading to Pascal isn't planned here for a while,.. not prepared to shell out the money needed for a GeForce 1080 to replace my 980Ti; especially since my whole system is watercooled which adds another 100+ bucks for the cooler,..)

Small follow-up: today I was prompted by GeForce Experience that a 'GeForce Game Ready Driver' was available (version 378.66; release date 2017/02/14) and since I'm always a bit curious I installed it and like I suspected DGDecNV doesn't work with it so back to 376.33, till the next driver release.

a. You can't use Avisynth 64bit in Hybrid
b. Avisynth 64bit is even more unstable than Avisynth MT (which is one of the reason for a.)
c. lots of filters are not available for Avisynth 64bit (which is one of the reason for a.)

-> downgrade your drivers (last working were 376.33 )

I normally try to keep my drivers up-to-date since in example NVCEncC often only works properly with the latest drivers installed.
Hopefully NVIDIA will fix the issue with their drivers in one of their next updates.

Cu Selur

tried the hotfix drivers, issue is still present.
So I'll stick to 376.33 and test the next version.

Cu Selur

Okay, that was fast.
Just switching to the previous version 376.33 solved the problem.

Issue is solved then.

Cu Selur

Okay, did the clean install of the latest drivers and a reboot after. DGIndexNV and the other programs show the same error again. :( -> so the solution again seems to be downgrading the drivers. (will test the drivers down to 369.30 to see which is the last working version) btw: Thanks a lot for the...

Gimme a second, before you set it to resolved.
Will try to see what happens if I now upgrade to the latest drivers (clean install).

Okay, since GeForce Experience just popped up I know at least the drivers changed.
The toolkit installed the 369.30 drivers and GeForce Experience now offers to upgrade to 378.49 again.

No clue why PhysX isn't there. (didn't dis- or enable anything during the installation aside from that a clean install should be used) The normal NDVIDA settings app shows that the card is used for PhysX. Hmm, can you run CPU-Z Performance tab? It actually runs a small CUDA app. G PU-Z doesn't have ...

Okay, so much for not installing the AMD Software, Windows itself installed the Radaon Software through Windows update. Ran GPU-Z and output looks fine to me: https://s29.postimg.org/jablrbezr/gpuz.png attached the report of 'GPU Caps Viewer CUDA tab' downloading ' CUDA Toolkit 8.0.44' now Cu Selur

Will download and install the CUDA Toolkit 8.0 once I got the adapters running again. Will keep NV as primary (which it was anyways to no big change there). Will report back once I got my system fully running again, installed the Toolkit and ran NvDecodeD3D9 again. Thanks for taking the time to test...

No other GPU apps running at the same time? Folding? Anything?

Nope nothing, made sure to even close firefox and thunderbird (so their hardware acceleration couldn't interfere) when running NvDecodeD3D9 and DGIndexNV.

Cu Selur

ran NvDecodeD3D9.exe -i=plush.m2v -o=plush.yuv and NvDecodeD3D9.exe -displayvideo -i=plush.m2v -o=plush.yuv both times I got the same output as before: Command Line Arguments: argv[0] = NvDecodeD3D9.exe argv[1] = -displayvideo argv[2] = -i=plush.m2v argv[3] = -o=plush.yuv [NVDecodeD3D9]: output file...

No clue what changed. (normal system updates happened, but nothing else that comes to mind; didn't install any new software apart from updates.) --- Removed the AMD card physically from my pc. Deleted DGIndexNV.ini. Tried DGIndexNV (32bit). Same error. Deinstalled all Radeon software. Rebooted syste...