Next I will try again my worst case…
Spawn delay 20 min., 10 enemy a/c’s on the ground, and guns guns guns. 
The last time I tried, I had still my old rig with a i5-3450 (3,2 GHz) and a GTX-960, and the result, after hitting most of the a/c’s in one run, was a “down to under 10 FPS”.
Worse case scenario: Campaign, DAY1 0730, Poor weather, 100% Cumlus, TGP + WPN + FLIR on HUD, 12 displayed contrails. => 20FPS. Still playable, perfect for me.
If not really needed by the player, you can disable HDR lightning in the config. It raises up to 10 FPS…
2c
Earlybite
Hi,
I checked my folders!
New Vanilla
Texture 1,37 GB 1,32 GB 50 MB
Texture Pollak 1,27 GB 1,22 GB 50 MB
Texture Osan 61,7 MB 9,17 MB 52,53 MB
This is from new tiles for Osan…
objects 3,82 GB 3,42 GB 400 MB
objects files 1,26 GB 1,16 GB 100 MB
KoreaObj 1,86 GB 1,56 GB 300 MB
And this from the database (AFAIK)…,
and from additional textures.
So, complete, and this is correct, contains my upload ca. + 350 MB data (uncompressed).
And again, my upload contains only the vanilla installation + the/my Osan mod. The file size of 680 MB results mainly of the the size of the vanilla objects folder.
Best regards
Earlybite <who is=“” having=“” currently=“” a=“” good=“” cup=“” of=“” green=“” tee=“” <lg=“”>></who>
Hi dema!
No issue there, or here.
But I still do not understand correctly…
What the current download contains is my object folder, ‘is’ in the case that all relevant files are present.
And my object folder is, without my mod, full vanilla.
That is the reason, why the download size is 680 MB (zipped).
But I can make a new upload with the complete objects folder, and a separate upload only with LOD’s.
Let me know…
But that would increase the download size. My backup vanilla objects folder size is 3,4 GB, current 4,3…
Maybe a clean db with your mod included (zip object folder) could avoid a ban
Just an idea
I’m not pretty sure, who do you mean, or what exactly you mean (ban, me, what)…, but…
One word to that (kind of) upload:
IMHO is it for a “normal” user not so easy to work with the LE, and even if one has experiences with the LE, there are 21 LOD’s, and it is not alone to install them, you need to update all Hitboxes, place them via BMS Editor, etc…
This kind of upload is based of an older thread “Vanilla Osan”, I only took the file names and made a batch file. [1]
680 MB results from the size of the vanilla object folder. My mod needs, like I’ve shown also in a description on my web page, additional 300 MB, because of the textures.
IMHO is a C&P the easiest way for one, who wants to use that mod…
And if you made a backup of your “old” Terrdata folder, anything is fine.
[1]
SET mPath_Source=“C:\Falcon BMS 4.33 U1\Data\Terrdata\objects”
SET mPath_Dest=E:\0-Install\Data\Terrdata\objects
SET mFile_1=bmsrack.dat
SET mFile_2=f4sndtbl.sfx
SET mFile_3=FALCON4.ACD
SET mFile_4=FALCON4.ct
SET mFile_5=falcon4.ddp
SET mFile_6=FALCON4.FCD
SET mFile_7=falcon4.fed
SET mFile_8=FALCON4.ICD
SET mFile_9=FALCON4.ini
SET mFile_10=FALCON4.OCD
SET mFile_11=FALCON4.PD
SET mFile_12=FALCON4.PHD
SET mFile_13=FALCON4.RCD
SET mFile_14=falcon4.rkt
SET mFile_15=FALCON4.RWD
SET mFile_16=FALCON4.SSD
SET mFile_17=FALCON4.SWD
SET mFile_18=FALCON4.UCD
SET mFile_19=FALCON4.VCD
SET mFile_20=FALCON4.VSD
SET mFile_21=FALCON4.WCD
SET mFile_22=FALCON4.WLD
SET mFile_23=KoreaObj.HDR
SET mFile_24=KoreaObj.LOD
SET mFile_25=KoreaObj.TEX
SET mFile_26=rack.dat
SET mFile_27=sp_hdr_lod_tex.txt
copy %mPath_Source%%mFile_1% %mPath_Dest%
copy %mPath_Source%%mFile_2% %mPath_Dest%
copy %mPath_Source%%mFile_3% %mPath_Dest%
copy %mPath_Source%%mFile_4% %mPath_Dest%
copy %mPath_Source%%mFile_5% %mPath_Dest%
copy %mPath_Source%%mFile_6% %mPath_Dest%
copy %mPath_Source%%mFile_7% %mPath_Dest%
copy %mPath_Source%%mFile_8% %mPath_Dest%
copy %mPath_Source%%mFile_9% %mPath_Dest%
copy %mPath_Source%%mFile_10% %mPath_Dest%
copy %mPath_Source%%mFile_11% %mPath_Dest%
copy %mPath_Source%%mFile_12% %mPath_Dest%
copy %mPath_Source%%mFile_13% %mPath_Dest%
copy %mPath_Source%%mFile_14% %mPath_Dest%
copy %mPath_Source%%mFile_15% %mPath_Dest%
copy %mPath_Source%%mFile_16% %mPath_Dest%
copy %mPath_Source%%mFile_17% %mPath_Dest%
copy %mPath_Source%%mFile_18% %mPath_Dest%
copy %mPath_Source%%mFile_19% %mPath_Dest%
copy %mPath_Source%%mFile_20% %mPath_Dest%
copy %mPath_Source%%mFile_21% %mPath_Dest%
copy %mPath_Source%%mFile_22% %mPath_Dest%
copy %mPath_Source%%mFile_23% %mPath_Dest%
copy %mPath_Source%%mFile_24% %mPath_Dest%
copy %mPath_Source%%mFile_25% %mPath_Dest%
copy %mPath_Source%%mFile_26% %mPath_Dest%
copy %mPath_Source%%mFile_27% %mPath_Dest%
SET mPath_Source=“C:\Falcon BMS 4.33 U1\Data\Terrdata\objects\KoreaObj”
SET mPath_Dest=E:\0-Install\Data\Terrdata\objects\KoreaObj
SET mDDS_01=6058.dds
SET mDDS_02=6059.dds
SET mDDS_03=6060.dds
SET mDDS_04=6061.dds
SET mDDS_05=6062.dds
SET mDDS_06=6063.dds
SET mDDS_07=6064.dds
SET mDDS_08=6065.dds
SET mDDS_09=6066.dds
SET mDDS_10=6067.dds
SET mDDS_11=6068.dds
SET mDDS_12=6069.dds
SET mDDS_13=6070.dds
SET mDDS_14=6071.dds
SET mDDS_15=6072.dds
SET mDDS_16=6073.dds
SET mDDS_17=6078.dds
SET mDDS_18=6079.dds
SET mDDS_19=6080.dds
SET mDDS_20=6081.dds
SET mDDS_21=6082.dds
SET mDDS_22=6083.dds
SET mDDS_23=6084.dds
SET mDDS_24=6085.dds
SET mDDS_25=6086.dds
SET mDDS_26=6087.dds
SET mDDS_27=6088.dds
SET mDDS_28=6089.dds
SET mDDS_29=6090.dds
SET mDDS_30=6091.dds
SET mDDS_31=6092.dds
SET mDDS_32=6093.dds
SET mDDS_33=6094.dds
copy %mPath_Source%%mDDS_01% %mPath_Dest%
copy %mPath_Source%%mDDS_02% %mPath_Dest%
copy %mPath_Source%%mDDS_03% %mPath_Dest%
copy %mPath_Source%%mDDS_04% %mPath_Dest%
copy %mPath_Source%%mDDS_05% %mPath_Dest%
copy %mPath_Source%%mDDS_06% %mPath_Dest%
copy %mPath_Source%%mDDS_07% %mPath_Dest%
copy %mPath_Source%%mDDS_08% %mPath_Dest%
copy %mPath_Source%%mDDS_09% %mPath_Dest%
copy %mPath_Source%%mDDS_10% %mPath_Dest%
copy %mPath_Source%%mDDS_11% %mPath_Dest%
copy %mPath_Source%%mDDS_12% %mPath_Dest%
copy %mPath_Source%%mDDS_13% %mPath_Dest%
copy %mPath_Source%%mDDS_14% %mPath_Dest%
copy %mPath_Source%%mDDS_15% %mPath_Dest%
copy %mPath_Source%%mDDS_16% %mPath_Dest%
copy %mPath_Source%%mDDS_17% %mPath_Dest%
copy %mPath_Source%%mDDS_18% %mPath_Dest%
copy %mPath_Source%%mDDS_19% %mPath_Dest%
copy %mPath_Source%%mDDS_20% %mPath_Dest%
copy %mPath_Source%%mDDS_21% %mPath_Dest%
copy %mPath_Source%%mDDS_22% %mPath_Dest%
copy %mPath_Source%%mDDS_23% %mPath_Dest%
copy %mPath_Source%%mDDS_24% %mPath_Dest%
copy %mPath_Source%%mDDS_25% %mPath_Dest%
copy %mPath_Source%%mDDS_26% %mPath_Dest%
copy %mPath_Source%%mDDS_27% %mPath_Dest%
copy %mPath_Source%%mDDS_28% %mPath_Dest%
copy %mPath_Source%%mDDS_29% %mPath_Dest%
copy %mPath_Source%%mDDS_30% %mPath_Dest%
copy %mPath_Source%%mDDS_31% %mPath_Dest%
copy %mPath_Source%%mDDS_32% %mPath_Dest%
copy %mPath_Source%%mDDS_33% %mPath_Dest%
SET mPath_Source=“C:\Falcon BMS 4.33 U1\Data\Terrdata\korea\texture\texture_Polak”
SET mPath_Dest=E:\0-Install\Data\Terrdata\korea\texture\texture_Polak
SET mFile_1=HOSAN004.dds
SET mFile_2=HOSAN005.dds
SET mFile_3=HOSAN008.dds
SET mFile_4=HOSAN009.dds
SET mFile_5=HOSAN010.dds
SET mFile_6=HOSAN011.dds
SET mFile_7=HOSAN014.dds
SET mFile_8=HOSAN015.dds
SET mFile_9=HOSAN016.dds
SET mFile_10=HOSAN017.dds
SET mFile_11=HOSAN004N.dds
SET mFile_12=HOSAN005N.dds
SET mFile_13=HOSAN008N.dds
SET mFile_14=HOSAN009N.dds
SET mFile_15=HOSAN010N.dds
SET mFile_16=HOSAN011N.dds
SET mFile_17=HOSAN014N.dds
SET mFile_18=HOSAN015N.dds
SET mFile_19=HOSAN016N.dds
SET mFile_20=HOSAN017N.dds
copy %mPath_Source%%mFile_1% %mPath_Dest%
copy %mPath_Source%%mFile_2% %mPath_Dest%
copy %mPath_Source%%mFile_3% %mPath_Dest%
copy %mPath_Source%%mFile_4% %mPath_Dest%
copy %mPath_Source%%mFile_5% %mPath_Dest%
copy %mPath_Source%%mFile_6% %mPath_Dest%
copy %mPath_Source%%mFile_7% %mPath_Dest%
copy %mPath_Source%%mFile_8% %mPath_Dest%
copy %mPath_Source%%mFile_9% %mPath_Dest%
copy %mPath_Source%%mFile_10% %mPath_Dest%
copy %mPath_Source%%mFile_11% %mPath_Dest%
copy %mPath_Source%%mFile_12% %mPath_Dest%
copy %mPath_Source%%mFile_13% %mPath_Dest%
copy %mPath_Source%%mFile_14% %mPath_Dest%
copy %mPath_Source%%mFile_15% %mPath_Dest%
copy %mPath_Source%%mFile_16% %mPath_Dest%
copy %mPath_Source%%mFile_17% %mPath_Dest%
copy %mPath_Source%%mFile_18% %mPath_Dest%
copy %mPath_Source%%mFile_19% %mPath_Dest%
copy %mPath_Source%%mFile_20% %mPath_Dest%
@Switch:
Why would I be flaming? I just wonder how people who already modded their install can do with that…
They would need to add the provided LODs themselves, add new features (CT and FCD), modify your export file to replace CT references in there with the ones they would use. Not really user friendly, my opinion. I could do that in 5 minutes, not everyone can…
We could meet but I don’t want to and German beers taste like shit, so I’ll pass the invitation.
I have no beer for you. And that wasn’t an invitation… You know exactly what exactly it is…, but you are not man enough! So hurry up, back into your cave, “man”. And stay away from my threads.
@Switch:
680MB, that a joke?
If you used the 3DDB builder in sticky, it could be like 10-20MB…
I do not know, what/who you are, but, no, it isn’t….
BTW: Sir, are you flaming?! If so, let’s meet a little!
Earlybite
Hi!
I’ve made a new objective with non rooting for AI taxxing.
With rooting it can happen, that an a/c that has a take off after you, taxi before you, and in that case it will stand in front of its root point waiting you will have past.
And great a/c’s, for ‘Large ParkingPoint’, are travelling, under circumstances, along the whole taxi points…
It can happen, if you e.g. change an existing TE and place flights before yours.
You can download the new objective here:
http://www.individcore.de/Downloads/Osan/Osan-Objective-1-3-Non-Root.zip
To enable that objective, open the Editor, select ‘Clear all’, and import than that new one. Ready.
Best regards
Earlybite
Operational rooting for AI taxxing!
Normally it works for take off, except a flight after yours is taxxing before you, it would stand in front of you next to the rooting point, waiting that you have passed.
And a/c’s for 'Large parking point, are, under circumstances, travelling along all taxi points, even if their parking points are the first ones in the cue.
Fully operational rooting for AI taxxing would, IMHO, improve the whole ramp start scenery, let you exploit the possibilities given of an air base.
Best regards
Earlybite
Hi,
I’ve made a download!
So, if you want it, you can have it…
http://www.individcore.de/Earlybite/BMS/OsanAirbase-DL.html
BTW:
I’ve reworked the taxi light model a little, a little slimmer.
Now also runways have that “taxi light”, which are runway lights there.
AI taxxing is with rooting. It works. Only to inform…
Enjoy, have fun, feel Osan Airbase.
Best regards
Earlybite