@Gavlar50 said in HUD display with DelanClip:

I’ve settled on moving my default position back so I can see more of the cockpit, as the default position felt far too close to the controls.

How exactly are you doing this?

I’ve taken 2 screenshots — top one is a silly 120FOV, the bottom is a more reasonable 90FOV

fov

As you can see, the HUD text is well within the glass. Look at altering set g_fMaximumFOV and set g_fDefaultFOV to find what you like.

@williang83
I’m just about finished with a replica cockpit and at the moment, I’m having to “feel” my way around some of the switches on the side consoles. However, once I’ve established my hand’s “location,” I can easily navigate to the switch or dial I want. The side consoles are new to me hence this issue.

For my ICP, I just need to establish where it is in the space in front of me and I can quickly use it due to a little bit of muscle memory forming. If ever I get “lost,” I just re-orient myself using the bumps on the ICP’s face.

Having the correctly-shaped switch cap does help a lot with confirming that I am in the right place holding the right switch; same thing with dials/rotaries.

Is it a better option? It depends. A lot of time has been spent making the cockpit, then a lot more time has to be spent building up muscle memory. Being able to see my hands via a passthrough would be great and remove the need for the majority of muscle memory requirement or “feeling around” to get orientated in the cockpit. If you’re not a rampstart-to-shutdown kind of guy, it might be less attractive to spend this much time and resources for stuff you won’t use all the time.

At the moment, my focus is more on finishing the cockpit and then integrating other bits of my sim gear so I’ve not looked into passthrough options just yet.

@SOBO-87
LOL!! I hoped you were SAYING it was working now 😵

I use my PointCTRL finger buttons for most of the controls.

… that was in reference to OpenKneeboard controls. I use the finger buttons for “next/prev page” or “next/prev chart”. Not to interact with the cockpit. Sorry for the confusion 🤕

@Cryo use voiceattack or fozvox for comms. Just press the radio button and talk to it.

@zap737 Yeap, that’s a really well known member of the BMS community 🙂

AR is comming in 4.37.4 as stated in this post:

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

Kind regards!

I recommend disabling vr output on the screen, and then using SteamVR’s VR display to record from.

Use:
set g_bVRNoPresent 1

@b0bl00i Same for me, Quest 3 resolution is already too much for my system to handle.
RTX2080 TI
I9 9900 @5.2
32GO ram

if I run the quest 3 at 100% resolution, everything is perfectly readable so I don’t really care about an headset that would provide a bigger res.
If I want the experience to be fluid on the ground I would need to turn everything down and have a steam resolution around 60-70% which makes the game awfull and unreadable.

I have no issue on an empty airfield, but add a few units and simply looking in their direction tanks the fps, looking low inside of the cockpit seems to be very demanding too. Bad weather seems to severly impact the fps also.

I could make more precise benchmark in the TE benchmark if that can help people to make a more educated choice about potential config.

@Fish44 said in Varjo just dropped their new headset range...:

@I-Hawk Bytedance have just laid off many of their gaming staff. Pico 4 (like Q3) is pretty much a loss leader with the hopes of making money on content and services. While i’m a big fan of my Pico 4, I would not be holding my breath for a new range from them.

I hope they will at least get us the Pico5 series out before that… it would be too bad not to.
If the fate of most successful flight sim headsets (Reverb, Pico, Quest? some say also Pimax) is to die, then maybe the time is still too early for the world to adopt, I don’t really know.

Unfortunately, the less companies involved, the more we will suffer crazy prices. But I believe it’s just a bump on the road, with time VR will get more and more popular and at some point in the future, all the big companies will be there and there will be competition, like with phones.

Hey, sorry if this is already too old, but I’ve talked with a friend about the similar issue you guys are experiencing. I put together a quick video on how I resolved the problem for myself with OBS. I hope it helps. Cheers!

And this is what it looks like in the end.

Oh, by the way, this is the original game window, and not the Steam VR mirror. I’ve also experienced lagging while trying it out with the Steam VR mirror.

It seems like version 4 will comes with OpenXR implementation and that will increase some fps without steamVR layer

Hi,
I am a quest pro user. Usually I run with oculus link, but yesterday I wanted to try Virtual Desktop.
It was very laggy and stuttery. At first I thought it was inferior tecnology (wifi vs cable) but then I tried DCS and it was buttery smooth (with OpenXR and Eye tracking).
After some trials I turned off OpenKneeboard, and then it was buttery smooth again also with BMS and SteamVR (same performance and quality as with the link cable).
So did someone experience the same issue?

@rubbra said in [OpenKneeBoard] WDP Converter Tool:

@Virus Frequencies for ATC, Flight etc? They’re right on the datacard.

31081a56-8d45-445c-a443-ee8d7d8d0801-image.png

Thanks…I didn’t think of it.
So only the channels are missing

@Snake122 I could swear it disappeared for a while, but I could equally attribute the issue to my declining mind. Anyway, it’s there now and is a great help to those with fuzzy VR vision.

@martini
add this in your user config file:

@Flash-0 I had the same issue. just an FYI that this was resolved in the latest v59 update. it looks great now.

Thank you all!!!.. I’ll save for another Xmas at least

Kind regards

I do have the same effect on my U3. U2 was great, now its totally blurry like on your pictures.
Let me know if your tinkering with AF is effecting something, I cannot test it over the weekend unfortunately.

@Snake122 If PointCTRL was working, my plan was just to put surfaces at the right places so I can physically place my finger while using the FCUs to activate the relevant control.

@Snake122 said in Does Point CTRL work well with BMS?:

there is something satisfying to building stuff. Flipping the real switch is still slightly more satisfying than the PointCTRL, just lots more expensive and more time involved.

I come from using 2x touchscreens and Helios. Getting an ICP showed me how much easier it was with correct controls plus the physical/tactile feedback was just so much more satisfying. BMS going to VR was the last straw and I just had to build a “correct” cockpit.

@williang83 centre dash? You mean the front console? Or the CPD?

In any case, I would only suggest that you get it as close to the right spot as possible. Being off by a little bit is so much easier to mentally adjust for; if you reach for the parking brake switch and you end up grabbing the LG lever is way different. For the MFDs, that can be even worse with little/no reference for your hand. I printed out some MFD buttons with raised edges to help me distinguish the buttons and make sure I’m pressing the right one. However, this is a recent mod so I’ve not tried it out yet as I’m still building the new cockpit.

https://forum.falcon-bms.com/topic/25768/hp-g2-v2-fs-eu-only-please