REDFLAG 4.0 ROUND III STARTS at Saturday the 8th November 2014 17:00 ZULU
-
The trouble, AS, is if you have Tom’s tiles installed in the default Korea theater, they are imported into Red Flag.
Negative. RF has its own dedicated theater (terrain). But on the other hand even KTO campaign would need to be made compatible with TomCatz 2015 terrain i believe.
Imagine a graphical terrain mod and elevation patch as grid…but then the campaign file…the objectvies in it and all the “pathes” need to be aligned with the new “graphics” - if that makes sense. -
AFAIK, Red Flag has to be installed over a stock BMS installation, right? That means no Janhas’ LVN2 models, no CCIP cockpits, nothing that changes entries on the DB through LOD Editor. Otherwise, installation will be porked.
Can anyone confirm this?
-
NO!
Ok… explanation required here …
Redflag it installed in its OWN “Add-on Redflag” folder (as any other add-on theater aswell).
Redflag uses its own indepentend campaign, database and terrain structure. The only common used folder (“fall-back” to stock) is the “Sim” folder.If you install Redflag it will create unique folders/files. The only folder Redflag is copy-pasting from the stock BMS into Add-on Redflag is:
:\Falcon BMS 4.32\Data\Terrdata\objects*KoreaObj*
to
:\Falcon BMS 4.32\Data\Add-On REDFLAG\Terrdata\objects*KoreaObj*
as those are the “textures” everyone ALREADY has in his install and as it would be to much to ask for clients to downlaod an extra 1GB of data for files they already have.
Hence this part is just “copied” from the stock BMS install INTO the Add-on Redflag folder. Rest is unique.Hope i was clear enough.
PS: In terms of mods, cockpits, textures … Redflag follows the same policy as BMS Team (only “clean” stuff without probable “complications” such as copyright or other “mine mine mine” issues).
-
@A.S:
Negative. RF has its own dedicated theater (terrain). But on the other hand even KTO campaign would need to be made compatible with TomCatz 2015 terrain i believe.
Imagine a graphical terrain mod and elevation patch as grid…but then the campaign file…the objectvies in it and all the “pathes” need to be aligned with the new “graphics” - if that makes sense.@ A.S: I had Tom’s Korea 2014 tiles installed, JanHas’s LVN2 models for every block (and skins) and the mooded CCIP cockpit installed over my base Korea install.
When I installed RF, I got the feeling that the installer copied the KoreaObj.LOD, KoreaObj.HDR and other files from the “base” KTO, because when entering 3D I noticed that RF uses stock F-16 models ans stock terrain tiles.
So far so good with the tiles, but the models had JanHas’ textures applied, so nogo. Also the CCIP cockpit with EHSI was somewhat messed up, probably due to ACDATA folder.
I’ve managed to fix things using these procedures:
- uninstalling RF
- backing up my Falcon BMS 4.32 folder
- uninstall Falcon BMS through Windows uninstaller (ensuring cleaned Registry from Falcon entries)
- making a new fresh BMS install + U1-U7
- install Red Flag over the fresh BMS install
- copy the …data\Add-on Redflag\ folder from the fresh install to my backup Falcon BMS 4.32\Data folder
- manually delete de fresh install
8 ) move (or copy) the backup BMS folder to the original place and with the original forlder name (Falcon BMS 4.32) - Add the two entries in \Data\Terrdata\Theaterdefinition\Theater.lst
This way, my modded install prior to installing RF remains exactly the same, while the Red Flag installation occured as intended.
I hope I made some sense here, as most probably other guys had/will encounter a similar problem when installing RF.
So, AFAIK, Red Flag installer demands a “clean” database, without mods.
Can you confirm this?
Thx in advance
PS: sorry, by the time I was writing this, didn’t catch your post above. Thx for the explanations
-
Did you even read what i wrote ? :?
PS: Redflag installs ITS OWN database (*starfiles). The only thing used from stock BMS are the KoreaObj TEXTURES, hence, what you change or mod in your stock BMS database is irrelevant for the operation of Redflag. Just dont change anything under “Add-on Redflag” as long as you intent to fly on the Falcon Online server with it.
In future (Redflag 5.0) will come 100% independent will all files unique to the install …but in return it will be a 3GB downlaod (as alot of new things are implemented).
-
@Nuno:
AFAIK, Red Flag has to be installed over a stock BMS installation, right? That menas no Janhas’ LVN2 models, no CCIP cockpits, nothing that changes entries on the DB through LOD Editor. Otherwise, installation will be porked.
Can anyone confirm this?
@A.S:
NO!
…. The only folder Redflag is copy-pasting from the stock BMS into Add-on Redflag is:
:\Falcon BMS 4.32\Data\Terrdata\objects*KoreaObj*
to
:\Falcon BMS 4.32\Data\Add-On REDFLAG\Terrdata\objects*KoreaObj*
….
Sorry, but now I’m confused. The answer above is not compatible with the answer below (as far as I understand it).
The trouble, AS, is if you have Tom’s tiles installed in the default Korea theater, they are imported into Red Flag.
@A.S:
Negative. ……
-
The KoreaObj folder contains textures for objectives and models (such as skins) and NOT terrain textures. Maybe that´s the confusion?
-
@A.S:
The KoreaObj folder contains textures for objectives and models (such as skins) and NOT terrain textures. Maybe that´s the confusion?
Yes. Ok, thanks. You’re correct …. I did not know that.
(apologies if I added to the confusion)
-
-
@A.S:
Did you even read what i wrote ? :?
Nuno Santos has right A.S. When you got JanHas LVN2 models installed before RF there will be JanHas textures copied from “\Data\Terrdata\objects\KoreaObj” as well when installing RF. Those textures are different and do not fit to RF (default) Vipers 3D models. But this is the only problem.
-
Of course. KoreaObj contains original objectives and 3D models textures. Thus, if you modify those prior to RF install they will be copy-pasted into the Add-On Redflag structure.
But that´s not my responsibility what others “mod” or “don´t mod” !!!, because my work is based on STOCK BMS conditions. I can never know nor control what mods people install on their simulation, therefore it´s their responsibility to check for compatibilities. I am always available for questions (community is + for me).To avoid this in future Redflag 5.0 will have its own KoreaObj textures…in other words you will have to downlaod 1GB EXTRA, just for files you actually already have had on your dirve (HDD).
PS:
- My recommendation - install BMS U7 fresh, set it up and BACKUP the whole thing - just in case.
- In future this problem might be solved otherwise aswell by something Aphex is working on.
-
AS even battle for balkans copies the textures from the BMS koreaobj?
-
AS even battle for balkans copies the textures from the BMS koreaobj?
I think not. You might ask Danguard for that (creator of BfB FO).
-
AS even battle for balkans copies the textures from the BMS koreaobj?
No… Only RedFlag as far as Falcon Online theaters are concerned.
-
Ok thank you.
-
Ok thank you.
Now here is a perfect example where the TY button could be used to good effect.
-
8 hours (on fast internet) to DL the latest (232 MB) RP6 theater??
-
8 hours (on fast internet) to DL the latest (232 MB) RP6 theater??
Sorry, but just now less that 2 minutes here. It was done before I could upload the picture to photobucket.
Check your ‘fast’ internet connection. Maybe reload Falcon-Online or restart your browser.
-
@A.S:
…
- The virtual pathes (road and river definitions) will not match up with the textures making your groundunits move wrong.
…
Tom has altered the virtual paths for the KI so they follow the roads-textures. He wrote that in our squadrons forum.
- The virtual pathes (road and river definitions) will not match up with the textures making your groundunits move wrong.
-
Tom has altered the virtual paths for the KI so they follow the roads-textures. He wrote that in our squadrons forum.
I haven´t looked into it yet, how well he did that, but good news.
Did he also re-built a korea.thr file from that (goes into campaign folder), so the ground-units actually understand them??My whole point is, that terrain-textures, elevations, pathes, areas etc. ( in Data\Terrdata\korea terrain or textures) need to be made compatible or in sync with the content of the campaign folder (save0.cam, TE_new.cam, korea.thr, Ojbective locations etc.). Just “patching” one part is not so wise imo.