Skip to content
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

Trains not being picked up by SL-MOD #69

Open
SoWphilstyle opened this issue Jan 9, 2022 · 3 comments
Open

Trains not being picked up by SL-MOD #69

SoWphilstyle opened this issue Jan 9, 2022 · 3 comments
Assignees

Comments

@SoWphilstyle
Copy link

Various train assets are not being picked upy by SL-MOD. Here is evidence from the DCS log, with SL-MOD errors:

2022-01-09 08:30:44.153 INFO    Scripting: event:type=shot,initiatorPilotName=No.54 Philstyle,t=464.412,weapon=SC 50,initiatorMissionID=7,
2022-01-09 08:30:44.775 INFO    Scripting: event:type=shot,initiatorPilotName=No.54 Philstyle,t=465.038,weapon=SC 50,initiatorMissionID=7,
2022-01-09 08:30:45.713 INFO    Scripting: event:type=shot,initiatorPilotName=No.54 Philstyle,t=465.974,weapon=SC 50,initiatorMissionID=7,
2022-01-09 08:30:46.541 INFO    Scripting: event:type=shot,initiatorPilotName=No.54 Philstyle,t=466.802,weapon=SC 50,initiatorMissionID=7,
2022-01-09 08:30:48.435 INFO    Scripting: event:type=hit,initiatorPilotName=No.54 Philstyle,target=DRG_Class_86,t=468.696,initiatorMissionID=7,targetMissionID=1061,
2022-01-09 08:30:48.435 INFO    Scripting: event:type=hit,initiatorPilotName=No.54 Philstyle,target=German_covered_wagon_G10,t=468.696,initiatorMissionID=7,targetMissionID=0,
2022-01-09 08:30:48.669 WARNING LOG: 1 duplicate message(s) skipped.
2022-01-09 08:30:48.669 INFO    LuaNET: SLMOD ERROR: error in stats, could not match target unit in hit event with a mission editor unit name.  Could it be a map object? Event Index: 31
2022-01-09 08:30:48.669 INFO    LuaNET: SLMOD ERROR: SlmodStats error- either tgtSide or initSide does not exist for hit event! Event Line follows:
2022-01-09 08:30:48.669 INFO    LuaNET: SLMOD WARNING: { ["initiatorPilotName"] = "No.54 Philstyle", ["targetMissionID"] = 0, ["initiator_z"] = -27311.56842181, ["initiator_y"] = 226.24061061325, ["numtimes"] = 2, ["target"] = "", ["initiator_name"] = "9./SG4 1 (HOT no fuel)-1", ["initiatorMissionID"] = 7, ["type"] = "hit", ["initiator"] = "9./SG4 1 (HOT no fuel)-1", ["stoptime"] = 468.696, ["initiator_objtype"] = "FW-190A8", ["targetCategory"] = 3, ["initiatorID"] = 16777474, ["initiator_x"] = -24940.356157131, ["t"] = 468.696, ["initiator_coalition"] = "blue", }
@mrSkortch
Copy link
Owner

Trains are in a weird state as far as the scripting engine is concerned. There might be special exceptions I need to specify in order for slmod to know how to categorize them. I will look into it.

@mrSkortch mrSkortch self-assigned this Jan 10, 2022
@SoWphilstyle
Copy link
Author

SoWphilstyle commented Jan 10, 2022

thanks for the reply. SL-MOD has been critically importand for SoW. We really appreciate your work on it.

@mrSkortch
Copy link
Owner

Looks like a fix is possible but I don't think it'll be as simple as I may have initially thought. Basically slmod uses a database of all units to get information about that unit when populating stats. Trains aren't normal units where each and every car in it has a unitName, unitId, etc. As a result trains aren't in the database. It should be possible to use what is in the events to pass that data to the stats code for it to use.

Scenery trains would still be a problem and wouldn't be able to be tracked separately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants