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

5 Jul 18

Reply #135

Offline nefo

  • Members
  • Rookie
  • *

Got all the way to the end of the original campaign and it crashes after I exit the mission debrief screen when I complete the mission. See attached for the error that popped up.

Also, you already know it's buggy, but Op4 Mission 16 (I think) is SO buggy, after completion it moved around pilots that weren't even in the mission at all. I had to clear my mech bay to work around the bug.

edit by RizZ: Waypoint bug - access violation - see here.
« Last Edit: 9 Jan 19 by RizZen »

6 Jul 18

Reply #136

Offline matthewfarmery

  • Members
  • Rookie
  • *

Yeah, it crashes for me as well, when I get to the debriefing screen, what OS are you using by any chance?

I'm using windows 7 64bit. still, RizZen wasn't able to reproduce it. so wondering if the crash is OS specific?

10 Jul 18

Reply #137

Offline nefo

  • Members
  • Rookie
  • *

I'm on OSX 10.12.5 using the PortingKit solution. I'm not sure what OS it's emulating.

10 Jul 18

Reply #138

Offline nefo

  • Members
  • Rookie
  • *

Another bug: At the end of the Expansion campaign, after the final video plays 'I think I owe you a cold one', it sticks to a black screen instead of... doing whatever it's supposed to do.

- edit by RizZ: the original game just closes the app - i dunno why ur screen isnt be closed - just close it - there is nothing coming after that video - game over.
« Last Edit: 9 Jan 19 by RizZen »

10 Jul 18

Reply #139

Offline nefo

  • Members
  • Rookie
  • *

Expansion Op3 around Mission 14, after salvaging Kotare's Turkina, it shows up as a Mad Cat in the briefing screens and only adds 75 tons to the deployment load. When you're in mission, magically it's a Turkina!

- Edit by RizZ: bug solved with v4.0 -
« Last Edit: 9 Jan 19 by RizZen »

10 Jul 18

Reply #140

Offline RizZen

  • Members
  • Ace
  • *

One more repeated bug again... and i will close this thread. The last reported REAL bug is much too long ago to leave this shit open.

You can read the thread and report THEN - but dont shit your line in this thread to blow it up. Im not tolerating this much longer.

Hey nefo: My hand will turn magically into a fist soon until people not starting to read my shit.

Oh that was a bad day - im sorry :D

General information:

- most of the recent reported bugs are already solved
- before reporting any bug - update your full versions with version 3.3

When version 3.3 is installed and running and your bugs still happening you can report.

For version 3.0 i offer no bugreport service anymore.
« Last Edit: 9 Jan 19 by RizZen »

10 Jul 18

Reply #141

Offline nefo

  • Members
  • Rookie
  • *

Rizzen, I really appreciate the incredible investment you've made here, so I'm open to admitting I've fucked up in some capacity. Lets keep it civil, please.

I'm 99% sure I'm running the 3.3 patch, see the following:

Code: [Select]
MacBook-Pro:Downloads nefo$ cd 000_MCG_Darkest_Hours_FULL_VERSION_3.0/
<<<NOTE: This is a freshly extracted 3.0 download (1.5GB)>>>
MacBook-Pro:000_MCG_Darkest_Hours_FULL_VERSION_3.0 nefo$ cd MCG\ Darkest\ Hours/
MacBook-Pro:MCG Darkest Hours nefo$ md5 00_MUpdate.fst && md5 01_PuWa.fst && md5 XRiz0204.FST && md5 XRiz0301.FST
MD5 (00_MUpdate.fst) = 00ba81b2a208a55c926f168e18dc108e
MD5 (01_PuWa.fst) = b7a43dfc310314670c689bcfc5efcb3d
MD5 (XRiz0204.FST) = b585cb2bc69d2a51000c7782dec37885
MD5 (XRiz0301.FST) = 8cb985a75eeb26d330954555aa66cc4f


MacBook-Pro:MCG Darkest Hours nefo$ cd /Applications/MechCommander\ Gold.app/drive_c/Program\ Files/MicroProse/MCX/MCG\ Darkest\ Hours/
<<<NOTE: This is the actual application directory where I run the game, all the .exes are in here>>>
MacBook-Pro:MCG Darkest Hours nefo$ md5 00_MUpdate.fst && md5 01_PuWa.fst && md5 XRiz0204.FST && md5 XRiz0301.FST
MD5 (00_MUpdate.fst) = 956aa2b6249fa51260ee29d432fad4cd
MD5 (01_PuWa.fst) = 9458087f775944bc9e98b78c925ab1b8
MD5 (XRiz0204.FST) = 7e1d2774b858f24f49a7161c9e56a13a
MD5 (XRiz0301.FST) = b8df886a58bc692b8d2f40d2c304a9d3


