Theater conversion from 4.33 to 4.34
-
In the end of the day we all are human beings and of course we can’t all be pleased all time
I understand to some extent what you say Dee-Jay. And i believe that is a pain in the A** to make a full changelog document. What im only complaining is that some BMS Devs who are also theaters devs could at some point share some highlights to the rest of the theaters devs. I’m not blaming anyone here
I’m just a little bit sad that me and the rest of the POH Dev team have to delay our 4.34 full conversion until POH is available.
Again not blaming anyone just my 2 cents.
Let’s work people and we will make it even better that the last version and follow the amazing developments of 4.34.
“To Infinity… and Beyond!”
-
Not possible. If we had to list each values for each CTs, each Tex Id … each everything, anytime we commit a change, 4.34 would have been released few years later.
I’m not talking about BMS deejay I’m talking about theater developers. So you understand perfectly the issue.
If u don’t keep such a detailed log then you can’t update when a new db comes to town.Στάλθηκε από το MI 5 μου χρησιμοποιώντας Tapatalk
-
Gents,
The purpose for this thread is to share knowledge amongst everyone as/when/if possible, not to complain for what we have or don’t have.
Fortunately, we have all the time in the world to get the job done, and we (the community) have alot of people to help and support.
So, let us be patient, get the job done and stay on topic, please ;).
Cheers!
-
If you get a few ct error notices in mc when converting te_new or cam files….
What I did, was go back to 4.33 and change (in my case about 10) objectives to any other objectives that did not call ct error in conversion. Write them down, Then save.
It was mostly carrier objectives in my case.
Then when I convert, those ct errors are gone, and change them to correct objective with new db after conversion.
-
Do you mean errors or questions? I am pretty sure you got questions about the carriers.
which you only need to answer.
Changing CTs does not do anything for the convert process. That is the good thing about the MC mission conversion.TerrainEditor can be used and is also what I am doing. But do not save a mission file with TE as this will not work with 4.34.
You just need to save the XML database in the old bin version as a start.
In case you want to see the objectives, use a te_new.tac with file version 73.Gr Falcas
-
File version 73?
Sent from my SAMSUNG-SM-T818A using Tapatalk
-
File version 73?
Sent from my SAMSUNG-SM-T818A using Tapatalk
Check here : https://www.dropbox.com/s/vowd2zvr000j34l/Save73.jpg?dl=0
-
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.