• Offizieller Beitrag

    An alle Piloten!

    Falcon BMS 4.32 - Update 1 ist da.

    Aufgrund der unklaren Installationsanweisung wird zunächst noch keine Freigabe zum Aufspielen erteilt. Diese wird zunächst getestet und anschl. als Hilfestellung für alle Member mit einer Anleitung veröffentlicht!

    Stand by! Keine voreilige Installation! Kein "Mischbetrieb"!

    Der C/O

    Diese Zeilen gelten auch für Bluebird und Flash. :winki:

    --------------------------------------------------------------------------------------------------
    Geboren zu fliegen, aber gezwungen zur Arbeit!

  • Changelog
    V4.32 Update 1
    Exe
     fix for jet wash in MP behind a player
     Fixes for padlock mode. The padlock callbacks that were priority specific we broken (AA and AG) as were the next/prev padlock functions. These should all work more as expected now separately and together.
     Fix for Angle test value beeing doubled when aerobraking. This fixes the yawing issue when touching in cross wind and fix the gear break as well in cross wind landing.
     Fix for light airplane not rolling when brake released while heavy was rolling OK.
     Increased RTT line width for the RWR for better visibility, and as an example of how to set different RTT line widths for different virtual displays or bigger chunks of drawing code. Width for RWR is configurable by g_fRTTLineWidthRWR right now, we could move this to the 3dcockpit.dat files if we like.
     Implemented additional A/P disconnects:
    o when DBU is engaged
    o when stall horn is active
     Corrected dashed lines in SMS main and S/J pages.
     Corrected DED ALOW page, now it will be always on the CARA ALOW line when the page is entered.
     Fix for padlock mode: only missiles that are guiding on ownship are treated as high priority now. That includes friendly missiles (which is new) and means that missiles that are not guiding are treated as very LOW priority for padlocking (also new behavior).
     Added code to update the new "Current Keyfile" output on the Setup/Controllers UI screen.
     Hydraulic A and B pressure are now monitored. In case of loss of hydraulic power, the hydraulic pressure is lost more quickly if controls are used fixes the instability of AFM when engine shut down and EPU takes a few seconds to take over.
     Added new config variable g_bExternalWindowsOnTop, which will ensure that external windows are always rendered on top of all other windows and the taskbar. Default is 0 (old behavior), set to 1 to activate.
     Tacref, Loadout, Recon & Gfx Preview in setup: Fix for black screen when FSAA is forced on by the video driver. Fix busted specular highlights and glass shader.
     Corrected DEST OA1/OA2 page DCS up/down behavior.
     Changed gun damage scoring.
     Fixed CTD when the following cfg values were set:
    o set g_bShowRainDrops 0
    o set g_bShowRainRings 1
     Fix for AIM-120 LOSE/LOSE TOI. The missile kinematic prediction code will now update projections even if the missile shows a losing condition. This should fix the problem where a bandit that turns back into you should make for a winning end game for the missile in some cases and this wasn't reflected previously in the HUD cues.
     Fix for deadlock while client screws with waypoint data, fix crash in 3d.
     3D pit view panning: Reduced translation for small FOVs to make it smoother.
     Fixed Terrain Line-of-Sight Test.
     Corrected IDM OSB Label ("XMT") position being moved while expanding the HSD.
     WinAmp control:
    o adjusted playback "resumed" to "started"
    o corrected volume up/down linearity (by using the new Winamp 2.x volume API)
    o added new config variable g_bWinAmpOldVolumeAPI (default 0), which allows to revert to the old Winamp 1.x volume API in case someone still needs it
     Fixed SetByHQ PAK button falsely reactivating in MP campaign.
    TO BMS1-F16CJ-AMLU-34-1-1
    150
     Added config variable g_nCampPeriodicSaveMinutes (default 0 = disabled), which allows for cyclic autosave on the campaign host. This enables public hosts to run w/o monitoring and still have a recent savegame available in case the server crashes. Note that the time is in "game" minutes, not real minutes, and that the saving will only be done if the time compression is set to x1.
     AddAdded config variable g_sCampPeriodicSaveName (default "Auto") to set the prefix for the automatic cyclic save name (campaign date and time will be added automatically).
     Fixed HCMS knob vanishing under certain conditions if used as analogue axis.
     WOW trigger modification.
     Animated effects and ambiance sounds will now be frozen correctly if the sim is paused.
     Alert flights (and so intercept) are now generated only when Squadron is HQ controled
    this can be disabled with g_bInterceptsRequireHQSquadControl , true by default
     Fixed stick trim being enabled while A/P was active. Now it only works if A/P is off.
     Corrected AA FCR tracks not being displayed on the HSD in NAV mode, now they are.
     Added a "Theater Check" and a "Falcon Version Check" for client connection attempts. Clients which don't match the host theater and BMS version (patch level) will not be able to connect to the host. Please note that there is currently NO proper feedback on the client about WHY the connection has been refused, the client only sees the usual "unable to connect" message.
     CTD fix (aka Mav CTD - probably a 1000 years one) when trying to change Maverick polarity when no missiles on-board. The code was dereferencing Sms->curWeapon which was of course NULL. WPN MFD is in OFF mode without weapons and the crash probably was never found because no one tried to change polarity when in OFF mode. Anyway, it won't crash anymore.
     Fixed debriefing actual TOT "seconds/minutes early/late" display.
     Adjusted UI keymap display to hide the assigned keytext for blue header lines.
    Just FYI, keyfiles come with 4 different possible visibility states:
    o -2 = hidden
    o -1 = visible and locked in UI, header (blue background, no keytext)
    o 0 = visible and locked in UI, normal entry (green keytext)
    o 1 = visible and changeable in UI, normal entry (white keytext)
     Corrected OTWGlanceForward getting reversed under certain conditions.
     Fixed a bug in HARM POS mode where a HARM that doesn't find a target on the way to the reference STPT was hitting the exact STPT position (What makes it kind of "GPS guided" missile). Fixed that by setting some randomness in the STPT location, not too large so the HARM will find a target if there is and not too small so it'll not hit too close to STPT exact position when a target wasn't found.
     Excluded texture memory check from low memory warning calculation as it is not reliable enough. Lowered low memory warning threshold for the other counters to 64 MB.
     Fixed ACMI shadowmap position.
     Added additional "Environment" entry to the ACMI options menu, where options regarding the environment rendering can be selected:
    o "Time of Day": If set (default), ACMI playback will honor the tape timestamp. If deselected, ACMI will render the view in full 12 o'clock noon sunlight, which will help e.g with night tape reviews.
    o "Weather": If set (default), ACMI playback will honor the tape weather. If deselected, ACMI will render the view in SUNNY condition w/o clouds or fog, which will help e.g. with bad weather tape reviews.
    o "Shadows": If set (default), ACMI playback will render the shadowmap. If deselected, ACMI will be rendered w/o shadows, which will help e.g. with shadow rendering issues.
     Added additional "Big Fonts" entry to the ACMI "Labels" options menu. If selected, this will render the ACMI labels with a bigger font, which will help with readability issues.
     Fixes for DX button mappings set for the button release event. Previously all such bindings resulted in the callback being invoked with key up semantics. Since most discrete callbacks are coded to function with key down invocation there was no way to get the required functions to work completely. The new code allows you to specify three behaviors for any DX button binding and to have separate choices of those behaviors for both button press events and button release events. You can now specify that a binding is invoked with key down, key up or default behavior.
    TO BMS1-F16CJ-AMLU-34-1-1
    151

  • An example to clarify:
    First the conventional form of a DX binding line still looks the same:
    SimDMSDown 20 -1 -2 0 0x0 0 "SimDMSDown"
    The -2 means: this is a DX button binding, 20 is the button ID# and the -1 says dow key up/downdefault behavior. This means that the SimDMSDown callback is invoked both for the press and release of the button and the two invocations get the key-down and key-up parameters respectively.
    Now...if instead of the -1 in the second numeric field we place a -2, that means invoke this binding with a key down semantic only.
    SimDMSDown 20 -2 -2 0 0x0 0 "SimDMSDown"
    This results in the SimDMSDown callback being invoked only one time even if you physically press and release the joystick button.
    In addition, you can as before set a different binding line up for the joystick button release event, this is done as before by placing 0x42 in the 4th numeric field of a DX button binding line as follows:
    SimDMSDown 20 -4 -2 0x42 0x0 0 "SimDMSDown"
    Note in this case the value in the second field is now -4. -4 in that field of a DX button binding line means invoke this callback with a key up semantic. So, if this 0x42-equipped line were the only line in the key file for button 20, what would happen when you physically press the button is that no callback would be invoked but you would get the SimDMSDown callback invoked when you released the physical button but with the key up semantic.
    In effect then these two lines:
    SimDMSDown 20 -2 -2 0 0x0 0 "SimDMSDown"
    SimDMSDown 20 -4 -2 0x42 0x0 0 "SimDMSDown"
    Do the same as:
    SimDMSDown 20 -1 -2 0 0x0 0 "SimDMSDown"
    However, a more interesting and useful example is what you would do for the mechanical on/off switch on the HUD SYM wheel that controls the power for the HUD display if you have that set up to deliver a DX button event via your controller:
    SimHUDOn 20 -2 -2 0 0x0 0 "HUD power on"
    SimHUDOff 20 -2 -2 0x42 0x0 0 "HUD power off"
    The result of these two lines is that when button 20 (which recall is actually the 21st button on a Windows joystick controller, F4 numbers them starting from 0 as the first and Windows numbers starting with 1) turns on, the SimHUDOn callback is invoked with key down semantics and the HUD should power up. Conversely when button 20 turns off, the SimHUDOff callback is invoked but noting the -2 in the 2nd numeric field it is also invoked with key down semantics.
     CTD fix for pressing DX buttons in the setup control panel with the new individual DX press/release keymappings.
     Usage of SimMotionFreeze is now prohibited in MP.
    TO BMS1-F16CJ-AMLU-34-1-1
    152
     Added additional BMS exe icons colors (gold/green/purple). You can select your preferred icon color for the BMS exe shortcut by right-clicking on it, then select "Properties". Go to the "Shortcut" tab and find the "Change icon" button in the lower middle.
     E3 project dome DOF changed from 2 to 14.
     Added a config option g_bMouseButton4TogglesClickablePit (default false). If set, the 4th mouse button (if available) will toggle between mouselook and clickable pit. By the way: the wheel is button 3.
     Added additional "Wind Check" option to the Tower Approach ATC radio menu. If called, the tower will reply with the current wind heading at the airbase in three digits, rounded to full 10 degree steps, and the wind speed in knots in two digits.
     Fix for HARMs not finding targets in POS mode because screwed-up setting of target location causing the missile to go too high and loss ability to find the intended radar target.
     Corrected framerate logfile ("-log") output directory.
     Fix a bug in HARM HAS mode. When locked up, it was dropping target if other threats of the same type (which are not the locked target) were behind 3-9 line. It should drop only if the locked target passes the line.
    Data
     E-3 changed to complex. re-DOFed the model and added lights.
     Fixed TDOF for HSI cursor translation.
     Fixed typo in DTC UI. It read Chaff PFM instead of Chaff PGM.
     Fixed SimStepIntercomVolumeUp appearing twice into SimStepIntercomVolumeDown in Keyfile-generator.xls.
     Updated Hub.exe to hide the "confusing" platform label. It will only show when both platforms are available.
     UI Update: Help windows updated with the descriptions of the new functionalities (Ruler, Set bullseye...)
     UI Updates: Pop menus, changed the delete option, not it has better positions to prevent hit it by mistake
     UI Fix: Setup window, now Blur and Boom options works as desired (before one did the work of the other one)
     Logbook patches: Added new vSquadron patch
     Updated the patch list for be able to use all logbook patches in campaign mode
     FM updates for:
    o HasOldLandingLight set to zero
    o Added TGP and HTS data
    o E-3 changed to complex. re-DOFed the model and added lights.
     Corrected HSI bezel template texture.
     Fixed Hub.exe problems with Windows XP.
     Updated SR-71 skins BY MANIACSKINWORKS/ZELEGEND, OCT.2011 RELEASE FOR FALCON BMS 4.32
     Added additional Launcher.exe icons colors (gold/green/purple). You can select your preferred icon color for the Launcher.exe shortcut by right-clicking on it, then select "Properties". Go to the "Shortcut" tab and find the "Change icon" button in the lower middle.
     Added a "Confirm" option for "Set Bullseye" to the UI map right-click menu to avoid accidental Bullseye moves.
     Added additional delimiters to the UI map right-click menu to clearly separate "display" from "set" entries.
     DogFight icons glitches fixed
     UI maps (JSTAR, PAK included based on the wonderful Red Dog's ONC chart) and icons refinements… fit with the BMS's Converted additional theaters (same presentation)
     Numeric scale to PAK slider added
     Updated RF and IF campaigns for KTO
    o - Replaced RAAF F-111 with RAAF F-18C (75 Sqn)
    o - Replaced ROK F-4D with F-15E-229 (since we don't have the F-15K, the F-15E is its nearest cousin)
    o Updated Camo.cfg for KTO
    TO BMS1-F16CJ-AMLU-34-1-1
    153
    o - Squadrons with appropriate skins, in the game, should now use them
     Falcon4.CT: Reordered Specific for all bombs and fixed wrong Type for CT# 2138 (CBU-89).
    Added WCMD.
    Changed BRU-55 data in bmsrack.dat so it loads only JSOW, JASSM, JDAM (Up to 1000lb) and WCMD.
    Fixed Subtype for WCMD bombs. It was 1 instead of 5.
     Deleted the training mission 17 HMC AIM9 combination due a typo
     Added the mission 17 HCMS AIM9 combination to fix the typo (HMCS)
     Added a full working training scrip of the mission 17 HMCS AIM9
     Changed all text to white in the comms window
     String updates for briefing page / mission list / action point list, e.g. fixes for some overlapping texts.
     Removed dysfunctional high/med/low filter selection from the UI map pop up "Installations" menu.
     Hub.exe: Fixed current directory being passed to CreateProcess.
     Fixed TDOF for HSI cursor translation.

  • Grad nen Screenshot gefunden.. nur keine Ahnung ob Fake oder nicht.. aber die Karte im HSD.. das wäre ja zu genial :thumbup:

  • hier vorab der Link zum direkten download...

    Link


    bitte noch nicht installieren....


    Anmerkung aus dem BMS-Forum zum installieren:


    If you carried out a standard install when BMS was first released you should have a setup folder called

    C:\Users\Home\Documents\Falcon BMS 4.32 Setup

    This is where you extract the update files and then run the "setup.exe" file that is contained in that setup folder.

    Your install folder should look like this...

    C:\Falcon BMS 4.32

    This seems to be a common misunderstanding with the update.

    -Eine Smith&Wesson übertrumpft vier Asse-

    -You Gotta Be Shittin' Me-

    • Offizieller Beitrag

    "If called, the tower will reply with the current wind heading at the
    airbase in three digits, rounded to full 10 degree steps, and the wind
    speed in knots in two digits."

    Schön zu lesen. :thumbup:

    Zum Vorgehen.

    Wir brauchen einen "Beta"-Tester" welcher sich vorab mit der Installroutine befasst.

    Wichtig ist, was wir "retten" müssen. Sind die Keyfiles, Logs, TE`s davon betroffen? Wird das Update über die bisherige Install gespielt?

    Wer erklärt sich dazu bereit? Im Anschluss gilt es dieses an die Member weiterzugeben.

    Gibt es bereits Postings in anderen Foren?

    Ich konnte keine "Änderungen" zum Backupfunk lesen?

    Thx.

    Gruß
    Dro16

  • werde mal ab kommenden Dienstag das Update drauf spielen.....

    Bericht folgt...

    da ich vor kurzem erst mein System neu gebastelt hab, hab ich noch alle Sicherungen...

    Jaws :hmmz:

    -Eine Smith&Wesson übertrumpft vier Asse-

    -You Gotta Be Shittin' Me-

  • Auf das erlernte dürfte sichso gut wie gar nix auswirken. Verfahren wurden keine geändert, udn wenn man den Vogel vorher fliegen konnte dann auch jetzt :D
    Hier die Info eines der Macher von dem Update bezüglich DX-Befehlen:

    Zitat

    Kannst alles lassen wie es ist. Kam nur "neue" Funktionalitaet dazu, die aber fuer "normale" Joysticks ueberhaupt keinen Nutzen hat. --XXX-- hat das kurzfristig fuer ein paar Leute mit exotischer (militaerischer) Cockpithardware reingebastelt. Ist wie gesagt fuer Otto-normal-Heimflieger-mit-Cougar-und-Co. uninteressant.

    :)

    We’re the wingmen and you know we never miss

    We just shot our flight lead down and now he’s fucking pissed :rolleyes:

    We’re the wingmen and we hate to be alone

    Without someone to follow we would never make it home :saint:

    signatur_cupra.png

    • Offizieller Beitrag

    Könnte mal ein "BETA-Tester" die nachfolgenden Zeilen auswerten, ggf. in eine Struktur bringen, testen und das Ergebnis anschaulich veröffentlichen?

    Thx.

    Gruß
    Dro16

    Also du musst Update installieren z.B.auf dem Desktop.Dort hast du nun
    einen Ordner Falcon BMS 4.32 Setup.In dem Ordner ist die Datei "data".In
    dieser Datei sind 3 files du du kopieren musst.Jetzt öffnest du deine
    Falcon BMS 4.32 Setup Datei (nicht die vom Desktop,sondern von wo du
    Falcon BMS installiert hast) dort findest du auch einen Datei mit dem
    Namen "data".Dort fügst du die 3 files rein.Dann nochal auf den Setup
    Button drücken und bist auf der Select Setup Action Seite.Markierung bei
    "Check the Internet for product updates"lassen und den Next Button
    drücken.Dann auf der Online Update Seite in der Mitte bei Downloaded den
    4.32 Update markieren,auf Next drücken und fertig ist die Laube.

  • Grad nen Screenshot gefunden.. nur keine Ahnung ob Fake oder nicht.. aber die Karte im HSD.. das wäre ja zu genial :thumbup:


    ne Cupra is ned dabei......was ich auf den ersten blick erkenen konnte sind nur einpaar unwichtige sachen verändert worden sowie die menü furung zum verstellen des bulleyes und einpaar linien.....womöglich is auch mehr getan worden...konnte ich aber noch nicht finden....ich bleib dran falls ich zeit dafür hab... :arghs:

    .."unmöglich"..,sagte die Tatsache...."versuch es"..,flüsterte der Traum..

  • Falcon BMS 4.32 UpDate,
    ich habe es so gemacht:
    1. zuerst den Falcon Ordner sichern!! (wichtig, falls etwas schief geht)
    2. Falcon_BMS_4.32_Update_1 downloaden (falls noch nicht vorhanden)
    3. die Datei entpacken und die drei Dateien aus "data"
    - 4.32_Update_1_Part_1.bsf
    - 4.32_Update_1_Part_2.bsf
    - local.ver
    in den Ordner "Falcon BMS 4.32 Setup" (ist von der Installation von BMS 4.32 vorhanden) in den Ordner "data" kopieren und die vorhandenen Dateien überschreiben.
    4. die "setup.exe" in diesem Ordner starten.
    5. die "exe" startet und alles weitere ist selbst erklärend.

    Das wars....
    Na denn man toooo....

    Gruß
    Witch

    TheWitch_LtCol.png

    suum cuique

  • hallon Witch

    ...wo hast du beim entpacken des BMS_Updats "drei Dateien ?

    habe beim entpacken nur "" Falcon_BMS_4.32_Update_1.exe""

    ?(

    Hooker

  • @Hooker,
    "löse" mal die "Falcon_BMS_4.32_update_1.exe" aus.
    Es ensteht ein neuer Ordner "Falcon BMS 4.32 Setup" wahrscheinlich im ROOT-Verzeichnis, darin sind die 3 Dateien enthalten.

    TheWitch_LtCol.png

    suum cuique


  • Wichtig ist, was wir "retten" müssen. Sind die Keyfiles, Logs, TE`s davon betroffen? Wird das Update über die bisherige Install gespielt?

    Moin
    Soweit ich das beurteilen kann bleiben , wenn man eine bestehende version aktualisiert alle Daten erhalten.

    Einzig die BMSconfig ( wird auf Standardwerte zurückesetzt) muss im Bedarfsfall neu angepasst werden.(Im Startmenü über Configuration)

    Bitte nicht die "alte" falcon bms.cfg sichern und zurückspielen, das soll zu Problemen führen.
    Eine gute Idee ist auch den kompletten Progammordner sicherheitshalber zu kopieren und umzubenennen.
    So kann man schnell (durch umbenennen) zwischen den beiden Versionen wechseln)

    Yippieayee.................

    Viper
    C/O 47th VFS " Dragonfighters"

    dragonfighters_sig_viper_s.jpg

    Intel® Core i7-6700K | ASUS Z170 PRO GAMING Mainboard | 32 GB DDR4-2133 |AMD Radeon RX6800XT Red Dragon 16GB DDR6 | Win 10 Pro |
    Displays: 1x Samsung 40" / 3 x 10" TFT / 1x 4,3" TFT / 1x 7" TFT | HOTAS Cougar FSSB-R1 | Simped Vario Pedals | 7 x Arcaze USB | 2 Arcaze LED Driver | AIC | Arduino Uno

  • Moin,

    was fehlt ist: unser Patch im Log ist wech. @Deamon Frage: ich hab den Patch gesichert und spiele ihn mal zurück, mal sehen was passiert....

    alles zurück, Patch ist wieder da....

    Gruß
    Witch

    TheWitch_LtCol.png

    suum cuique

    Einmal editiert, zuletzt von TheWitch (19. Februar 2012 um 12:26)

    • Offizieller Beitrag

    Hatten wir nicht gesagt wir wollten noch warten? :cursing:

    Es soll mir keiner am Dienstag mit einer anderen Version kommen!

    Wen haben wir denn schon alles: Witch, Hooker, Popy, ...

    Der C/O

    • Offizieller Beitrag

    Ich bitte mal die riesige Gemeinde der Beta-Tester die Anlage zu prüfen.

    Das Updat-Guide stammt von Westy, 47th Dragon Fighter. Thx für die Arbeit!

    Das dazugehörige Posting:

    Wozu die zusätzlichen Einträge jetzt bei Campaign ?

    ///////////////////////
    // Campaign Settings //
    ///////////////////////

    set g_bMessageStatistics 0
    set g_bEnableRakNetPacketLogger 0

    In meiner alten config waren die zwar auch drin aber unter Multiplayer settings, dazu kam noch  

    set g_bShareMpClouds 0

    Wir müssen wir mal testen ob wir die zusätzlichen Einträge noch brauchen oder ob die Probleme zu deren Lösung die mal hinzugefügt worden sind (riesige Logdateien, connect zu lange /unmöglich) nicht schon eliminiert worden sind.  

    Ich wiederhole: "Es gibt Vorgaben zum Standard, diese wollen wir nicht aufweichen!"


    Früheste Umsetzung: nach dem Dienstagtraining!

    Der C/O