BEEN_Nath_58 wrote on 2025-04-23, 21:13:

This is fine. […]
Show full quote

crazyeyes wrote on 2025-04-23, 21:12:

Here are the settings and audio files I've been using for the last several posts. Did I miss something? I haven't been using Pla […]
Show full quote

Here are the settings and audio files I've been using for the last several posts. Did I miss something? I haven't been using Play from CD.

This is fine.

Btw I have this game too. I can check next week if you don't figure the problem out.

Just to add again, Alt+Tab and Do not notify on task switch aren't the most pleasant things for the game

Yeah, I figured that part. I was just fiddling. I turned that off. However, I did figure out that if I change the window size to 1280x960, use "Desktop center," and turn on the mouse clipper, it fixes the scaling (since native game res is 640x480, there is aliasing on 800x600), always appears in the center of my screen, and it captures my mouse. So I rather like that config over fullscreening.

Thanks for your help thus far by the way. I would not have expected this sort of charity from any community. There is no rush, I can deal with only one music track playing per mission.

crazyeyes wrote on 2025-04-23, 21:26:

BEEN_Nath_58 wrote on 2025-04-23, 21:13:

This is fine. […]
Show full quote

crazyeyes wrote on 2025-04-23, 21:12:

Here are the settings and audio files I've been using for the last several posts. Did I miss something? I haven't been using Pla […]
Show full quote

Here are the settings and audio files I've been using for the last several posts. Did I miss something? I haven't been using Play from CD.

This is fine.

Btw I have this game too. I can check next week if you don't figure the problem out.

Just to add again, Alt+Tab and Do not notify on task switch aren't the most pleasant things for the game

Yeah, I figured that part. I was just fiddling. I turned that off. However, I did figure out that if I change the window size to 1280x960, use "Desktop center," and turn on the mouse clipper, it fixes the scaling (since native game res is 640x480, there is aliasing on 800x600), always appears in the center of my screen, and it captures my mouse. So I rather like that config over fullscreening.

Thanks for your help thus far by the way. I would not have expected this sort of charity from any community. There is no rush, I can deal with only one music track playing per mission.

Sure you can make changes as you want, since dgVoodoo2 isn't in my hands and some things may need edits. LEt me know if there's something else. I will check the music issue next week

Same as the previous poster, I have no music in the game. CD image is mounted with the latest Daemon Tools and audio tracks rip via WMP with no issue. I am using the all in one installer via the PS script. Tried all the options under the CDAudio tab in DXWnd (play from CD, then Rip + use audio files after ripping) with no effect. Tracks are ripped properly with the Rip feature to a Music folder but still no luck. The CD player monitor window shows no activity in any case.

Any ideas?

Also, most of the time, but not always, upon destroying a mech, the game sort of half-crashes - all audio stops, GUI elements stop responding, all objects except terrain disappear and the game becomes completely unplayable.

That's the memory leak which I was told is fixed. It takes about 10-15 minutes
All I can suggest is see if windows 10 22h2 does it - with the installer.

Given that I played through the entire Titanium trilogy in in nov... 23? on w10, I think Microsoft broke something.

Ah, my apologies, I hadn't put those other posts together with my symptoms. Didn't mean to squawk for help on something that's a known active issue.

I'm actually on 22H2 (19045.5737). Confirmed it's definitely the memory leak issue, I consistently have the same two crash types at roughly 1.6GB of RAM (either the 'disappearing stuff' crash or the 'game stops rendering, audio keeps going for a few seconds, then everything freezes' crash).

I don't see the dxwnd shims available that are mentioned in previous posts either, guessing those got removed or moved around in this release (2.06.09.rc18) . Happy to test stuff out if I can help, I am not savvy on the finer points of a lot of these settings but I can try stuff and take methodical notes.

Update: Audio issue also fixed by a previous myne post - I had multiple CD drive emulators, the tidbit that the game/dxwnd is looking for the first ('lowest' letter) drive was the issue. Music is now playing from ripped files without issue. Apparently I need to reread this whole thread, sorry for the oversights.

