Author Topic:  MechCommander Gold - Darkest Hours v3.0 - Bug Reports & Solutions  (Read 4429 times)

30 Aug 17

Reply #75

Offline ilikeredheads

  • Members
  • Rookie
  • *

I have been encountering an very annoying bug that crashes the game whenever the mouse cursor touches the corner of the screen.  It doesn't happen 100% of the time but lately it has been happening more frequently.  I tried playing at resolutions lower than 1080p but to no avail.

This is the crash error popup

Quote
EXCEPTION (Access violation at 0x006B9B20)
Address  : 0x006B9B20
Location : ScenarioMap::cellPassable() +0x50
File     : G:\mcx\ai\Move.cpp(936)

Processor/Stack    EAX=0x00232EA2 EBX=0x04BE3F88 ECX=0x001CA062 EDX=0x03CF8210    Flags=0x00210212
===============    ESI=0x00004000 EDI=0x00000007 EBP=0x0018ECE4 ESP=0x0018ECD0    EIP=0x006B9B20
0x006D26FF InterfaceObject::UpdateMouseState() +0x184F L:\mcx\iface\Iface.cpp(5459)
0x006CE8BC InterfaceObject::handleEvent() +0x23FC L:\mcx\iface\Iface.cpp(3116)
0x006CA2E0 aMechBar::handleEvent() +0x50  L:\mcx\iface\Iface.cpp(894)
0x006116DC handleEvent() +0x72C           G:\mcx\gui\Asystem.cpp(3647)
0x00612A52 CheckMouse() +0x272            G:\mcx\gui\Asystem.cpp(4424)
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     


DLL Version numbers
===================
amstream.dll     - Version 6.6.7600.16385
quartz.dll     - Version 6.6.7600.16385
devenum.dll     - Version 6.6.7600.16385
dsound.dll     - Version 6.1.7600.16385
dinput.dll     - Version 6.1.7600.16385
Could not find 'd3dhalf.dll'
d3dim.dll     - Version 6.1.7600.16385
ddraw.dll     - Version 6.1.7600.16385
dplayx.dll     - Version 6.1.7600.16385
Could not find 'dplay.dll'
ntdll.dll     - Version 6.1.7600.16385
rpcrt4.dll     - Version 4.00.1073
Ir50_32.dll     - Version R.5.10.15.2.55

Information returned by Game
============================

ScenarioTime: 815.65
ScenarioTurn: 48872
MoverUpdateFreq: 000.00
TurretUpdateFreq: 000.00
WorldStateUpdateFreq: 000.00
WeaponFireUpdateFreq: 000.00
MissionAppName : MechCommander Expansion Release  Version: 02.99.07.2601 -- ae160e40_6d2b_11d5_b342_9b660c8eb532
DrawingVFXElement : mblip1
VFXType : 2

31 Aug 17

Reply #76

Offline RizZen

  • Moderator
  • Veteran
  • *

That's waypoint bug, read above. Doesn't have anything to do with your mouse movement. Solution also above.

10 Sep 17

Reply #77

Offline wherewulf

  • Members
  • Rookie
  • *

First of all, amazing work. Playing through this game has brought back so many memories (and if you could do the same for Mechcommander 2 so I could actually play it on Win10 I just might give you my first born son). I know a couple of people have already mentioned the bug after Op2Mission13 in the expansion but I just wanted to give you my crash report in case you needed more info to get it fixed. Running Windows 10 and Darkest Hours 3.0.

Quote
EXCEPTION (Access violation at 0x0060CBE0)
Address  : 0x0060CBE0
Location : aPort::frame()
File     : L:\mcx\gui\Aport.cpp(413)

Processor/Stack    EAX=0x0810F46C EBX=0x081176A0 ECX=0x00000000 EDX=0x02DBE628    Flags=0x00010202
===============    ESI=0x08898BAC EDI=0x08119DC0 EBP=0x0019F478 ESP=0x0019F1D4    EIP=0x0060CBE0
0x006D4D12 MechInventoryBlock::handleEvent() +0x172 L:\mcx\logistics\invblock.cpp(424)
0x006116DC handleEvent() +0x72C           G:\mcx\gui\Asystem.cpp(3647)
0x00612A52 CheckMouse() +0x272            G:\mcx\gui\Asystem.cpp(4424)
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:\Games\MCG Darkest Hours\MCX1024x768.EXE
Current time, date        : 16:45:23 Sunday 9/10/2017
Executable time, date     : 08:40:43 Friday 8/25/2006
User name                 :
Machine name              :
Processor                 : GenuineIntel Pentium II MMX
Operating system          :
Version                   :
Time since booted         : 79h 13m 35s
Physical memory           : 2,147,483,647 bytes  (2047 Meg)
Available physical memory : 2,147,483,647 bytes  (2047 Meg)
Swapfile size             : / bytes  (0 Meg)
Swapfile available        : / bytes  (0 Meg)
Virtual memory            : 2,147,352,576 bytes  (2047 Meg)
Available virtual memory  : 1,949,097,984 bytes  (1858 Meg)
Memory load               : 60%

