Hi dege,
have you ever thought about adding support for fancy 3d apis (like CIF, S3D, MSI, PowerSGL...)?

The Steam overlay is working fine now.

Dege wrote:

Ok, I changed to 'unspecified' scaling mode when setting the desktop resolution, it still seems to work fine on my computers (AMD, nVidia).
If not even this one will work for you then I think I cannot do anything else for this issue. 🙁

Can we test it a little bit before release? 😀

Just a suggestion for the configuration utility. Check if dgvoodoo.conf is in the current directory and use it for editing if it exists in the current directory.

Myloch wrote:

Hi dege,
have you ever thought about adding support for fancy 3d apis (like CIF, S3D, MSI, PowerSGL...)?

Yes, I bugged him about it a while back. 😁

VEG wrote:

Dege wrote:

Ok, I changed to 'unspecified' scaling mode when setting the desktop resolution, it still seems to work fine on my computers (AMD, nVidia).
If not even this one will work for you then I think I cannot do anything else for this issue. 🙁

Can we test it a little bit before release? 😀

Yes, I just made some other changes so partly re-testing DX/DX8 was needed.
I intend this state to be the final one altough I found regression bug(s) in Glide that are still to be fixed (Diablo II, dynamic shader compiling).

I also fixed some gamma-ramp related problems in DX8, so Need For Speed Hot Pursuit 2 and NFS3 with DX8 renderer both work now.

http://dege.fw.hu/temp/dgVoodooWIP19.zip

Stiletto wrote:

Myloch wrote: Hi dege, have you ever thought about adding support for fancy 3d apis (like CIF, S3D, MSI, PowerSGL...)? […]
Show full quote

Myloch wrote:
Hi dege,
have you ever thought about adding support for fancy 3d apis (like CIF, S3D, MSI, PowerSGL...)?

Yes, I bugged him about it a while back.

😁
Would be nice, but I'm not planning it now, it all is too time-consuming.

Dege, thanks. This one works good 😀

But what about this suggestion?

VEG wrote:

Just a suggestion for the configuration utility. Check if dgvoodoo.conf is in the current directory and use it for editing if it exists in the current directory.

I would like to place dgVoodooSetup.exe in the drivers/dgvoodoo/ subdirectory, and it will be nice if it detect dgvoodoo.conf in the own directory and start to edit it automatically.

Another suggestion to change the name of dgVoodooSetup.exe to dgVoodooConf.exe. Just because Windows thinks that dgVoodooSetup.exe have to setup something, but it doesn't, and as the result Windows sometimes asks me if this installer is failed. Just stupid heuristics =)

Does dgVoodoo Napalm support these sizes of the textures?

1/* Napalm extensions to GrLOD_t */
2#define GR_LOD_LOG2_2048        0xb
3#define GR_LOD_LOG2_1024        0xa
4#define GR_LOD_LOG2_512         0x9

UPD. I have tested it and it seems that it supports these texture sizes 😀

Texture corruption problem with stretching+AR is camera angle dependent:

VEG wrote:

Dege, thanks. This one works good 😀

Cool!

VEG wrote:

But what about this suggestion? […]
Show full quote

But what about this suggestion?

VEG wrote:

Just a suggestion for the configuration utility. Check if dgvoodoo.conf is in the current directory and use it for editing if it exists in the current directory.

I would like to place dgVoodooSetup.exe in the drivers/dgvoodoo/ subdirectory,
and it will be nice if it detect dgvoodoo.conf in the own directory and start to edit it automatically.

Ok, I can do that. If the current folder is already in the folder list then it could be selected by default, instead of the user appdata folder.

VEG wrote:

Another suggestion to change the name of dgVoodooSetup.exe to dgVoodooConf.exe. Just because Windows thinks that dgVoodooSetup.exe have to setup something, but it doesn't, and as the result Windows sometimes asks me if this installer is failed. Just stupid heuristics =)

Right, I think dgVoodooSetup is not the best name, after all it's a configurator, but it's a legacy from dgVoodoo1. It's a pity I choosed that back then (what is more, it would have been better not to name this wrapper 'dgVoodoo').
But I won't rename it in this version, I should re-draw its icon. 😁

VEG wrote:

Does dgVoodoo Napalm support these sizes of the textures? […]
Show full quote

Does dgVoodoo Napalm support these sizes of the textures?

Copy code to clipboard