MacBook-Pro:MCG Darkest Hours nefo$ cd ~/Downloads/000_MCG_Darkest_Hours_3.3_Patch/MCG\ Darkest\ Hours/
<<<NOTE: This is the patch download I originally downloaded a month ago>>>
MacBook-Pro:MCG Darkest Hours nefo$ ls -al
total 2640
[email protected] 6 nefo  staff     204 Mar 26 10:15 .
[email protected] 8 nefo  staff     272 Jul 10 16:47 ..
[email protected] 1 nefo  staff  227935 Apr  3 20:45 00_MUpdate.fst
[email protected] 1 nefo  staff  524150 Apr 28 10:26 01_PuWa.fst
[email protected] 1 nefo  staff  223614 Mar 24 17:15 XRiz0204.FST
[email protected] 1 nefo  staff  369542 Mar 25 10:47 XRiz0301.FST
MacBook-Pro:MCG Darkest Hours nefo$ md5 00_MUpdate.fst && md5 01_PuWa.fst && md5 XRiz0204.FST && md5 XRiz0301.FST
MD5 (00_MUpdate.fst) = 956aa2b6249fa51260ee29d432fad4cd
MD5 (01_PuWa.fst) = 9458087f775944bc9e98b78c925ab1b8
MD5 (XRiz0204.FST) = 7e1d2774b858f24f49a7161c9e56a13a
MD5 (XRiz0301.FST) = b8df886a58bc692b8d2f40d2c304a9d3


You can see all the locations of the files above, so I'm open to admitting I pasted it in the wrong place, or copied the wrong folder. The main menu still says '3.0' in the background but I'm not sure if that is supposed to change.

For convenience, here are the 'application folder' files and their metadata:
FilenameLast ModifiedMD5 Checksum
00_MUpdate.fst   Apr 03, 2018   956aa2b6249fa51260ee29d432fad4cd
01_PuWa.fst   Apr 28, 2018   9458087f775944bc9e98b78c925ab1b8
XRiz0204.FST   Mar 24, 2018   7e1d2774b858f24f49a7161c9e56a13a
XRiz0301.FST   Mar 25, 2018   b8df886a58bc692b8d2f40d2c304a9d3

I just re-downloaded the 3.3 patch again, rechecked it, and the modified dates / MD5 checksums match up with what was already installed in the Application folder.

I skimmed the front page for bug reporting instructions and it was pretty topical, so if you have a preferred method of bug reporting (all in one post, on a separate bug tracking system, etc.) I'm happy to help out. I didn't include that I was on 3.3 or running on OSX, so my bad.

