
AF Israel theater
-
-
sieht geil aus. wie is es mit der stabilität?
-
oh mein Gott.
nicht nur die Koreanische Staatspolizei besucht uns, sondern jetzt auch der Mossad!
-
Hi
Sind die anderen Theater auch für AF?
Lg Bflat
-
ich glaub ned. dessert storm wäre noch cool
-
- Offizieller Beitrag
Wow, das ist was für mich!
Mit neuen Ideen in ein neues Fluggebiet, neue WarStory ...... Wir könnten auch nur temporäre zum Einsatz gehen.....
Ich bitte mal um eine Test. Wer könnte dieses in die Hand nehmen?
Thx.
Gruß
Dro16 -
...habe es jetzt das "4 x" probiert, bei ca. der Hälfte des Downloads immer wieder Abbruch.
Troublemaker,
Desert_Storm speziell für AF gibt es.
Nennt sich: ""ODSAF_MODTEAM_v100"" -
Wir von der 8th FW Wolfpack standen vor gut einem Jahr auch vor der Entshceidung, zusätzlich zu den Standart-Theatern Korea und Balken Zusatztheater zu verwenden. Das Hauptaugenmerk wurde darauf gelegt, dass die Campagnen eine Herausforderugn beiten und das Spiel auch Online stabil ist, sprich so gut wie keine CTD oder ähnliche Probleme. In die Endauswahl haben es dann folgende geschafft:
- PMC Operation Desert Storm V1.07
- Panama V1.01
- Israel Mk2 (incl dem Hotfix)All diese Theater haben sich bei uns bewährt. Abstürze sind so gut wie keine zu verzeichnen, lediglich die Verwenung der Ayes-Pits für HiRes Auflösungen udn Widescreendarstellung ist etwas aufwändiger, aber funktioniert am Ende Problemlos
Desert Storm zeichnet sich halt durch Flugzeiten von teilweise 4 Stunden und mehr aus, is nur was für echte Freaks. Es gibt da aich ne 1.1 Version oder so, aber die haben wir nicht getestet, in wie fern die läuft, keine Ahnung
-
Getestet und es ist o.k.
-
und noch ein mehr fotos
-
Moin,
leider funzt der Link nicht. Siehe Hooker, nach der "Hälfte" bricht er ab.Gruß
Witch
-
Versucht mal das:
Und danach diesen Patch:
Je nach Eisntellunen braucht ihr noh diese Zeile dann in der bfops.cfg:
set g_bEnableColorMfd 1
Allerdigns nur, wenn eure MFD komplett grün sind danach.
Enjoy
-
Hi
Nach dem Install des Israel und Nevada Theaters war die RPM Anzeige im Hud weg.Das habe ich schon wieder hinbekommen.
Aber es fehlt noch der Sound von der F16 in der aussansicht.Eine Idee dazu?
P.s.:Wäre nicht schlecht wenn man wüsste was alles was in der Bfops steht genau bewirkt bei einer änderrung und was sich lohnt noch hinein zuschreiben.Wenn einer einen Link hat dazu bitte posten
Lg Bflat
-
Hi
Ich habe es rausgefunden.set g_bUse3dSound 0
Man musste von 1 auf 0 stellen.Bitte trotz allem sollte jeder der was zur BFops sagen kann hier posten.Vielleicht finden sich ja verbesserrungen.
Lg Bflat
-
Hier mal ein kleiner Teil, was alles möglich ist. Quelle ist das Forum der ukfalconeers.com
ZitatDIGGING THE SECRETS
In conclusion, if u want these new options in AF, you simply have to create with NOTEPAD a file,
naming it BFops.cfg placing it in the main folder where the exe resides, and putting in each line of this file a text that modifyes the sim.
If u do'nt like some of the tweacks created, u simply cancel its line.
The form of each text line that changes parameters
is similar to the following:
set g_nPadlockBoxSize #
where # is a number, in some cases 0 or 1 (boolean), in other incremental numbers, integer or
decimals.
F.i. the line above changes the dimensions of the
padlock box with the increment of #.
If u set it as follows:
set g_nPadlockBoxSize 0
that 0 means turn completely off the padlock box.
With a higher # ( try 5 for example) u make it bigger.GROUP A
Possible parameters to put into the BFops.cfg file that surely work in AF and do not harm MP flights are:set g_nPadlockBoxSize #
Explained aboveset g_bNoRPMOnHud #
Possible values 0/1
With 1 no RPM on HUD, with 0 u can see RPM on HUD.set g_nShowAVTRStatus #
Possible values 0/1/2
It changes the AVTR "RECORDING" message on
screen (0 = No message on screen, 1 = Yes, 2 = Blink start/stop)
For example:
set g_nShowAVTRStatus 0 turns it off.
If u like it blinking, write
set g_nShowAVTRStatus 2
This might remind u not to do somthing dumb while tape is rolling-LOLset g_bUse3dSound 1
Possible values 0/1
1 enables 3D Sound : recommended
If u have a decent sound card, test it to experience improved stereo sound .
An other advantage is for Vocal Commands programs users: I tested VAC with this option
on,and got vocal recognition much improvedset g_bOldSoundAlg 0
It reverts to older sound system (polled interface) in case of problems.
To be used for safety together with use3Dsound.set g_bMFDHighContrast #
Possible values 0/1
Default is 0
1 recommended for better screens reading.
Use different colours on colour MFD (helps colour blindness distinction), it changes the color scheme of some MFD's symbols and lines.set g_fCursorSpeed #
Default is 1.0
2.0 or 3.0 recommended for having radar cursor working smoothly .set g_fRadarScale #
Possible values 0.1 with increasing decimals
1.0 (100%) is the default.
Changes Radar Blips size.
Not recommended to go less than 0.5 because the blip size becomes little as a pixel and difficult to bug/lock.
0,8 recommended: blips are smaller than the default size preventing overlapping, but still
comfortable to bug/lockset g_bEPAFRadarCues #
Possible values 0/1
0 is the default, bugged/locked radar targets are drawn as triangles, how we are used to see in
standard version .
With 1, bugged/locked radar targets are drawn as square boxes with an arrow vector for speed and
heading, rather than triangles.
This is the default for EPAF countries F-16 models.set g_fPOVSpeed #
Possible values 1 increasing incremental
Default is 1.5
With 5, the POV speed is very sudden and uncomfortable.
Not recommended to go more than 2.5 or 3set g_bUseMouse3forSOI #
Possible values 0/1
With 0 (default) u use arrows keyboard keys for moving radar cursors, as we're used to.
With 1 (recommended, more handy) u can use also the MIDDLE MOUSE Button for moving radar cursors: u press it and while pressing now u can move the radar (or HARM, MAV or LGB) cursors with mouse.set g_fMfdTransparency #
Possible values 0 to 100(%)
Default is 50
This adjusts transparency MFD in HUD Only view.
0 is full transparent, 100 is not transparent at all.set g_bCATIIIDefault #
Possible values 0/1
Default is 0
1 sets the aircraft configuration to CATIII upon entering the cockpit, regardless of your loadout.WARNING!!!!!
THE FOLLOWING ARE CHEATING MODESset g_fPadlockBreakDistance #
Default is 8
Possible values 1, increasing incremental.
It changes the padlock break distance: if u set it 60, u'll be able to padlock till this distance.set g_bAllowOverload #
Possible values 0/1
Default is 0
0 does'nt cause damages to airframe on high G manouvres.
1 causes damages.WARNING!!!!!
THE FOLLOWING IS ACTIVE BUT MESS UP VISION ON 3D VIEWset g_b3dDynamicPilotHead 1
Possible values 0/1
Default is 0
With 1 your pilot's head will move around in response to g's and roll input in the 3d virtual
cockpit, but also all instruments move around on the screen messing up vision.
Not recommendedTo give an idea, what follows is an example of possible content of GROUP A for the bfops.cfg :
set g_bUseMouse3forSOI 1
set g_fPOVSpeed 2
set g_fRadarScale 0.8
set g_bUse3dSound 1
set g_bMFDHighContrast 1
set g_fCursorSpeed 2.5
set g_bEPAFRadarCues 1
set g_bNoRPMOnHud 0
set g_fMfdTransparency 35GROUP B
Possible parameters to put into the BFops.cfg file that surely work in AF, BUT are suspected to harm MP stability in TE or Campaign, thereby recommended only for solo flight .
Suggestion: it might be possible to have 2 files , one named BFOPS.SOLO that contain all of the
variables (A and B groups) mentioned here and the second BFOPS.MP with different variables set (only A group).
When flying MP , the BFOPS.MP file should be renamed BFops.cfg before launcing Falcon.
When flying Solo flights , then the BFOPS.SOLO file should be renamed BFops.cfg.
An other way might be that all human pilots have the same A and B groups settings in BFops.cfg.set g_nMaxSimTimeAcceleration 16
limits the simulation to 16x time acceleration: recommended .
If u choose 32x or 64x, time acceleration reverts to 16x.
It's common knowledge that accelerating more than 16x can cause nasty consequences to Campaign or also TE, expecially on MP.set g_nNoPlayerPlay #
Possible values 1, increasing incremental
Default is 2
# sets the hours to run a campaign without suffering player not flying, where # is the number of hours of no player flights.
F.i. if u set 720, these are the hours that the campaign will run without being degraded even if
player does'nt fly.set g_bEnableWindsAloft #
Possible values 0/1
With 1 winds will change direction and strength with altitude. This makes dumb bombs very innacurate from high level, but LGBs are unaffected.
U can check the presence of winds aloft by pressing SEQ on 4 positions rotary switch on ICP:
on the DED the wind direction and its strenght will now be shown.
If u also switch down the DRIFT C/O then u'll have on HUD a dramatic vision of the wind's effect.set g_bAWACSRequired #
Possible values 0/1
If 1, AWACS does'nt reply unless there is an assigned flying AWACS
If 0, AWACS always repliesset g_npercentage_available_aircraft #
Possible values 0 to 100(%)
Default 75%
The 'percentage available aircraft' determines what proportion of your squadron's roster will be
available to undertake missions in a given tasking cycle.
You can adjust this between 0% and 100%.
However, beware; if your setting makes the number of available aircraft less than 4, you won't get any four-plane missions scheduled.
Similarly, if your setting makes the number of available aircraft less than 2, you won't get any
missions at all!
Also note that as you squadron loses planes through attrition, your percentage will represent
gradually fewer and fewer planes.set g_nminimum_available_aircraft #
Possible values 1 increasing incremental.
The 'minimum available aircraft' setting allows you to limit the effect of a low 'percentage' setting.
This setting applies a lower-limit to the number of available aircraft calculated from your 'percentage'.
You can set the 'percentage' to 0%, but if you also set your 'minimum' to 2, you will get two
aircraft available per planning phase - at least, until the point you only have one aircraft left in the squadron.Die bfops.cfg bietet also die Möglichkeit, sehr viel an den PC und den Spieler anzupassen. Radarkontaktgrössen, Padlockreichweiten, Boxengrösse, etc. Einiges davon sind auch Cheats wenn man so will. Hier sollte man halt einfach auf die Ehrlichkeit der Leute appelieren. Wobei ich denke, dass das in ner Staffel wo man sich kennt kein Problem sein sollte. Gruppe A Modfikationen sind für Muliplayer meist irrelevant, Gruppe B hingegen können das Game kaputt machen.
Es gibt noch weitere, ein Blick mit Google bringt da erstaunliches an den Tag
-