ChronoReaperX wrote on 2024-11-01, 15:03:

Khoidoan1@hotmail.co wrote on 2024-11-01, 14:59:

Forgot to mention, updating the Dxwnd seems to have removed the memory leak issue as well. Mem seems to cap out at about 2688MB.

How do you update Dxwnd without messing with previous settings for MechWarrior 2 3DFX?

Just downloading the latest version of Dxwnd and pasting it over seemed to worked fine but then again I'm now having 186 memory error so maybe don't do that.

Khoidoan1@hotmail.co wrote on 2024-11-01, 15:36:

NVM it was working great yesterday but now everytime I try to go through the game's menus I get a fatal error that says "out of memory at 186 in D\:Titanium\code\database.cpp" which isn't even where I installed the game so IDK what is happening now.

Alright strange discovery. If you use MWinstaller as it is and run the Mercenaries 2 titanium trilogy edition. It works right up till memory failure (4 GB patch only extends time you can play). If you paste over the most recent Dxwnd, it gives you the 186 memory error but you can prevent this error by going straight to instant action and then aborting. Now all I need to do is check if that also fixes the memory issue (who knows starting and instant action and then aborting might even prevent the out of memory issue IDK).

As long as this memory leak issue isn't resolved, some missions in the Titanium Edition can't be finished. Need to use cheat code to skip those missions.

ChronoReaperX wrote on 2024-11-01, 15:03:

Khoidoan1@hotmail.co wrote on 2024-11-01, 14:59:

Forgot to mention, updating the Dxwnd seems to have removed the memory leak issue as well. Mem seems to cap out at about 2688MB.

How do you update Dxwnd without messing with previous settings for MechWarrior 2 3DFX?

There are some issues with how DxWnd on newer versions handle full screen exclusiveness when interacting with a GDI window first.
Also the DxWnd dev has been experiencing issues on his computer to even run the game (generic 0xc00000142) so it just slows down my ability to help:
https://sourceforge.net/p/dxwnd/discussion/ge … /310b/b7ba/3487

To answer your question, download the DxWnd package and copy the .dll files and the dxwnd.exe.

Khoidoan1@hotmail.co wrote on 2024-11-01, 15:36:

NVM it was working great yesterday but now everytime I try to go through the game's menus I get a fatal error that says "out of memory at 186 in D\:Titanium\code\database.cpp" which isn't even where I installed the game so IDK what is happening now.

This should be a generic memory fault. Returning to menu is an issue in newer DxWnd, like 2.06.05+ and it may be related. Could you try on an older DxWnd release, earlier than what the default package packed?
For example: this is the latest one that worked fine for me with games, so if this doesn't work, maybe try the just earlier version

ChronoReaperX wrote on 2024-11-01, 16:14:

And there is no option for shim:EmulateHeap or patch:HeapLeak or patch:SafeHeap in the "Tweaks" tab of my DxWnd.

Maybe look at the "Libs" tab, you should find HeapLeak and SafeHeap and Emulate Win9xHeap (this one might not work on Win8)

Khoidoan1@hotmail.co wrote on 2024-11-01, 23:39:

Alright strange discovery. If you use MWinstaller as it is and run the Mercenaries 2 titanium trilogy edition. It works right up till memory failure (4 GB patch only extends time you can play). If you paste over the most recent Dxwnd, it gives you the 186 memory error but you can prevent this error by going straight to instant action and then aborting. Now all I need to do is check if that also fixes the memory issue (who knows starting and instant action and then aborting might even prevent the out of memory issue IDK).

At this point, I am confused with all that is being reported: can you report your DxWnd version (Help > About) Which mw2installer did you use?

ChronoReaperX wrote on 2024-11-02, 05:47:

As long as this memory leak issue isn't resolved, some missions in the Titanium Edition can't be finished. Need to use cheat code to skip those missions.

This again confuses me, I finished 3 mission in game which worked fine, while myne completed the entire game. I think he can give the best idea of the configuration he used, and which version of the mw2installer he used. Which mw2installer did you use?

I think something may have gone wrong with the dxwnd/dgvoodoo config since here:Re: A comprehensive guide to install and play MechWarrior 2 on new versions on Windows.

I don't have access to that compuetr to get that old file. Been, do you by chance have one from then so the cfgs can be tested?

myne wrote on 2024-11-02, 07:13:

I think something may have gone wrong with the dxwnd/dgvoodoo config since here:Re: A comprehensive guide to install and play MechWarrior 2 on new versions on Windows.

I don't have access to that compuetr to get that old file. Been, do you by chance have one from then so the cfgs can be tested?

No. I think the best I can do now is test the games, it is unlikely an installation error, and see if I can reproduce the error in any DxWnd version

@ChronoReaperX @Khoidoan1@ hotmail.co

