It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
So, running Windows 10 64-bit. Been trying everything to get Mechwarrior Titanium (and BattlePack) running with MechVM. I get as far as the menus but both versions crash whenever it tries to start a mission. Tried compatiblity modes, installing nglide, copying dplay.dll, nothing works so far.
Which error do you get? Found something in a logfile? :)
Nope, nothing. Just a hard crash to desktop.
Install or reinstall DirectX 9 on your system.

Also you may have to dig into the Windows 10 control panel and manually enable DirectPlay.
Enabling DirectPlay was how I got MechCommander 1 working on Windows 10 64bit
Nope still same thing. I've tried dgVoodoo2 but I don't think the game even tries to load the wrapper, since I don't have any 3dfx splash screen. Can't get the game to load a mission with either a 3dfx or directx wrapper. I think MW2 TT uses directx5.

I saw a thread on vogons where someone figured out that MW2 TT uses a very old version of glide which can't make calls to the dgVooodoo glide2.dll API... or something. But he said he could rewrite the dlls to redirect all glide.dll calls to glide2.dll and to do that he would need the dgVoodoo source code and it ended at a dead end there.

So I don't think its possible to run the MW2 TT or BattlePack on windows 10 or anything later than windows 98 I guess.
MechVM + the titanium versions of Mechwarrior 2 definitely worked on Windows 7 64bit.
Ordinarily I'd say skip MechVM, and try running the Titanium CDs in DOSBox, but I can't remember
how gimped the dos versions included on the titanium CDs are.


Mech2.org is the definitive resource for the Mechwarrior 2 games.
Someone on mech2.org had a similar issue with Windows 8.1 + MechVM w/ Titanium disc.
http://www.mech2.org/forum/viewtopic.php?t=1384
The fix someone in that thread came up was to use the free version of VMware Player + Win98 SE, then install the Mechwarrior games in software mode.

Mechwarrior 2 CD's are always fun to deal with, because there is roughly 7+ different CD versions for each Mechwarrior 2 series game. Some of the Mechwarror 2 CD's are hardware dependant (require the original GPU card/sound card), others are shareware versions, and others are pure DOS versions or pure Win95 versions. Overall, the pure DOS CD versions of the Mechwarrior 2 series games are superior, because they can be run in DOSBox with zero issues.
I just dug up my copies of the Mechwarrior 2: Titanium Trilogy CDs from my closet.
Going to see how DOSBox handles them.

Normally I use the DOS versions & DOSBox to play the Mechwarrior 2 series
I did some research and found out the Titanium version was a very buggy release rushed out and quickly abandoned. I wish I could get my hands on the Battlepack version, which seems to be the most complete and functional release of MW2. Anyone at GOG paying attention? Lol.

Anyway, I can't seem to get any windows version of MW2 working with MechVM, so I think the problem is MechVM itself. But that's also the only way I could install MW2 TT. So far the only success I've had is running the original version on DosBox.
Post edited April 30, 2018 by Big.Wickett
The Titanium CDs don't work in DOSBox, and MechVM , like you said, just doesn't work in Windows 10 anymore.
Best advice I have for you is: Track down the DOS CD versions of the Mechwarrior 2 games and use DOSBox.
Why are you interested in the Battlepack versions of Mechwarrior 2?


I can help you get them running in DOSBox, it's a pretty simple process.
Customized dosbox configuration script, and I would highly advise imaging your Mechwarrior 2 game CDs (because at best they are 20 years old and not easily replaced).

Not expecting to see ANY of the older Mechwarrior games to be resold, there is too many conflicts, and the current holders (PGI) of the Mechwarrior trademark & IP license is extremely unlikely to sublicense or approve anything that would tkae away interest in their Mechwarrior games, especially if the older Mechwarrior games have working in 2018 multiplayer capabilities.
Post edited April 30, 2018 by morrowslant
Yeah I can run the DOS versions in DOSbox. I just really wanted to play one of the enhanced re-releases of the original MW2, ya know, with textures, lol. The major issue with the DOS version is I can't rebind the controls. Whenever I start a mission the key binds revert back to the defaults. All I really want to change is the throttle keys but changes I make won't stick.

I also tried the Playstation version in an emulator. It's not bad, but it's hard to aim.
Post edited May 01, 2018 by Big.Wickett
Agreed, the basic textures, even maxed out in the MW2 game options, are not that great in the DOS versions of the Mechwarriors 2 games. My biggest issue with the Mechwarrior 2 games is that Ghost Bear had VRgoogle support instead of netmech. Love netmech and it's game hosting options though, don't think Mechwarrior Online offers as many tweaks for a match.

MW2 series Control scheme: I got used to it, Mechwarrior 2 uses roughly half of the keys on a standard keyboard, and definitely predates WSAD control schemes.

The game remapping the keys you already remapped: Are you using the DOSBox keymapper (Ctrl+F1) or another key mapping tool?
I have the same problem that "Big.Wickett" is reporting. However, if you check out the error log, you will find the following error information:
Faulting application name: realMW2Win.exe, version: 0.0.0.0, time stamp: 0x3513234f
Faulting module name: WINMM.dll, version: 10.0.16299.15, time stamp: 0xdcaf6b0f
Exception code: 0xc0000005
Fault offset: 0x0000374c
Faulting process id: 0x5f8
Faulting application start time: 0x01d417ed7875c0d4
Faulting application path: G:\Titanium\Mechwarrior2\realMW2Win.exe
Faulting module path: C:\WINDOWS\SYSTEM32\WINMM.dll
Report Id: 68020db0-6e50-4f26-b418-2575cfecbdcc
Faulting package full name:
Faulting package-relative application ID:
--- Info Part of Log
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: realMW2Win.exe
P2: 0.0.0.0
P3: 3513234f
P4: WINMM.dll
P5: 10.0.16299.15
P6: dcaf6b0f
P7: c0000005
P8: 0000374c
P9:
P10:

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_realMW2Win.exe_34cbbd257b3499020d68dc0fb4d253166497b 3_38894dbb_1437abd5

Analysis symbol:
Rechecking for solution: 0
Report Id: 68020db0-6e50-4f26-b418-2575cfecbdcc
Report Status: 4102
Hashed bucket:

I have not fully looked into correcting the problem but I am sure someone might. I am hoping this information could help someone else determine what the actual problem is and/or how to resolve it. I might look into it more in the future but have been distracted by a lot of other higher priority issues in my life right now. I hope this helps out.

Have a great day.