@myne in the SF forum you replied back a month ago the combination Emulate9xHeap + Heap pad allocation worked.

The reason we didn't follow it through is because the Emulate9xHeap wasn't portable back then, but now it is. I think I wrote 2 weeks ago in a followup of changes you could test, so that we can finalise which "heap" method is better. Probably you didn't get a notification

The original game had Emulate9xHeap enabled as well, but we didn't consider putting it since it would complicate finding the other bugs.

@admiralsenn Yes the first drive is generally read. There are settings Hide empty drive letters in the IO tab which may help with a 2nd or later drive

admiralsenn wrote on 2025-04-28, 04:06:

I'm actually on 22H2 (19045.5737). Confirmed it's definitely the memory leak issue, I consistently have the same two crash types at roughly 1.6GB of RAM (either the 'disappearing stuff' crash or the 'game stops rendering, audio keeps going for a few seconds, then everything freezes' crash).

I meant to say unupdated.
Ie vanilla 22h2 as it was in 22h2.

BEEN_Nath_58 wrote on 2025-04-28, 05:16:

@myne in the SF forum you replied back a month ago the combination Emulate9xHeap + Heap pad allocation worked. […]
Show full quote

@myne in the SF forum you replied back a month ago the combination Emulate9xHeap + Heap pad allocation worked.

The reason we didn't follow it through is because the Emulate9xHeap wasn't portable back then, but now it is. I think I wrote 2 weeks ago in a followup of changes you could test, so that we can finalise which "heap" method is better. Probably you didn't get a notification

The original game had Emulate9xHeap enabled as well, but we didn't consider putting it since it would complicate finding the other bugs.

@admiralsenn Yes the first drive is generally read. There are settings Hide empty drive letters in the IO tab which may help with a 2nd or later drive

Yeah I haven't got around to testing. I was hoping you'd throw a single zip together with all settings and files.

myne wrote on 2025-04-28, 06:12:

BEEN_Nath_58 wrote on 2025-04-28, 05:16:

@myne in the SF forum you replied back a month ago the combination Emulate9xHeap + Heap pad allocation worked. […]
Show full quote

@myne in the SF forum you replied back a month ago the combination Emulate9xHeap + Heap pad allocation worked.

The reason we didn't follow it through is because the Emulate9xHeap wasn't portable back then, but now it is. I think I wrote 2 weeks ago in a followup of changes you could test, so that we can finalise which "heap" method is better. Probably you didn't get a notification

The original game had Emulate9xHeap enabled as well, but we didn't consider putting it since it would complicate finding the other bugs.

@admiralsenn Yes the first drive is generally read. There are settings Hide empty drive letters in the IO tab which may help with a 2nd or later drive

Yeah I haven't got around to testing. I was hoping you'd throw a single zip together with all settings and files.

I can but I would rather keep the Vogons message edit count to less else I can get locked out 😉

It's just one setting right.

I just tried with this version of the installer (Re: A comprehensive guide to install and play MechWarrior 2 on new versions on Windows.), Emulate9xHeap (using 9xheap from latest Dxwnd) and heap pad allocation enabled, still have the leak. Also tried with WAIL32.DLL MSS32.DLL SMACKW32.DLL loaded.

Unfortunately this is my main PC so I don't really have the option to roll back to a clean install of W10 22H2 for testing.

I'll stop cluttering up the thread unless you guys have a specific option you want me to test. Happy to help any way I can.

Thank you guys for all the work on this, it's a real labor of love.

admiralsenn wrote on 2025-04-28, 16:35:

