I'm testing Unreal in D3D wrapped to D3D11 by DGV2 on an i3 8300 and I must say tath the CPU is really important, more than the GPU actually (a 750 Ti beats a 1050 Ti thanks to the quad core vs dual core+hyperthreading).
Of course I say that having only tested with death/success movies, so I tried copying the story movies and it starts crashing 100% of the time when selecting new game. This seems to be a regression since 2.55 works perfectly. Windowed mode also works perfectly (sort of like Requiem?). Three logs attached if Dege wants to read, Thief 2 running with movies in fullscreen (and crashing), Thief 2 running with movies in windowed mode (and running fine) and Thief 2 running with no movies (except lose/win ones, also runs fine).
I'm not sure but I think I found the reason. BloodRayne2 happens to crash for me all time when skipping from the intro movie to the game.
I did a modification for the sake of DXVK in 2.55.1 and it turned out to be bad.
Some more uninteresting (as in they all work perfectly) games tested:
Mangchi The Hammer Boy doesn't like dgVooodoo 2.55.1+, otherwise no problems. Minor graphic glitches with resolution forcing.
Room Zoom: Race for Impact doesn't like dgVoodoo 2.55.1+ either, but no other problems.
Kaan: Barbarian's Blade also seems to have a problem with dgVoodoo 2.55.1+, but otherwise has no problems.
Gift seems to share enough similarities with Kaan that I think it runs on the same engine, however it works fine in dgVoodoo2 2.55.1+ and shows black screen instead of FMVs when resolution forcing is on.
Dead Man's Hand is an Unreal Engine game with no issues. Needs a framerate limiter though.
Highland Warriors (demo) has double cursor issue when resolution forcing, though the game has perfect high resolution support and no need for it anyway.
Lords of Everquest works perfectly, but is a bit weird with resolution forcing. It will break menus unless you change resolution to a forced resolution ingame. If you want resolution forcing for UI scaling here you might want to make a script to set the game to desktop resolution before starting it then changing to your desired UI resolution ingame afterwards. Also avoid forced texture filtering and non-integer scales.
Then you want to run Compatibility Administrator (32-bit), right click on "New Database(1) [Untitled_1]", rename it to something, then right click again "create new > application fix", fill in the three fields, click next two times, you'll find a list, you want to only check "Win98VersionLie", then next and finish. Now click "File > Save as", save the database somewhere, then click "File > Install".
I'm guessing the game starts on a code path intended for NT OSes if it doesn't detect 95/98 😖
Thanks. It works for intro CGI and some CGI but not for others. it doesn't work for CGI like travelling in hulline forest.
I'm testing Unreal in D3D wrapped to D3D11 by DGV2 on an i3 8300 and I must say tath the CPU is really important, more than the GPU actually (a 750 Ti beats a 1050 Ti thanks to the quad core vs dual core+hyperthreading).
A D3D11 wrapper is available here : http://kentie.net/article/d3d11drv/index.htm .....dgvoodoo2 is useless.......cpu load is very high with dgvoodoo like the OPEN GL renderer ....
Config : ASUS PRIME H270 PRO / CORE i7-7700/ 16 GB DDR2400 / MSI GTX1060 6GT OCV1 @391.01/ Moniteur @1080p ...WINDOWS 10 64 bits V1803 @17134.191
I'm testing Unreal in D3D wrapped to D3D11 by DGV2 on an i3 8300 and I must say tath the CPU is really important, more than the GPU actually (a 750 Ti beats a 1050 Ti thanks to the quad core vs dual core+hyperthreading).
A D3D11 wrapper is available here : http://kentie.net/article/d3d11drv/index.htm .....dgvoodoo2 is useless.......cpu load is very high with dgvoodoo like the OPEN GL renderer ....
Config : ASUS PRIME H270 PRO / CORE i7-7700/ 16 GB DDR2400 / MSI GTX1060 6GT OCV1 @391.01/ Moniteur @1080p ...WINDOWS 10 64 bits V1803 @17134.191
?
That is NO wrapper, it's a dedicated renderer (Unreal got dx7->11 renderers through unofficial - oldunreal - patches)
dgVoodoo useless? It's perfect as far as an universal wrapper can be.
I'm testing Unreal in D3D wrapped to D3D11 by DGV2 on an i3 8300 and I must say tath the CPU is really important, more than the GPU actually (a 750 Ti beats a 1050 Ti thanks to the quad core vs dual core+hyperthreading).
A D3D11 wrapper is available here : http://kentie.net/article/d3d11drv/index.htm .....dgvoodoo2 is useless.......cpu load is very high with dgvoodoo like the OPEN GL renderer ....
Config : ASUS PRIME H270 PRO / CORE i7-7700/ 16 GB DDR2400 / MSI GTX1060 6GT OCV1 @391.01/ Moniteur @1080p ...WINDOWS 10 64 bits V1803 @17134.191
kentie is that you? Not that i care that much.😀 1 post , joined today, looks very...normal
I'm testing Unreal in D3D wrapped to D3D11 by DGV2 on an i3 8300 and I must say tath the CPU is really important, more than the GPU actually (a 750 Ti beats a 1050 Ti thanks to the quad core vs dual core+hyperthreading).
A D3D11 wrapper is available here : http://kentie.net/article/d3d11drv/index.htm .....dgvoodoo2 is useless.......cpu load is very high with dgvoodoo like the OPEN GL renderer ....
Config : ASUS PRIME H270 PRO / CORE i7-7700/ 16 GB DDR2400 / MSI GTX1060 6GT OCV1 @391.01/ Moniteur @1080p ...WINDOWS 10 64 bits V1803 @17134.191
?
That is NO wrapper, it's a dedicated renderer (Unreal got dx7->11 renderers through unofficial - oldunreal - patches)
dgVoodoo useless? It's perfect as far as an universal wrapper can be.
You're right ...it's a renderer... I love DGVOODOO but UNREAL has many renderers .....no need of a wrapper...
I'm testing Unreal in D3D wrapped to D3D11 by DGV2 on an i3 8300 and I must say tath the CPU is really important, more than the GPU actually (a 750 Ti beats a 1050 Ti thanks to the quad core vs dual core+hyperthreading).
A D3D11 wrapper is available here : http://kentie.net/article/d3d11drv/index.htm .....dgvoodoo2 is useless.......cpu load is very high with dgvoodoo like the OPEN GL renderer ....
Config : ASUS PRIME H270 PRO / CORE i7-7700/ 16 GB DDR2400 / MSI GTX1060 6GT OCV1 @391.01/ Moniteur @1080p ...WINDOWS 10 64 bits V1803 @17134.191
kentie is that you? Not that i care that much.😀 1 post , joined today, looks very...normal
Dege wrote:Well, I always like to see your game reports. :)
Nicely presented with details. […] Show full quote
ZellSF wrote:
Some more uninteresting (as in they all work perfectly) games tested:
Well, I always like to see your game reports. 😀
Nicely presented with details.
As for the 2.55.1+ issue, plz try the new WIP I just released. I fixed the regression bug.
Those games are all fixed in 2.55.3.
Mouse input for RIM: Battle Planets is also fixed, but just to give you more to look at with this problematic game...: https://www.youtube.com/watch?v=OBcV4TKZdDA&feature=youtu.be
Remember how 3D models didn't show in this game? Well they still disappear too often when moving the camera. Notice how when I move the camera, the 3D models for the units disappear before they've left the camera. This isn't supposed to happen. It does not happen natively. This is the second level of this demo: https://www.fileplanet.com/59680/download/Rim … le-Planets-Demo
Need for Speed™ Porsche® 2000
Main menu with bumped up resolution w/o issues with latest dg 2.55.3; full 32 bit color, instead of 16 bit default.
Unfortunately, there is a problem with lighting heavy flickering (screenshot is not showing this of course, but flickering is very intense); not spotted by me before, due to playing only day levels. 😀
Like Jessietail a few pages back, I have a similar issue with LEGO Rock Raiders. v2.53 was the last working version(with some lighting issues) of voodoo before the newer versions caused problems running the game. I have a GTX 970, tried the latest version 2.55.3 and the game locks up a few seconds into a level after the mission briefing disappears.
Not sure if it this helps but this is the last error it x32dbg logs. Tried different levels in case it was particular, same error every time.
In the leadup to that (other than Guard page exeptions, the last debug string from voodoo was
1DebugString: "[dgVoodoo] INFO: DirectDrawSurface (09881510)::QueryInterface: Aggregated Direct3DTexture (17B65AD8) object is created and initialized.\n"
If i try to editing config of dgVoodoo2 i can't see changes in-game... (version 2.55.3)
edit: same problem with 2.55.2 !!
edit2: no problems with 2.55
version 2.55.1 is detected by windows defender...
edit3: with new versions i see that dgVoodoo.conf file is into dgVoodoo2 main folder (because it's already included into archive... it wasn't in 2.55 and all other old versions) and not in C:\Users\yourname\Appdata\Roaming\dgVoodoo folder and this cause that problem... i've moved that file in correct folder and now 2.55.3 version it works fine
Last edited by FulValBot on 2018-08-23, 23:23. Edited 15 times in total.
Like Jessietail a few pages back, I have a similar issue with LEGO Rock Raiders. v2.53 was the last working version(with some lighting issues) of voodoo before the newer versions caused problems running the game. I have a GTX 970, tried the latest version 2.55.3 and the game locks up a few seconds into a level after the mission briefing disappears.
Not sure if it this helps but this is the last error it x32dbg logs. Tried different levels in case it was particular, same error every time.
In the leadup to that (other than Guard page exeptions, the last debug string from voodoo was
1DebugString: "[dgVoodoo] INFO: DirectDrawSurface (09881510)::QueryInterface: Aggregated Direct3DTexture (17B65AD8) object is created and initialized.\n"
Thanks mate!
I also debugged the problem with DebugView++ and the debug version of dgVoodoo 2.55.3
It (sometimes) reports the (game) error
1C:\Dev\SourceSafe\gods98_dx6\gods98\src\Files.c(330) : Error in call to File_Open
(Though this might just be the game trying to load a sound file for the item)
From that point onwards, all rendering stops (the game looks frozen). However, the game continues to run and you can still perform actions in the game (indicated by the sounds). The game remains fully operational aside from not showing anything.
There are still a lot of DirectDraw calls that do seem to succeed (don't show signs of failing), but these are not reported as dgVoodoo messages.
As Cyrem stated, this error did not occur under version 2.53
(After a while of gameplay (~15 minutes) I do get this same problem. This might have a different cause however)