Mission Commander beta release
-
@Falcas
Many thanks Falcas, yes I already saw the possibility to have a different tail for wingman than the usual one. Many, many thanks to drive me in the right direction for the rest.
G -
@luke777 said in Mission Commander beta release:
I ran into an issue converting a campaign from ITO .35 to ITO .36, all objectives had the correct X and Y coordinates (except a very few which were off by 1 unit in either X or Y), the N and E coordinates for all objectives were off on both values, usually the decimal part but in several cases the minutes were different compared to the original save (both .35 and .36 vanilla save files were compared against the converted save). This didn’t happen in NTO. The same procedure was used in both instances as detailed in MC Convert Mission. MC version 0.5.20.686.
Hey,
Not enough is clear about what you are doing to give a clear answer.Converting a campaign? You mean the base file (saveX.cam) or a running campaign?
The difference must be clear, there are no Objectives in the running campaign file.During a conversion the coordinates of Objectives are not changed as this is not needed for a conversion. So why would you see a difference.
If you talk about 1Unit, you mean 1KM?
As you can now place Objectives with 0.001 KM accurate now as 1.0Km before.Do you have 2 compare screenshots to see what you mean?
-
@Falcas said in Mission Commander beta release:
During a conversion the coordinates of Objectives are not changed as this is not needed for a conversion. So why would you see a difference.
I wouldn’t have asked if I knew why.
saveX.cam to saveX.cam
One unit as one unit e.g.100 in place of 101
Left converted right original. Discepancy in N and E coordinates.
-
The KM X/Y are the same, both X 329 Y 282. That is the only thing that matters and actually places the Objective in the game.
So see why I asked about units being KM?The coordinates in Falcon have always been fake and just some close calculation to get you something showing. But has nothing to do with placement.
Although this is a bit strange. Input is the same, the calculation is the same and so the result should be the same. Will see if I can find something.
EDIT: What can be the case is that the base data for the theater 4.35 and 4.36 is not the same!!! Meaning the set coordinates of the lower left corner. This could explain the difference.
-
New version released, latest is 0.5.21.691
Main
- Added, HeliPt count/check at various placed in the tool.
Objectives
- Check obj links will also check for bridges only having one link.
Flight
- When changing a mission type, set old_mission as well.
-
@Falcas said in Mission Commander beta release:
EDIT: What can be the case is that the base data for the theater 4.35 and 4.36 is not the same!!! Meaning the set coordinates of the lower left corner. This could explain the difference.
I took the ITO save0.cam, removed all units, painted the occupation map and added units from scratch (.35). No tamparing with data. I converted the campaign with MC, there were only very few objectives that needed to be re assigned (.36). I started looking into this after some reports of stand off guided weapons not hitting targets when using tgt stps. One isolated case can be attributed to a delta not zeroed, too many cases are suspicious. I rebuilt the campaign using the standard save0.cam that comes with ito, no conversion, checked the coordinates and all matches (.35 and .36). Will test it asap.
-
@luke777 Sorry m8, how do you have “delta” (on objectives) on day0 (saveX) ?
I don’t think you should. But, you know that? (just delete all delta’s)If for “occupation owner” (original/current) , then use those respectively … not delta(s).
btw… for units… I’ve found that export/import works just fine, you could try it… MUCH less hassle when cleaning/rebuilding cam.
@Falcas And again, great!. Thanks
-
Clear enough now?
-
@luke777 AAAh , wrong delta … A - OK Mister!!!
-
I don’t see any relation between STP delta and Objectives.
-
Could it be that magnetic declination is in effect or not between versions, that could give minor deviations even for identical maps. It is an option set in the .tdf
-
@Falcas said in Mission Commander beta release:
New version released, latest is 0.5.21.691
Main
- Added, HeliPt count/check at various placed in the tool.
Objectives
- Check obj links will also check for bridges only having one link.
Flight
- When changing a mission type, set old_mission as well.
Thanks Falcas.
-
My apologies if you’ve addressed these already:
- I just updated to Mission Commander 0.5.21 (and a fresh re-install of BMS 4.36 and U1) and got the following when first loading a mission.
- I get this every time I Open a squadron:
- Feature request:
a) Maybe I’m not seeing it’s already in MC, but is it possible to implement a bulk squadron move to a specific airbase, in addition to closest base?
-
About 1 and 2, as these could occur due to the same reason.
Check if MC is pointing to the correct database for the correct theater.
Yes normally MC loads the theater database in case you load a mission from a different theater. You get a question about this. Answering for the wrong theater will load the incorrect database and obviously these things might occur.About 3
You have the option to move a Squadron to any airbase you like.
For this, open the Squadron and you will find a button for it.
However, only one at the time. -
For 1 and 2, I’m loading a mission in the default KTO.
Are these the correctly-loaded parameters(?):
For # 3, I am making a feature request.
-
I am sure I read in some thread that it is not wise to install BMS falcon 4.36 in the same folder of Microprose Falcon 4.0.
This is probably the reason for these problems. -
@UglyGrendel
I don’t have 4.36 in the vanilla Falcon 4.0 directory, though both are in a Games folder. That wouldn’t be an issue, would it? -
No normally this is not a problem.
However if this directory is in a place which Windows protects a lot like “Progam Files” this might cause some read/write issues. Its a windows thingFor MC and WDP just make sure NOT to have those in your BMS install. Just any other location will be fine.
Both mentioned above are very unlikely the cause of your issue btw
-
-
Added a couple of FAQs to the first post of this thread.
So if anybody ask… just point them to theseFAQs
Getting a error " Unable to load DLL ‘LzssNative.dll’" This DLL file should be in the same directory as MC. For some this files has a hard time to load. Reinstalling BMS , Windows or buying a new PC will NOT help. Just grab the file from WDP or any other previous version that did work for you. Is MC Compatible with 4.36U2, U3 or whatever. Yes, MC is always compatible with these versions as its being build for the latest code in the Dev team.
-
@Falcas Hi, just a quickie
Is there an explanation , why most of the times MC’s LZSS dll(s) works oob , and somewhere eg, requires copying from wdp … ? why ?I mean, if antivir… , for me is working from day0 , even without touching anything , eg. white-listing exe , exception dir … , and I really mean from day0, from winXP till today win10 … (I won’t go win11 never) .
Just strange …
Cheers and Thanks for all the fish