BEEN_Nath_58 wrote on 2023-08-20, 10:52:

Bug report:
https://sourceforge.net/p/dxwnd/discussion/ge … /133f/6d43/6f8b

I need that function call. Otherwise on high dpi displays the viewport size will be wrong.

I could move it over to a support library in a later build or dynamic link.

[EDIT] It's fixed and should be available in the next alpha.

How do you select the renderer in Heavy Gear 1 (the full game)?

I don't have a renderer option under "combat variables."

I tried changing DLLFILE.INI to RENDDRAW.DLL without any changes.

Installing dgvoodoo's ddraw.dll did help and the game listed Rendline as a renderer, but starting the training mission it switched back to software.

[EDIT]

Appears to be working without bilinear filtering.

[EDIT2]
Nm. Fixed.

feda wrote on 2023-08-15, 00:21:

Nvidia GTX 1060. […]
Show full quote

sharangad wrote on 2023-08-14, 03:58:

Just out of curiosity, what kind of gpu are you using? I'd like to know if this runs on amd cards. Soda has major issues on Intel hd gpus.

Nvidia GTX 1060.

Tested Heavy Gear 1 full version (1.0 and 1.1).
There are texture glitches which stop once you get closer (doesn't happen with the other renderers).
After every mission, the menu screen is black and you can't continue (not the wrapper's fault per se, since this and other issues happen with other renderers except when using D3D via DgVoodoo 2).

This is fixed. Expect it in the next alpha.

For @sharangad

While you are working in RReady, could you check if games like MechWarrior 2 or Team Apache, or any game that runs (or runs better with DxWnd) using RRedline, run fine with the DxWnd patch here: https://sourceforge.net/p/dxwnd/discussion/ge … 43/?page=3#37fa

I saw this was crashing MechWarrior 2 Titanium's every edition with RRedline, and this patch will be uploaded to the next DxWnd release 2.05.98, so if you test that patch you could know if there's a problem (and report to him)

BEEN_Nath_58 wrote on 2023-08-21, 08:45:

For @sharangad

While you are working in RReady, could you check if games like MechWarrior 2 or Team Apache, or any game that runs (or runs better with DxWnd) using RRedline, run fine with the DxWnd patch here: https://sourceforge.net/p/dxwnd/discussion/ge … 43/?page=3#37fa

I saw this was crashing MechWarrior 2 Titanium's every edition with RRedline, and this patch will be uploaded to the next DxWnd release 2.05.98, so if you test that patch you could know if there's a problem (and report to him)

Will do right after this. What's the DxWnd setting to fix the virtual memory size issue with Myth TFL?
[EDIT] Am I supposed to use with 2.0.97?

I tried it with that and get a fault in Mech Warrior 2 Mercenaries.
Interstate '76 doesn't appear to run. with both Wip19 and 20.

[EDIT2] Might need to reboot.
[EDIT3] Shutdown unknown fault. Wip19 with Mercenaries.

sharangad wrote on 2023-08-21, 11:48:

Will do right after this. What's the DxWnd setting to fix the virtual memory size issue with Myth TFL? [EDIT] Am I supposed to u […]
Show full quote

BEEN_Nath_58 wrote on 2023-08-21, 08:45:

For @sharangad

While you are working in RReady, could you check if games like MechWarrior 2 or Team Apache, or any game that runs (or runs better with DxWnd) using RRedline, run fine with the DxWnd patch here: https://sourceforge.net/p/dxwnd/discussion/ge … 43/?page=3#37fa

I saw this was crashing MechWarrior 2 Titanium's every edition with RRedline, and this patch will be uploaded to the next DxWnd release 2.05.98, so if you test that patch you could know if there's a problem (and report to him)

Will do right after this. What's the DxWnd setting to fix the virtual memory size issue with Myth TFL?
[EDIT] Am I supposed to use with 2.0.97?

I tried it with that and get a fault in Mech Warrior 2 Mercenaries.
Interstate '76 doesn't appear to run. with both Wip19 and 20.

[EDIT2] Might need to reboot.
[EDIT3] Shutdown unknown fault. Wip19 with Mercenaries.

I used wip.16 in all my tests (present in the same page) for my RReady tests since it was probably last good version.

For Myth TFL, I enabled the 4 "Limit ..." flags present in DxWnd's Compatibility tab. You can manually change the memory values in Menu bar ->Global settings ->Defaults, but probably it won't be required.

