How can I reproduce this in the easiest way if I start a new game with a new character?

Hello and thanks for replying!

I cannot say if you will be able to produce it, but the only dgVoodoo files I have copied into my EQ1999 folder are:
D3D8.dll
D3D9.dll
D3DImm.dll
DDraw.dll

For example, one of the screenshots is from the East Cabilis zoneline to Field of Bone, where behind the two Trooper guards, are some very dark looking stones. When u get closer to those rocks, you can see there's a bit of dark blue tint in them, as if there would be something wrong with the way the light/reflections are being produced by the game (when having these .dll files in the EQ1999 folder)

If I install the dgVoodoo2.exe file, will I perhaps be able to do some changes in the graphic settings to see if I can solve this?

Should I try to mess around with my nVidia control panel if that might help?

Thanks again.

I tried various places but didn't see such glitches. I cannot start at East Cabilis, the game says it's unavaliable (try it later or sg like that).
Just to make sure, do you get these glitches with D3D12 output too?

Thanks for the reply, Dege.
Sorry for noob question, but what is D3D12 output? Is that another .dll file that I should download and copy over to my folder?

No, you just select D3D12 in the CPL General page, option 'Output API'.
Though it's only available with Win10 or later.

Thanks again, Dege.
I'm on Win7 🙁

I managed to fire up the dgVoodoo 2.76.1 control panel now and I've been messing around with some settings but without any success.

I recorded a short video to demonstrate the issue:
https://youtu.be/kBvErb58xFo

Thanks. Just to make sure, could you test it with the MS WARP renderer (option Output API)? It'll be slow but I'm curious if the appearance is the same.

Thanks for the reply, Dege.
Appearance is exactly the same, but significantly slower FPS (just to confirm the Output API change took place).

Gonna add here that I am NOT able to get the 3Dfx Watermark nor the 3Dfx Splash screen showing, so I guess that confirms Glide isn't activated?
I've downloaded the 3dfxspl2.dll and 3dfxspl3.dll and put them in the root folder of the game. As well as the three Glide dlls from the 3Dfx\x86 folder.
And I've of course checked the 3Dfx Watermark and 3Dfx Splash screen boxes in the control panel. I also downloaded the latest version (2.77) to make sure I'm updated.

Here another example in East Commonlands, near the West Freeport border.

Ok, I'll have a look at a tutorial and try to install the game because I have a feeling that the one I have is not exactly the same that we're talking about.
Btw, it's a DX game so you cannot have the 3Dfx watermark here.

Thanks, Dege.
I'm playing on the EverQuest Project 1999 server.

I followed this tutorial:

https://www.youtube.com/watch?v=mj_MMVgJ_Dk

and installed the game. I chose this server:

I created 8 different characters and explored many landscapes but didn't encounter black objects. Everything look fine, like this:

So, either the bug only comes at your specific locations or I can't reproduce it.

I've made progress!
There's something in my eqclient.ini file (it's the configuration file for the game) that is making those black textures.
I downloaded a clean install of EverQuest and I replaced my old eqclient file with the one I downloaded, and I have NO issues.
Now, of course there are tons of settings in my own eqclient file that I want to keep, so I will go through every single line in that text file and see exactly what causes it. It might help other players in the future who might encounter the same problem, so we can keep this thread alive for a while.

Until then, thanks again for the swift replies, Dege!

I have found it!
In the very beginning of my eqclient config file, in the [Defaults] section, I had an entry like this:

HardwareTnL=FALSE

Removing this, the game looks great - NO issues.

For researching/geek purpose, can you try to reproduce it by adding that line in your eqclient config file, in the [Defaults] section? Would be interesting to see if you can reproduce it.
And, as a curious person I am, do you have any idea what that entry does to the game and how/why it collides with the dgVoodoo .dll files?

All the best!

Edit: Apparently, this command tells the game to not use the Hardware Transform and Lighting features of the video card. This entry is NOT included in the original eqclient.ini file of Project 1999, so it must have been added later, probably by myself when trying to solve some screen tearing issues 3 years ago.

Thanks, that' s a nice find! Now I could reproduce and fix it.

Yes, disabled Hardware TnL (sw vertex processing) forces vertex shaders / FF pipeline to be executed on the CPU. As a "side effect", it also controls how (in what way) vertex (buffer) data is got copied to the video memory.
dgVoodoo never executes shaders on the CPU when they're invoked implicitly from the Draw calls but keeps compatibility by using sw vertex buffers (that's where I found a bug), so I don't recommend HardwareTnL=FALSE anyway.

I'm glad it got solved and happy to have contributed to something!
Thumbs up for your product and great support.