Hello Forum,

What are the minima below which will cause an airfield to de declared “Black” and closed?

Thanks,

Bayonet.

Hi guys,

As the tittle suggests. Since I changed to a new laptop, I get a quasi blanc screen when I open TacView. Anyone an idea? 8a225732-8462-4d54-8a51-27f0c1af8586-image.png

@Falcas

1) I’m not sure if this is intentional or a bug: When I click Load in any other tab, e.g. PPT, EWS, MFD, etc., the window opens up to the respective directory in the main WDP folder

WDP_3.7.24_4.37\Files\EWS
WDP_3.7.24_4.37\Files\PPT
etc.

In the case of Lines however, clicking Load defaults to the Campaign folder opening up. From there I have to navigate to where I have WDP installed and drill down to the Lines directory.

2cc0b6a5-30a1-49ba-bc44-ca98f1b315c0-image.png

2) The sentence in the Change Area box is cut off. Changing the screen size under Settings does not fix it.

04b7c808-9cdd-4cee-8e90-5df8aeddfa6d-image.png

The idea is that you fly through the circle to begin the maneuver then do your heading change over to OA2 (or under OA1) immediately into your climb toward OA1. Passing OA1 (apex) you pull down to target (or AOP/OA2 if you set that option).

The benefit is both seeing where to pull up to in terms of alt/angle and to recognize passing it. Without the apex mark you climb until when?

It works perfectly, only one arduino micro for DED and FFI.

@Ricky said in MouseMasterVR - Mouse functions utility app:

@SemlerPDX Got it, thanks.

There’s a similar app called VR Neck Safer: https://gitlab.com/NobiWan/vrnecksafer

It allows you to temporarily increase your viewing angle with a HOTAS button. Although your idea of the curves might be more elegant.

Interesting find! This solution of requiring two physical buttons is definitely not ideal. If you are familiar with TrackIR, this was the sort of thing I was describing - if BMS could implement anything along these lines or if SteamVR would allow for such things, it would be a lot more user-friendly. Even OpenTrack has something like this, afaik, and the whole point is that it is a custom curve, not something that you have to press buttons to achieve, it’s always on:

766ecf5c-1f5f-4770-8afc-9f53501af62f-image.png
…and of course, there are options to select each axis from the drop-down box.

MouseMasterVR will not ever have something like this, it is merely a mouse centering and rebinding app.

@dave76 said in any fuel calculator program ?:

right, i was asking how to understand which is the amount of bingo fuel to include in total (say block fuel) to have enough to return to home plate …and how to calculate it during PREFLIGHT …hope i explain myself 🙂 🙂

In that case, the best tool would be Weapons Delivery Planner, which you also should have as it is so helpful - great for printing out data card if that’s your thing, too! 🍻

First thing is to check the numerical values of the destinations (not steerpoints) in terms of latitude-longitude. What L/L did you expect? Is your destination that L/L or is it different? Remember that steerpoint location is destination + any cursor slews which apply in that “bucket.” This means either CZ before using the STEER page or use the DEST page. Looking at the STEER page while there are slews will not show the DTC-loaded L/L values for that point.

Using the navigation pointers/distance is a good way to notice there’s an issue but it’s not a good way to diagnose the issue.

@Raptor-One Thanks it work s for me for BMS 4.37 update 2 except for the view 2

I look forward to using this when I get VR set

@Ironman53rd said in WDP and 4.37U2:

yes it is

Thank you!

@Tyrant
Understood.

@eido1706 there’s new stuff, for VR and also the new ECM jammer modes… a few other things, like 8-way directional cursor slewing

but notwithstanding all that, a key file from 4.36 should continue to work as is

https://forum.falcon-bms.com/topic/23897/migrating-key-file-from-4-36-new-changed-callbacks

Can someone - preferably using 190-beta9 - try the “Trim Before” and Trim After" options and see if they work or as it does in my case crash back to Desk Top.

The Trim Before and Trim After option are find behind the “notepad” icon on the top of the TacView screen.

Many Thanks,

Ironman

@Aragorn This is correct, although I had mistakenly thought I had this situation handled already. This one slipped through the cracks.

Edit: It should be fixed in the latest release.

Now MFDE works : .BMS 4.37 and Windows 11
After download :Microsoft Visual C++…2005 64 and 86 Redistributable
Microsoft Visual C++…2010 64 and 86 Redistributable
MFDE zip version 0.6.3.0 as suggested by Waldorf ( on Falcon Lounge)
Thank you for your help.

@Atlas said in AutoKneePads for Falcon BMS:

@linknet Is there a way to get the charts into this? I’m referring to the airport and approach charts that we have in the Helios profile that you get to by clicking on the RWR, then choosing which airbase to display.

Interesting idea, how would you select which airbase charts to display? Also the charts would all need to be resized to 1024x2048 from the current 850x1181 or 2904x4455 which means you’d have an awful lot of white space at the top and bottom.

You could use WDP Update Kneeboards to add the charts to all of the kneeboards pages but you’d still need to resize them all first.

@Novum

Thank you so much from me too. I was missing it.

With best regards.

@Dee-Jay - this is a reason I’m using all ON state switches in my cockpit build…I want to do something a bit the opposite, in hardware.

What I want to do is send all of the current cockpit switch states to BMS on command - this requires that I have a positive ON state (logic 1) for all ON and OFF positions; and that they all be sent as “one shot”. This is to get BMS in synch with however I have (or have not) forgotten to set my switches previously.

I’m probably going to set my interfacing to omni-send switch states with some sort of shift command - like CMS->dwn + Paddle…or some Viper unused HOTAS or button set. Haven’t gotten that far yet.

@falcon4 Thank you!