Last time I tried this game it (almost) worked for me both with Glide and D3D (on Win7...).

There is a known issue with the mouse: unusable with 'scale, keep AR' scaling modes. The mouse cursor is locked to the upper left corner.
I know what the problem is, I just don't know how to fix it without a new CPL option.

Anyway, will check it again later.

Yes, the game quits with an error message if Glide renderer is chosen.
This is a bug in dgVoodoo, in cooperating between DDraw and Glide, I fixed it. (Native DDraw + dgVoodoo Glide may work, I didn't check it.)
(As a side note, for the Glide renderer, Voodoo2 or earlier 3Dfx card must be selected in the CPL because the game assumes tiled videocard memory (2048 byte wide) and it otherwise crashes when trying to display the in-game menu in response to pressing Esc.)

I cannot skip the credits, it's true...
What is interesting, it all is independent on the renderer type (Glide, DDraw, D3D) and the scaling mode. Unemulated modes works for me.
Capturing the mouse however is not applied (it's a bug...) but in turn, the mouse cursor is fully usable for accessing the menu items, so it's a good bug after all... 😁

I remember having a font issue in directx mode via dgVoodoo in Outlaws GOG version. The messages in the top left corner of the screen were very small and illegible via dgVoodoo. Glide mode via nGlide did not have the font problem.

I've found the problem, and reworked the needed parts of the code.
I checked all the games I remembered (once/ever) having input issues and now all of them seems to be working properly:
- Outlaws (DDraw/Glide transitions still have problems but it's not an input issue)
- Croc
- Turok2
- King's Quest 8
- GTA 1 (ddraw version)

Fonts rendered with the original game (no resolution forcing):

Dege wrote:

I've found the problem, and reworked the needed parts of the code. I checked all the games I remembered (once/ever) having input […]
Show full quote

I've found the problem, and reworked the needed parts of the code.
I checked all the games I remembered (once/ever) having input issues and now all of them seems to be working properly:
- Outlaws (DDraw/Glide transitions still have problems but it's not an input issue)
- Croc
- Turok2
- King's Quest 8
- GTA 1 (ddraw version)

Fonts rendered with the original game (no resolution forcing):

I also had problems with Requiem: Avenging Angel, I wonder if that's fixed now too.

Controls seem to be fine, but it has another issue.
If forced res + forced msaa is used then menu items become black squares, it's a regression but because it worked fine with 2.53.
I want to fix it anyway.

Also, there is another issue: with emulated stretching modes, forced res the mouse cursor (game menu) doesn't move because never gets redrawn, only when the selection moves from one menu item to another.
The same issue with Settlers III.
I'd like to fix it too, somehow.

No longer seems to drop inputs, but something is still a bit off, but not sure if it's the game or dgVoodoo2, will try to figure it out a bit later, but a new problem:

That river is supposed to be less white. Attached a save game, though you can just type "olscore" until you get to the fifth level. Walk close and you'll see it, far away it will be fine.

Yes, indeed, I checked it.
Whiteness is position and view angle dependent though, I can position myself to get the waterfall to appear as it should.
Glide renderer is OK.
I'll check the reason later.

The game creates 2 textures for the waterfall and one of them is released right after it created and loaded with bitmap data.
Later, when choosing which one to render, the texture is not found by its associated texture handle, so whiteness is symptom of a missing texture.
It very seems to be an Outlaws-D3D renderer bug. BTW, I never thought that D3D renderer of Outlaws is D3D2. Good old execute buffers... 😁

Dege wrote:

The game creates 2 textures for the waterfall and one of them is released right after it created and loaded with bitmap data.
Later, when choosing which one to render, the texture is not found by its associated texture handle, so whiteness is symptom of a missing texture.
It very seems to be an Outlaws-D3D renderer bug. BTW, I never thought that D3D renderer of Outlaws is D3D2. Good old execute buffers... 😁

I knew Outlaws' Glide and D3D renderers were just post-support patches and probably not all that good, but I'm surprised they left a so huge problem, but you're right I just checked the D3D patch notes:

Known issues: * Outlaws Version 1.1 or higher is required for use with this update. * Textures may be missing from the faces […]
Show full quote

Known issues:
* Outlaws Version 1.1 or higher is required for use with
this update.
* Textures may be missing from the faces of waterfalls.

Sigh, guess there's no perfect 3D render for Outlaws.

ZellSF wrote:

Also I can't get the Glide render working at all with dgVoodoo2.

To get the Glide renderer working with dgVoodoo2, you need to copy the DLL files from both the 3Dfx and MS folders in the dgVoodoo2 distribution. I didn't really see any benefit to that over nGlide, though.

CoolGamer wrote:

I remember having a font issue in directx mode via dgVoodoo in Outlaws GOG version. The messages in the top left corner of the screen were very small and illegible via dgVoodoo. Glide mode via nGlide did not have the font problem.

You need to choose a lower resolution in olcfg.exe. Choose 640x480 for the text to be the size that it was designed. That won't actually be the resolution that the game engine runs in. The 3D engine will use the resolution that you force in dgVoodoo's control panel and the 2D overlays will use the resolution set in olcfg.exe. It's a bit weird, but that's the case. As for the illegibility, I found that that was caused by Render overlays in 3d acceleration in olcfg.exe->Direct 3D->Advanced. De-select that.

Osprey wrote:

ZellSF wrote:

Also I can't get the Glide render working at all with dgVoodoo2.

To get the Glide renderer working with dgVoodoo2, you need to copy the DLL files from both the 3Dfx and MS folders in the dgVoodoo2 distribution. I didn't really see any benefit to that over nGlide, though.

You need to read the entire conversation before replying to it. I did do everything correctly, it was a bug in the dgVoodoo2 version that Dege replied about and fixed.

The advantage is: if you don't mind messing with Borderless Gaming and changing resolution before you start the game then dgVoodoo2 can offer instant transitions between cinematics/menus and gameplay. DXGL+nGlide can do pretty good transitions too, but not as perfect as dgVoodoo2 in windowed mode.

Osprey wrote:

CoolGamer wrote:

I remember having a font issue in directx mode via dgVoodoo in Outlaws GOG version. The messages in the top left corner of the screen were very small and illegible via dgVoodoo. Glide mode via nGlide did not have the font problem.

You need to choose a lower resolution in olcfg.exe. Choose 640x480 for the text to be the size that it was designed. That won't actually be the resolution that the game engine runs in. The 3D engine will use the resolution that you force in dgVoodoo's control panel and the 2D overlays will use the resolution set in olcfg.exe. It's a bit weird, but that's the case.

Outlaws actually does some 3D correction in higher resolutions that forcing resolution via dgVoodoo2 (or nGlide) won't replicate. Being able to run in higher resolutions is the main advantage of Direct3D mode. If you set Outlaws to 640x480 and force resolution you might as well use the Glide render (which has no ugly waterfall glitches).

The Glide render actually supports 800x600, if you set it in the registry, but it's not enough to avoid glitches like this:

ZellSF wrote:

You need to read the entire conversation before replying to it. I did do everything correctly, it was a bug in the dgVoodoo2 version that Dege replied about and fixed.

That, I do, and you need to be a little more appreciative when someone's simply eager to help you. I even offered a potential solution for an issue that you didn't get an answer for, and that got ignored. I don't "need" to try to help.

OK, sorry for wasting your time, I should have actually mentioned that the bug I ran into was fixed in the latest dgVoodoo2 and that the mouse cursor missing was an notice for Dege not something I can't figure out how to work around myself (I use a utility called nomousy). If there's many games with such issues Dege might want to consider fixing it.

ZellSF wrote:

OK, sorry for wasting your time, I should have actually mentioned that the bug I ran into was fixed in the latest dgVoodoo2 and that the mouse cursor missing was an notice for Dege not something I can't figure out how to work around myself (I use a utility called nomousy). If there's many games with such issues Dege might want to consider fixing it.

Yeah, I realize now that you're only talking to Dege and not actually looking for help from others. I didn't the other day, since I'd just registered here.

Some better comparisons on forced dgVoodoo2 resolution vs higher internal Outlaws resolution:

https://www.youtube.com/watch?v=h4NbVc80D-A

So I just tried Outlaws in newer DXGL versions and waterfalls work just fine. Chances are if they work fine in DXGL, there was graphic hardware they worked properly with which is why the Direct3D render shipped with the bug. More importantly it means waterfalls can work in the Direct3D render. So can you fix it? Pretty please? It's all that's remaining to make Outlaws work perfectly with no compromises.

Also, I'm guessing you've already noticed, but apparently Outlaws is broken in newer dgVoodoo versions on AMD cards.

The thing is, I can't fix it. Last time I debugged it, it revealed that the (game) renderer releases (destroys) some of its textures before they get rendered.
Isn't it a bug in DXGL instead? I mean, DXGL may not release the texture objects when they should be released and so it works only by chance?

BTW, unfortunately I don't have an AMD card at all by now. But I see that AMD texturing problem is a growing issue.
I'd need some little app (a scene demo maybe) that it can be reproduced with, and send it to the AMD bugreport system.

If I had anything resembling a modern AMD card I would try to find something, but I don't 🙁

I should investigate if Outlaws renders correctly on any hardware.