49.10 Stuka STU-K5b2 or Jeep not transfered to Megemek / shown as destroyed upon return to MekHQ

[mwberlindeu]

Environment

MekHQ version: 49.10

Description
I have started a scenario from MekHQ that included several "Stuka STU-K5b2". However those aero fighters did not appear in the game (MegaMek) and were later shown as destroyed upon return to MekHQ. The other units worked well. I assume there is an issue with this unit. When I migrated from 49.9 to 49.10 I had to delete the unit and add it anew to get the campaign working (but I did not report that issue).

Files
As a recreation is rather lengthy, I have not attached any files yet. I can do on request.

[mwberlindeu]

I may add, this also with a Jeep.

[Windchild292]

We'd need files to do anything on this, namely log files from when it failed to transfer, campaign, and customs.

[mwberlindeu]

I did another check and I found the following log entries. Does this help?

21:49:30,202 ERROR [megamek.client.generator.RandomUnitGenerator] {Random Unit Generator unit populator}
megamek.client.generator.RandomUnitGenerator.readRat(RandomUnitGenerator.java:236) - The unit Stuka STU-K5b could not be found in the SLDF Heavy (2766) SLDF Royal RAT (rat_default.zip:(2766) - Liberation of Terra/Star League/Aerospace/Heavy/SLDF Heavy Aero (2766) SLDF Royal.txt)

21:49:30,235 ERROR [megamek.client.generator.RandomUnitGenerator] {Random Unit Generator unit populator}
megamek.client.generator.RandomUnitGenerator.readRat(RandomUnitGenerator.java:236) - The unit Stuka STU-K5b could not be found in the SLDF Heavy Aerospace Fighters - SLDF Royal RAT (rat_default.zip:(2786 - 2821) - First Succession War/SLDF/Aerospace/Heavy/SLDF Heavy Aerospace Fighters - SLDF Royal.txt)

21:49:30,238 ERROR [megamek.client.generator.RandomUnitGenerator] {Random Unit Generator unit populator}
megamek.client.generator.RandomUnitGenerator.readRat(RandomUnitGenerator.java:236) - The unit Stuka STU-K5b could not be found in the Terran Hegemony Heavy Aerospace Fighters - Terran Hegemony Royal RAT (rat_default.zip:(2786 - 2821) - First Succession War/Terran Hegemony/Aerospace/Heavy/Terran Hegemony Heavy Aerospace Fighters - Terran Hegemony Royal.txt)

21:49:30,240 ERROR [megamek.client.generator.RandomUnitGenerator] {Random Unit Generator unit populator}
megamek.client.generator.RandomUnitGenerator.readRat(RandomUnitGenerator.java:236) - The unit Stuka STU-K5b could not be found in the 2821 Operations Klondike Clan Heavy Aerospace RAT (rat_default.zip:(2790 - 2850) - Operation Klondike/Clans/Aerospace/Operations Klondike Clan Heavy Aerospace.txt)

21:49:30,242 ERROR [megamek.client.generator.RandomUnitGenerator] {Random Unit Generator unit populator}
megamek.client.generator.RandomUnitGenerator.readRat(RandomUnitGenerator.java:236) - The unit Stuka STU-K5b could not be found in the ?Clan (Other) Aerospace Fighters, Widowmaker Absorbtion (2834) RAT (rat_default.zip:(2834) - Widowmaker Absorbtion/Clan (Other)/Aerospace.txt)

21:49:30,244 ERROR [megamek.client.generator.RandomUnitGenerator] {Random Unit Generator unit populator}
megamek.client.generator.RandomUnitGenerator.readRat(RandomUnitGenerator.java:236) - The unit Stuka STU-K5b could not be found in the 2860 Golden Century Heavy Aerospace RAT (rat_default.zip:(2850 - 3048) - Golden Century/Aerospace/Golden Century Heavy Aerospace Post 2860.txt)

21:49:30,245 ERROR [megamek.client.generator.RandomUnitGenerator] {Random Unit Generator unit populator}
megamek.client.generator.RandomUnitGenerator.readRat(RandomUnitGenerator.java:236) - The unit Stuka STU-K5b could not be found in the 2874 Golden Century Heavy Aerospace RAT (rat_default.zip:(2850 - 3048) - Golden Century/Aerospace/Golden Century Heavy Aerospace Post 2874.txt)

21:49:30,245 ERROR [megamek.client.generator.RandomUnitGenerator] {Random Unit Generator unit populator}
megamek.client.generator.RandomUnitGenerator.readRat(RandomUnitGenerator.java:236) - The unit Stuka STU-K5b could not be found in the 2858 Golden Century Heavy Aerospace RAT (rat_default.zip:(2850 - 3048) - Golden Century/Aerospace/Golden Century Heavy Aerospace.txt)

