U2 and ITO 1.0.1 compatibility
-
IMO … the easiest and safest way for theatre Devs to maintain their theatres working along updates without the need of endless binary DB rebuild from scratch … is to use default database and accept some compromises.
True, this would be the easiest way. Regarding the Ikaros theater we have passed the point of no return. That means lots of work and DB editing in 4.33 U1. So, we have agreed to implement only the U2 or U3, U4 etc. features that are / will be relevant to the theatre. A full scratch rebuilding will be done in 4.34.
I believe the same path will be followed by other major theater creators, otherwise we will stuck forever in development.
-
IMO … the easiest and safest way for theatre Devs to maintain their theatres working along updates without the need of endless binary DB rebuild from scratch … is to use default database and accept some compromises.
Sorry but this is not the only way.
We have talked thoroughly in this forum about it I believe.
If theaters are stack with default database only then there is no uniqueness, no differentiation than terrain and TE.
In that way the database should be locked or not in a structure that theater creators could adjust it as previously. I mean before 4.33.So avoiding a database tool to easily make theaters compatible with new versions of BMS ain’t the way I believe.
If theater guys start updating and in the meantime adding altering etc they will release for a few months and then a new bms version and ok here we go again and again and again…
So at some point re inventing the wheel should be stopped. -
Matlab for db edits I see trouble….
Sent from TapaTalk
-
If the Greek and Turkish communities would be blessed in the future bms releases to have unique F-16 airframe records in the stock database, for our 4 main HAF aircraft versions, as and the respective 4 THK ones, then that would be more than enough to help reduce in half the necessary time for our theater mods. Now we have only one “generic” version with/without CFT’s (representing a single-seat HAF PXIII bird), and to be honest, that would help not only Ikaros, but other area theaters like EMF and Aegean the same way. Just like ITO has populated its unique airframes for Netz, Barak’s and Sufa, single-seats and two-seaters.
(And if, as my hopes, one day we get the CFT’s implemented properly as external tanks with the relevant code, and not requiring a full airframe model only to represent the CFT version, this would also help reduce the records. But that’s another story.)
So m8, can you please at least pass internally this personal request, if devs can consider and evaluate such an addition for the future? Please?
-
Please release a useful DB-conversion/adaptation tool soon.
As we (theater devs) respect your work, consider you guys respecting ours.
This endless developing really discourages other than Korea’s theater devs…It would be much wiser to stop releasing Ux updates, or even 4.xx versions if no conversion/adaptation tool is included.
Along with the FalconBMS as a super-duper simulation software, THEATERS variants are the two key elements that keep the falcon community still alive. Remove one, Falcon dies.
-
I do agree, BUT, i consider more valuable to have the proper assets (F-16’s) in the stock db, just like ITO.
-
And because we are not so crazy and we understand the pain the BMS team has to deal with and we know how much effort and time needs a database tool for theaters compatibility. I believe it would be, for a first stage, easier to have excel import and export.
Something like that will be needed for the db tool we talk about also I believe, so the work for such excel import export will not be in vain.
Having this feature I believe it will not be ideal but for sure can help greatly to manage such changes , spot them in the blink of the eye and import back what the theater team wants. By this what will remain would be the 3ddb issue but it would be better than nothing.
Even for the 3ddb a same tool will help by knowing previous records and new records in excel. The dev will easily know what and where to do it. -
If the Greek and Turkish communities would be blessed in the future bms releases to have unique F-16 airframe records in the stock database, for our 4 main HAF aircraft versions, as and the respective 4 THK ones, then that would be more than enough to help reduce in half the necessary time for our theater mods. Now we have only one “generic” version with/without CFT’s (representing a single-seat HAF PXIII bird), and to be honest, that would help not only Ikaros, but other area theaters like EMF and Aegean the same way. Just like ITO has populated its unique airframes for Netz, Barak’s and Sufa, single-seats and two-seaters.
(And if, as my hopes, one day we get the CFT’s implemented properly as external tanks with the relevant code, and not requiring a full airframe model only to represent the CFT version, this would also help reduce the records. But that’s another story.)
So m8, can you please at least pass internally this personal request, if devs can consider and evaluate such an addition for the future? Please?
+1
-
i too, second this petition since the HAF BLKs are widely used by many players
-
A theater update tool seems more urgent than ever. BMS has come a long way and evolved in a point that a solution needs to be provided in order to allow a smooth integration of new updates with specific theaters we all love to fly and fight in BMS such as ITO, Ikaros, and POH.
Unique F-16 HAF and TUAF airframe records in the stock base is something i think should be included in future releases in order to enhance the realism and accuracy of BMS towards a complete F-16 user database.
If people with extensive involvement in theater development suggest that this solution would also provide a more helpful environment for their future work then i see a lot of sense in this! Hope BMS devs will consider this!
-
Just to clarify since this thread meandered off to discuss strategies for keeping the db up to date, am I correct that:
- 1.0.2 is coming, and it’ll work with U2.
- Those with a campaign in progress should not update.
- 1.0.2 might be able to load the campaign saves from 1.0.1/U1. Still TBD.
Is that all right?
(Basically I am on day 3 and my campaign is going well, I’d like to retain my progress!)
-
how about U3 and 1.0.2 compatibility?
-
Please release a useful DB-conversion/adaptation tool soon.
As we (theater devs) respect your work, consider you guys respecting ours.
This endless developing really discourages other than Korea’s theater devs…It would be much wiser to stop releasing Ux updates, or even 4.xx versions if no conversion/adaptation tool is included.
Along with the FalconBMS as a super-duper simulation software, THEATERS variants are the two key elements that keep the falcon community still alive. Remove one, Falcon dies.
A tool for this is already in development, thanks again on the creation of CET
However, it takes a lot of time to create and test.
So no promisses on a release date.gr Falcas
-
how about U3 and 1.0.2 compatibility?
was never tested. However, 1.0.3 will be here soon.
-
Falcas, your PM box is full.
-