Theater conversion from 4.33 to 4.34
-
Any chance of making this thread a “Sticky”, at least for the time being? It’s going to be quite a hot topic during the coming months.
Thanks
-
This post is deleted! -
Here is a vid of me using lodediter on 4.34 might be helpful to some.
Is there anyway that you can upload this video to Youtube so it can be download to one’s PC system?
-
Is there anyway that you can upload this video to Youtube so it can be download to one’s PC system?
It is on YouTube already
Sent from my SAMSUNG-SM-T818A using Tapatalk
-
Arty’s right, it is on YouTube. There are tools that’ll allow you to capture YouTube videos and store them on your own PC though.
-
@Red:
Gents this is a chapter I wanted to be in the tech manual but I wasn’t able to write it not being a theater developer myself. So this post if formatted correctly could certainly be used as the back bone for the well needed new chapter of the technical manual.
I’ll be listening, and don’t be afraid to be exhaustive so that even me can understand the step by steps requiredI couldn’t agree more Red Dog, that’s exactly what we needed.
Not sure what’s happened tbh. Clearly 2 designers have been given an inside track into converting theatres into BMS 4.34 so why haven’t they been asked to write the chapter you describe above as part of the deal? I really don’t understand it tbh but I guess we have to live with it and move on. Not entirely down to you, I understand that, but surely lessons to be learned for the future.
Cheers
-
I couldn’t agree more Red Dog, that’s exactly what we needed.
Not sure what’s happened tbh. Clearly 2 designers have been given an inside track into converting theatres into BMS 4.34 so why haven’t they been asked to write the chapter you describe above as part of the deal? I really don’t understand it tbh but I guess we have to live with it and move on. Not entirely down to you, I understand that, but surely lessons to be learned for the future.
Cheers
You couldn’t be more right Duke. In fact those theaters Devs are BMS Devs also so they prepare the theaters along with the 4.34 development. Very unfair to the rest of us but its life
What i’m stunned is that knowing that theaters turn complete obsolete with 4.34 BMS Dev tem should at least warn the main theaters dev months ago, at least to inform what kind of changes should we start to make.
Now we are months behind but no problem we will make it and in the process make note of all we have done to make sure that everyone now and in the future can change their theatres.
-
Gentlemen,
even if positively NOT a theater maker or the like, I’m following closely this interesting discussion, made clear in language and expressions for me as well.
Duke and Decimal, you got a main point both, especially about making this a sticky topic of discussion and sharing experiences and points of view.
And - this is my own little cent here - I wouldn’t ever forget a matter, true also about this particular topic.
As per Red Dog’s (as many others, I guess) statements in years and almost everywhere, BMS is a friendly ‘association’ of enthusiasts making and developing a flight simulation for other enthusiasts, for free and in their free time.
A lack of information to us, the public, is therefore almost unavoidable to my eyes.
I don’t assume that releasing such a sim, listening always the bunch of complaints from the users, and answering to each of them, and surviving to the last minute clash of big and little preparations preceding the release of this great update (to call it so), is a nightmare mission to me, you know. Well, more or less.
I agree with you, Decimal: we will make it, will even take this months. Or a little bit, as I hope.
We too are a ‘team’, more than sometimes doing close to the developers.With best regards to all.
-
What i’m stunned is that knowing that theaters turn complete obsolete with 4.34 BMS Dev tem should at least warn the main theaters dev months ago,
It has been said here and there.
at least to inform what kind of changes should we start to make.
Nothing you can do before having the DB in your hand. For info, some CT changes few weeks ago so if you had started to work on it before, you would have restarted from scratch just after.
Now read carefully: It will be the same with 4.35
-
so why haven’t they been asked to write the chapter you describe above as part of the deal?
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.
-
not difficult, just pratice, we are all newbie, again
-
We are ahead of time here guys.
We are expecting some tools as i understood that will help out theater development.
You complain to bms team.
They said it that theaters will be incompatible, i even started a thread about it. It was loud and clear.
Let’s give the guys a brake. Its Easter time and some are not available they said. So let’s wait and respect their free time.If you want u can start the conversion. U have all the info at hand. Its hard but its there. Bfast the balls of those that have done it already to help out. They surely know and its fresh to them.
I was about to start the excel thing, but got a full stop after warnings and the announcement that the tools are ready and a its a matter of time. No need to re invent the wheel.
Edit: i forgot… Its not just bms team… terrain editor is also incompatible to some extend.
The best practice is to have a ful detailed log of all changes. That way in db changes at least you know and dont have to remember which goes where, oh the ct# changed and things like that. Look at the ct if u dont use it just scrap it. Now you can delete it. in the past we couldn’t. And look at the forest, all these are done for the greater good.
But sure the complain is needed as this happens and reinventing the wheel to do the theater is a pita. Same for In bms dev theater devs. They should be more balls basting to requests for theater tools… [emoji38]Sent from my SAMSUNG-SM-T818A using Tapatalk
-
The best practice is to have a ful detailed log of all changes.
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.
-
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