This is an interesting bug lol. Only seen like 1 other person get it.
As a means to try and figure out what could be causing it can I ask for some various information about your system?
Laptop or Desktop?
What operating system and version are you on?
What CPU do you have?
What GPU do you have?
Do you use my proxy? (Direct3D8 to Direct3D9 proxy.)
Do you use dgVoodoo?
Do you use ReShade?
Do you have any other third-party dlls/libs similar to dgVoodoo/ReShade?
This is an interesting bug lol. Only seen like 1 other person get it.
As a means to try and figure out what could be causing it can I ask for some various information about your system?
- Laptop or Desktop?
- What operating system and version are you on?
- What CPU do you have?
- What GPU do you have?
- Do you use my proxy? (Direct3D8 to Direct3D9 proxy.)
- Do you use dgVoodoo?
- Do you use ReShade?
- Do you have any other third-party dlls/libs similar to dgVoodoo/ReShade?
What operating system and version are you on? Win. 10 Pro
What CPU do you have?Intel Core I7-4791K 4.00 Ghz
What GPU do you have?NVIDA GTX 970
Do you use my proxy? (Direct3D8 to Direct3D9 proxy.) Not sure.
Do you use dgVoodoo?Yes
Do you use ReShade?Yes
Do you have any other third-party dlls/libs similar to dgVoodoo/ReShade?None.
- Laptop or Desktop? Desktop
- What operating system and version are you on? Win. 10 Pro
- What CPU do you have?Intel Core I7-4791K 4.00 Ghz
- What GPU do you have?NVIDA GTX 970
- Do you use my proxy? (Direct3D8 to Direct3D9 proxy.) Not sure.
- Do you use dgVoodoo?Yes
- Do you use ReShade?Yes
- Do you have any other third-party dlls/libs similar to dgVoodoo/ReShade?None.
Given that it is dgVoodoo there isn't much that can be done to fix it. Since it is closed src there is no way for us to find where the cause may be with their code that would alter how the rendering is happening between the DX8 -> DX11/12 translation.
You could bug report it to them but I dunno how active they are with things.
Given that it is dgVoodoo there isn't much that can be done to fix it. Since it is closed src there is no way for us to find where the cause may be with their code that would alter how the rendering is happening between the DX8 -> DX11/12 translation.
You could bug report it to them but I dunno how active they are with things.
Any time i load it, i get a PiP version of the addon. I can click some things but cannot tell what it all is. Any plans on updating/fixing this?
This is an interesting bug lol. Only seen like 1 other person get it.
As a means to try and figure out what could be causing it can I ask for some various information about your system?
Going to assume this is related to dgVoodoo or ReShade. Can you try with one or the other disabled, then both and see if it still happens?
Ok, it is DGVoodoo or Reshade. Give me a sec and ill reload one to see which it is
Ty for your assistance
Confirmed, it is DGVoodoo that causes it.
Given that it is dgVoodoo there isn't much that can be done to fix it. Since it is closed src there is no way for us to find where the cause may be with their code that would alter how the rendering is happening between the DX8 -> DX11/12 translation.
You could bug report it to them but I dunno how active they are with things.
Going to close this issue since the problem is with dgVoodoo.