Hi Shades, it´s me again.
In last mission we played, the host machine crashed. While we were waiting for the eventlog, we made a trial with our local eventlog to see if it could work (it didn´t).
Now we have the host´s eventlog, but:
I had a backup of the database "previous" of mission building. When I restore that backup and create the mission again (to analyze it, not to actually host it), the interal names of the units (36_Chief0...) are not the same as in the original built mission giving as result, that SEDCS gives lots of errors when it does the analysis...
Is there anything we can do to build the mission in the exact same way it was originally built?
Thanks in advance
Unit codes in built missions
Moderator: SEOW Developers
The host eventlog works only on the new database after mission building . Each time, you build a new mission from the original database (database before building), the internal names of the units (36_Chief0...) change...
So, you can't use it. It's important to backup AFTER building...
I have no simple solution...
If your eventlog file is not too big, you could do that:
- Restore your database before mission building
- Generate new mission
- Compare line by line the 2 missions file (the OLD you have flown, and the NEW one)
- Replace in the eventlog file all names of units by the names of new mis file.
- Analyse your mission.
So, you can't use it. It's important to backup AFTER building...
I have no simple solution...
If your eventlog file is not too big, you could do that:
- Restore your database before mission building
- Generate new mission
- Compare line by line the 2 missions file (the OLD you have flown, and the NEW one)
- Replace in the eventlog file all names of units by the names of new mis file.
- Analyse your mission.
-
IV/JG7_4Shades
- Posts: 2211
- Joined: Mon 08 Jan 2007 11:10 pm
- Location: Perth, Western Australia
I agree with Dore.
If you re-build a mission, the Wing and Chief sections should be the same I think (apart from GATTACK, TAKEOFF or LANDING targets in the Wing section), but the Stationary section will likely change. The reason for this is that there are some die rolls that take place when SEOW places stationaries. These rolls are made when determining whether a vehicle is broken down or not, and whether parked aircraft actually appear or not, etc.
SEOW keeps a list of all units in the campaign and how each one appears in the mission file. This list is in the Unit_Name_Mapping table. It is possible to go through and correct this list for the newly built mission version. But if you get this wrong you will likely see errors again.
For simplicity, I would suggest that you simply go to your backup, build the mission again, re-fly it, analyze and move on.
Cheers,
4Shades
If you re-build a mission, the Wing and Chief sections should be the same I think (apart from GATTACK, TAKEOFF or LANDING targets in the Wing section), but the Stationary section will likely change. The reason for this is that there are some die rolls that take place when SEOW places stationaries. These rolls are made when determining whether a vehicle is broken down or not, and whether parked aircraft actually appear or not, etc.
SEOW keeps a list of all units in the campaign and how each one appears in the mission file. This list is in the Unit_Name_Mapping table. It is possible to go through and correct this list for the newly built mission version. But if you get this wrong you will likely see errors again.
For simplicity, I would suggest that you simply go to your backup, build the mission again, re-fly it, analyze and move on.
Cheers,
4Shades
IV/JG7_4Shades
SEOW Developer
SEOW Developer
Thanks to all for the advices. This is what I´ve tried and didn´t work:
With a compare software (Compare It), I´ve opened both mission files: The original one, and the newly generated one too.
Also opened the eventlog from the host.
I browsed through the eventlog and each time I say an event with a _static involved in it, I followed this steps:
* In original misison, i took note of the position of that unit (x,y) and searched for same position in new mission file.
* Replaced unit name in eventlog.
After doing this for the whole eventlog, I analized it but got a bunch of errors anyway. And when SEDCS was trying to insert into ObjMissionData, there was some kind of error and that table remained empty. So when I go to MP, the map is completely empty of units.
If anyone wants to try it, I can upload both mission files + eventlog + sql to generate the DB.
With a compare software (Compare It), I´ve opened both mission files: The original one, and the newly generated one too.
Also opened the eventlog from the host.
I browsed through the eventlog and each time I say an event with a _static involved in it, I followed this steps:
* In original misison, i took note of the position of that unit (x,y) and searched for same position in new mission file.
* Replaced unit name in eventlog.
After doing this for the whole eventlog, I analized it but got a bunch of errors anyway. And when SEDCS was trying to insert into ObjMissionData, there was some kind of error and that table remained empty. So when I go to MP, the map is completely empty of units.
If anyone wants to try it, I can upload both mission files + eventlog + sql to generate the DB.
-
IV/JG7_4Shades
- Posts: 2211
- Joined: Mon 08 Jan 2007 11:10 pm
- Location: Perth, Western Australia
Hi Anubis,
I would recommend restoring your pre-Build backup, build the mission again and fly it again. Alternatively let me d/l your campaign databse ande all the relevant mission and logfiles and I will see what I can do with it.
Cheers,
4S
ObjMissionData should never be empty once a campaign is started. By the way, once you have experienced a bad Analyze stage, the DB needs to be "fixed" to get it ready for a re-Analyze.ObjMissionData, there was some kind of error and that table remained empty
I would recommend restoring your pre-Build backup, build the mission again and fly it again. Alternatively let me d/l your campaign databse ande all the relevant mission and logfiles and I will see what I can do with it.
Cheers,
4S
IV/JG7_4Shades
SEOW Developer
SEOW Developer
Hi Shades,
Yes, that´s exactly what I do. I have a back up previous to the build state. So I build the mission, and compare the new object names against the eventlog.
I don´t touch the mis file or the database, I only change the names in the eventlog to the ones in the new mis file.
The error that I mentioned before, is a popup window in SEDCS, it has starting part of the SQL instruction that caused the error, but I don´t know exactly what part is causing the error as I don´t see the complete SQL sentence. But I think that this sql, is the one that populates ObjMissionData and as it fails, the table stays empty.
I will upload the files I told you as well as a screenshot of error message.
I know it´s not easy to fix it, and because we´re using the random failure for aircrafts, sometimes the mission has more and sometimes less planes.
Thanks a lot for your help
Yes, that´s exactly what I do. I have a back up previous to the build state. So I build the mission, and compare the new object names against the eventlog.
I don´t touch the mis file or the database, I only change the names in the eventlog to the ones in the new mis file.
The error that I mentioned before, is a popup window in SEDCS, it has starting part of the SQL instruction that caused the error, but I don´t know exactly what part is causing the error as I don´t see the complete SQL sentence. But I think that this sql, is the one that populates ObjMissionData and as it fails, the table stays empty.
I will upload the files I told you as well as a screenshot of error message.
I know it´s not easy to fix it, and because we´re using the random failure for aircrafts, sometimes the mission has more and sometimes less planes.
Thanks a lot for your help