|
|
colors issue+contrast.png (98,147 bytes) |
|
|
Yes, it could very well be related to running out of GPU RAM. I'm not sure if there's much I can do about it. I guess I could handle it more gracefully if Direct3D reports problems, but other than that I don't know what to change. Have you tried lowering the GPU queue size and maybe the number of pre-presented frames in the fullscreen exclusive mode section, and the number of backbuffers in the windowed mode section? |
|
|
Lowering these settings to their respective minima allows me to play more videos simultaneously before I can consistently reproduce the issue (for example five instances of colors.ytp at otherwise identical settings), so yeah, low GPU RAM issue it is. The issue does not spread across player instances, but on the other hand I did not manage to make it go away by closing the other instances and playing with rendering settings for the affected instance. |
|
|
Hmmmm... Ok. So is there anything I can do about this? Right now I don't know what... |
|
|
I'd say there's no pressing NEED to do anything about this, as low on memory / out of memory cannot be considered normal conditions a renderer should work under, but I figured maybe it is interesting for you to see where and how this happens (and maybe why madVR never recovers from this issue, unless playback is restarted completely). |
|
|
Ok, I'll close this one for now. At some point I'll probably revisit the way I'm handling Direct3D error states, which may improve the behaviour. But not soon. |
- Anonymous
