There is some info in this thread:
https://forum.falcon-bms.com/topic/18727/turns-in-vectored-approaches/7
ATC is assuming a 45° bank angle for turn (in IFR it should rather be about 30° maximum but we had to make compromises)
There is some info in this thread:
https://forum.falcon-bms.com/topic/18727/turns-in-vectored-approaches/7
ATC is assuming a 45° bank angle for turn (in IFR it should rather be about 30° maximum but we had to make compromises)
clicking with my eyes closed
I will probably do that. I don’t want to see the exact temperature and wind strength that’s going to come up in 7 days. I guess the weather forecast can predict weather pretty accurately for such a short period of time, but it still kinda ruins my immersion knowing the exact values, even if I won’t probably remember it.
probabilistic weather
That’s what I’m currently using. The downside is that it applies to the whole theater from what I’ve read in the manual. Another downside is that it doesn’t “randomize” the values defined within each preset (fair, sunny, etc). So each “inclement weather” will always be the same.
@Snake122
The word “random” is being used differently here. When we say “random”, we mean realistically behaving weather, but with a random starting point. The real weather tool is great, but you’re limited by the current state. As in, you don’t fancy flying in cold rain just because it’s currently early winter in the theater of your choice and the probability for it is higher.
I would like to be surprised with an initial state when starting the campaign and it could realistically change from that point on, e.g.: starts out cloudy and rainy, but eventually clears up on day 5, all while transitioning within realistic rules. The tool linked up there seems to be able to do exactly that. Just that it’s kinda tedious to set up (having to run it before every campaign and create days worth of maps, which is substantial given that its resolution is hourly changes).
@Mav-jp
This is a pretty neat tool. There are some user-experience issues though.
For example I have to close my eyes and keep clicking for a long time to generate a few days worth of maps. I don’t want to be spoiled by knowing precisely what weather awaits in the next 10 days. The simple forecast is enough. It would be easier if one could just specify a time period and it would create all the maps for it. It seems like the tool isn’t being supported anymore though.
I still think that having a button which would essentially do all of this internally inside of Falcon BMS would be a great addition. Just abstract everything with a simple “Random weather” button and have it create 10 days worth of weather maps. Ideally with a randomized seed each time you click it and perhaps even alter the wind and temperature fields for extra variation.
@Mav-jp
What’s the name of the program that can create random weather maps?
@hiuuz
Apparently the crew that’s working on the plane sets everything up in a same, consistent way, also following checklists.
But you can use this: https://forum.falcon-bms.com/topic/21008/falcon-bcc-randomize-cockpit-switches-during-a-cold-start
It’s not updated for 4.37.3 though, I have to check if there are new or changed callbacks.
The TO 1F-16CMAM-34-1-1 BMS manual, Part VI, section 6.1. on page 592 lists that the F-16AM Block 15 RNLAF doesn’t have JHMCS ability, but in the game it does have it.
Manual:
In game:
I haven’t tested all of the other variants, perhaps it’s possible to quickly check it inside some kind of database instead of manually going through all of them in-game?
Falcon BMS version: 4.37.3 build 1329
Default Korea theater
Moving the power switch (to OPER) on the ECM panel moves the DISP switch on the CMDS panel (in the Dutch MLU). I cannot find anything in the manual if this is intended behaviour.
Falcon BMS version: 4.37.3 build 1329
Default Korea theater, but also in the Balkans theater (latest version as of writing this).
@airtex2019 said in Help Listing Comms Callbacks:
we may need a named-pipe, or open a local network socket or some similar sort of IPC interface, for companion apps like FoxVox to invoke callbacks.
That would be great and simplify a lot of 3rd party utilities.
@Badger
The general computer button UI convention seems to be that depressed is the “on” state. Depressed buttons are usually darker, to visually represent them being pushed in.
I mean, the fact that we are discussing this kinda speaks for the issue itself, doesn’t it.
@Micro_440th
Thanks, that does indeed answer the question.
I still stand by the point that one shouldn’t really need to consult a technical manual to figure out a UI button’s state.
The command line buttons in the Launcher don’t convey their state properly.
Upon a fresh install, a few are pressed and a few aren’t. It is difficult to figure out whether they are on or off. Does the grey represent that they’re toggled, i.e. on? Does the white, them being brighter, mean that they’re on?
Perhaps something like a check-mark with text above would be a saner choice from a user experience point of view.
@S3NTRY
Yes, that one has been pretty helpful, I basically copied everything from there. But unfortunately that one is lacking the FalconSharedMemoryAreaString part as well. There’s an open issue regarding that, perhaps someone with more knowledge might eventually chime in and figure it out.
@Mav-jp said in 4.37 Screenshots:
Procedural doesn’t look good
Only interest of procedural is low altitude when texture gets pixelised
NT uses both
That’s actually pretty cool and solves my worries mentioned above.
Looks like 3D structures, buildings and vegetation. Nicely promising. The detailed terrain looks great, but what’s keeping my enthusiasm at bay is that the ground is just textures. Mainly because of issues like the above mentioned baked in clouds/shadows and looking bad when viewed from up close.
@Flow32 said in Keyfile for TUSBA + Warthog Joystick:
Why not use the excel file provided with BMS to generate a clean keyfile ? It is an amazing tool
Is that file still being kept up-to-date with the latest callbacks and such?
Did you hit the “Print” button on the briefing screen? I’m pretty sure you have to click that.
@Xeno said in NVG google:
In general one of the GFX aspects i’d love to e improved in the future are optical phenomena like focus for sensors/nvg, blinding by strong light sources (direct sunlight by day, hud/hmd/mfds at night).
I’d love that too. It would make the ability to adjust their brightness/contrast usable.
Before the more modern methods like Link 16 were available, was the IDM used and tied to an AWACS airplane? Basically adding the AWACS airplane to your flight and have them send you normal IDM stuff? Is that even possible in real life with IDM?
@b-s said in Print Briefing 4.37U1 CTD:
If looking here anyway, can an automation be baked in? Maybe with a user config option, that automatically writes the Brief to briefing.txt when the user clicks commit to 3d (if enabled in the config)?
g_bPrintBriefingOn3dCommit 1Thanks!!
I would also love that feature. It would streamline getting the briefings to an external device (smartphone) even more.
@bmebr
https://forum.falcon-bms.com/post/94384
Applies to both the Pro and non-Pro versions of the X52. Again, I don’t understand why people insist on mapping their ministick to keyboard keys and experiencing this problem instead of using it as the analog axis it is and having a perfectly working radar cursor.