Which theaters are compatible with 4.33U1 ?
-
Falcon Editor.
Export from 4.32
Import from 4.33Of course where ever this is available.
-
I am a little confused, what exactly causes a previous version like 4.32 to not work with 4.33? What exactly gets busted, causing crashes or what? What is the fix, is it Step 1, 2, 3, , , , etc different across every theater?
-
I am a little confused, what exactly causes a previous version like 4.32 to not work with 4.33? What exactly gets busted, causing crashes or what? What is the fix, is it Step 1, 2, 3, , , , etc different across every theater?
The problem is I recycled many DB entries of 4.32 and in 4.33 can be elements what with same CT and other entires are the same but are used for different role. For ex. now we have ECM pods and chaff/falre pods with unique ECM values - even all AC and pod have the same value but now you can set up different - etc.
-
Molni - are you doing DB now? I know you like spreadsheets, you sent me enough of them, hehehe.
The way I keep things sorted is do a total assessment of the DB - break it down by CTs, parents, models, skins, Flight models etc, all on Excel spreadsheets - so that you know what connects with what - that is the only way I an keep from introducing conflicts as I step my way thru a DB with new material. I keep a detailed change log of every DB edit session and test it, clearing all the crashes and bugs each time before moving forward. I have found that being systematic like that avoids fixing one thing but breaking another. Falcon is very interconnected.
-
Molni - are you doing DB now? I know you like spreadsheets, you sent me enough of them, hehehe.
The way I keep things sorted is do a total assessment of the DB - break it down by CTs, parents, models, skins, Flight models etc, all on Excel spreadsheets - so that you know what connects with what - that is the only way I an keep from introducing conflicts as I step my way thru a DB with new material. I keep a detailed change log of every DB edit session and test it, clearing all the crashes and bugs each time before moving forward. I have found that being systematic like that avoids fixing one thing but breaking another. Falcon is very interconnected.
Currently I’m not working on anything and I did not documented everything becaues it would take forver creating the theater.
Funny thing I do not ever remember I how created exactly the JP-233 usage in my MOD what was explained by WaveyDave 5-6 years ago.
-
Molni,
There very first rule of DB for me is to create a ton of spreadsheets, extract all the raw data and put into those sheets - then, when you wan to make an edit - your ensure your edit doesn’t share one single data point with any other item. Otherwise you wind up chasing your tail. Yes, the spread sheets take a while to put together, but once you have them the pay big dividends and most all your edits then work without causing crashes.
The other really good thing is late at night, you can, with a cup of Earl Grey tea, sort the various spreadsheets in different rows to check for data entry errors - I found a lot of errors where a digit was dropped or somehow a 0 or 255 pops up like a sore thumb that doesn’t below. Once you look at the data long enough you begin to recognize obvious errors or when common entities are hugely different and have no reason to be.
Currently I’m not working on anything and I did not documented everything becaues it would take forver creating the theater.
Funny thing I do not ever remember I how created exactly the JP-233 usage in my MOD what was explained by WaveyDave 5-6 years ago.
-
You read the matrix not see it.
There is no spoon Neo.Nice one. But excel for the extent falcon db has I believe is not the way.
Maybe good to work on specific things or if no other tool available. But bms team might leap and I’ll be left looking those spreadsheets for looooooong.Sent from TapaTalk
-
Molni,
There very first rule of DB for me is to create a ton of spreadsheets, extract all the raw data and put into those sheets - then, when you wan to make an edit - your ensure your edit doesn’t share one single data point with any other item. Otherwise you wind up chasing your tail. Yes, the spread sheets take a while to put together, but once you have them the pay big dividends and most all your edits then work without causing crashes.
The other really good thing is late at night, you can, with a cup of Earl Grey tea, sort the various spreadsheets in different rows to check for data entry errors - I found a lot of errors where a digit was dropped or somehow a 0 or 255 pops up like a sore thumb that doesn’t below. Once you look at the data long enough you begin to recognize obvious errors or when common entities are hugely different and have no reason to be.
Next time maybe I follow this way in case will be next time, but the problem is I would make a table only for relevant DB changes not for all DB values because what I do not change is not important for the MOD. The problem in case anybody wish to integrate new stuff from later DB. This is the problem. Manually doint this kind of Excel table creation is simply so time consuming…
Is the any way export the whole DB (different tab values and CT values) to Excel tables?
-
yeap time consuming but ensures legacy.
For me every dev or modder should have and use.
Once he stops or leaves something in the middle with full record of his work and steps another one can jump in and continue from where the other left. This in case we want to share for the common good, and not just go for the personal credit gouhooouuu goohooou.Am sure lack of those info or comments drive manual or guides ppl nuts… RedDog am sure was pulling his hair in the process of writing the manuals…
I know it’s a killer and boooooring and rather extend the work or add to the work but equally valuable.Imagine Ranger822 now giving models away with no info on dofs switches tex sets scripts hitbox values etc… would they be usable? or how much more time will be needed to rediscover the wheel?
-
yeap time consuming but ensures legacy.
Even if I made such table in case of CT and other later conflicts I cannot do anything… With F4B I could make a copy of existing battalion, sensor or anything and F4B do the most of the work to avoid conflitcs, I just had to give the right value to give good unit icon, setting good battalion properties, recalt of battalion stats., link IR sensor to new missile, etc. But I never was able to delete or doing anything if cometing had bad cross references in DB…
I apllied some very basic steps over and over and the result was my MOD with totally different DB which provided totally different environment.
-
Sure…
Falcon Editor desperately needs the functionalities of Objective Editor (File Edit Selection)
like import export save as xls or allow to select all lines and copy paste…
select all
copy pasteAlso a comments field column on all tables might be helpful. like “Molni changed value from xxx to yyy” or “this value is in meters” or tag some things to group them or flag them for personal use - filter functionality also instead of only short records. To be done / done / needs testing…
In many cases a flag field with fixed values of like: no status / not started / working on / awaiting verification / done , could greatly help also. those flags or tags or fields don’t need to be in the database tables of the ones that Falcon loads when flying but only when you fire up Falcon Editor…but…
-
Thanks to Starrat’s fix, the Kuwait Theatre is now compatible with 4.33.1:
-
Gentlemen,
let me add to the list in the first page of this topic the OMA 3.0 theather by dema, TCKnight and all their crew, so all the credits must be addressed to those guys.
It’s a fair good new update of their previous releases, it’s conceived to be played online and I’m just having great fun since I decided to install it.With best regards,
-
Gentlemen,
let me add to the list in the first page of this topic the OMA 3.0 theather by dema, TCKnight and all their crew, so all the credits must be addressed to those guys.
It’s a fair good new update of their previous releases, it’s conceived to be played online and I’m just having great fun since I decided to install it.With best regards,
Thanks! today new version 3.1 make for release, full support update 2 bms 4.33
-
We need something serious here.
A real list for tracking which theaters are compatible with the various versions/ updates of BMS.
It seems BMS is getting versions/ updates out, way faster than theater devs can coupe with the compatibilizations.
We don’t want the BMS to wait for anything, I know, but paradoxically we also want theaters compatible with BMS.
So my best bet is on a thread with the true compatible list for the theaters vs each BMS version/update.
Arty, mate, this is a call for your handy experience here…. -
Well bit easy. Just a new thread after each update is one way.
The thing is theater devs will never catch up the BMS pace.
We all are super glad with BMS providing us the mana and in a secured way since the 4.33.1.
I have expressed the following another time. In the BMS dev efforts are and the theater dev tools which besides MC and Falcon editor are a bit behind and need to catch up with the core development.
Sure it will be a drawback but in overall will be a leap forward.The main focus and pain is compatibility and database manipulation.
Sent from TapaTalk
-
Was thinking of something like “Theater compatibility”.
Organized by theater with what BMS version/update it is compatible.
This way one thread will do… I believe. Just like Virtual Squadroons List… theater devs should post (after 1st post with the actualized list) their theaters compatibility. -
well I agree, it’s a nice idea but a whole thread for what 2-3 theaters?
For now it’s only Korea (stock - vanilla) and Balkans. In a few days - months ITO… and then the chaos…
Maybe (and it’s a huge maybe) another one will popup but till then 4.33.3 will come and here we go again on my own…It would better if MODS of this forum add a tag next to the theater thread like C. 4.33.2
And have an announcement what this tag means.Anyway I’ll think about it. I have a ship up my axx right now to finish, for a non U2 compatible theater not released yet… :mrgreen:
-
Yeah, just like POH.
Great discussion, followed by the decision of a release (soon, very soon) with compatibility to 4.33U1.
That theater name with a compatibility tag is a good idea… -
List updated with Aegean and Somalia.
Starting now : this list for 4.33 will not be maintained anymore. Considering it has been 2 years since 4.33U1 came out, I think the transition for theaters is over
This thread will still be stickied with the guidelines for theater devs and users in the first post.