PCI bus
=======

ISA bus
=======

DLL Version numbers
===================
amstream.dll     - Version 10.0.15063.0
quartz.dll     - Version 10.0.15063.0
devenum.dll     - Version 10.0.15063.0
dsound.dll     - Version 10.0.15063.0
dinput.dll     - Version 10.0.15063.0
Could not find 'd3dhalf.dll'
d3dim.dll     - Version 10.0.15063.0
ddraw.dll     - Version 10.0.15063.0
dplayx.dll     - Version 10.0.15063.0
Could not find 'dplay.dll'
ntdll.dll     - Version 10.0.15063.0
rpcrt4.dll     - Version 4.00.1073
Ir50_32.dll     - Version 10.0.15063.0

Information returned by Game
============================

ScenarioTime: 587.82
ScenarioTurn: 209529
MoverUpdateFreq: 000.00
TurretUpdateFreq: 000.00
WorldStateUpdateFreq: 000.00
WeaponFireUpdateFreq: 000.00
MissionAppName : MechCommander Expansion Release  Version: 02.99.07.2601 -- Logistics
DrawingVFXElement : actor1
VFXType : 

11 Sep 17

Reply #78

Offline RizZen

  • Moderator
  • Veteran
  • *

2/13 is out of discussion. Must be my mistake. Something is messing up the purchase files. They need an update. To introduce finished merge faster i didn´t changed the regular ID´s of purchase files in master purchase file. That seems to have implified a mistake while introducing new purchase files out of order. The only solution i can do is to rewrite all purchases in correct order and update master purchase file. Then it will be possible to finish expansion, too. My bad. I will work on this issue first when i have more time again to focus on it.

EXCEPTION (Access violation at 0x0060CBE0)

This is the only helpful information for me cause i had same crash too, still get it from time to time on certain maps. The mission where you receive falcon in regular campaign for example. When i cross the protected bridge with containers on one side and some rocketlaunchers and a wall - when my lance crosses bridge game crashes with exactly this error. Same in the first X-Ray mission where you have to get all those containers. When i cross the street in the middle of the map i get this error too. There are some more certain missions where this error occurs. It is an original error from MC.
The only solution i have is NOT to move across these areas of map. Means, not crossing the bridge i described but finding another way to extraction point. And this means NOT to cross the midstreet in first X-Ray mission but move across northside or southside of it. If necessary sending each unit seperate... - there is no way to erase this bug for me. The syntax of how MC maps are created is complicated, the coordinate system is a mess and when you open ANY map with editor there is no guarantee to edit and save it with LESS bugs than it may have had before. That´s why i made such a big workload to edit all missions for MC WITHOUT editing itself in the end. Means in spite of mission 1 - which is just a 100% rebuilt of original mission one from my side with a Mad-Cat gift - i did only to show what is possible to do. I never had the intention to change the original game, just to enlarge it, evolve it to a more comprehensive and complete version of that game i loved so much.

So Expansion campaign will get an update before december when i´m lucky with my time i can maybe have it online until september (end).
« Last Edit: 11 Sep 17 by RizZen »

12 Sep 17

Reply #79

Offline QuinnAllard

  • Members
  • Rookie
  • *

- Win 10 64bit
- darkest hours full version 3.0
- Starting menu, and prelaunch menu (mechbay, purchasing, etc) is TINY. Like 1/8th of my screen,
in game the screen isnt centered correctly and I cant move this cursor to command pilots more than a few inches.
- original campaign
- Every mission and menu
- I could give you screenshots but they wounldnt help

13 Sep 17

Reply #80

Offline RizZen

  • Moderator
  • Veteran
  • *

Play 1400x900 Maximum. Menu screen is always tiny on higher resolutions. I recommend reading the resolution notes I have added to my guide.
Screenshots would be very helpful. When you just play 1600-1050 there is no wonder you get problems. This resolution only works on certain cases. For all other cases lower resolutions have to be chosen. That's what makes MCG retro... you have to modify things before you can run it with low issues. I can't repeat that often enough as it seems.

