Theater conversion from 4.33 to 4.34
-
One part of each mission file (tac, cam or trn) is the file version.
This tells the program that load the file what is included or not.
Before 4.34 all mission file versions where 73 (except for AF)
With 4.34 this file version has been updated as the file include more data.So if you load a te_new.tac in TerrainEditor it first checks what the file version is.
TE can handle version 73 but not above.Gr Falcas
-
Hi Arty and Falcas this is what I was speaking of.
It is easy to work with,I am just making note of some of the things I do during conversion. some things may seem more helpful than others.
but you never know…
-
Attachment is not working
-
Is the 256 features limitation on objective gone or still there?
Sent from my SAMSUNG-SM-T818A using Tapatalk
-
Yes that is still here, as its not really a problem
To “solve” this place a second or third objective at the same location.
Best to be used for this is a hilltop type as this will not show up on the map.Gr Falcas
-
Hi Arty and Falcas this is what I was speaking of.
It is easy to work with,I am just making note of some of the things I do during conversion. some things may seem more helpful than others.
but you never know…
https://www.benchmarksims.org/forum/attachment.php?attachmentid=37276&d=1556377720In one of your previous posts you wrote that you changed CTs for the Carriers to “fix” a conversion issue.
This is the cause of what you see now.
Instead of changing stuff before, just answer the question MC is giving you during conversion.In the example of a carrier, the mission contained a carrier which is no longer in the DB. Many carriers have been remove. (Yes, don’t ask me why)
The conversion feature can’t find the objective (or any other entity) in the new database. So a screen pops up showing you what entity its about.
The Name, Type and CT from the old DB is shown. It will also come with a possible replacement.
In the example of the carrier you should have just picked a carrier which is available in the new DB.Gr Falcas
-
Just a quick question. I am importing LODs from a 4.33 theater during a conversion to 4.43 but I am having texture issues.
The models are using existing textures…
Is there any way to change the texture id in the LOD or ? -
Thanks Falcas for clarifying, I do many things outside the box.
USS Vinson will be just one of many. I see in docs that wasp is on the way too. I don’t wait until it is done. But i will adjust when it is,.C9 many thanks on post,but your thumbs up is not so helpful please elaborate.
-
Outside the box is fine and I am sure you know how to change/fix you DB.
I try to write my answers in such a way they apply to everybody.
Manually changing CTs before conversion is really not needed.
Thats the nice part of the conversions feature.However, if you have a modded database and maybe have incorrect data in it, good chance you will find out during conversion
Anybody who understands the BMS database and the mission files can understand how complicated the conversion process actually is.Don’t forget many mission have been converted already before 4.34 release, including all campaigns coming with 4.34. Without a conversion the new data would not be in the files and the mission files would be useless.
Some “rules” for conversion
- if you get a message to select a replacement entity (objective, squadron, taskforce etc) always, always select something. You can always change it after conversion
Just pick the best thing you can find. Is your Carrier missing, select a carrier which is in the new DB. - using the cancel button in this process will completely stop the conversion.
For some objectives the type of the obj has been changed. Some Kunsan stuff are changed to hilltops.
Roads, highways and intersections mixed.
So look for other types as well.Gr Falcas
- if you get a message to select a replacement entity (objective, squadron, taskforce etc) always, always select something. You can always change it after conversion
-
One more thing…
Once the conversion process is completed and you saved the mission, you are not completely done.
You just “revived” your mission so it works with 4.34.
The database between different versions of Falcon can be very very different.An example: you have a mission with a flight of Su-27 with some bombs loaded.
In the new Falcon version, these bombs could not be loaded on the hardpoints they where in the old version. Or can not be loaded at all.
(The whole AC could even be missing from the DB)
During the conversion process MC will ask you to choose the weapon you want to replace it with. Oeps… no bombs available on this hardpoint… But you always need to choose something, so you choose a AA-10.
Now you can understand that this Flight does not have the loadout as intended and the bombing mission will fail without bombsThese are things you might want to check and fix. Which can all be done in MC itself.
Also squadron stores have been changed. Weapons have been added and deleted for squadrons.
If you convert a Campaign, especially a beginning file like saveX.cam, its always good to go and take a look at the Advanced Unit Options.
“Resupply All Squadrons” is your help hereGr Falcas
-
All above good advice thanks falcas
-
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.