1/* Napalm extensions to GrLOD_t */
2#define GR_LOD_LOG2_2048        0xb
3#define GR_LOD_LOG2_1024        0xa
4#define GR_LOD_LOG2_512         0x9

UPD. I have tested it and it seems that it supports these texture sizes 😀

Yes, but only if a Voodoo4 is selected as the virtual card ("Other greater").

lowenz wrote:

Texture corruption problem with stretching+AR is camera angle dependent: […]
Show full quote

Texture corruption problem with stretching+AR is camera angle dependent:

I wish I could reproduce it myself.

If you have Republic Commando, try to change the resolution in-game (with dgVoodoo obviously 😁 ) and look around.

Dege wrote:

Yes, I just made some other changes so partly re-testing DX/DX8 was needed. I intend this state to be the final one altough I fo […]
Show full quote

VEG wrote:

Dege wrote:

Ok, I changed to 'unspecified' scaling mode when setting the desktop resolution, it still seems to work fine on my computers (AMD, nVidia).
If not even this one will work for you then I think I cannot do anything else for this issue. 🙁

Can we test it a little bit before release? 😀

Yes, I just made some other changes so partly re-testing DX/DX8 was needed.
I intend this state to be the final one altough I found regression bug(s) in Glide that are still to be fixed (Diablo II, dynamic shader compiling).

I also fixed some gamma-ramp related problems in DX8, so Need For Speed Hot Pursuit 2 and NFS3 with DX8 renderer both work now.

http://dege.fw.hu/temp/dgVoodooWIP19.zip

Stiletto wrote:

Myloch wrote: Hi dege, have you ever thought about adding support for fancy 3d apis (like CIF, S3D, MSI, PowerSGL...)? […]
Show full quote

Myloch wrote:
Hi dege,
have you ever thought about adding support for fancy 3d apis (like CIF, S3D, MSI, PowerSGL...)?

Yes, I bugged him about it a while back.

😁
Would be nice, but I'm not planning it now, it all is too time-consuming.

This WIP made Megarace 3 stop working.

Just bug reporting, it tries to start then crashes

I've added an ability to use large textures 512×512, 1024×1024 and 2048×2048 in the NFS3 Modern Patch. It would be nice to have an ability to choose more Onboard RAM, e.g. 32MiB, 64MiB, or even 128MiB.

VEG wrote:

I've added an ability to use large textures 512×512, 1024×1024 and 2048×2048 in the NFS3 Modern Patch. It would be nice to have an ability to choose more Onboard RAM, e.g. 32MiB, 64MiB, or even 128MiB.

I think you can type in the amount of RAM for the card you're using. Nice addtions to the rear view window.
Maybe after you finish with NFS 3 you can start with Splinter cell/ Pandorra T. 🤣 I'll send you some beer if this will be happening. 😀

@Dege. Fast access works for Splinter Cell PT. The light color problem is still there. For texture corruption try changing the resoltion to 640x480.
At this resolution there were some problems if i remember well, while certain mouse movements were performed(including black textures in certain areas).
There are also a number of game issue(non dgvoodoo related) dependent on mouse movement in SC PT. It would not be a bad ideea to see whats happening. 😁

I couldn't reproduce the texture corruption myself, but, found a very basic bug around the scaling that, according to the symptoms, can smoothly cause it. 😊
Does this fix solve the problem for you?

http://dege.fw.hu/temp/dgVoodooWIP19_1.zip

Matsilagi wrote:

This WIP made Megarace 3 stop working.

Just bug reporting, it tries to start then crashes

Trying to run with 'Unspecified' scaling mode? That's the one it works with (and ATI 8500 preset).
Otherwise it crashes at once for me too.

Not Found
The requested URL /dgVoodooWIP19_1.zip was not found on this server.
Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request.

Maybe there is no "temp" subdir in the URL :p

Addendum: why the size of D3D8 has grown so much? (130->600 KB)

Dege wrote:

I couldn't reproduce the texture corruption myself, but, found a very basic bug around the scaling that, according to the symptoms, can smoothly cause it. 😊
Does this fix solve the problem for you?

YOU GOT IT, MAN! Problem solved (in Splinter Cell Versus).

lowenz wrote:

Addendum: why the size of D3D8 has grown so much? (130->600 KB)

I think that Dege just forgot to pack this dll file. Usually he use dll/exe packer, but it is not a good thing. Packed DLL extracts itself every time when it is used.