25 Sep 17

Reply #81

Offline wherewulf

  • Members
  • Rookie
  • *

RizZen, pretty sure I'm encountering the Waypoint bug as well and haven't been able to find a work around. I know you said in an earlier reply that you posted a work around in this thread but I must be blind because I've read through this entire thread about 6 times now and still haven't found the work around.

Also, were the pilot damage files altered? I swear I can't make it through a mission without out at least half my pilots getting hurt. Mainly seems to effect the newly created pilots but even some of the original pilots, like Hunter, seem like they're made of glass. I might expect that on Hard difficulty but right now I'm doing a play-through on normal. I remember Hunter being pretty easily hurt in the original release but I've stopped taking him on missions now because every mission I take him on he ends up one point away from being killed. Maybe I just have horrible luck.

Edit: So finally found where you talk about the work around for the waypoint bug. I'm having the issue on Op5 Mission 6 just east of Objective 1. Unfortunately you're limited with where you can go on that part of the map and so far haven't been able to find a work around.
« Last Edit: 25 Sep 17 by wherewulf »

13 Oct 17

Reply #82

Offline Gunner

  • Members
  • Rookie
  • *

Minor bug - All (?) windows OS versions.

Not really a bug in this mod/version of the game, but one that has been present in every version of this game I have ever played, regardless of the computer or version of Windows OS.

Not sure what to call it but from the very first time you encounter a bridge (original game Op 1, Mis 2), the mechs stop when they get to a bridge if they cannot see the other side/end of the bridge.

This is one of the main reasons I started using the "mineeyeshaveseentheglory" cheat. It can be very hard to get the mechs to go across the bridge if the other end is covered by the "fog of war."

Once I got your remastered version up and running (GREAT job there and many thanks for breathing new life into an old favorite game!), I almost could not complete Op1, Mis 1 because my mechs kept refusing to go across the bridge. It took repeated effort to get them to cross it.

IF they can see the other end/side, there seems to be no problem, just click on the terrain at the other end and away they go, but if it is blacked out (especially on a long bridge such as this one), it can be a real PITA to get them to even try to cross it.

Not really sure if this is something which can be repaired/fixed internally, or if another method is needed (leave a small clear spot at the other end of the bridge?).
« Last Edit: 23 Oct 17 by Gunner »
There are two rules for success:
1.  Never tell everything you know.

13 Oct 17

Reply #83

Offline Gunner

  • Members
  • Rookie
  • *

Ran into another one (Win 7- 64 bit OS) while playing the basic campaign. (Sorry for the sketchy details, but I just started the game again and replayed the mission)

The mission was the one where you have to get the sensor control, then kill the admin building, then go up the hill to the extraction point - right into the teeth of a Mad Cat, two Hunchbacks and five Bulldogs.

I dropped a camera drone behind all of those, and of course, they all chased it. When they did hit it, the screen went black and the game crashed to the desktop with one of those "something violated something" messages. 

Like I said, I just ignored it and restarted the game, so I can't remember exactly what it said, but when they shot the drone (LRM from the Mad Cat, IIRC), the game just stopped.

Also, I too have experienced the game crash in the mission with Osis' Masakari - BUT - it has done that in the vanilla game too - before I even heard of Darkest Hours, so I don't believe DH is the cause. 

I usually just have my mechs target his leg (and take the beating he dishes out) until another mech can capture that seventh salvage rig and then the mission ends. I don't get the Masakari that way, but at least the game doesn't crash.
There are two rules for success:
1.  Never tell everything you know.

15 Oct 17

Reply #84

Offline Gunner

  • Members
  • Rookie
  • *

Odd happening at the start of a mission. Thunder starts complaining about being out of ammo. Since A) he is in a laser and SRM equipped mech and B) no shot has been fired yet, this does seem a bit odd. Below is a composite data pic of his mech.

(Sorry for the weird colors. This is the best Irfanview could do with the capture.)


As you can see, he is out of LRM ammo, which is consistent with the fact that THERE ARE NO LRMS FITTED ON THIS MECH. Not sure why this is happening unless the game somehow figures a Mad Cat must ALWAYS be fitted with LRMs, so when it couldn't find any ammo for them, it has the pilot complain about being "out of ammo."
« Last Edit: 15 Oct 17 by Gunner »
There are two rules for success:
1.  Never tell everything you know.

15 Oct 17

Reply #85

Offline Gunner

  • Members
  • Rookie
  • *

Taking a break from the game for a short bit. Game keeps crashing on one mission. Briefing header says "Linchpin 04PRDNO2 - Downtown Lights." (Where Hitman joins the crew)

Lots of weirdness on this one, like Captain Ward's Mad Cat has all LRMs, but NO ammo. AND she fired PPCs at one of my mechs even though the data screen says she has none. (Mech "health" is an empty bar, no green, yellow or red.)

Then there is Kotare's Turkina. It shows two C-SRMs mounted, but has no ammo readout, BUT it does show that the ammo for his LRMs is at zero - except, he doesn't have any LRMs fitted to his Turkina. The briefing lists killing his Turkina as a secondary (not required) task, but he will find you and start a fight. The only problem with that is, killing his Turkina crashes the game with an error message of "Bad Ammo Index In Ammo Explosion." (I wrote it down this time)  :D

Come to think of it, I believe that is the same message you get in the stock game when Osis' Masakari blows up. (And also crashes the game)

Anyway, I finally had to use a cheat to bypass this mission or I could go no further. I hope this can be fixed as it looks like a fun mission, but for now...
« Last Edit: 15 Oct 17 by Gunner »
There are two rules for success:
1.  Never tell everything you know.

16 Oct 17

Reply #86

Offline Gunner

  • Members
  • Rookie
  • *

AAAAARRGH!!! Same thing a few missions later when you have to use Outlaw and Blaze to kill the orbital gun. Osis' Masakari is guarding it and as soon as they kill his Masakari, the game crashes with "Bad Ammo Index In Ammo Explosion!" Looks like another mission to bypass until it can be fixed.

A suggestion, if I may? It would seem that these "special" Commander mechs are the problem. Possibly it might be better to just use a stock version of the mechs? Very frustrating to be playing along and then crash every time we run into one of these "specials."

EDIT/Additional thought: Any possibility that the previous post  about bad ammo readouts is related to the "Bad Ammo Index In Ammo Explosion!" crashes. Possible that it isn't the "special" mechs that are the problem, but the ammo readouts themselves?
« Last Edit: 16 Oct 17 by Gunner »
There are two rules for success:
1.  Never tell everything you know.

22 Oct 17

Reply #87

Offline Tyler799

  • Rookie
  • *

Windows 10
Darkest Hours V3.0

I'm having a couple problems. The main one is that I don't know how to exit a mission. In the old MCG, it automatically exited once you had completed all mission objectives. But in Mission 1, Op 1, I'm stuck. I complete the main 3 objectives but it never goes to the "win screen". What do I do to exit?

As well, the game seems to run fine with both the ISO mounted and NOT mounted, which is super strange.

The executable I run (the 1920x1080 one) also automatically removes its own compatibility settings. (Like XP SP2, Administrator mode, or reduced color mode). My only fix was to set it to read-only. I needed to set those because without them, the game window gets really weird. I was getting large chunks of the screen to the bottom and right that I couldn't move the cursor into.

As well, when I move my cursor to the top or left, the screen moves to follow, but not in the bottom or right sides.

In 1920x1080, I also notice sometimes the corners of the screen freak out a little and have visual artifacts.

Finally, the main menu and pre-game screens are all really tiny compared to the actual mission screen.

23 Oct 17

Reply #88

Offline Gunner

  • Members
  • Rookie
  • *



Finally, the main menu and pre-game screens are all really tiny compared to the actual mission screen.

It's mentioned elsewhere (honestly, I forget where) that this is a limitation of some kind due to the game's original screen resolution (640 x 480 ?) files. So, no matter which newer screen resolution you use for the game, those two screens will be tiny by comparison.

EDIT: Actually, here it is from the previous page:

http://www.nogutsnogalaxy.net/forum/index.php?topic=4429.msg25876#msg25876

Only ingame resolution is full screen, menu design was done for 640x480 only. There are no possibilities to make menu resolution optional.

« Last Edit: 23 Oct 17 by Gunner »
There are two rules for success:
1.  Never tell everything you know.

24 Oct 17

Reply #89

Offline Gunner

  • Members
  • Rookie
  • *

Another thing that needs mentioning.

I had to remove all (I think) of the new music files - not because I didn't like them, but because, even with the music set at the lowest setting in 'Preferences', they were so LOUD I could not hear what was going on in-game. The music overrode the mech pilots and Betty completely.

Which is a shame because I really do like some of it. Especially 'music22'. Which movie or game is that from? If there was a way to lower their overall volume in-game, I would gladly put them back in. There are two which I suspect as being from the R***cop movie series  ;) .
« Last Edit: 24 Oct 17 by Gunner »
There are two rules for success:
1.  Never tell everything you know.