All Activity

Always check all displays. Or...... Five miles to my airfield. I check all important indicators and prepare for landing. Everything looks good and I think I have the changes to the flight model under control. Suddenly the engine sputters and stops. What the f... is that? After a few seconds I discover my mistake. Ignored the fuel gauge. I'm simply out of gas.

On the other hand, I also noticed that since the last update 2.9.19.13478/ I have micro freezes again and the image jerks when I turn left or right quickly, which had disappeared with the previous update

Hi, please attach your dcs log, we can look for clues. thank you

Hello, after reading what Hot Dog said, I took a flight just to look in the fields, and the combine harvesters have disappeared too. !!

Почти похожий на dcs-совский.

@Wags Thank you for explaining why there is a delay in getting the new soldier models out there on the "Mover and Gonky" show (loved seeing you on the show by the way) These are something that I have been asking for recently and getting frustrated due to the lack of release when they seem to be ready from all the promotional videos.

Could it be a better headset than quest pro now? Sorry for offtopic I am planning upgrade from quest2. Only minimum of 90Hz troubles me. For my configuration it's now fine and stable on 72Hz.

Hi, here I am again. I changed my PC configuration as best I could. Hoping to improve performance, I reinstalled everything, but now it's getting to the end of the loading process and crashing! I'll try to send the log. Thanks in advance for your help. Regards Gaetano dcs.log dcs.log-20250819-102030.zip dcs.log-20250819-102342.zip

With the recent update the Bullseye data when enabled shows up fuzzy on the FCR and clear on the HSD. I noticed the same condition when swapping the FCR from left to the right MFD.

Imho sorely needed even if it has to come as an FC3 level module due to lack of documentation.

Thanks! I’ve read some Reddit posts saying the clarity or sweet spot is significantly lower than the Quest 3, which doesn’t really match what the publicity claims. How do you find it compared to the Q3 in terms of sweet spot and overall performance (especially running DCS and iRacing)? Have you also tried Virtual Desktop with the Q3, and if so, how does the BSB2E stack up in smoothness and clarity? Also curious if you notice any optical distortions around the edges, or if the image feels more consistent than on the Quest 3/Pimax.

Yes, this is expected behavior given his current implementation. You need to disable him first if you want to mess with that stuff in particular (Wheel > Presence > Disable, can also be bound to a key directly). Once the vision for Jester fully unfolds and everything is in place, these things should not be a problem anymore Are you sure about the elevation though? In all user supplied tracks ive seen on the topic so far, the elevation was usually good and did cover the airspace with the bandit in (he runs a sophisticated default scan pattern that touches pretty much the entire airspace ahead). The problem leading to not spotting the bandit on the screen is usually the gain, not the elevation. Either case, as a default uninformed scan behavior I think its quite good already. It just lacks, as explained earlier, an extra mode where he actively tries to uncover a target in a known area.

I've had mine (BSB2E} for a week now. Got it pretty well dialled in for DCS and Iracing. Coming from A G2 running 13700K/4090. Happy to answer any questions.

We have a report open, but it is a long standing issue. I have bumped the report internally, but I have no other news to share sorry.

That's fantastic! Nate

The M67 is quoted by the DOD to have an effective (50%) lethal radius of 5m with an effective (50%) casualty-producing radius of 15m. There are numerous sources claiming fragments can travel to distances exceeding 200 metres. I personally wouldn't like being inevitably being peppered with dozens of tiny steel fragments standing in the open 20 metres away from a hand grenade. Sure you're unlikely to die, but it's certainly not a pleasant experience.

+1 I would also like to have that option for my helicopter flights.

Bonjour, Depuis ce matin le spitfire part en montée comme si je tirai sur le manche à fond. Ce problème n'apparait pas avec le TF51. Mes réglage n'ont pas changés, je n'ai pas ajouté de nouveau périf, j'ai redémarré, j'ai pu voler sans Prb hier. Asus B550-F Ryzen 9 5950x Geforce RTX 4090 124MB Win 11 HOTAS Warthog + Stick, MFG Croswind

Thank you! @RealDCSpilot I'll try that. So, I shouldn't worry about the OpenXR layers warning?

I tried this procedure with TGP and have same result. Only Full Alignment is right for a start-up checklist If your loadout is AGM65. ARM or SIMULATE haven't done the thing. Yes HOT start is fine for boresight (in air spawn) Store HDG alignment I don't recommend. But I don't tell If this is real life function, that Store HDG has this "Disability" for no-Boresight AGM65. If does. It will be great to add in manual, that Full NAV Alignment is needed for boresighting AGM65.

following this topic, very nice idea thanks for sharing

Yep, it is a pain in the !@#$, I can't believe they haven't fixed it yet, it's a real problem for anybody with an exported display

Yes! This was exactly what was I looking for. Thank you.

@Priest pretty neat solution! I don't wanna waste any buttons, so I just say "map view" and "cockpit view". Also, you can use buttons/hats to browse the radio menu, and those hats/buttons will only browse the radio menu, when the radio menu is open. But, I don't use the radio menu, I use VAICOM, a free plugin for VoiceAttack. I just mention it for users in general. Cheers!

Hi, rato65! What about highskid variant? Have you got any news?