New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Array Index out of Bounds (Appears related to BA) 0.43.1 #372
Comments
Hello, The save file was created using 4.30, and neither 4.30 nor 4.31 can open it. I have more save files going bak but the most recent one I can still open is the last one I made before purchasing BA units using the AtB personnel market (which adds BA pilots and a BA unit to the roster with one click). |
What's happening here is that some of the equipment does not have its location set properly. Instead of being assigned to a particular trooper, its location is set to none. That much comes from the log file. The campaign file tells me which equipment and which units, but I haven't been able to reproduce it or find any way for it to have been changed to the incorrect value. I may be grasping at straws here, but knowing more about what led up to this should at least help me focus the investigation.
|
Hello, 1: Yes, see below (point 6) |
I've played around for a bit with MekHQ 0.4.31 New campaign, AtB, default settings. It appears I can reliably reproduce the issue by refitting BA units? |
I sure hope you're not using 0.4.31... there never was such a MekHQ version. I'm guessing you mean 0.40.31? Anyway, BA have never been fully implemented in MekHQ. It's a work in progress, but expect them not to work correctly and to cause issues like this. I realize I've been telling people this for the past 3 or 4 years, but it's still true. We're working on it, but we advise against using BA outside of just playing around; as they're not in a suitable state for most ongoing campaigns. At any rate, the bugs are definitely being looked at and worked on by the team. If you search around on both the GH tracker and the old SF tracker, you'll likely find a couple other bugs about them. |
Best advice if you want to keep using them anyway. Don't salvage them, don't repair them. Manually add, remove, and deduct the cost for the repairs. This should keep you from having another error like this and will also allow for a smoother usage of BA. |
I haven't been able to create any problems, nor have I seen any problems from repairing or salvaging. It is apparent that this is a bug caused by refits, which I will take a look at. If people don't attempt to use BA normally and report problems it's unlikely that we'll ever get them working properly. So as @Dylan-M said, don't depend on them and use them at your own risk, but please test them and report problems. |
Since it's pretty obvious that it's caused by refits, I'm going to close this one as a duplicate of #317 and work through the refit code to find the cause. Here is a fixed campaign file. |
From this post on the forums:
http://bg.battletech.com/forums/index.php?topic=57002.msg1311231#msg1311231
I'm having some trouble in 4.30 and 4.31. Specifically, it appears that for me the old bug about Battle Armour breaking the save file has returned.
I.e. taking BA into mission and recovering it, or salvaging it, and then saving results in a save file that can't be loaded again. According to a search of the bug tracker, this was meant to be resolved years ago.
Does anyone else have a similar experience in 4.3/4.31?
mekhqlog.txt
Stack Trace:
The text was updated successfully, but these errors were encountered: