FO - Battle For Balkans Theater
-
look the skins F-16+52 :shock:
i think is a bug!!! -
@ All.
Ok … It has been stated that Installer will warn ppl that their stock sim folder will be modified. Good with that. As A.S. … lets move on.
-
I’m not in a joking nor playing mood A.S.
Database includes “sim” folder.
Database :\Falcon BMS 4.32\Data\Terrdata\objects aka the “Starfiles”
is one thing
and the :\Falcon BMS 4.32\Data\Sim content (global files)
are two COMPLETLY different things with COMPLETLY different roles and purposes. Always has been and still is within the file-structure of F4.
You can agree to disagree and there is really no need to chew any longer on this as we probably just got lost in translation before.
PS:
I need to add something to this before it goes the wrong direction:
And i, nor other people working outside of the DEV team on BMS, are not in the mood to read between the lines NOR to be told what they can and can not do with an open source free and not lawfully restricted simulation, which whole root history is based on the modding of previous commercial versions and which pure purpose and evolution is still based on the modding and the work of many - internally and/or externally. If you haven´t realized it yet, this IS what makes this sim so strong - not only the DEVs, but also the community ITSELF!
If few elitists practise a self-appointed right or status, to be the only choosen ones who determine, what can be done or not doesn´t matter, regardless what they believe. Reality check!
Nevertheless, we all have responsibilities towards eachother and we all have to find a common ground, as the work of insider DEVs is as much important as the one of the external developers and both should respect and listen to eachother for the better good - WITHOUT attitude nor such “will enforcing tone” of that kind. -
Do what you want inside data/Add-xxxxx folder. Do not touch to stock files or announce it clearly.
That’s all. Not dificlut. No big deal.
Thank you.
-
Shit happens(ed). But i have a better solution for you: SIMCHECK, so NOONE can “touch” stock files (not only FM data).
Our thoughts are the same, just the language is different :mrgreen: -
SIM folder has the data used by the core falcon database. This is what the guys say… and we all play around the words.
So playing with the data files it’s the same as playing with the database.@Fenrir this is to everyone to decide, u know very well that with f4patch u can have a tide up setup and do as many changes as u like, if u know what u r doing. As for the theater dev’s using it and with a good guide (pdf txt whatever) u can guide ppl so that they will always have a clean stock setup. With F4Patch u give the tool to prevent accidental stock setup files to be altered and left, and on the same time u can alter those files as u want and like. Sure they can still fubar the setup but u give them the tool.
-
No m8 I never used it, it was suggested a while back but I didn’t do much more than open it, looked at it, closed it and thought that I would look at it again later but I never did
Anyway, thanks to the team behind this theatre!! Tomorrow I will have my maiden flight, hopefully I will rtb in one piece
Cheers
-
How i can change clouds ? stock clouds are about 100x better, those flat looking are no go
-
Is this cockpit light normal?
https://dl.dropboxusercontent.com/u/17606390/balkans_pit.jpg
I would like to have a green or a yellow lighting but not this mix….
-
with all your respect, it may be time to learn F4patch
Thanks but I’m in the process of writing my own application to do the job…
Implementing a “patch” into F4Patch is like threading a hotdog through the eye of a sewing needle.
-
Thanks but I’m in the process of writing my own application to do the job…
Implementing a “patch” into F4Patch is like threading a hotdog through the eye of a sewing needle.
well this is clear that BMS using F4patch, creating another patch “plug in” will be easy to manage for dev teams
viva uniformisation
-
well this is clear that BMS using F4patch, creating another patch “plug in” will be easy to manage for dev teams
viva uniformisation
I’m aiming for a 1 click solution…
Ie. Balkans Activated / Stock Activated, with a really big button so that people can mash their palm on the keyboard and still get the desired result.
Using feet should be also compatible, stay tuned!
I beg to ask a question to all the F4Patch supporters out there…
Let’s say we did back up the SU-27 dat, ok fine.
Then update 8 comes out (as an example, probably wont be the case)
User installs update 8, fine.
BUT
Lets say they un-install or un-F4Patch the add-on after updating the main BMS version.
Wouldn’t that add an older file (backed up or store at time of install) and technically break the install just as bad?
Swapping files is a BAD solution no matter how it’s implemented. What is required here is to de-localize the sim folder and have it theater specific.
Then we wouldn’t need to use F4Patch or any other switching tools. Make every Add-On completely isolated from the main build.
Please remember just as adding / overwriting stock files is a bad idea, so is restoring older files which may have changed since the user updating, breaking the install just as bad if not worse.
-
I’m aiming for a 1 click solution…
Ie. Balkans Activated / Stock Activated, with a really big button so that people can mash their palm on the keyboard and still get the desired result.
Using feet should be also compatible, stay tuned!
I beg to ask a question to all the F4Patch supporters out there…
Let’s say we did back up the SU-27 dat, ok fine.
Then update 8 comes out (as an example, probably wont be the case)
User installs update 8, fine.
BUT
Lets say they un-install or un-F4Patch the add-on after updating the main BMS version.
Wouldn’t that add an older file (backed up or store at time of install) and technically break the install just as bad?
Swapping files is a BAD solution no matter how it’s implemented. What is required here is to de-localize the sim folder and have it theater specific.
Then we wouldn’t need to use F4Patch or any other switching tools. Make every Add-On completely isolated from the main build.
Please remember just as adding / overwriting stock files is a bad idea, so is restoring older files which may have changed since the user updating, breaking the install just as bad if not worse.
delocalize sim folder ?
why ?
do you think an aircraft will perform differently in korea than in balkan ?i dont agree .
you want to change core elements of BMS, feel free, but be aware you will break MP compatibilty with 4.33 …
best way is to work hand in hand : you want to make a FM evolve, submit your FM to BMS dev team and if it is OK we will integrate it
we dont want to end like before BMS release, i.e. with thousands of falcon4 version
1 to rule them all : BMS
-
Is this cockpit light normal?
https://dl.dropboxusercontent.com/u/17606390/balkans_pit.jpg
I would like to have a green or a yellow lighting but not this mix….
Looks like HAF lighting. I didn’t like it much the first time I saw it, but I’ve grown to like it quite a lot.
-
Let’s say we did back up the SU-27 dat, ok fine.
Then update 8 comes out (as an example, probably wont be the case)
User installs update 8, fine.
BUT
Lets say they un-install or un-F4Patch the add-on after updating the main BMS version.
Wouldn’t that add an older file (backed up or store at time of install) and technically break the install just as bad?
Swapping files is a BAD solution no matter how it’s implemented. What is required here is to de-localize the sim folder and have it theater specific.
Then we wouldn’t need to use F4Patch or any other switching tools. Make every Add-On completely isolated from the main build.
Please remember just as adding / overwriting stock files is a bad idea, so is restoring older files which may have changed since the user updating, breaking the install just as bad if not worse.
BMS have always said to apply official updates over a vanilla install only, ie an install with no modified global files. So an informed user should unapply the FM patch, run the update, then re apply the patch (assuming the patch is smart enough to always back up the current file). It’s really up to us to conform to the current limitations in regard to global files, we can’t blame BMS. And maybe in the future it will be easier. I also made these suggestions in the past: https://www.benchmarksims.org/forum/showthread.php?10570-Suggestion-Files-that-should-be-theater-dependent
-
Is there a way to send this new fm to BMS Devs and if possible after they check all the stuff if it could be integrated in this 4.32 ( I think yes ) and
after have a new BMS update 8?So maybe we solve the problem…
Too hard to do?
Just an opinion…
cheers
-
They have the FM dema, as far as I understand AS sent it to Mav-JP a few months ago to evaluate it. It is not us who made this FM. Shadow is the author of the FM IIRC for the su-27, We included the Su-27 because we were requested to do so, Myself or AS or Arch don’t even fly it…
Regards,
Mystic
-
Thanks Mystic,
I’d like, really , You balkans Devs and BMS Devs could find a common point.
Everyone who read these thread page could understand wrong things.
From a part we can say Falcon has a limit about his database “locked”.
I know this since years even I could be the last user here in this forum who can speak. You touch a file and the install is ruined.
Always in some new released, even a simple skin, is suggested to do a backup.
Also, in Archer ts and in your server another time as your previous releases you have 50 pilots, now in a beta release.
This is a great thing.
As a member of both Communities I want to see everybody happy.I know you will find a common point soon, even why if you both devs you work to improve falcon you get to work togheter.
Try to understand what I mean.
cheers
-
delocalize sim folder ?
why ?
do you think an aircraft will perform differently in korea than in balkan ?.My point was referring to the breaking (overwriting) of stock files. It makes no reference to the actual differences in performance of the flight models in question, and TBH I’m not even sure what they are.
-
Archer look also at the other side of the coin… ppl love the Balkans. All this talk is to make it even better. There is not only Balkans or FO. Those limitations are forced to a closed group - squad. When u go public u r exposed to public action and reaction.
Dont take it personaly… noone has to split anything with noone. U have wonderfull coders, devs, modders at FO they can manipulate such things.
No one is perfect , no one says that all this hard work goes down the toilet… the oposite. we like it we want it, we r just strange and want something more that was minor for the team that assembeled it or was overlooked… not a big deal… just do it yesterday cause I wanna use that SU-27 I heard ruskies have better jdams then amerikanskie and I want to deliver some to u… :lol:
Oh and dont forget son… the coin has 3 sides…