Try the dbg version of dgvoodoo and see the log if there is any error message in it. Probably something with a display mode / refresh rate that's unsupported with that monitor.

Both monitors are the exact same.

I'm wondering if it's just an issue with Windows 11.

EDIT:

Got the dbg version in use and it still doesn't work.

Where do I find the log?

I'll take a video of what it does if that will help.

jmcinvale wrote on 2024-03-16, 19:15:

Both monitors are the exact same. […]
Show full quote

Both monitors are the exact same.

I'm wondering if it's just an issue with Windows 11.

EDIT:

Got the dbg version in use and it still doesn't work.

Where do I find the log?

I'll take a video of what it does if that will help.

Run DebugView before running the game and use the debug dgVoodoo2 dlls. The debug output will be in debugview program. Log the output and send here

Got the debug done.

Wasn't exactly sure how to use debugview so I just did the whole log after clearing the screen right before starting the game and stopping the capture right after the game didn't load.

Oh my graphics card is a PNY GeForce RTX™ 4080 16GB XLR8 Gaming VERTO EPIC-X RGB™

TBH, it's weird. The game does not crash but quits. I can only see one dgVoodoo error in the log, but I don't know what it is have to do with the monitor. Maybe it's completely normal, but a log from a monitor on which the game is running is needed to compare the two.

Btw, your monitor rect is a bit weird:

100000016	4:29:26 PM	[21836] [dgVoodoo] INFO: Direct3D9 (00D07C70)     Device 0: Name: "NVIDIA GeForce RTX 4080", Description: "\\.\DISPLAY16", Monitor rect: (-1366, 3, 0, 771)

It's not aligned vertically with the other but it's offseted by 3 pixels. Maybe that? Or with Win10 your other monitor is the primary so this one does not have negative coordinates which the game might not like for some reason?
I don't know, but you can give it a go by experimentally change the order of the monitors, to have this one being the primary.

I did try it on the third monitor and same result.

Is it possible that there's a setting in DgVoodoo or my graphics card settings that I have wrong?

No, I don't think so. If the game works on Win10 with the same config then it must be something else.

Could it be something with windows 11 or maybe my graphics card?

I did notice several instances in the log of some feature being unsupported when I glanced through it today.

It should not be. But, you can compare the 2 logs coming from the working and nonworking monitors. If they are the same (dgV error appears even with the working case) then I don't have idea.

Ok I'll get a log of the working monitor and post it here tonight.