They are tools and info that can’t be shared outside the BMS team…
Now, if you think you have the skills and talent to be part of BMS that’s another story…
Contribution to BMS has unfortunately limits due to tools and code not being shared for very obvious reasons (especially with planes and systems).
Now, up to you to tell us what you think the next step is.
We do understand, and have no problem with, the fact that hard code and other things are not shared outside of the Dev’s. But, things like the cockpit hotspot fixes have been available. And , as I wrote above, we would be very happy to get them to you in whatever way you would like.
I know we have the devotion and desire to be a “part of BMS”. As to what “skills and tools” we have, we invite the Dev’s to discuss that with us. I believe we can help, and also believe that our abilities will only increase with time. If you have followed Project Bug at all, you will read how we are “building the infrastructure” , developing ways to help in new areas like flight models.
I’m honestly unsure what you mean when you continue to write that “the next step is up to us”. Given that we have reached out to the Dev’s,and made our files available, my question is what step do you want? What do you want/need from us to facilitate us working closer together? And, PLEASE believe there is absolutely no malice in that question. Meanwhile, the best answer I can give regarding the" next step being up to us" to to share our current mindset. We as a group like to be open and sharing, and in no way “self-promoting”. We enthusiastically want to work with the Dev’s. If we can’t do that, then we will provide what we can to the Membership, just as we have done with the Mafia Files.
Max, to be honest I’ve been a bit hesitant to write my posts of the last couple of days, in responding to what’s been written here. We most emphatically do NOT want to be adversaries of the Devs!!!
All we care about is helping make BMS better. It really is as simple as that.
Edit the table data layer.
add 2 columns like X and Y.
For X set it to $x (from geometry)
For Y set it to $y (from geometry)
exit editing mode to save the new columns and their calculated data.
Now your X Y will be instead of real world coordinates Falcon coordinates thus from 0,0 to 1023,1023.
Export the layer as xls or csv whatever you like.
Export te_new.tac from Mission Commander by Falcas as csv.
Open the two files and merge what you want like.
“Ready” to do what ?
How do I generate the minimal files needed, to be able to pick a theatre within BMS ?
u can’t calculate the CRS. Edit: Unless u are a GIS knowledgeable person and can calculate it for Transverse Mercator.
just give me the theater center real coordinates in wgs84.
Ready to do what?
well u have GIS data as points on the map in a known official CRS format.
if u have them in QGIS how do u export it for falcon?
Falcon projection is a flat Earth and uses instead of real coordinates X,Y values ranged from 0 to 1023 thus 1024 and those are kilometers as are the kilometers of a 64 segments theater…
Oh dear u make me write stuff that are kinda in the guide, but anyway I’m expecting such…
so u have GIS data that you want to import in Falcon as objectives like cities factories bridges and whatever u want within limits of the DB. In order to be able to do so (import to Falcon) u must convert real coordinates to Falcon coordinates.
There comes in the Falcon theater CRS. This tells to QGIS that this 1024km (1Kkm for short) area will use a different CRS and will start here and end here and will be kinda flat (well all projections are kinda flat, or ellipsoid or cylindrical but they end up represented in a flat screen).
when u have the correct CRS in QGIS and u reproject the data u got to the theater CRS then when u tell QGIS tell me it’s geometry X and Y instead of Lat and Lon it will give u something like x=450 y=891. Feeding that to the te_new.tac CSV file as a new line and name it and add all the rest of the columns needed and import it back via MC you will have a new objective.
Now instead of doing it one by one to place name etc via MC you can get all the GIS data cities airports bridges and whatever and import them at once in MC like if you start a brand new theater.
Implemented for next release (Not 4.35 updates but next one)
Support particlesys.ini to be specific per theater.
specifying "terrdatadir" in theaterdef file of the theater will try to load the particlesys.ini from that directory
If not specified then the default KTO location is used, if specified but doesn't exist, then PS will be empty (same as loading the sim without particlesys.ini file)
As it still reads the save 100 version maybe save as version 100? Its a PITA cause you will have to have an empty 103 version and import everything after but it might just work. I use the currend MC (of course i started from scratch the objectives for Georgia) and already saved at 100 version and TE reads it. I had an issue with “overflow” (subscript 9) cause a city was at X1024 Y3 and ofc ourse it supposed to be at X1023 when i fixed that everything was fine!
Life’s got a bit easier now. Falcas saved us - Now you can “save as” v100 directly from “MC” , little checkbox in up-right corner. ,… and use your way to hack into 4.35 install/database/ with TerEd
… since , sniff , no support for v103 in "TerEd"yet. … but … still hoping.
I still need to fix DB discrepancies from 4.34 to 4.35 for my custom theater db … and even don’t know where to begin… crap, …whole world of objectives was “filtered” and renamed / changed … I could spend whole f3cking day just comparing the changes) - and there’s noway for automating the tasks …
If I was smarter , I’ve could just externalize my changes into separate xml’s then save them for later importing as seems fit … addon/replacement … now I have to do it all again…
I concur. This line isn’t working for me either.
The picture’s address used to be able to be linked to terdata/tacref.bin.
Now that it’s tacref.xml, I’m not sure what line to add , or even if address of pic can be added.
I made a post on @technical issues thread too.
Haven’t tried Obi1’s Hail Mary shot at adding entire address yet.
But I will try that later or any other suggestions.
Please let me join your wise and interesting discussion, Gentlemen.
If I dare so, that’s the spirit… and if those rumours running will become a reality, sooner or later doesn’t care, it will be worth to learn how the new theater structure has been developed and after that continuing your work from the point where you reached to.
Wise choise that yours, in short.
My best wishes for all, and please always behave safe.
With best regards.
You are right
I know (more or less) how the thater maker process works. that’s not the issue. The real problem is that the tools are out of date for a new system like BMS 4.34 and it is difficult to follow a tutorial that is not “aligned” with the current BMS version. Too many gaps. I believe that this new one will bring a new kind of tools and a diferent approach. The basic theater (terrain data) is here, that’s is the most important. HOW to work with this data that will change, I guess.
Ok, I found the problem and I will post to help other people with the same issue. I don’t know how or why but something (someone??) changed the e00 rules and this is preventing the dem2terrain to show labels AND generate tdf files. Funny thing is that I completely deleted dem2terrain, worldwide HDR and everyfile related to it. I cleaned the registry as well. Than I restarted the computer and reinstalled everything back to a diferent folder BUT the e00rule didn’t change back to default. I wonder where this “file” is stored…