FO - Battle For Balkans Theater
-
A.S and Archer you are missing my point - I didn’t criticize the inclusion of a modified SU-27 FM, but the fact that it is installed by default without user consent. since it is a global file it makes the install MP incompatible with the default install.
Point taken, but incompatible only if the Simdata folder would be validated (by BMS or 3rd party-tools) - future
For MP it has no impact whatsoever.I do agree though, that the installer (as in the previous ones Aphex made) should have included
a “Do you want to install this” option + explanation + rollback-backup.“Touching” global files is a very sensitive area and i personally (in RF i.e) avoid it completly, or the installer informed you (RF particle.sys file install/no install option in example).
For this theater though, it was a wish by community and thus a compromise was made i believe. Every coin has two sides. -
A.S and Archer you are missing my point - I didn’t criticize the inclusion of a modified SU-27 FM, but the fact that it is installed by default without user consent. since it is a global file it makes the install MP incompatible with the default install.
Ok let me Explain. Now during the making of BFB we clearly side that there will be a Su-27 Pit and FM, now before you install the Theater it clearly says in the credit list that there is a FM and A pit made by Mr. so and so. Now about the MP incompatibility i am sure FM of a jet which is hardly flown in Korea or IT theater is going to be a Issue at all, matter of fact it doesn’t cause any MP incompatibility at all.
-
It will also over write any custom particlesys.ini you may have, so I would recommend a separate install from your normal fly install if you are running anything custom. We at the 1st VFW have instructed our members to use a separate install.
-
Ok let me Explain. Now during the making of BFB we clearly side that there will be a Su-27 Pit and FM, now before you install the Theater it clearly says in the credit list that there is a FM and A pit made by Mr. so and so. Now about the MP incompatibility i am sure FM of a jet which is hardly flown in Korea or IT theater is going to be a Issue at all, matter of fact it doesn’t cause any MP incompatibility at all.
not everyone read the credits before installing, and not everyone may be aware of the meaning of it.
There should not be such thing as ‘slightly MP incompatible’ install… Either 100% or not. I believe BMS devs will agree.
BTW it won’t affect just when flying the SU27 but also if the AI is flying it since it uses the OFM.@A.S:
I do agree though, that the installer (as in the previous ones Aphex made) should have included
a “Do you want to install this” option + explanation + rollback-backup.“Touching” global files is a very sensitive area and i personally (in RF i.e) avoid it completly, or the installer informed you (RF particle.sys file install/no install option in example).
+1
Again I strongly recommend you clarify this in an ‘announcement’ of some sort to prevent future MP issues. -
-
Obviously one issue is 2 people flying SU27s with different FMs.
But since I don’t think anyone tested seriously MP with different FM files, who knows what else… Why get into it in the first place? -
Great news guys, I am excited to try your new mod. Unfortunately, the torrent is stuck at 0.7%. Is there any way we could get more folks seeding?
-
And after the wrong of not letting the user to know about it… is there an F4patch so the user to switch back and forth? or the user has to uninstall and reinstall each time he wants to fly mp for other theater?
So Su27 dat files and particle sys file… what else?
Also the member that created the Aegean v2.1 for 320FW installer has update capabilities and no virus warnings from no one…
could u please upload a simple rar with the files so to see and avoid the problems? I don’t want to create a new Falcon install just to compare and find the files.
oh thanx for the hard work and efforts but those would be a good thing to be looked and fixed.
Damn I must hurry and inform my squad members… this will totally fubar our setup…
-
must put the Balcans Objects Features by nove inside the theather
its gives to that amazing theather new ERA with this great airport cities and village!!! -
Hi guys
I thorougly enjoy FO. Thx for the hard work there.
And please clearly state if the installer does more than just installing a theater. Everybody can make an informed choice of installing it or not.Thats an easy thing to do.
Currently it is not clear.
Snowman
-
I can avoid all the mp problems having 2 installs.
When 4.33 will be out (hoping the su27 would be in) I hope this theater will be included in the setup.
Maybe should be right to inform the users to install this theater just in another new stock install and hardisk.I think the point is 2 installs. Faster for everyone.
cheers
-
Hmmm, there should be a serious warning on this product.
Downloading and flying the online Battle fo Balkan campaign will cause:
- Serious deprevation of sleep
- Prolonged human interaction through text and speech via the world wide web
- Combat anxiety and fear
- Pure joy
- Friends in all parts of the world
- Love for a fantastic product called F4 BMS
To the developers of this fantastic product….
Thank you !
-
Hhmmm…. on my own, I’d add a little one:
- Wifeys’ and gfs’ sense of deprivation and will to leave you alone at last
(and please tell me if is this nuts)
-
To Dema and Tsanis: +100 here gladly IMHO!:D
Not to mention the same for the newcoming Aegean theater, of course.
Best regards,
-
@Residual8effects:
It will also over write any custom particlesys.ini you may have, so I would recommend a separate install from your normal fly install if you are running anything custom. We at the 1st VFW have instructed our members to use a separate install.
False, Battle for Balkans does not overwrite BMS particlesys.ini.
For the record, the only BMS file which is overwritten is the SU27 FM dat.
All other files are “added” and did not previously exist, and are limited to the new pits (not over written), and 2 dats (Su27, 1 dat + 1 afm dat)
To all those who are worried about bonking your install with BfB, simply back up the SU27 Dat file under simdata as it’s the only file modified from the stock files.
-
And after the wrong of not letting the user to know about it… is there an F4patch so the user to switch back and forth? or the user has to uninstall and reinstall each time he wants to fly mp for other theater?
Don’t see the point of this. If anyone is worried just back up the 2 FM dats for the Su-27.
So Su27 dat files and particle sys file… what else?
Only the standard Su27 dat file. No idea why users are claiming particlesys was modified since it wasn’t.
Also the member that created the Aegean v2.1 for 320FW installer has update capabilities and no virus warnings from no one…
Any other non related facts to share? TBH I’ve always had a hard time spelling Aegean.
could u please upload a simple rar with the files so to see and avoid the problems? I don’t want to create a new Falcon install just to compare and find the files.
Ask your friend above who made the Aegean installer to check for you.
oh thanx for the hard work and efforts but those would be a good thing to be looked and fixed.
Thanks followed by the word “but” is generally passive aggressive in nature, but let’s just pretend you said “nice job guys, really like it.”
Damn I must hurry and inform my squad members… this will totally fubar our setup…
Seriously, dude. Seriously.
-
Good to know what is being changed. Thx for the info.
Snowman
-
Does this theatre includes a real structure of the Aviano AB? Or it uses the default korean one?
-
False, Battle for Balkans does not overwrite BMS particlesys.ini.
For the record, the only BMS file which is overwritten is the SU27 FM dat.
All other files are “added” and did not previously exist, and are limited to the new pits (not over written), and 2 dats (Su27, 1 dat + 1 afm dat)
To all those who are worried about bonking your install with BfB, simply back up the SU27 Dat file under simdata as it’s the only file modified from the stock files.
I just wish this had been said in the theater release thread(s) (not in some random model development thread). Would’ve prevented a lot of hemming-and-hawing, confusion, consternation and the associated un-necessary mis-understandings.
BTW, if I do this: “…. simply back up the SU27 Dat file under simdata as it’s the only file modified from the stock files” and fly BfB on the FO server, what happens? Problem or no problem?
-
Okay a Few Clarifications…
1. Whether the Su-27.dat File is changed or not does not matter. Because Hardly anyone flies the Su-27 without the Cockpit Installed. It is most of the time Flown just by the AI, and it shouldn’t change its behavior much, if at all…
2. The Su-27 Cockpit Package that Nizmo and MetalHead will release to the public will Contain the very same Su-27.dat file provided in Balkans.
3. We are not making changes to the F-16 or any other Important FM, obviously, though some who are proselytizing in this thread have done so in the past.
4. Particlesys.ini file has not been changed, it was changed for the better in Red Flag
5. It does not matter if people have different Su-27.dat file when playing Korea it will not affect anything.
6. We will update the Installer with the ability to backup the old version, and as a stop gap we will put the Su-27.dat file up shortly for people to re download to their backups.
Regards,
Mystic