You could report the problem in games in DxWnd thread yourself. I already did that but but maybe I'll have to wait (since I am the only one reporting now and not everyone is playing Mech2)

Fresh build August 22, 2023:

https://1drv.ms/u/s!As-dKk-N73dSlWiJjnsjyFptNVzt?e=fClOWC

(MD5: 657795403cccb3c02d2c765201983cf6)

Fixes:
- Adds support for "Myth the Fallen Lords" and "Interstate '76" (I76 requires DxWnd 2.05.96). Team Apache support vastly improved.
- Major shader bug fixed (Everything is affected, especially Heavy Gear 1).
- Shader chroma keying code tweaked. Should work with Myth the Fallen Lords and Interstate '76 now.
- Changes texture clamping modes for MDK and Interstate '76. Should no longer produce corrupted textures in some levels.
- Windows 7 should no longer complain about a missing DLL.
- Team Apache's menus and loading screens should now render. Glitches still remain including not updating the screen after exiting a mission and tracking the cursor.
The menu screens are front buffer based.
- Front buffer updates should render a lot better (Team Apache menus and vHexen II loading progress bars).
- RReady deviates from the spec for Interstate '76 and no longer toggles fullscreen. DxWnd should be able to hook a bit better.
- Interstate '76 forced copyback=1 is gone. Should work much better with DxWnd.

sharangad wrote on 2023-08-22, 09:47:

Fresh build August 22, 2023: […]
Show full quote

Fresh build August 22, 2023:

https://1drv.ms/u/s!As-dKk-N73dSlWiJjnsjyFptNVzt?e=fClOWC

(MD5: 657795403cccb3c02d2c765201983cf6)

Fixes:
- Adds support for "Myth the Fallen Lords" and "Interstate '76" (I76 requires DxWnd 2.05.96). Team Apache support vastly improved.
- Major shader bug fixed (Everything is affected, especially Heavy Gear 1).
- Shader chroma keying code tweaked. Should work with Myth the Fallen Lords and Interstate '76 now.
- Changes texture clamping modes for MDK and Interstate '76. Should no longer produce corrupted textures in some levels.
- Windows 7 should no longer complain about a missing DLL.
- Team Apache's menus and loading screens should now render. Glitches still remain including not updating the screen after exiting a mission and tracking the cursor.
The menu screens are front buffer based.
- Front buffer updates should render a lot better (Team Apache menus and vHexen II loading progress bars).
- RReady deviates from the spec for Interstate '76 and no longer toggles fullscreen. DxWnd should be able to hook a bit better.
- Interstate '76 forced copyback=1 is gone. Should work much better with DxWnd.

I can confirm on wip16:
Myth TFL fixed
Interstate 76 fixed
Team Apache bettered

The only problem that remains is with vHexen II. In-game Fullscreen resolutions less that 640x480 crash the game. I can confirm that my monitor supports 320x200, 320x240x,400x300, 512x384 that the game wants.

HG1 textures still borked (especially obvious in training missions 2, 3, 4. First one is okay for some reason). Menu still black after missions.

feda wrote on 2023-08-22, 13:21:

HG1 textures still borked (especially obvious in training missions 2, 3, 4. First one is okay for some reason). Menu still black after missions.

@feda can you describe how you are running the game? I never got the black screen so I am curious.

feda wrote on 2023-08-22, 13:21:

HG1 textures still borked (especially obvious in training missions 2, 3, 4. First one is okay for some reason). Menu still black after missions.

Sorry. I only tested the first level. Will do amore testing tomorrow.

BEEN_Nath_58 wrote on 2023-08-22, 15:00:

feda wrote on 2023-08-22, 13:21:

HG1 textures still borked (especially obvious in training missions 2, 3, 4. First one is okay for some reason). Menu still black after missions.

@feda can you describe how you are running the game? I never got the black screen so I am curious.

Once you complete a level, rready switches off and the the gdi/direct draw window is either corrupt (Intel hd) or black nvidia.

The black screen problem seems to be a DirectDraw problem fixable by dgVoodoo2, DxWnd or DDrawCompat. Maybe its a generic issue.

BEEN_Nath_58 wrote on 2023-08-22, 15:53:

The black screen problem seems to be a DirectDraw problem fixable by dgVoodoo2, DxWnd or DDrawCompat. Maybe its a generic issue.

I'm using dgvoodooo2. It doesn't seem to be helping.

CopyBack=1 might help, but it's currently broken. To create an OpenGL context setpixelformt has to be called. You generally can't call SetPixelFormat more than once.