21:49:30,405 ERROR [megamek.client.generator.RandomUnitGenerator] {Random Unit Generator unit populator}
megamek.client.generator.RandomUnitGenerator.readRat(RandomUnitGenerator.java:236) - The unit MechBuster (Standard) could not be found in the 3075 Heavy Conventional Fighters - Generic Inner Sphere RAT (rat_default.zip:(3075 - 3085) - A Time of War/Inner Sphere/Generic/Conventional Fighters/Heavy Conventional Air.txt)

21:49:30,405 ERROR [megamek.client.generator.RandomUnitGenerator] {Random Unit Generator unit populator}
megamek.client.generator.RandomUnitGenerator.readRat(RandomUnitGenerator.java:236) - The unit MechBuster (Standard) could not be found in the 3075 Heavy Conventional Fighters - Generic Inner Sphere RAT (rat_default.zip:(3075 - 3085) - A Time of War/Inner Sphere/Generic/Conventional Fighters/Heavy Conventional Air.txt)

21:49:30,409 ERROR [megamek.client.generator.RandomUnitGenerator] {Random Unit Generator unit populator}
megamek.client.generator.RandomUnitGenerator.readRat(RandomUnitGenerator.java:236) - The unit Svartalfa Ultra ProtoMech (LRM Variant) could not be found in the 3085 Clan Hells Horses Protomech Front Line RAT (rat_default.zip:(3076 - 3100) - FM 3085/Clan/Clan Hells Horses/Protomech/3085 Clan Hells Horses Protomech Front Line.txt)

21:49:30,410 ERROR [megamek.client.generator.RandomUnitGenerator] {Random Unit Generator unit populator}
megamek.client.generator.RandomUnitGenerator.readRat(RandomUnitGenerator.java:236) - The unit Svartalfa Ultra ProtoMech (LRM Variant) could not be found in the 3085 Clan Hells Horses Protomech Keshik RAT (rat_default.zip:(3076 - 3100) - FM 3085/Clan/Clan Hells Horses/Protomech/3085 Clan Hells Horses Protomech Keshik.txt)

21:49:30,411 ERROR [megamek.client.generator.RandomUnitGenerator] {Random Unit Generator unit populator}
megamek.client.generator.RandomUnitGenerator.readRat(RandomUnitGenerator.java:236) - The unit Stuka STU-K5b could not be found in the 3085 Clan Jade Falcon Heavy Aerospace Second Line RAT (rat_default.zip:(3076 - 3100) - FM 3085/Clan/Clan Jade Falcon/Aerospace/3085 Clan Jade Falcon Heavy Aerospace Second Line.txt)

[Windchild292]

I'll repeat that we will need the files, not a snippet (especially an unrelated one like this).

[mwberlindeu]

Here they are. I created them using a Jeep.

legacy.log
megamek.log
mekhq.log
entitystatus.txt

[mwberlindeu]

I noted another occasion of the same bug in 50.02. This time with a MashTruck. I will keep observing the issue and create files for a suitable test scenario once I am clearer what is happening.

[RaozSpaz]

I noted another occasion of the same bug in 50.02. This time with a MashTruck. I will keep observing the issue and create files for a suitable test scenario once I am clearer what is happening.

Simple question first. Have you played multiple battles in the same session of HQ [aka - without closing and reopening HQ]?.
If so
Have you had that unit eject or be destroyed in any of those prior battles [even if you GM restored it]

[mwberlindeu]

I noted another occasion of the same bug in 50.02. This time with a MashTruck. I will keep observing the issue and create files for a suitable test scenario once I am clearer what is happening.

Simple question first. Have you played multiple battles in the same session of HQ [aka - without closing and reopening HQ]?. If so Have you had that unit eject or be destroyed in any of those prior battles [even if you GM restored it]

I do not remember if the games in question were played in the same session. I will check and recheck with a fresh session.

The Mash Truck was not ejected, destroyed (and possibly restored) in a previous battle in the same or previous session. On the jeep I am not sure but if yes many days passed in MekHQ. I will run another test as I discovered one similar issue with another unit.

[mwberlindeu]

I just noticed the issue again with a custom unit (Vincent). The game log shows that the unit was rejected as it was illegal. However, neither MekHQ nor MegeMekLab show any reason why the unit should be illegal (it was successfully used in a previous match in version 49.19.1.)

***Server: Player Hunting Hellhounds attempted to add an illegal unit design (Vincent Corvette Mk 39bis (3055) - Hunting Hellhounds), the unit was rejected.

Vincent Corvette Mk 39bis (3055) - Hunting Hellhounds.zip

[RaozSpaz]