FWIW, I think I also had the same issue that matthew listed earlier in this post (http://www.nogutsnogalaxy.net/forum/index.php?topic=4431.msg26636#msg26636) -- if this is the mission you pick up Scarab in mission.

I see in the 3.3 patchnotes you said you have addressed the Turkina/MadCat issue, and the crashes after campaign completion, so do I have to delete other files elsewhere and replace with the hotfix files you provided a few months back?

Is it possible the Turkina issue is different in the expansion campaign than the original campaign where you originally fixed this?

Since I'm running on OSX, using PortingKit, and cannot control compatibility mode, is it possible there is another issue causing the campaign crash?

Edit by RizZ: In order to update your mainscreen you need to enter your Art directory. If you find ANY *.tga files in that directory - simple delete them. Newer versions of that *.tga files got implemented into game core but will only show up when there are no other versions in your DATA\ART\... directories.
Game in general ALWAYS uses files that are extracted in this directories FIRST. But my update content nowadays is compressed in FST files... - for that reason you may delete orphan files from older updates that may have been released in extracted form.
« Last Edit: 5 Feb 19 by RizZen »

13 Jul 18

Reply #142

Offline matthewfarmery

  • Members
  • Rookie
  • *

@Rizzen

Sorry for upsetting you, but this is a bug report thread is it not?

And if 2 people are having issues with the game, (and yes I am running 3.3 as well) then there must still be an issue somewhere? did you check the saves that I uploaded for that mission debriefing screen crash? as I still can't progress past op 3 mission 14 of the expansion.

You have put a lot of work into this mod, and its a great game, no mistake. but bugs will happen, even if you can't always detect them. (and I am a former beta tester for a few games and programs)

So do you want bug reports in this thread or separate posts for bugs? As dupe bug reports will or should indicate there is something wrong.

Edit, I also suspect that op 3 mission 14 could be a pilot swap issue, I read your notes on the original mission, as you lose a pilot after you complete the mission, as you couldn't add in new people to the roster, so swapping was the only way to fix the issue. So I suspect this could be the similar issue with the expansion.

here are my saves again

www.matthewfarmery.net/MCG/SAVEGAME.rar

see if the crash happens for you, if you use my saves.


Edit by Rizz:
After analyzing your savegame in detail i found out that your savegame may be corrupted. May it be that you started this savegame/campaign before some major updates? If so - i can remember making minimum one update that made older savegames corrupted like this. The reason for those corrupted savegames are the bugs this campaign had in the past. By replacing / reordering the last missions the older savegames got corrupted. But those changes where necessary to solve the last bugs remaining from the introducing process and the fact that some of those missions had some cosmetic - but annoying mistakes in it that where not corrected in 15 years.
I´m sorry for that late answer, but i promis this won´t happen again when you start the campaign from the beginning. Later i may have time to "repair" your savegame.
When other people have the same problem, i have uploaded an optimized savegame for this late mission so that people that have already reached this point don´t need to start this campaign again. Replacement... just mission 5 but better play nine missions again instead of the whole.



Edit by RizZ: This bug got solved with MCG Darkest Hours v4.0 release!
« Last Edit: 5 Feb 19 by RizZen »

29 Sep 18

Reply #143

Offline Splina

  • Rookie
  • *

helo here, im back a bit :)
great patch, nice to see that updates are still on

after a quick check i see that op5 mis 13 stil dont work..colonel Wirth still dont complete its mission when its killed :(

ill be back with more feedback
cheers ! ;)

Edit by RizZ: This bug got solved with MCG Darkest Hours v4.0 release!


Read this - for more information!
« Last Edit: 5 Feb 19 by RizZen »

8 Oct 18

Reply #144

Offline occn

  • Members
  • Rookie
  • *

I have a same issue at expansion mission OP.3 9.
After mission completed when I try to move on to the next next the game crashes and same error message pops up.
I somehow found solution I think at least.
When I read the very 1st sentence from the top it says Warrior in an assigned mech is NULL.  So I assumed the game may not be able to read/recognize the pilots from the mech bay Ready Area after the mission is completed.
I am pretty sure most of us keep the Read Area full or half full for our own convenience.
Btw the mission allows you to have only a single 45ton slot.
1. I tried my shadow cat J with a new art work mech warrior = same message pops up.
2. Tried shadow cat J with original mech warrior = same message pops up.
3. Tried a vehicle, swift (Now at this point I had to use the cheat in order to fasten up the process and there is no way to clear the mission with a vehicle)  = same message pops up.
4. Finally I REMOVED ALL the mechs from the Ready Area and began the mission with same vehicle from 3. = worked no more error messages.
5. After I cleared the mission I immediately went back to the mission and tried the mission same method as 4 but this time I used shadow cat J. = no more error messages.
Due to the error message, I have not reached your mission yet.  Your mission has more than a single slot and 45ton.  I suggest try the mission with only necessary mechs from the Ready Area.


Edit by RizZ: This bug got solved with MCG Darkest Hours v4.0 release!
Back in time there was a warrior bug (some warriorbugs) within expansion campaign. With v3.3 those got solved. With v4.0 the bugfixes got implemented into fullversion!
« Last Edit: 5 Feb 19 by RizZen »

23 Nov 18

Reply #145

Offline RizZen

  • Members
  • Ace
  • *

Okay. I have read the last reports and must say (definitely relating to the Let´s play movies on youtube) that people nowadays seem to play MechCommander different - compared to how it was MS Zone times. People judge very fast today. It is easy to just "overview" this board - recognizing my bad language (English is not my native) - and some judge: He is an autistic servant. On the first view many people don´t understand / read or focus on the words i have left here in the past years.
Many didn´t know the original game - or they forgot about it. They just see there was one guy (or many) who remastered / updatet an old retro style game.

