Theater conversion from 4.33 to 4.34
-
Precious info, Falcas.! Many thanks.
Quick question: I’ve converted Save0. Cam, and have changed the objectives accordingly.
Then, instead of saving in “73” format, it saved in “100” format.
I was expecting to see it in “74” format.
Is everything correct?Cheers
-
Can’t do everything at the same time. PPL were crying for having this 4.34 released. They have it now.
Next time we will delay the release by one year or more the time to write a “conversion manual”? … I won’t do it on my side. I have no idea how to do this. Or I would say the following:_- Grab 4.34 UI files, sound DB and and DB.
- Inject your terrain + Terrain textures.
- Extract 3DDB, add you models, rebuild 3DDB.
- Update/change Obj Textures to your needs.
- Create your Te.new.tac as new working base._ - Modify Art files to your needs. - Build your Campaign(s). Nothing that a 3rd party theater Dev is not accustomed to. The only real change (new feature) are the ATC files.
It’s not so simple to convert old db to work with new editor/bms , but I’ve managed…
Example is .PD .PDX files , from old db …, are merged into only .PDX file (with PD structure)… doh… , … and also new string names (Height vs MaxHeight) … so there were 13000+ search and replaces
Not complyin with above just leads to crash…
Aaaaaandd…
!!!How to import old /Sim directory , hence changes in 4.34 include AcData and VehDef , which many od dat’s are unreadable to new system??
What to do?Please.
-
@Nuno:
Precious info, Falcas.! Many thanks.
Quick question: I’ve converted Save0. Cam, and have changed the objectives accordingly.
Then, instead of saving in “73” format, it saved in “100” format.
I was expecting to see it in “74” format.
Is everything correct?Cheers
How to F… did you convert save0.cam to v100 ??? , MC crashes everytime on my save2.cam , even with replaced (tuned) db with new units…
Please , more info.
THX -
@Nuno:
Precious info, Falcas.! Many thanks.
Quick question: I’ve converted Save0. Cam, and have changed the objectives accordingly.
Then, instead of saving in “73” format, it saved in “100” format.
I was expecting to see it in “74” format.
Is everything correct?Cheers
Yes you want files for 4.34 are file version 100.
Gr Falcas
-
How to F… did you convert save0.cam to v100 ??? , MC crashes everytime on my save2.cam , even with replaced (tuned) db with new units…
Please , more info.
THXReally, don’t change your units before you start to convert, this only causes more issues later on.
At least I assume that your DB is as it shouldBetter show me what the error is, in that case I can be of more help.
gr Falcas
-
Really, don’t change your units before you start to convert, this only causes more issues later on.
At least I assume that your DB is as it shouldBetter show me what the error is, in that case I can be of more help.
gr Falcas
OMDG!!!
Your words ARE making magic… Just did re-re-re-conversion … and it passed , … no questions asked… ‘Where do you want your save2.cam today, sir?’
(actually , it asked one question , Do you want new callsigns , … of course YES … )-‘In my theatre please’
That’s it … else is just model updatin’ and my work can continue where I left in 4.33 … (well, still need to figure what do I do with changed /Sim/Acdata/Vehdef issue, but the PAIN is gone now
I have (finally) save2 in v100. TaaDaa
What can I say, THANK YOU (again) Falcas for your kind words of support… can’t figure what made the difference (and I don’t care )
Woohooo:woohoo:
– msg begin: OLD 4.33 THEATRE WITH CUSTOM DB CAN (be made) WORK IN BMS 4.34
-
@white_fang, let me describe what I did from the beginning:
1st - adapt the whole folder structure to 4.34 standards
2nd - check folders and files one by one to see what has to be replaced or may be used from older version
3rd - extract both databases
4th - copy from 4.33 DB all the parents from our new features into 4.34 DB and build the new DB
5th - (here’s where the pain started) create all new features from scratch in 4.34 DB. Next, the objectives.
6th - te_new.tac, instant.cam and savex.cam conversion.
7th - (current stage now) complete placing all the features in the new objectives and recheck PHDs. Another major pain in the but.
8th - didn’t get there yet, but I assume the comms/navaids.(To be continued)
PS: almost forgot: between 2nd and 3rd I have redone the whole UI again, to match all the changes to 4.34
-
Take a little break from converting missions.
Eagle-Eye has sent me a mission which he had trouble with and this has revealed an issue in the code.
Fix is coming soon.Gr Falcas
-
We standby Falcas.
All stated advice already proved useful.
Very different db is most likely my main issue. Functionality of MC is not.
I understand and see many useful changes since last iteration.
And look forward to new changes as well.
When I hit problems, it is usually on my end. -
We standby Falcas.
All stated advice already proved useful.
Very different db is most likely my main issue. Functionality of MC is not.
I understand and see many useful changes since last iteration.
And look forward to new changes as well.
When I hit problems, it is usually on my end.Coffee break is over… back to work
-
Guys,
Little help, please.
To add a new squadron in database, I’ve addcopied the vehicle, then the squadron and finally the unit. Database ok.
Now I can’t remember which .txt files I have to edit, besides validac.act and teplanes.lst for the new plane to be selectable in TE Editor. I’m sure there’s at least one or two more, but can’t remember which.
Can anyone shed some light here, please?
Cheers!
EDIT: Got it, “units.irc” and “textids.id” inside Art\Main folder
-
For the validAc and tePlanes.
Start MC and load a mission, te_new.tac for example.
Go to the Planes tab and the rest you will see how it works.Gr Falcas
-
Thanks, Falcas!
First squadron created in DB and available in dropdown list:
Only 3 zillion more to go!:D
-
As well as doing your station+ils… use MC
Gr Falcas
-
-
@Nuno:
Thanks, Falcas!
First squadron created in DB and available in dropdown list:
https://i.imgur.com/Mm08m1F.pngOnly 3 zillion more to go!:D
Great work mate.
Keep it up!About Stations+ILS and RadioMap, am already working on it…
Will be ready soon… -
Guys, another question.
In 4.33 I had exported all our custom objectives using BMS Editor, which made extremely easy to recover feature and PHD data, for instance, when updating the DB.
Since right now, in 4.34, the CT#s have changed, is there a practical way of recovering the previously exported objective´s data or one has to redo them by hand? (so far it’s what I’m doing, but it’s a tedious workload…)
So far, the only thing I’ve been able to recover is the PHD data from airbases (which could be improved also due to new taxiway branch capability), while trying to recover the feature data gives an obvious CTD in BMS Editor.
So, only way is populating the objectives from scratch?
Thanks!
-
Can someone shed some light to the ‘naming scheme’ for the new db update (upgrade) scheme with single xml file(s) – Terrdata/Objectives/RCD , /SSD , /UCD etc… dirs.
Like it is done in ‘Add-On Korea TvT’ , where theater/campaign use default (fallback) database but units/objectives are updated via xml’s , eg… ‘/Objects/WLD/115_F-18CD 37.xml’ or
‘/Objects/UCD/6_Battalion_Patriot MIM-104.xml’ …WOW, WHICH I THINK is pretty Cool feature , in the future no more countless GB’s of databases with copyofcopyofcopy of the same database over and over.
So is there a ‘respect’ to the names of xmls or it just looks inside the header idx ?
THANKS
@Nuno , maybe you can do this approach , check the TvT objectives folder , yes they are overrides… but unfortunately only to the DEFAULT (Korea/Terrdata) database.
-
The single XML files are to overwrite the database. As you can see with TVT, this is used to keep the same DB as KTO, but have small differences where needed.
If your theater has its own database, this is probably not something you are going to use much as you can do the changes as you like.
It can be very useful in many cases though.Gr Falcas
-
The single XML files are to overwrite the database. As you can see with TVT, this is used to keep the same DB as KTO, but have small differences where needed.
If your theater has its own database, this is probably not something you are going to use much as you can do the changes as you like.
It can be very useful in many cases though.Gr Falcas
ON CONTRAIRE … it is VERY VERY VERY useful for my theater , … since I’ve already converted my old DB to 4.34 format so I can read it with ‘4.34 Editor’ then export my units/whatever… and re-import to new eg.Balkans default db , as single xml overrides. There are not too ‘MANY’ changes… I think
Only problem is they are overrides to a default KTO db , not the ADD-ON DB , so I need to think… I would need to do 2 sets of overrides . 1.set between new Balkans DB and KTO DB , then … 2nd set between MY DB and KTO DB.
Only then, as I figured, that would work as intended…But… somehow I think it is more complicated lol , then , as You’ve said , making OWN db.
IF you could DEFINE another ADD-ON DB as default, eg in .TDF file , add another ‘switch’ >defaultObjectsDatabase …/add-on/terrdata/SomeObjectsDir<… then overrides would be EVEN great stuff… but let’s leave that for another update , just as an option to think on.
----But , what was question,… Are the XML naming scheme important/crucial , or can it be ‘whatever/random’ … well, i can test myself tho, but if someone knows?
Cheers