@myne there is a major flaw in the profile creation mechanism:

• Some games prefer to be run with single process affinity for stability. Some don't, such as Titanium. However the profile creation mechanism sets all games to NOT use single process affinity
• Win95 31st century combat is better without disabling DDSCL_EXCLUSIVE, while Mercenaries and GBL run better when they are disabled. However the profile creating assigns the same thing to every one.
• The Desktop screen setting is set for Titanium games only, but it also takes into effect in Win95 games too, leading them to not return to their windowed shell and instead stuck in the fullscreen mode.
• Some issues related to MechLab

Ok...
But you configured the profiles?
I just applied them with the installer

myne wrote on 2024-03-19, 10:11:

Ok...
But you configured the profiles?
I just applied them with the installer

Yes there are differences in profiles of every game. However installer just installs a common one on the same game.

+ I found another error that may correspond to the registry in Mercenaries: the clickable areas in Mercenaries have a text which is not displayed when the PS installer is used, similarly the movies are disabled.

If you want, I can send all the profiles individually.

Huh? There are at least 3 profiles you made and are in the installer.

Eg $compatpatch="mech2startupfix.sdb"

myne wrote on 2024-03-19, 11:34:

Huh? There are at least 3 profiles you made and are in the installer.

Eg $compatpatch="mech2startupfix.sdb"

Dxwnd profiles, not sdb patches-

Oh. Right.
So it's not a major issue with the installer, it's new settings for dxwnd you've discovered that work better on different versions.

Probably best to upload the various configs here, and let users sort it out.
I'll note that the only 2 people that seem to care are you and I, so... I'm not convinced it's worth the effort to update the installer.
All the issues reported so far are just editions that weren't originally in the list.

No one's commented on the issues you're noticing.
Maybe they remember how flaky it was 30 years ago and are just dealing with it like we did then?
Maybe they fire it up for 5 mins, get their nostalgia fix, and quit?
Maybe they're just moving to titanium when they have issues because it has been proven to the finish?

No idea. No one's commenting once their edition is installing.

myne wrote on 2024-03-19, 23:56:

Oh. Right.
So it's not a major issue with the installer, it's new settings for dxwnd you've discovered that work better on different versions.

Different engines, different games, of course different settings. Many of them are already there in the first post's attachment.

myne wrote on 2024-03-19, 23:56:

Probably best to upload the various configs here, and let users sort it out.

Okay, but how for "mw2installer.rar"?

myne wrote on 2024-03-19, 23:56:

All the issues reported so far are just editions that weren't originally in the list.

Which issues? The ones I said yesterday? These games were already in the list from the start

myne wrote on 2024-03-19, 23:56:

Maybe they remember how flaky it was 30 years ago and are just dealing with it like we did then?
No idea. No one's commenting once their edition is installing.

No it was less flaky then I reported to be. with the config the installer installs

myne wrote on 2024-03-19, 23:56:

Maybe they fire it up for 5 mins, get their nostalgia fix, and quit?
Maybe they're just moving to titanium when they have issues because it has been proven to the finish?

Only true opinion

These are the two DXW files you put in the zips in the first post - which as best I understand builds the DXWind ini file.
(I used titanium v2)

There are no notable differences except possibly coord0 which I don't know what it does.

myne wrote on 2024-03-20, 08:25:

These are the two DXW files you put in the zips in the first post - which as best I understand builds the DXWind ini file. (I us […]
Show full quote

These are the two DXW files you put in the zips in the first post - which as best I understand builds the DXWind ini file.
(I used titanium v2)

dxwdiffs.JPG

There are no notable differences except possibly coord0 which I don't know what it does.

There were more changes, I went through the previous files and noticed some got other settings used as well (for eg: GBL settings in another installer). But one setting isn't enough for all.

Firstly I would need to declare that all Titanium games use the same profile, Win95 games all need different ones, the proprietary games like 3dfx interactive and d3d mercs also have minor differences.

What do you propose then?

Will the first step is to share the damn configs 🤣
Like I said above. Let the users sort it out, and I'll get to integrating it if/when I find time

myne wrote on 2024-03-20, 21:48:

Will the first step is to share the damn configs 🤣
Like I said above. Let the users sort it out, and I'll get to integrating it if/when I find time

fixed the Mercenaries and GBL issues.

Probably tomorrow I will send everything

BEEN_Nath_58 wrote on 2024-03-23, 21:48:

myne wrote on 2024-03-20, 21:48:

Will the first step is to share the damn configs 🤣
Like I said above. Let the users sort it out, and I'll get to integrating it if/when I find time

fixed the Mercenaries and GBL issues.

Probably tomorrow I will send everything

+ got battlepack working too. They contain some pesky resolution bugs, achievable in original HW too so they were game bugs.

Although I get a "negative thread" error on mission exit but it doesn't harm the gameplay so its manageable

BEEN_Nath_58 wrote on 2024-03-23, 22:13:

BEEN_Nath_58 wrote on 2024-03-23, 21:48:

myne wrote on 2024-03-20, 21:48:

Will the first step is to share the damn configs 🤣
Like I said above. Let the users sort it out, and I'll get to integrating it if/when I find time

fixed the Mercenaries and GBL issues.

Probably tomorrow I will send everything

+ got battlepack working too. They contain some pesky resolution bugs, achievable in original HW too so they were game bugs.

Although I get a "negative thread" error on mission exit but it doesn't harm the gameplay so its manageable

Meanwhile Mech2 Mercs 3DS broke: the game hangs when releasing the D3D session. Please wait again.

myne wrote on 2024-03-20, 21:48:

Will the first step is to share the damn configs 🤣
Like I said above. Let the users sort it out, and I'll get to integrating it if/when I find time

Hi myne.... it is me again.

Ok now I have identified the category of the crash which I've experienced when playing the Titanium Edition (3DFX). It happened during the last wave of enemies in Mission 02 (Defend on Mannedorf) of MechWarrior 2: Ghost Bear's Legacy.

When the last 2 enemy mechs approaching the base on the icy planet, my HUD becoming "empty", malfunctioned and no sound whatsoever. Then if I'm lucky when I try to move the mouse, I could see kinda notification on the screen above, text in green which say "Memory is running low - strange things may happen". When you pressed ESC, nothing happened, it just crash.

Some missions in MechWarrior 2 Mercenaries Titanium Edition (3DFX) also share the same symptom during gameplay (usually at the end of/ in the middle of a mission) but I couldn't remember which mission (I will check it later). I think it gotta do with memory usage/ allocation via DXWND or DGVOODOO 2 wrapper used.

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

Hi myne.... it is me again. […]
Show full quote

myne wrote on 2024-03-20, 21:48:

Will the first step is to share the damn configs 🤣
Like I said above. Let the users sort it out, and I'll get to integrating it if/when I find time

Hi myne.... it is me again.

Ok now I have identified the category of the crash which I've experienced when playing the Titanium Edition (3DFX). It happened during the last wave of enemies in Mission 02 (Defend on Mannedorf) of MechWarrior 2: Ghost Bear's Legacy.

When the last 2 enemy mechs approaching the base on the icy planet, my HUD becoming "empty", malfunctioned and no sound whatsoever. Then if I'm lucky when I try to move the mouse, I could see kinda notification on the screen above, words in green say "Memory is running low - strange things may happen". When you pressed ESC, nothing happened, it just crash.

Some missions in MechWarrior 2 Mercenaries Titanium Edition (3DFX) also share the same symptom during gameplay (usually at the end of/ in the middle of a mission) but I couldn't remember which mission (I will check it later). I think it gotta do with memory usage/ allocation via DXWND or DGVOODOO 2 wrapper used.

The games work without dgVoodoo2, you could eliminate one and try what happens

BEEN_Nath_58 wrote on 2024-06-11, 04:21:

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

Hi myne.... it is me again. […]
Show full quote

myne wrote on 2024-03-20, 21:48:

Will the first step is to share the damn configs 🤣
Like I said above. Let the users sort it out, and I'll get to integrating it if/when I find time

Hi myne.... it is me again.

Ok now I have identified the category of the crash which I've experienced when playing the Titanium Edition (3DFX). It happened during the last wave of enemies in Mission 02 (Defend on Mannedorf) of MechWarrior 2: Ghost Bear's Legacy.

When the last 2 enemy mechs approaching the base on the icy planet, my HUD becoming "empty", malfunctioned and no sound whatsoever. Then if I'm lucky when I try to move the mouse, I could see kinda notification on the screen above, words in green say "Memory is running low - strange things may happen". When you pressed ESC, nothing happened, it just crash.

Some missions in MechWarrior 2 Mercenaries Titanium Edition (3DFX) also share the same symptom during gameplay (usually at the end of/ in the middle of a mission) but I couldn't remember which mission (I will check it later). I think it gotta do with memory usage/ allocation via DXWND or DGVOODOO 2 wrapper used.

The games work without dgVoodoo2, you could eliminate one and try what happens

I couldn't start the game without DGVOODOO 2.

I installed the game via Myne's all in one installer in which packaged with DGVOODOO 2 inside it.

ChronoReaperX wrote on 2024-06-11, 07:14:

BEEN_Nath_58 wrote on 2024-06-11, 04:21:

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

Hi myne.... it is me again. […]
Show full quote

Hi myne.... it is me again.

Ok now I have identified the category of the crash which I've experienced when playing the Titanium Edition (3DFX). It happened during the last wave of enemies in Mission 02 (Defend on Mannedorf) of MechWarrior 2: Ghost Bear's Legacy.

When the last 2 enemy mechs approaching the base on the icy planet, my HUD becoming "empty", malfunctioned and no sound whatsoever. Then if I'm lucky when I try to move the mouse, I could see kinda notification on the screen above, words in green say "Memory is running low - strange things may happen". When you pressed ESC, nothing happened, it just crash.

Some missions in MechWarrior 2 Mercenaries Titanium Edition (3DFX) also share the same symptom during gameplay (usually at the end of/ in the middle of a mission) but I couldn't remember which mission (I will check it later). I think it gotta do with memory usage/ allocation via DXWND or DGVOODOO 2 wrapper used.

The games work without dgVoodoo2, you could eliminate one and try what happens

I couldn't start the game without DGVOODOO 2.

I installed the game via Myne's all in one installer in which packaged with DGVOODOO 2 inside it.

Okay I didn't realise it's the Titanium Edition.
Well you can try launching the game Directly from the dxwnd.exe application by double clicking the entry there. See if it makes sense

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

Hi myne.... it is me again. […]
Show full quote

myne wrote on 2024-03-20, 21:48:

Will the first step is to share the damn configs 🤣
Like I said above. Let the users sort it out, and I'll get to integrating it if/when I find time

Hi myne.... it is me again.

Ok now I have identified the category of the crash which I've experienced when playing the Titanium Edition (3DFX). It happened during the last wave of enemies in Mission 02 (Defend on Mannedorf) of MechWarrior 2: Ghost Bear's Legacy.

When the last 2 enemy mechs approaching the base on the icy planet, my HUD becoming "empty", malfunctioned and no sound whatsoever. Then if I'm lucky when I try to move the mouse, I could see kinda notification on the screen above, text in green which say "Memory is running low - strange things may happen". When you pressed ESC, nothing happened, it just crash.

Some missions in MechWarrior 2 Mercenaries Titanium Edition (3DFX) also share the same symptom during gameplay (usually at the end of/ in the middle of a mission) but I couldn't remember which mission (I will check it later). I think it gotta do with memory usage/ allocation via DXWND or DGVOODOO 2 wrapper used.

I had a crash on one map because the copy I had was corrupt. Not sure if yours is the same issue, but these discs are 30 years old.

Myne, can you try your changes in your installer with DxWnd 2.06.04

I'll give it a go.
It sure is a pain of a game.