So whatever the GDI rendering expects is gone after RReady has run. I intend to fix copyback.
[EDIT2] Setting CopyBack=1 in rendition.cfg does fix the black screen with a massive drop in framerate.

[EDIT] I see the corrupted textures.

sharangad wrote on 2023-08-22, 17:05:

I'm using dgvoodooo2. It doesn't seem to be helping. […]
Show full quote

BEEN_Nath_58 wrote on 2023-08-22, 15:53:

The black screen problem seems to be a DirectDraw problem fixable by dgVoodoo2, DxWnd or DDrawCompat. Maybe its a generic issue.

I'm using dgvoodooo2. It doesn't seem to be helping.

CopyBack=1 might help, but it's currently broken. To create an OpenGL context setpixelformt has to be called. You generally can't call SetPixelFormat more than once.

So whatever the GDI rendering expects is gone after RReady has run. I intend to fix copyback.
[EDIT2] Setting CopyBack=1 in rendition.cfg does fix the black screen with a massive drop in framerate.

[EDIT] I see the corrupted textures.

With DxWnd I always had Handle Exceptions enabled like all other MECHWARRIOR 2 engine games. This fixed the black screen for the game with DxWnd

BEEN_Nath_58 wrote on 2023-08-22, 15:53:

The black screen problem seems to be a DirectDraw problem fixable by dgVoodoo2, DxWnd or DDrawCompat. Maybe its a generic issue.

Yup, Dgv2 fixes it. I previously thought it couldn't work in conjunction with RReady, but it actually does.

Ideally though, this wrapper should include its own fixes to avoid having to use extra wrappers 🤣

feda wrote on 2023-08-22, 23:08:

BEEN_Nath_58 wrote on 2023-08-22, 15:53:

The black screen problem seems to be a DirectDraw problem fixable by dgVoodoo2, DxWnd or DDrawCompat. Maybe its a generic issue.

Yup, Dgv2 fixes it. I previously thought it couldn't work in conjunction with RReady, but it actually does.

Ideally though, this wrapper should include its own fixes to avoid having to use extra wrappers 🤣

I agree with you. At some point RReady will need it's own DDraw component. But first I need a fully functional wrapper. A DDraw component would allow Interstate '76 and Myth: TFL to run independently. Maybe even upscale these games.

Heavy Gear 1 default constant fogging value fix:

https://1drv.ms/u/s!As-dKk-N73dSlWqrlXPcYGyXkQZD?e=eotpUA

MD5: 7c6771be2976016c49c1cfd79d1d03fe

This should fix the corruption in Heavy Gear 1.

I will try the fix a while later.

Btw what do you intend to do with running I76 and Mech2 directly. Mech2, as far as I know, will need patching in CPU scheduling, GDI BitBlt tweaking, some FirstFindFileA API tweaking, some 8.3 pathname tweaking, a custom heap and the most problematic - the mission loading exceptions (yes I had to manage all that when I worked on it in 2021 Q4 - 2022 Q4).

Interstate 76 has IDIV0 exceptions that MS can handle, but on my machine there are other ones too (for which I need DxWnd).

Also how do you intend to limit the FPS: for I76 is designed to run at 25FPS over which physics start breaking (notable at over 30).

feda wrote on 2023-08-22, 23:08:

BEEN_Nath_58 wrote on 2023-08-22, 15:53:

The black screen problem seems to be a DirectDraw problem fixable by dgVoodoo2, DxWnd or DDrawCompat. Maybe its a generic issue.

Yup, Dgv2 fixes it. I previously thought it couldn't work in conjunction with RReady, but it actually does.

Ideally though, this wrapper should include its own fixes to avoid having to use extra wrappers 🤣

What settings do you use to get rid of the black screen?

BEEN_Nath_58 wrote on 2023-08-23, 04:30:

I will try the fix a while later. […]
Show full quote

I will try the fix a while later.

Btw what do you intend to do with running I76 and Mech2 directly. Mech2, as far as I know, will need patching in CPU scheduling, GDI BitBlt tweaking, some FirstFindFileA API tweaking, some 8.3 pathname tweaking, a custom heap and the most problematic - the mission loading exceptions (yes I had to manage all that when I worked on it in 2021 Q4 - 2022 Q4).

Interstate 76 has IDIV0 exceptions that MS can handle, but on my machine there are other ones too (for which I need DxWnd).

Also how do you intend to limit the FPS: for I76 is designed to run at 25FPS over which physics start breaking (notable at over 30).

Missions are working well!