One way the game can create a memory error, or at least the HUD going away, is if you are running the game from the Desktop shortcut. The Desktop shortcut will make the game hook its "fixed elements" on window creation, which leads to things like memory structure and heap structure not being "changed" as the game wants to see, from DxWnd.

Can you confirm that the same issue occurs if the game is run from DxWnd.exe and double clicking the game?

Also is ChronoReaperX playing "MERCS3DFX-Mercs3DFX-Mercenaries 3DFX"

BEEN_Nath_58 wrote on 2024-11-02, 12:25:

@ChronoReaperX @Khoidoan1@ hotmail.co […]
Show full quote

@ChronoReaperX @Khoidoan1@ hotmail.co

One way the game can create a memory error, or at least the HUD going away, is if you are running the game from the Desktop shortcut. The Desktop shortcut will make the game hook its "fixed elements" on window creation, which leads to things like memory structure and heap structure not being "changed" as the game wants to see, from DxWnd.

Can you confirm that the same issue occurs if the game is run from DxWnd.exe and double clicking the game?

Also is ChronoReaperX playing "MERCS3DFX-Mercs3DFX-Mercenaries 3DFX"

Yes the same issue occurs when I run it directly from Dxwnd.exe (by double clicking the game's icon inside it)

The issue occurs when I'm playing Ghost Bear's Legacy Titanium Edition and Mercenaries Titanium Edition.

For the Mercenaries Titanium Edition, the CD title as it appears during the installation process of mw2installer is TITAN_MERCS-TITMERW95-Mercenaries Titanium Edition

ChronoReaperX wrote on 2024-11-02, 15:06:

Yes the same issue occurs when I run it directly from Dxwnd.exe (by double clicking the game's icon inside it) […]
Show full quote

BEEN_Nath_58 wrote on 2024-11-02, 12:25:

@ChronoReaperX @Khoidoan1@ hotmail.co […]
Show full quote

@ChronoReaperX @Khoidoan1@ hotmail.co

One way the game can create a memory error, or at least the HUD going away, is if you are running the game from the Desktop shortcut. The Desktop shortcut will make the game hook its "fixed elements" on window creation, which leads to things like memory structure and heap structure not being "changed" as the game wants to see, from DxWnd.

Can you confirm that the same issue occurs if the game is run from DxWnd.exe and double clicking the game?

Also is ChronoReaperX playing "MERCS3DFX-Mercs3DFX-Mercenaries 3DFX"

Yes the same issue occurs when I run it directly from Dxwnd.exe (by double clicking the game's icon inside it)

The issue occurs when I'm playing Ghost Bear's Legacy Titanium Edition and Mercenaries Titanium Edition.

For the Mercenaries Titanium Edition, the CD title as it appears during the installation process of mw2installer is TITAN_MERCS-TITMERW95-Mercenaries Titanium Edition

Just to speed up your process, would you be able to test the same issue with the MechVM game? If you can affirm to test it, here is the MechVM you need to install the game:
https://mechvm.org/downloads/MechVM-win32-2022-05-03.7z

Let me know once you are done, I will change DxWnd accordingly

BEEN_Nath_58 wrote on 2024-11-02, 17:58:

Just to speed up your process, would you be able to test the same issue with the MechVM game? If you can affirm to test it, here […]
Show full quote

ChronoReaperX wrote on 2024-11-02, 15:06:

Yes the same issue occurs when I run it directly from Dxwnd.exe (by double clicking the game's icon inside it) […]
Show full quote

BEEN_Nath_58 wrote on 2024-11-02, 12:25:

@ChronoReaperX @Khoidoan1@ hotmail.co […]
Show full quote

@ChronoReaperX @Khoidoan1@ hotmail.co

One way the game can create a memory error, or at least the HUD going away, is if you are running the game from the Desktop shortcut. The Desktop shortcut will make the game hook its "fixed elements" on window creation, which leads to things like memory structure and heap structure not being "changed" as the game wants to see, from DxWnd.

Can you confirm that the same issue occurs if the game is run from DxWnd.exe and double clicking the game?

Also is ChronoReaperX playing "MERCS3DFX-Mercs3DFX-Mercenaries 3DFX"

Yes the same issue occurs when I run it directly from Dxwnd.exe (by double clicking the game's icon inside it)

The issue occurs when I'm playing Ghost Bear's Legacy Titanium Edition and Mercenaries Titanium Edition.

For the Mercenaries Titanium Edition, the CD title as it appears during the installation process of mw2installer is TITAN_MERCS-TITMERW95-Mercenaries Titanium Edition

Just to speed up your process, would you be able to test the same issue with the MechVM game? If you can affirm to test it, here is the MechVM you need to install the game:
https://mechvm.org/downloads/MechVM-win32-2022-05-03.7z

Let me know once you are done, I will change DxWnd accordingly

I am never able to make the game running via MechVM.

ChronoReaperX wrote on 2024-11-03, 07:33:

BEEN_Nath_58 wrote on 2024-11-02, 17:58:

Just to speed up your process, would you be able to test the same issue with the MechVM game? If you can affirm to test it, here […]
Show full quote

ChronoReaperX wrote on 2024-11-02, 15:06:

Yes the same issue occurs when I run it directly from Dxwnd.exe (by double clicking the game's icon inside it)

The issue occurs when I'm playing Ghost Bear's Legacy Titanium Edition and Mercenaries Titanium Edition.

For the Mercenaries Titanium Edition, the CD title as it appears during the installation process of mw2installer is TITAN_MERCS-TITMERW95-Mercenaries Titanium Edition

Just to speed up your process, would you be able to test the same issue with the MechVM game? If you can affirm to test it, here is the MechVM you need to install the game:
https://mechvm.org/downloads/MechVM-win32-2022-05-03.7z

Let me know once you are done, I will change DxWnd accordingly

I am never able to make the game running via MechVM.

The game doesn't run on MechVM, I am asking if you would be able to test the game when I provide the instructions

BEEN_Nath_58 wrote on 2024-11-03, 08:14:

ChronoReaperX wrote on 2024-11-03, 07:33:

BEEN_Nath_58 wrote on 2024-11-02, 17:58:

Just to speed up your process, would you be able to test the same issue with the MechVM game? If you can affirm to test it, here is the MechVM you need to install the game:
https://mechvm.org/downloads/MechVM-win32-2022-05-03.7z

Let me know once you are done, I will change DxWnd accordingly

I am never able to make the game running via MechVM.

The game doesn't run on MechVM, I am asking if you would be able to test the game when I provide the instructions

Yes sure... I can try

ChronoReaperX wrote on 2024-11-03, 11:03:

BEEN_Nath_58 wrote on 2024-11-03, 08:14:

ChronoReaperX wrote on 2024-11-03, 07:33:

I am never able to make the game running via MechVM.

The game doesn't run on MechVM, I am asking if you would be able to test the game when I provide the instructions

Yes sure... I can try

Alright then, download MechVM from here:
https://mechvm.org/downloads/MechVM-win32-2022-05-03.7z

Install your Titanium Mercenaries, but run MechVM.exe as administrator.
After installation, go to the games folder of MechVM, then to the mw2-mercs-tt folder, and rename mercswin.exe to something else.
Copy all the files from "Install/data" folder of your CD to your installed game, but don't overwrite.
Copy all the files from "Install/16bit" folder of your CD to your installed game, again don't overwrite.

Use the attached profile in the latest DxWnd version downloaded from SourceForge. Let me know what changes (if any) you face.

Just tested it in titanium mercs
This one doesn't have a memory leak.

Re: A comprehensive guide to install and play MechWarrior 2 on new versions on Windows.

I haven't looked into the differences yet.
Alls I know is that that is stable.

I think trying to make every single version work is causing more issues than they're worth.

myne wrote on 2024-11-04, 02:59:

Just tested it in titanium mercs This one doesn't have a memory leak. […]
Show full quote

Just tested it in titanium mercs
This one doesn't have a memory leak.

Re: A comprehensive guide to install and play MechWarrior 2 on new versions on Windows.

I haven't looked into the differences yet.
Alls I know is that that is stable.

I think trying to make every single version work is causing more issues than they're worth.

If this works great, then I would better "move away" the other games, maybe have them separate settings and not have a "common" one. Can you try this game on the latest DxWnd release (dxwnd.exe and dxwnd.dll) so that I can update it without regressions

Why...?
It's working. Why fix it?

This is worth testing. It's the OLD files sdbs etc and the new install script.
Not sure why people weren't reporting issues earlier.

myne wrote on 2024-11-04, 05:22:

Why...?
It's working. Why fix it?

Other games -

myne wrote on 2024-11-04, 05:22:

Why...? It's working. Why fix it? […]
Show full quote

Why...?
It's working. Why fix it?

This is worth testing. It's the OLD files sdbs etc and the new install script.
Not sure why people weren't reporting issues earlier.

Hi guys, I tryed this attachment and got injection error on MW2 31 Titanium.

GetThreadContext Error = 5

Windows 10. Another version of installer script didnt recognize my disc image. So, what would you advise?

...maybe I just used versions that weren't the most current, but honestly I can't figure out which version is current, considering that the post at the top of the thread references another one, which points to a third one as the most current, while being edited much later than the one it points to.

Its a bit of a mess. Some people are reporting memory leaks.
So I backtracked a year.
That one seems to work with mercs.
You say it doesn't work with mw2. Ok.

Does the main one?