@Crassus the better and I think already made request would be to have the link section dynamic so that user can configure a certain amount of links to their liking.
Requesting a specific application to be added might only be valuable for a fraction of users that use that application

@Stevie
I have been trained and have been a training officer on various,simulators over the course of nearly 2 decades.

1. IMHO BMS was is and will be a game.
2. The distinction is the usage of a piece of software and as long as you are not a service member training for a purpose you play a game and not train on a sim
3. Even without that distinction even in full fidelity military simulators there are shortcomings that can’t replicate 1:1 Real life conditions and even in those environments adaptation and compromise are made to overcome those technical short commings.

As on the discussed topic, having the option to change how the in baked rendering of the HMCS is performed left right both, even if someone refuses the presaid game vs sim aspect, still the RL physical setup function is no value to the asked question as 99.999% of any BMS gamer won’t wear a helmet with a replicated JHCMS while playing the game.

Again that brings us back to #3 and using such option makes the sim not less sim or the game more sim or the game more gamey

And last but not least up until 4.37 we wouldn’t have that discussion at all as guess what: We all had a both eye HMCS on our flatscreen monitors

@molnibalage is about to be finished

As I have been mentioned.

as there is no real working solution for hand tracked cokpit interaction and as well in those games where it is integrated I find it not really reliable especially with a packed tight space of a aircraft cockpit, I personally with my own requirement to be able to operate BMS without any mouse or keyboard usage I went with a Mixed reality setup.

this is my physical setup

which then in the technical setup with a Quest 3 and Virtual desktop in combination of hand tracked passthrough look like this in the headset

@SN00PY
The “normal” user wouldn’t have the need to tinker around in those files at all and those who have the need are usually techsavy enough to to it anyway.

@jack-jalek reading the manual might help

As the USB-C -Eth adapter connection feature had been broken with previous PTC updates of Quest 3 OS I make it a habbit to test and announce with every new update. Can confirm that USB-C Eth adapter still working with latest Meta V76 update

@decimalminimal said in BMS 4.35 Screenshots:

Finally after almost 2 years I put all my stuff in 4.35 and in POH.

More to come soon.

[img]https://i.imgur.com/iFgzW5U.png[/img]

[img]https://i.imgur.com/GoNwyby.png[/img]

[img]https://i.imgur.com/Qqcjils.png[/img]

https://imgur.com/iS3HgG8

BBCodes don’t work use markup i.e

![](https://i.imgur.com/iFgzW5U.png)

@Bayonet same as any other markpoint. Make markpoint active steerpoint, make HSD SOI, Comms switch in longer than 0.5 sec

@Maru
I have been asked by the guys from Falcon Events today why acmi recordings of Gibraltar when loaded to tacview are showing up at KTO locaction.
So I checked the included Theater.map file and it doesn not contain the

struct TacviewTheaterBounds {
    double west;
    double east;
    double south;
    double north;
};

I showcased how to add the Theater boundaries to the .map file so that the theater recordings would include the correct ReferenceLong and ReferenceLat to the acmi.txt

Even so that could be done on a per user basis IMHO that should be included into the theater itself.

Instructions how to extent the theater.map file to have the correct theater boundaries set for tacview to be found here

https://forum.falcon-bms.com/topic/23065/supporting-native-tacview-in-bms-4-36-1?_=1736931237599

@jagfour have you asigned axis already.
POV hats are inly recognized on devices that have either pitch roll or throttle axis assigned

@Alpha there wouldn’t have been the need to reinstall, you could have fixed the entire issue by just editing the reg key

@Browning said in Recommendations for HOTAS Beginner:

T.16000M

to be honest 100-120€ unless you find a bargain deal on a T.16000M +TWCS there are no options for a new HOTAS that’s woth buying.
Sub 200€ there are bsically only 2 options T.16000 or Logitech X52.

I used a X52 for many years, would I still recommend it nowadays? Surely not.

Another sub 200€ option and maybe the best option in that price range would be if you can find a VBK Gladiator MKII (it’s currently out of stock, here in Germany kaufland.de sells a rebrand as FR Tec Raptor 2 and pair it with a standalone TWCS

Next option is to look out for a used X56

Last but not least spend a bit more 180.220 on a VBK NXT Stick and save up to pair it with a throttle later

@MCDeedle images are usually packed into rsc files but for tacref IIRC 3d models and not images are used

@Yılmaz with correct feed into a gpt that a perfect candidate to do the entire job from feeding the source to getting a formated pdf out of it

@CobaltUK no issue as of U6

@Lukas none of 4.37 terrain stuff applies to 4.38

Helios can be forced to ignore different scalings.

Check here

https://forum.falcon-bms.com/post/425894

Helios has its own implementation of display extraction might use use that instead of BMS RTT Client. As you just drag the MFD component into your profile and place it there. No need for ini coordinates

@jack-jalek reading the manual might help