On newer operating systems Mechcommander Gold can occassional have issues with corrupted textures in the main menu. When you start Mechcommander Gold the colours may display incorrectly, which will cause your game menu to look something like this:
To fix the colour/texture issue you can either put the game into windowed mode and then back to fullscreen using alt + enter or follow the steps below if you want a more permanent solution:
- Create a shortcut to MCX.exe.
- Disable desktop composition. Right click on the shortcut and select properties. Under the compatibility tab select “Disable desktop composition” and click apply (the issue is caused by having a Windows 7 Aero theme active).
- Start the game from the shortcut.
*NOTE* If you can’t get around it don’t worry, this colour/texture issue only appears to be a problem in the game menu and the colours go back to normal once you start a mission.
If you’ve followed the above steps and are still having issues with the Mechcommander Gold corrupted textures issue, please post in the comments below. To increase your chances of a solution being found include as much detail as possible (which version of the game you’re running, what operating system you have, what video card you have and steps to reproduce the issue). Screenshots are also very useful!
I got this:
ASSERT (00000005 – could not open scenario file )
Address : 0x006F6F2E
Location : No .PDB file found
File : No .PDB file found
Stack
=====
0x0072B7F2 Mission::StartScenario() +0xD2 L:\mcx\mission\mission.cpp(1253)
0x006DCD97 BriefingScreen::handleEvent() +0xB27 L:\mcx\logistics\logbri.cpp(1011)
0x006116DC handleEvent() +0x72C G:\mcx\gui\Asystem.cpp(3647)
0x006128EA CheckMouse() +0x10A G:\mcx\gui\Asystem.cpp(4378)
0x00615846 aCallback::exec() +0x16 G:\mcx\gui\Asystem.cpp(6142)
0x0061455C aSystem::run() +0xCC G:\mcx\gui\Asystem.cpp(5407)
0x00610EE1 RealWinMain() +0x301 G:\mcx\gui\Asystem.cpp(3081)
0x0075F82A WinMain() +0xCA L:\mcx\rmain.cpp(74)
0x00762CF2 WinMainCRTStartup() +0xCE
Machine Details
===============
Executable name : D:\MCX.EXE
Current time, date : 16:49:36 Friday 12/19/2014
Executable time, date : 22:02:58 Monday 7/26/1999
User name :
Machine name :
Processor : GenuineIntel Pentium II MMX
Operating system :
Version : 4.10.2222
Time since booted : 54h 7m 26s
Physical memory : 267,862,016 bytes (255 Meg)
Available physical memory : 235,843,584 bytes (224 Meg)
Swapfile size : 1,879,617,536 bytes (1792 Meg)
Swapfile available : 1,860,378,624 bytes (1774 Meg)
Virtual memory : 2,143,289,344 bytes (2044 Meg)
Available virtual memory : 1,946,619,904 bytes (1856 Meg)
Memory load : 5%
PCI bus
=======
(Version ) by
(Version ) by
(Version ) by
(Version ) by
(Version ) by
(Version ) by
(Version ) by
(Version ) by
(Version ) by
(Version ) by
(Version ) by
(Version ) by
(Version ) by
(Version ) by
(Version ) by
(Version ) by
ISA bus
=======
DLL Version numbers
===================
amstream.dll – Version 6.6.9600.16384
quartz.dll – Version 6.6.9600.16384
devenum.dll – Version 6.6.9600.16384
dsound.dll – Version 4.07.00.0700
dinput.dll – Version 4.07.00.0716
Could not find ‘d3dhalf.dll’
d3dim.dll – Version 4.07.00.0700
ddraw.dll – Version 4.07.00.0700
dplayx.dll – Version 4.07.00.0700
Could not find ‘dplay.dll’
ntdll.dll – Version 6.3.9600.17031
rpcrt4.dll – Version 4.00.1073
Ir50_32.dll – Version 6.3.9600.16384
Information returned by Game
============================
ScenarioTime: 000.00
ScenarioTurn: 0
MoverUpdateFreq: 000.00
TurretUpdateFreq: 000.00
WorldStateUpdateFreq: 000.00
WeaponFireUpdateFreq: 000.00
MissionAppName : MechCommander Expansion Release Version: 02.99.07.2601 — Logistics
DrawingVFXElement :
VFXType :
still wont work, starting the mission has the same colour issues also
I followed the advice at the base post of this thread; when hitting alt + Enter, it will go into windowed mode and that has normal graphics, but alt + Enter again brings you back to the same corrupted textures. This happens whether run from a shortcut [as above] or not.
Hmm that’s unexpected. It worked on two of my machines so I assumed it was a general fix, but if it’s not working for you it might only be a valid fix on some machines/OS version.
What graphics card are you using and what version of Windows are you on?
>> Twitter @alexgophermix