So it appears. For some reason you need to change the DirectX tab Renderer from "Primary Surface" to "gdi" or "OpenGL" if you want to run Rainbow Six in software mode without mouse trails.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks, they both work perfectly. Do you know if it's possible to increase the performance for the Software mode, they lag a lot? When I used dgVoodoo2 alone, the mouse trail problem occurs, but when I try to use DxWnd with dgVoodoo2 the game doesn't launch anymore.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Do you know if it's possible to increase the performance for the Software mode, they lag a lot?
The DirectX tab option "Suppress ZBUFFER attach" seems to improve software rendering performance but causes graphical glitches. Might be a hint though that the performance issues are caused by the Z-buffer.
When I used dgVoodoo2 alone, the mouse trail problem occurs, but when I try to use DxWnd with dgVoodoo2 the game doesn't launch anymore.
I did not have much success with DgVoodoo2 but in theory you should be able to marry Dxwnd with alternate ddraw wrappers by placing them in the Dxwnd\alt.dll\ folder. Then enable the tweaks tab option "hook:ReplaceDirectXDLLs".
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Please, be aware that dgVoodoo2 is a software in continuous development. I saw that in some cases the support for advanced features (like pixel shaders) was made at the cost of some lost support of legacy DirectX releases. I can't be more precise about that (you may ask DeGe, if you like) but I only wanted to suggest trying some of the older dgVoodoo2 releases to see if they work better with legacy software.
In any case, DxWnd logs should be able to tell where the problem is more exactly.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I know what you mean. I had 40 column mode display on my Commodore 64 and it was plenty enough. ;-)
Apparently if the limit is increased the Program Files directories may not pose any more problem, since they both crossed the 80 character limit.
Last edit: BEEN_Nath_58 2021-04-02
RE: Mouse trails in software mode:
So it appears. For some reason you need to change the DirectX tab Renderer from "Primary Surface" to "gdi" or "OpenGL" if you want to run Rainbow Six in software mode without mouse trails.
Thanks, they both work perfectly. Do you know if it's possible to increase the performance for the Software mode, they lag a lot? When I used dgVoodoo2 alone, the mouse trail problem occurs, but when I try to use DxWnd with dgVoodoo2 the game doesn't launch anymore.
The DirectX tab option "Suppress ZBUFFER attach" seems to improve software rendering performance but causes graphical glitches. Might be a hint though that the performance issues are caused by the Z-buffer.
I did not have much success with DgVoodoo2 but in theory you should be able to marry Dxwnd with alternate ddraw wrappers by placing them in the Dxwnd\alt.dll\ folder. Then enable the tweaks tab option "hook:ReplaceDirectXDLLs".
Please, be aware that dgVoodoo2 is a software in continuous development. I saw that in some cases the support for advanced features (like pixel shaders) was made at the cost of some lost support of legacy DirectX releases. I can't be more precise about that (you may ask DeGe, if you like) but I only wanted to suggest trying some of the older dgVoodoo2 releases to see if they work better with legacy software.
In any case, DxWnd logs should be able to tell where the problem is more exactly.