I noted another occasion of the same bug in 50.02. This time with a MashTruck. I will keep observing the issue and create files for a suitable test scenario once I am clearer what is happening.

Simple question first. Have you played multiple battles in the same session of HQ [aka - without closing and reopening HQ]?. If so Have you had that unit eject or be destroyed in any of those prior battles [even if you GM restored it]

I do not remember if the games in question were played in the same session. I will check and recheck with a fresh session.

The Mash Truck was not ejected, destroyed (and possibly restored) in a previous battle in the same or previous session. On the jeep I am not sure but if yes many days passed in MekHQ. I will run another test as I discovered one similar issue with another unit.

How many days pass in HQ do not matter. If a unit is rendered 'destroyed' by any means [death/abandonment/weather/whatever] and is returned to HQ, the next time it is sent to battle if HQ is not saved > closed > reloaded, then you'll run into what we call the "Ghost Unit" bug. Where MM still believes that the unit is destroyed and thus doesn't allow it to enter or deploy. And then because it doesnt exist when you return to HQ, HQ things its lost [since its not in the MUL]

[RaozSpaz]

I just noticed the issue again with a custom unit (Vincent). The game log shows that the unit was rejected as it was illegal. However, neither MekHQ nor MegeMekLab show any reason why the unit should be illegal (it was successfully used in a previous match in version 49.19.1.)

***Server: Player Hunting Hellhounds attempted to add an illegal unit design (Vincent Corvette Mk 39bis (3055) - Hunting Hellhounds), the unit was rejected.

Vincent Corvette Mk 39bis (3055) - Hunting Hellhounds.zip

This is likely a different bug and should be opened as such.

[mwberlindeu]

I noted another occasion of the same bug in 50.02. This time with a MashTruck. I will keep observing the issue and create files for a suitable test scenario once I am clearer what is happening.

Simple question first. Have you played multiple battles in the same session of HQ [aka - without closing and reopening HQ]?. If so Have you had that unit eject or be destroyed in any of those prior battles [even if you GM restored it]

I do not remember if the games in question were played in the same session. I will check and recheck with a fresh session.
The Mash Truck was not ejected, destroyed (and possibly restored) in a previous battle in the same or previous session. On the jeep I am not sure but if yes many days passed in MekHQ. I will run another test as I discovered one similar issue with another unit.

How many days pass in HQ do not matter. If a unit is rendered 'destroyed' by any means [death/abandonment/weather/whatever] and is returned to HQ, the next time it is sent to battle if HQ is not saved > closed > reloaded, then you'll run into what we call the "Ghost Unit" bug. Where MM still believes that the unit is destroyed and thus doesn't allow it to enter or deploy. And then because it doesnt exist when you return to HQ, HQ things its lost [since its not in the MUL]

I checked again with a Jeep and a MASH Truck that have not previously been used in a scenario. Thus, they could not have been destroyed before.

***Server: Player Hunting Hellhounds attempted to add an illegal unit design (Jeep), the unit was rejected.
***Server: Player Hunting Hellhounds attempted to add an illegal unit design (MASH Truck), the unit was rejected.

In the megamek log I can find an entry that may point to a wrong unit design (intro dates) for the Jeep and a wring weight for the Mash truck although logs are not glass clear.

11:14:56,239 ERROR [megamek.server.totalwarfare.TWGameManager] {Packet Pump}
megamek.server.totalwarfare.TWGameManager.receiveEntityAdd(TWGameManager.java:26452) - Standard armor has intro date of 2455
15 ICE has intro date of 2100

11:14:56,243 ERROR [megamek.server.totalwarfare.TWGameManager] {Packet Pump}
megamek.server.totalwarfare.TWGameManager.receiveEntityAdd(TWGameManager.java:26452) - Chassis: MASH Truck (self) - IS_Advanced (2671)
Movement: 5/8
Weight: 25.0 is greater than 20.0
Engine: 80 Fusion [Vehicle] 4,0
Structure: 10 (Standard) 2,0
Controls: 1,0
Heat Sinks: 2 0
Armor: 64 Standard 4,0
Turret: 0,5
Equipment:
MASH Equipment (0 ..BD 2,5
MASH Equipment (0 ..BD 2,5
MASH Equipment (0 ..BD 2,5
MASH Equipment (0 ..BD 2,5
MASH Equipment (0 ..BD 2,5
Small Laser TU 0,5
Small Laser TU 0,5

In MegamekLab I am getting a warning on the Mash truck.

It appears the weight is somehow wrong for the Mash Truck.

It appears dates are somehow wrong for the jeep.

The Stuka STU-K5b2 seems to be fine though (but this was an older issue, and I need to retest this). Possibly this will work but I do not have a Stuka STU-K5b2 on the TOE right now to test.