I just tried with this version of the installer (Re: A comprehensive guide to install and play MechWarrior 2 on new versions on […]
Show full quote

I just tried with this version of the installer (Re: A comprehensive guide to install and play MechWarrior 2 on new versions on Windows.), Emulate9xHeap (using 9xheap from latest Dxwnd) and heap pad allocation enabled, still have the leak. Also tried with WAIL32.DLL MSS32.DLL SMACKW32.DLL loaded.

Unfortunately this is my main PC so I don't really have the option to roll back to a clean install of W10 22H2 for testing.

I'll stop cluttering up the thread unless you guys have a specific option you want me to test. Happy to help any way I can.

Thank you guys for all the work on this, it's a real labor of love.

You don't have to roll back, I had the same leak on Windows 10 as well so it is likely now a version thing. The problematic thing is now that we have a third variant: here's the setting that previously worked for myne (followup reply on next page):
https://sourceforge.net/p/dxwnd/discussion/ge … 7/?page=14#9aff

DxWnd is getting another Detours based hook, so you may consider trying that once. Set the injection mode in Hook tab, from Inject DLL to Detours. Maybe try running the game from the Dxwnd app instead of the desktop shortcut.

No guarantees yet. Additionally you can consider adding Copat./Handle Exceptions if game crashes somewhere

Tried replacing my dxwnd.dll with that one and the Detours option isn't available. Not sure if there's some other step I should be doing. DXWnd shows the updated build number.

However, some combination of that .dll and an older .ini file resulted in fixing the leak! So I am a happy MechWarrior. I'm attaching the working .ini file, this is working for me on DxWnd 2.06.10.rc4 using Titanium edition.

Notable tweaks:

• Hook tab: WAIL32.DLL MSS32.DLL SMACKW32.DLL added under additional modules per previous suggestions
• Libs tab: Safe Heap checked and Repair unchecked, Emulate Win9X heap checked, Heap pad allocation checked. Copied 9xheap.dll into the game directory manually from the installation folder (per previous discussion this was not always available so the current install script doesn't copy it).
• Various video tab and Main tab edits to make the game work in a window - while it's great to have it play in full screen, on an ultrawide the aspect ratio makes things a bit odd!

For all of my testing I am launching from within DXWnd, not the desktop shortcut, but it also works the same from the shortcut.

I'll report back if I have any other issues but this is promising. What's strange to me is I had these exact settings on a previous DxWnd build (I literally copied my .ini file over as a test 'just to see') and still had the issue. I didn't think any of the updates specifically targeted this issue but something seems to have fixed it.

One other note for weirdos like me who have their Desktop folder on other drives: I edited the install script to pull the Desktop location directly from the system, as follows (line 600 or so). Probably unnecessary for 99.9999% of people but with the number of times I tried fresh installs it was getting annoying having to make new shortcuts.

$WshShell = New-Object -comObject WScript.Shell
$DesktopPath = [System.Environment]::GetFolderPath([System.Environment+SpecialFolder]::Desktop)
$Shortcut = $WshShell.CreateShortcut("$($Desktoppath)" + '\' + (Get-Variable -Name $edition).value +".lnk")

admiralsenn wrote on 2025-04-28, 18:58:

[*] Libs tab: Safe Heap checked and Repair unchecked, Emulate Win9X heap checked, Heap pad allocation checked. Copied 9xheap.dll into the game directory manually from the installation folder (per previous discussion this was not always available so the current install script doesn't copy it).

Notably this was my setting when I tested it out in 2021. Maybe that's the best one. Keep playing, let me know if everything works out.
Edit: About the setting of Detours, use the DxWnd.exe from its latest build

Will do!

The archives attached to that SF thread only have .dlls in them. Would I have to build from source to get the .exe?

admiralsenn wrote on 2025-04-28, 19:08:

Will do!

The archives attached to that SF thread only have .dlls in them. Would I have to build from source to get the .exe?

No. Here's my package:

admiralsenn wrote on 2025-04-28, 18:58:

Tried replacing my dxwnd.dll with that one and the Detours option isn't available. Not sure if there's some other step I should […]
Show full quote

Tried replacing my dxwnd.dll with that one and the Detours option isn't available. Not sure if there's some other step I should be doing. DXWnd shows the updated build number.

However, some combination of that .dll and an older .ini file resulted in fixing the leak! So I am a happy MechWarrior. I'm attaching the working .ini file, this is working for me on DxWnd 2.06.10.rc4 using Titanium edition.

Notable tweaks:

• Hook tab: WAIL32.DLL MSS32.DLL SMACKW32.DLL added under additional modules per previous suggestions
• Libs tab: Safe Heap checked and Repair unchecked, Emulate Win9X heap checked, Heap pad allocation checked. Copied 9xheap.dll into the game directory manually from the installation folder (per previous discussion this was not always available so the current install script doesn't copy it).
• Various video tab and Main tab edits to make the game work in a window - while it's great to have it play in full screen, on an ultrawide the aspect ratio makes things a bit odd!

For all of my testing I am launching from within DXWnd, not the desktop shortcut, but it also works the same from the shortcut.

I'll report back if I have any other issues but this is promising. What's strange to me is I had these exact settings on a previous DxWnd build (I literally copied my .ini file over as a test 'just to see') and still had the issue. I didn't think any of the updates specifically targeted this issue but something seems to have fixed it.

One other note for weirdos like me who have their Desktop folder on other drives: I edited the install script to pull the Desktop location directly from the system, as follows (line 600 or so). Probably unnecessary for 99.9999% of people but with the number of times I tried fresh installs it was getting annoying having to make new shortcuts.

$WshShell = New-Object -comObject WScript.Shell
$DesktopPath = [System.Environment]::GetFolderPath([System.Environment+SpecialFolder]::Desktop)
$Shortcut = $WshShell.CreateShortcut("$($Desktoppath)" + '\' + (Get-Variable -Name $edition).value +".lnk")

Exciting development indeed... hope the memory leak problem can be resolved finally. Keep it up Mr.

Hi i've been lurking this thread for a few weeks, been encountering the memory leak bug where the hud starts to flicker and disappear and eventually crashes but i am pleased to report with admiralsenn's dxwnd .ini file i was able to play for a good 2+ hours last night without a single crash. I even unbound the shutdown override key so i was able to play without being able to exploit the infinite heat bug in Titanium edition combined with playing on hard makes it quite a thrilling experience.

ChronoReaperX wrote on 2025-04-29, 17:22:

admiralsenn wrote on 2025-04-28, 18:58:

Tried replacing my dxwnd.dll with that one and the Detours option isn't available. Not sure if there's some other step I should […]
Show full quote

Tried replacing my dxwnd.dll with that one and the Detours option isn't available. Not sure if there's some other step I should be doing. DXWnd shows the updated build number.

However, some combination of that .dll and an older .ini file resulted in fixing the leak! So I am a happy MechWarrior. I'm attaching the working .ini file, this is working for me on DxWnd 2.06.10.rc4 using Titanium edition.

Notable tweaks:

• Hook tab: WAIL32.DLL MSS32.DLL SMACKW32.DLL added under additional modules per previous suggestions
• Libs tab: Safe Heap checked and Repair unchecked, Emulate Win9X heap checked, Heap pad allocation checked. Copied 9xheap.dll into the game directory manually from the installation folder (per previous discussion this was not always available so the current install script doesn't copy it).
• Various video tab and Main tab edits to make the game work in a window - while it's great to have it play in full screen, on an ultrawide the aspect ratio makes things a bit odd!

For all of my testing I am launching from within DXWnd, not the desktop shortcut, but it also works the same from the shortcut.

I'll report back if I have any other issues but this is promising. What's strange to me is I had these exact settings on a previous DxWnd build (I literally copied my .ini file over as a test 'just to see') and still had the issue. I didn't think any of the updates specifically targeted this issue but something seems to have fixed it.

One other note for weirdos like me who have their Desktop folder on other drives: I edited the install script to pull the Desktop location directly from the system, as follows (line 600 or so). Probably unnecessary for 99.9999% of people but with the number of times I tried fresh installs it was getting annoying having to make new shortcuts.

$WshShell = New-Object -comObject WScript.Shell
$DesktopPath = [System.Environment]::GetFolderPath([System.Environment+SpecialFolder]::Desktop)
$Shortcut = $WshShell.CreateShortcut("$($Desktoppath)" + '\' + (Get-Variable -Name $edition).value +".lnk")

Exciting development indeed... hope the memory leak problem can be resolved finally. Keep it up Mr.

Can you try the dxwnd.ini from admiralsenn and the 3 files from the archive I posted a few posts back? I think if 2 got it working, you should too