- Thread starter
- Moderator
- #4,031
Hi Guys
V330 in first post
- Preparing Frame grabber (Auto3D) and fix memory leak for screenshot when using madVR (fix on madVR side in the future next version)
- Fix subtitle delay (setting was reinitialized when D3D subtitle device was set for madVR)
- Disable Core CC parser for madVR
- For now only Screenshot feature will use the new madVR code (the GrabFrame code in there but no enable because it trigger performance issue)
So Atmolight/ambilight should work as before (only when D3D9 is used).
Screenshot can be done for all kind of mode (leak is fixed on MP side and the one from madVR will be in the next future version).
@daWooky the Auto3D detection works if there is no madVR stats on screen and when using D3D9 later when performance issue will be fixed, it will work for all kind of settings (even with madVR stat on screen).
V330 in first post
- Preparing Frame grabber (Auto3D) and fix memory leak for screenshot when using madVR (fix on madVR side in the future next version)
- Fix subtitle delay (setting was reinitialized when D3D subtitle device was set for madVR)
- Disable Core CC parser for madVR
- For now only Screenshot feature will use the new madVR code (the GrabFrame code in there but no enable because it trigger performance issue)
So Atmolight/ambilight should work as before (only when D3D9 is used).
Screenshot can be done for all kind of mode (leak is fixed on MP side and the one from madVR will be in the next future version).
@daWooky the Auto3D detection works if there is no madVR stats on screen and when using D3D9 later when performance issue will be fixed, it will work for all kind of settings (even with madVR stat on screen).