Theaters updates to 4.33.1 -Strategies and ¿Has anyone gone the other way around?
-
Hi!,
This intention with this post is NOT to ask about strategies, but rather to compare the ones we are taking to update the theaters, and to rise a question about going another way which could have been faster (maybe):
Mine is nothing new:
- I got stock KTO database and have started adding our custom db entries.
2)Then we will get stock KoreObj.Lod from KTO and begin inserting our custom 3d models .lods related to their database entries.
- Then we will include our own textures for the models in the KoreaObj folder.
4)Then we will re-arrange objective features, PHDs/PDs, using export utility in FE
Since KTO database numbers (CTs… etc) AFAIK haven’t changed the te_new.tac and so won’t need rework.
¿Am I missing something?
This simple process is a lengthy one because we have many custom entries and models in our database and they have to be included one by one. But according to the changelog the changes to the database itself and to the 3d part of the database are a few. So the question rises:
Has anyone done it the other way around? I mean, to get ther custom database “AS IS” and introduce the changes that have been done using the changelog as guide.
I know is a risky one, since the changelog might miss something, but It could definitely save a ton of work if it is successfully done.
So, Has anyone done it? Or considered it?
I did but chicken out. Nuno Santos came up with the idea to do so. Pretty clever I must say.
I know It could save me a ton of work, but if I miss something I might end up “wasting” time while on the other hand, the safe way is slow but certain. -
Well mostly it’s for code-database related issues.
I mean if there are no code changes regarding the database structure a theater of 4.33 should work on 4.33.1 and would need just new directories declaration.
If stock bms entries ain’t critical then no need to go all the way in to trouble.
About nunos idea well it’s good but are all changes logged?This was why in the past I was barking for such a tool to zip-zap and your databases are synched.
Oh U2 update is on the way u will have to redo.
All will.
Should we - the devs consider of loosing theater devs?
Theater devs instead of reinventing the wheel could spend time for optimization and enrich the theaters.
This is your third time on POH doing the same thing?
Have courage wishing all the best.sent from my Xperia Z3 compact via TapaTalk
-
My first. Nuno did the one from 4.32 to 4.33… About 3 months ago…
Geee this time I am keeping a copy of the db before including lods so we can use f4browse for this part of the process.
I had to use the deletion of last registry a couple times… And im very glad I could. Saved me a few hours of work.
The issue is the changelog. How much can we rely on it.
Theather development is important to push the limits. Plus… Korea is just… Well. The same ol.
Different scenarios fit well with the new cockpits (f/a 18, harrier,…). And we are this close… After so many years… Of so many different people working on this…
Not a chance we give up.
-
I hope in this thread the current process to be written down and also some tips and tricks to make things securely and faster.
Also if a tool will come up to help… it will be more then welcomed.