Closed mcclure closed 6 years ago
Sorry about that, looks like the serialisation of WGL_NV_DX_interop
got broken in the refactor for v1.0 and I didn't catch that in my testing.
(Gory details: it was only calculating the number of mip levels to save while reading, not while writing, so while writing it skipped the main loop. Then the read path tried to read data that wasn't there, and got a vastly incorrect size and bailed out. At least the error-detection code caught it and didn't explode trying to allocate 3944961821114368 bytes).
That fix above should sort it, I was able to repro the problem on a test program for that extension. You can test with the next nightly build.
Thanks, will test on Monday
I tried the latest nightly build along with a pre-built copy of lovr from lovr.org, and it seemed to work for me now at least on the 'no game' screen. Closing this issue now, but please comment if you run into problems.
I forgot to test sorry!! And thanks
Have been using RenderDoc 0.9x (don't remember) with https://github.com/bjornbytes/lovr (a self built version...) on Windows 10. It worked great.
Today opened it and it asked if I wanted to upgrade to 1.0. I said sure! It downloaded and I restarted the application.
I am now 100% getting this error when I try to do a capture of my program.
Here is how I got this error message: I opened renderdoc. I selected lovr.exe and gave it a nonexistent input file (so it would just go to its 'file not found' screen). I selected capture frame 5. I started. I double clicked frame 5. I got the error.
Below are screenshots of the app when the error occurred and the diagnostic log. " Reading invalid array or byte buffer - 3944961821114368 larger than total stream size 40576." looks suspicious. Let me know if I should gather additional data.