To be precise:
NASCARs (2000 and Revolution) were launched under dgvoodoo2 using the fix that is in another topic - Nascar Revolution - need a fix for the alt key problem
MrPepka wrote on 2020-11-06, 22:01:Okay, about Speedboat Attack, using the installer from [LINK REMOVED] adapted to new systems, the game works through dgvoodoo2, but first it crashes at the start of the race, and after replacing two instructions with NOP and running the code, the game works, but the vehicle we are moving constantly flickering, and after losing a race and clicking Esc the game generates an exception that cannot be avoided
But when you NOP out those instructions (rep movs*) then the boat HUD (cockpit) doesn't show up, right?
I checked out this game and fixed the HUD problem on the wrapper side, and also, I had to modify sg else to avoid crash in the wrapper when the game closes the Glide session when returning to the main menu.
But, this game also has heap overwrite bugs so it still crashes by a good chance (RtlFreeHeap) when returning to the main menu.
I release a new version because I have some fixes but at this rate they'll never be released otherwise:
=========================
2.72:
=========================
- Fixing a state management bug in the D3D11/12 backend (XIII)
- Fixing a DDraw incompatibility bug (Tetris Worlds)
- Fixing a Glide LFB locking bug + shutdown incompatibility (Speedboats, but this game has other problems too, causing crash)
- Fixing a DDraw palette bug (Jedi Knight 2, ... and other old Star Wars games)
- Fixing a bug in D3D9 frontend (Gothic 3)
- Fixing an incompatibility in D3D8/9 frontend (Gothic 3)
- Fixing some bugs in the D3D11 backend when revising code
- Minor CPL improvements: adding 4GB to DX predefined videomemory values and observing textboxes to detect config changes
- Internal changes/minor optimizations for future features
http://dege.fw.hu/dgVoodoo2/dgVoodoo2_72.zip
http://dege.fw.hu/dgVoodoo2/dgVoodoo2_72_dbg.zip
Dege wrote on 2020-12-10, 15:51:observing textboxes to detect config changes
😁
2.72 3DMark 2001 SE (Radeon 570 - 1920x1080, MSAA 4x, no texture compression)
dgv + D3D12
no dgv - original MS D3D8.dll (not the tweak one)
Great performance, way above the original DX8 on today's hardware, but pixel shaders still run a bit worse: 350 vs 590 (maybe it's impossible to match the results)
Is it me or the driver settings for Lod bias don't have any influence on dgvoodoo? At least I experimented quite a bit with it and didn't see any difference. And it looks like by default dgvoodoo tends to set lod bias more on the negative side? Cause I'm getting strong moire patterns on mipmaps even with sgssaa
Dege wrote on 2020-12-10, 15:51:I release a new version because I have some fixes but at this rate they'll never be released otherwise: […]
I release a new version because I have some fixes but at this rate they'll never be released otherwise:
=========================
2.72:
=========================- Fixing a state management bug in the D3D11/12 backend (XIII)
- Fixing a DDraw incompatibility bug (Tetris Worlds)
- Fixing a Glide LFB locking bug + shutdown incompatibility (Speedboats, but this game has other problems too, causing crash)
- Fixing a DDraw palette bug (Jedi Knight 2, ... and other old Star Wars games)
- Fixing a bug in D3D9 frontend (Gothic 3)
- Fixing an incompatibility in D3D8/9 frontend (Gothic 3)
- Fixing some bugs in the D3D11 backend when revising code
- Minor CPL improvements: adding 4GB to DX predefined videomemory values and observing textboxes to detect config changes
- Internal changes/minor optimizations for future featureshttp://dege.fw.hu/dgVoodoo2/dgVoodo2_72.zip
http://dege.fw.hu/dgVoodoo2/dgVoodo2_72_dbg.zip
the links are dead dege
also could someone test Diablo 2 with the glide DLL's, the game itself is glitching even with default settings
Version 2.72 are on github.
https://github.com/dege-diosg/dgVoodoo2
Deffnator wrote on 2020-12-15, 23:58:Dege wrote on 2020-12-10, 15:51:I release a new version because I have some fixes but at this rate they'll never be released otherwise: […]
I release a new version because I have some fixes but at this rate they'll never be released otherwise:
=========================
2.72:
=========================- Fixing a state management bug in the D3D11/12 backend (XIII)
- Fixing a DDraw incompatibility bug (Tetris Worlds)
- Fixing a Glide LFB locking bug + shutdown incompatibility (Speedboats, but this game has other problems too, causing crash)
- Fixing a DDraw palette bug (Jedi Knight 2, ... and other old Star Wars games)
- Fixing a bug in D3D9 frontend (Gothic 3)
- Fixing an incompatibility in D3D8/9 frontend (Gothic 3)
- Fixing some bugs in the D3D11 backend when revising code
- Minor CPL improvements: adding 4GB to DX predefined videomemory values and observing textboxes to detect config changes
- Internal changes/minor optimizations for future featureshttp://dege.fw.hu/dgVoodoo2/dgVoodo2_72.zip
http://dege.fw.hu/dgVoodoo2/dgVoodo2_72_dbg.zipthe links are dead dege
also could someone test Diablo 2 with the glide DLL's, the game itself is glitching even with default settings
F*ck, Glide3.dll was damaged in dgVoodoo2_72.zip... I fixed it and Diablo2 works as before.
I reuploaded dgVoodoo2_72.zip both to my site and GitHub.
Also, fixed the links as well.
Icy wrote on 2020-12-12, 06:30:Is it me or the driver settings for Lod bias don't have any influence on dgvoodoo? At least I experimented quite a bit with it and didn't see any difference. And it looks like by default dgvoodoo tends to set lod bias more on the negative side? Cause I'm getting strong moire patterns on mipmaps even with sgssaa
Lod bias is always application driven in dgVoodoo, it's passed to the driver unaltered. But, if it proves to be a bug, plz report it and I'll check it out.
MrEWhite wrote on 2020-11-25, 23:50:Trying to enumerate refresh rates with Guitar Hero III and World Tour (don't have Aerosmith, so I can't see if this occurs there) causes the games not to open. Would be nice to see this fixed as they love opening with just 60 Hz enabled instead of a higher one.
This still occurs with 2.72.
Dege wrote on 2020-12-16, 11:18:Icy wrote on 2020-12-12, 06:30:Is it me or the driver settings for Lod bias don't have any influence on dgvoodoo? At least I experimented quite a bit with it and didn't see any difference. And it looks like by default dgvoodoo tends to set lod bias more on the negative side? Cause I'm getting strong moire patterns on mipmaps even with sgssaa
Lod bias is always application driven in dgVoodoo, it's passed to the driver unaltered. But, if it proves to be a bug, plz report it and I'll check it out.
Tested it a bit more and it seems that some games do set lod bias in a more agressive way. Though it still looks like dgvoodoo ignores driver settings? Cause when I run any game by itself I could definitely set lod bias in any way I want using driver settings, but not when it's being run with dgvoodoo, it just ignores it completely this way.
And if it has something to do with how dx11-12 works or something like that, could it be possible to force lod bias from dgvoodoo too?
Dege wrote on 2020-12-16, 10:47:F*ck, Glide3.dll was damaged in dgVoodoo2_72.zip... I fixed it and Diablo2 works as before. I reuploaded dgVoodoo2_72.zip both t […]
Deffnator wrote on 2020-12-15, 23:58:Dege wrote on 2020-12-10, 15:51:I release a new version because I have some fixes but at this rate they'll never be released otherwise: […]
I release a new version because I have some fixes but at this rate they'll never be released otherwise:
=========================
2.72:
=========================- Fixing a state management bug in the D3D11/12 backend (XIII)
- Fixing a DDraw incompatibility bug (Tetris Worlds)
- Fixing a Glide LFB locking bug + shutdown incompatibility (Speedboats, but this game has other problems too, causing crash)
- Fixing a DDraw palette bug (Jedi Knight 2, ... and other old Star Wars games)
- Fixing a bug in D3D9 frontend (Gothic 3)
- Fixing an incompatibility in D3D8/9 frontend (Gothic 3)
- Fixing some bugs in the D3D11 backend when revising code
- Minor CPL improvements: adding 4GB to DX predefined videomemory values and observing textboxes to detect config changes
- Internal changes/minor optimizations for future featureshttp://dege.fw.hu/dgVoodoo2/dgVoodo2_72.zip
http://dege.fw.hu/dgVoodoo2/dgVoodo2_72_dbg.zipthe links are dead dege
also could someone test Diablo 2 with the glide DLL's, the game itself is glitching even with default settings
F*ck, Glide3.dll was damaged in dgVoodoo2_72.zip... I fixed it and Diablo2 works as before.
I reuploaded dgVoodoo2_72.zip both to my site and GitHub.
Also, fixed the links as well.
it still has artifact issues after playing for a while, ddraw has none even with reshade in it
Dege, can you check Tribal Rage?
It's a bit weird Starcraft clone that uses some kind of windows (both the SO and the UI element) API for the game display and most UI elements. That cracks completely the compatibility with DirectDraw wrappers like dgVoodoo2 or DXWnd, even the GOG wrapper.
It works "fine" natively, but the menu background is white, instead of black, and there are some corrupted UI elements here and there. Ingame it works perfectly.
Deffnator wrote on 2020-12-17, 01:54:it still has artifact issues after playing for a while, ddraw has none even with reshade in it
Game 2020-12-16 22-47-42.jpg
Game 2020-12-16 22-47-17.png
1.14D and Glide?
Other Glide wrappers results?
stranno wrote on 2020-12-17, 14:04:Dege, can you check Tribal Rage? […]
Dege, can you check Tribal Rage?
It's a bit weird Starcraft clone that uses some kind of windows (both the SO and the UI element) API for the game display and most UI elements. That cracks completely the compatibility with DirectDraw wrappers like dgVoodoo2 or DXWnd, even the GOG wrapper.
It works "fine" natively, but the menu background is white, instead of black, and there are some corrupted UI elements here and there. Ingame it works perfectly.
I get black backgrounds and I don't see any corrupted UI elements in your video?
The background color is using Windows system colors, the game sets them during start, so something is prevented that.
lowenz wrote on 2020-12-17, 15:42:Deffnator wrote on 2020-12-17, 01:54:it still has artifact issues after playing for a while, ddraw has none even with reshade in it
Game 2020-12-16 22-47-42.jpg
Game 2020-12-16 22-47-17.png1.14D and Glide?
Other Glide wrappers results?
No issues at all using Sven's wrapper
as a Side note i came to test jane's FA again
Unforced Resolution + SVGA card seems to fix the game's black flickering issues along with some changes that i did out of nowhere on the cfg file
Icy wrote on 2020-12-17, 00:07:Dege wrote on 2020-12-16, 11:18:Icy wrote on 2020-12-12, 06:30:Is it me or the driver settings for Lod bias don't have any influence on dgvoodoo? At least I experimented quite a bit with it and didn't see any difference. And it looks like by default dgvoodoo tends to set lod bias more on the negative side? Cause I'm getting strong moire patterns on mipmaps even with sgssaa
Lod bias is always application driven in dgVoodoo, it's passed to the driver unaltered. But, if it proves to be a bug, plz report it and I'll check it out.
Tested it a bit more and it seems that some games do set lod bias in a more agressive way. Though it still looks like dgvoodoo ignores driver settings? Cause when I run any game by itself I could definitely set lod bias in any way I want using driver settings, but not when it's being run with dgvoodoo, it just ignores it completely this way.
And if it has something to do with how dx11-12 works or something like that, could it be possible to force lod bias from dgvoodoo too?
dgVoodoo simply passes the incoming lod bias to the driver (and then happens what happens). But, if you show me a game with the problem, I could check it out, I may found a bug somewhere.
But, keep in mind that forcing a larger resolution (than the game resolution) always offsets the resulting LOD to the negative direction.
Deffnator wrote on 2020-12-17, 01:54:it still has artifact issues after playing for a while, ddraw has none even with reshade in it Game 2020-12-16 22-47-42.jpg Gam […]
Dege wrote on 2020-12-16, 10:47:F*ck, Glide3.dll was damaged in dgVoodoo2_72.zip... I fixed it and Diablo2 works as before. I reuploaded dgVoodoo2_72.zip both t […]
Deffnator wrote on 2020-12-15, 23:58:the links are dead dege
also could someone test Diablo 2 with the glide DLL's, the game itself is glitching even with default settings
F*ck, Glide3.dll was damaged in dgVoodoo2_72.zip... I fixed it and Diablo2 works as before.
I reuploaded dgVoodoo2_72.zip both to my site and GitHub.
Also, fixed the links as well.it still has artifact issues after playing for a while, ddraw has none even with reshade in it
Game 2020-12-16 22-47-42.jpg
Game 2020-12-16 22-47-17.png
I cannot reproduce it on my machine. What about earlier dgVoodoo versions? I didn't touch anything in Glide in 2.72 that could produce such artifacts.
Or, is it tied to a specific location in the game?
Dege wrote on 2020-12-19, 15:42:Deffnator wrote on 2020-12-17, 01:54:it still has artifact issues after playing for a while, ddraw has none even with reshade in it Game 2020-12-16 22-47-42.jpg Gam […]
Dege wrote on 2020-12-16, 10:47:F*ck, Glide3.dll was damaged in dgVoodoo2_72.zip... I fixed it and Diablo2 works as before.
I reuploaded dgVoodoo2_72.zip both to my site and GitHub.
Also, fixed the links as well.it still has artifact issues after playing for a while, ddraw has none even with reshade in it
Game 2020-12-16 22-47-42.jpg
Game 2020-12-16 22-47-17.pngI cannot reproduce it on my machine. What about earlier dgVoodoo versions? I didn't touch anything in Glide in 2.72 that could produce such artifacts.
Or, is it tied to a specific location in the game?
Using the default english version of the game 1.14d
i've tested it again with a fresh copy of 1.14d, it has some image scaling issues with both napalm and stock glide3x.dll and all configurations
with Sven's wrapper Glide3x.dll everything works perfectly