Then they download it - when it attracts them on the first view - or they are just excited. Then they start to play. And many meet old problems then. Problems the game had from the beginning. Some minor and major bugs that are hardcoded and can´t be solved by my hands - nor others hands past the last two decades.

Many people think that i brought the game into these conditions - but sorry to disappoint you. It was not me. Time did it. The technological evolution of twenty years didn´t passed by over MechCommander without leaving scares and scratches behind. Nowadays the game can not be physically installed on a newer OS like Win10.

So when i put back my personal emotions about that - calming down and focussing on the main problem - i see there is a problem for people nowadays to play the game right. Playing it under conditions that reduce the chances to crash / bug / malfunction.

The information how to play right. How to reduce ingame lack - is here in this forum. But how may i get this information into the heads of a nowadays playing community. Only possibility left related to this maybe a list or something - an explanation under what circumstances you can really enjoy the game without crashing while doing a mission, modifying lances/mechs, managing the mechbay - just by following some general and basic rules that need to be considered when playing MechCommander 1 (basic game & expansion, user expansions & darkest hours.

23 Nov 18

Reply #146

Offline MoNrOo

  • Members
  • Rookie
  • *

Sorry to disappoint you, but simply people are too stupid. Internet give at too many uneducated the possibility to write their silly thoughts around the WWW.
I think the only solution is ignoring them.

24 Nov 18

Reply #147

Offline RizZen

  • Members
  • Ace
  • *

Deleted my own rage.
All updates and patches that where made in the past ten pages are included in version update patch v3.3. You can download them all at once with this update!
Thread closed.

___


Later i will add some information to that last post about the bugs of MechCommander in general and the technological conditions that force the user to handle the game more "specific" - stabilizing it with external conditions while playing MechCommander on Windows10.

You are free to leave single bugreports in the general forums at all. I still will answer / assist. But my work for MCG-DH v3.0 introducing process is over. My own bugs are definitely solved and many others in addition. I made the two user campaigns working that never worked before in the past two decades. Chapter closed.
« Last Edit: 6 Dec 18 by RizZen »

8 Dec 18

Reply #148

Offline RizZen

  • Members
  • Ace
  • *

My apologies to
matthewfarmery!


He definitely found a bug. Pilot Mantis is Mission Gift in this mission but available for purchase earlier. This will be fixed with final v4.0 purchase update. I will release the update seperate before Fullversion will be released. Only solution for now is to sell Mantis before Operation 3, Mission 14 starts -  and mission will end without crashing. Some skill-boosts may be lost this way but you will be able to play the campaign up to it´s ending. Again my apologies.

--- Download savegame ---
--- Operation 3, Mission 14 ---
--- from RizZen´s walkthrough ---


Pilot bug "Mantis" in Expansion merge:
The pilot becomes available in Operation 1, Mission 8 - but will be mission gift later in Op3Mis14 - therefore there will be a purchase fix, changing pilot status from "available" to "unseen" before Op3Mis14 starts. For people who "accidantly" got him ealier need to swallow the pill of selling a possibly outmaxed warrior. My bad, sorry for this.

And thank you matthewfarmery for the report - here is the seperate Purchase fix for quick-download:

PuWa.fst (for mainfolder X:\Games\MCG-DH\...)
- purchase files 06-40 updatet in order to solve "double warrior" bug (hopefully the last one)



Important notice: This bugfix and all bugfixes and resulting updates from pages above are actually implemented into and available as pre-installed full version: Version 4.0 - downloadpage

For Version 3.0 and 3.3 users i recommend downloading and installing v3.3to4.0 patch download.



My last postings in this thread
I have to apologize to all bug reporters - i have read this thread now multiple times again - and some reports - from that i thought they where posted twice - where not. So i was wrong and the reporters where right. I´m sorry for my harsh reaction - but what to say - it was a bad day - i was in a bad mood - and i said bad things. And i even can´t promise to not act like this again. Sometimes i can be really an asshole to others. I don´t want to blame anyone here neither i had any attention to hurt others. So when i was upsetting YOU - i can understand that - you didn´t upset me that day - i already was. So i hope you don´t mind - sometimes things are sh*tty.


Edit by RizZ: Download latest fullversion: MCG Darkest Hours v4.0 release!
The content of cumulative bugfix patch 4.1 you can see here!
« Last Edit: 5 Feb 19 by RizZen »