I have to admit I find that a bit funny — a bug that stayed hidden simply because basically nobody ever managed to upload a 256³ LUT anywhere before. 😄

Good to hear it's confirmed on the Envy side though. Now I'm genuinely curious: once madVR ships the fix, will we finally be able to upload a full 256³ LUT successfully on the Envy ...

The text used there is from madVR themselves, when they discovered the bug.

And when the Envy bug is fixed it should work exactly as the madVR HTPC (madTPG for example) works.
That is already proven working, and is why I repeatedly said to test that.

But, it will only work if your PC has the resources to actually generate 256^3 LUTs.

Steve

Environment Variables were much more commonly used when Windows was a GUI overlaid on MS-DOS, and were added or modified if needed in Windows' startup files. They still exist under the surface, but most Windows apps today use the system's resource management. When a special need arises, you can invoke them. As Steve says, you can Google how to change them.

There has been some more feedback from madVR Labs.
They have found more issues associated with the 256^3 LUT Upload, and have generated an updated dll for ColourSpace, as well as fixing the firmware in Envy.
To quote Mathias' own words "Sorry once more for the bugs, and please feel free to officially blame me for these issues. "

The next release of ColourSpace will have the required new madVR dll included, and with the Envy firmware update all should then work as it does with madVR HTPC.

Steve

When can we expect the new CS release? The Envy firmware is already available.

Yesterday I tried to load but after 5 hours nothing happened, I deleted the environment variable, in the meantime envy added a new software around 9:30 pm but the software does not load! Without the environment variable, all the old 3dluts crash at 80%

Gian luca
Set the Env. Variable as stated in the madVR user Guide page!

Steve

As the issue is the madVR dll, I guess you could just get that from madVR and replace it...
It's not actually a ColourSpace issue.

Steve

Steve
I solved it by downgrading madvr envy

Ah - so you were already using the Env. Variable, or you have a lower ColourSpace license without the 256^3 capability.
That likely means you could also have replaced the madVR dll with their new one.

Steve

I have the madVR dll and I'm still debbuging with Mathias. The Upload works now but there seems to be other problems now when using the native 256^3 Upload function.

As has been said a few times, test and compare with madVR HTPC...

Steve

Steve please stop suggesting to test with madvr htpc which isn't an option. I have an envy and that needs to work.

We're still investigating but I think you shouldn't Advertise that feature anymore to be honest.

The testing with madVR HTPC is to verify that works.
Envy should work exactly the same, which then shows the issues are not ColourSpace.
Doing such testing would help you debug with Mathias.

Steve

Okay will do we will see how it goes.