Mission Commander beta release
-
@Falcas said in Mission Commander beta release:
To give a very, very short way of how MC was designed to work with.
Build/create all your Objectives in the te_new.tac.
When its time or you have made plenty of changes, use the “Import Obj for Campaigns” feature to import what you have done to the campaign files.
!!!NO, there is NO need to export the Obj to cvs, its not used!!!
!!!NO, there is NO need to export/import any Units for this!!!
The TeamOccupation is used during this process. After all the Objs are imported, the TeamOccupation file is read to see what team occupies what part of the theater.
Objectives owners are set correctly this way and… Flags are also set as needed.Wake up call for me.
Thank you! -
@Falcas said in Mission Commander beta release:
See my point? What are you doing manually changing export files for?
And yes this is a real questionAaah, my freind, there’s too much to list all of the changes. (I’ve “repaired” half of db which is in state it was 20yrs ago - don’t want to do it again and again) - so, for sake of simplicity (for myself, after any falcon/theater update) … I’m externalizing all my changes , so on update… copy - paste… bit more complicated, but anyway much less work in the future.
-decided to keep whole theater in (xun, csv) - can import to any compatible map. … along with db update and all that jazz. same/similar thing what has been done with TvT.
(and bit of testing adventures in process…eh)I didn’t know that some functions are caveat… so I guess it is sometime better to listen and adjust the process accordingly.
Nothing more.
-
@yavuz hello,
I solved this problem with the EMF map.!
used this map (https://www.photobox.co.uk/my/photo/full?photo_id=505318006244)
-
@Corsair556 said in Mission Commander beta release:
@yavuz hello,
I solved this problem with the EMF map.!
used this map (https://www.photobox.co.uk/my/photo/full?photo_id=505318006244)
Hello comrade
It is impossible for me to download the EMF file from the site where you have uploaded it.
Could you upload it here, or to a download site, please?Thank you very much
Fresco
-
@Fresco hello
semd me PM your email i will send there.! -
@white_fang said in Mission Commander beta release:
-about external db, - so, it is only SSD sq-stores which are not read properly by MC
@Falcas
finally had a look, MC is parsing /SSD/* but doesn’t load files… your code might know more
All others are parsed normally.
-its not a big deal , just strange, so kept me thinking… personally, don’t have a lot squadron stores changes, just 4… for now… -
@white_fang said in Mission Commander beta release:
@white_fang said in Mission Commander beta release:
-about external db, - so, it is only SSD sq-stores which are not read properly by MC
@Falcas
finally had a look, MC is parsing /SSD/* but doesn’t load files… your code might know more
All others are parsed normally.
-its not a big deal , just strange, so kept me thinking… personally, don’t have a lot squadron stores changes, just 4… for now…First of all… what do you mean with External DB?
MC loads the database belonging to the theater, depending how the theater has been setup. Meaning where is the location of the database pointed to.
If this loading of a specific database file is not found or failed, it reverts back to Korea and tries to load this.
Not loading of the SSD file for a different theater than Korea has never been a problem. Looks like you have something going on with your specific theater setup.
-
@Falcas
I mean , external files (xml’s) for db in /objects/SSD dir. (squadron stores).So, MC is totally fine loading all other xml’s in subdirs /UNI , /SWD, /WCD etc. - but somehow … /SSD is the problem- don’t know why - there’s nothing different then in other examples…
I tracked file/disk behavior with procmon and MC still parses /SSD subdir when (re)loading db, but it just skips the files in it … so that’s kinda opposite then with others… and that’s strange.
I would gladly that it is something on my end… but there’s nothing different then in other examples. - just don’t know - so I believe that it may be in the MC’s code - but of course cant be 100% sure.
So, that’s why I was asking - if you can check on your end… for sake - just create /SSD subdir and export few “squadron stores” files in it… edit quantity … then check with the squadron if (type and) quantity of weapons have changed in MC squadron view.
- I can’t get it to work … changes in original SSD are loaded normally - no any problem there., but external SSD’s - are somehow a problem.
Thanks
p.s. … just maybe… MC expects “different” ?? / “none” filetype ? for /SSD , other then xml ?
-
see how they did it for Korea TVT :
-
I’ve tried naming SSD_xxx.xml - so it’s not that … BMS/EDITOR works just fine with any filename as long ext/filetype is xml.
-
The file name should be “SSD_X.xml”.
Where the X is the number of the SSD.
Else BMS and the tools won’t work.Can’t see anything wrong in the code TBH
-
“ I’ve tried naming SSD_xxx.xml - so it’s not that … BMS/EDITOR works just fine with any filename as long ext/filetype is xml.”
You could see the data like this as you might have save the difference to the “normal” falcon_SSD.xml
-
@Falcas
Mother… - trucker
And I’ve been busting my head.
Yeah, yeah… been there … got the t-shirt.
Case closed.
-guess what … SSD_32.xml is working in MC… (previously I’ve tried SSD_32_Ka52 and that is nogo IN Mc… - in BMS/editor anything goes)So, yes… MC is kinda picky for the filename., like I said, BMS EDITOR dont care about filename as long as long ext is xml, and has xml struct inside.
Thank you for everything, including patience
Cheers …
-
The SSD is not for one specific aircraft.
If can be for only one, but it can also be used by multiple different AC.
So the name of the AC was never designed in the filename. Also the BMS code looks for SSD_X.xmlBut BMS code might be a bit more forgiving I assume.
-
@Falcas said in Mission Commander beta release:
But BMS code might be a bit more forgiving I assume.
I can understand that, who would have dozens of files named VCD_1 - VCD_xxx … complete mess for navigation only.
…but SSD’s , well … retained “original structure” -
Please, which last version works with AF? Or is the current version F4AF friendly please?
-
@Lukas
Hmm… I do have some old versions of MC … now , which one?But… what is the goal??
… you can “prepare” MC (setup.ini) to load Lead Pursuit/Battlefield Operations database , then just load cam/tac …
You can also … copy all F4AF files /Art /objects . .etc… but! RESPECTING Bms directory structure … MC don’t care which version of Falcon you load… just give him wanted files … of course some like stations+il.dat don’t exist …I’ve managed (just now) to open cam file from F4AF (just by editing MC’s setup.ini ) with current version of MC. - so … it can
work.[Main] FalconDir=d:\Lead Pursuit\Battlefield Operations FalconKey=1.0 Database=d:\Lead Pursuit\Battlefield Operations\terrdata\objects\
-
I want to build a TE, fly it, save the end results and then build a follow up TE after modifying it with MC. Problem is when loading saved TE in MC there are many, many errors listed.
Is this not possible to do or is there something I’m not doing correctly to accomplish my goal?
-
@Badger said in Mission Commander beta release:
I want to build a TE, fly it, save the end results and then build a follow up TE after modifying it with MC. Problem is when loading saved TE in MC there are many, many errors listed.
Is this not possible to do or is there something I’m not doing correctly to accomplish my goal?
Please describe what you mean with “Error”.
I am pretty sure there is not a single error.What you probably mean is a message saying MC found use of double ID and fixed this. Which are not errors at all, but a simple notification. BMS does this, which is not nice, but MC fixes this automatically for you and notify you about it.
Nothing to worry about.
-
@Falcas No, it’s not that. I don’t have a pic to share right now but, from memory it’s about CT not found or indexes out of range. Then the map does not show all the units.
I’ll get a pic up here in a day or so…
-
@Badger said in Mission Commander beta release:
@Falcas No, it’s not that. I don’t have a pic to share right now but, from memory it’s about CT not found or indexes out of range. Then the map does not show all the units.
I’ll get a pic up here in a day or so…
Okay, interesting to see what it is.
Repro case (file) would also be nice -