Galinette

Do you have a VTB/HUD mod?

Remember that magnetic heading changes over time... If the CP was magnetic, it should be updated every year.

I don't have any controller, and I don't have any problem. If you don't really need them, maybe you can unlink them.

OK... After many tests, the culprit was Reprojection. Disable it completely, and everything runs smooth. Re enable it, and play in a situation where FPS gets low so that reprojection has more work, SteamVR crashes. Even in stable for SteamVR and WMR plugin. I played since the G2 came out with reprojection, without any issue. I have no clue why it started crashing one week ago, but it does. Looking at other forums, this is an issue reported by many people, but still it doesn't happen everywhere. I may end up by reinstalling everything if I want to enable reprojection again.

When switching from 4 to 5 it shouldn't briefly connect to 8... There is maybe a short impedance state which isn't addressed properly.

You can't use a selector switch with more than 6 positions on a BU0836* as it's a 6x6 matrix input. The 12 switches have a single common pole so you can't matrix them. You need a BBI-32 or BBI-64 for that, but it will be a wire mess for a couple of switches. The BBI-32 specific 12-pos selector solution is, if it works as intended, very interesting.

Yes... I read somewhere that FS2020 isn't even WMR native but uses OpenXR as an intermediate layer. To be confirmed though...

If it's just a current or voltage measurement, maybe a cap could filter the mess out.

You may be right, I did not try any SteamVR game. What puzzled me is that FS2020 suffers the same issue, even worse. But it may be also be much more noticable on flight sims because you have both very close planes (cockpit) and objects at infinity.

Because the hardware calibration is just a measure that is stored inside the headset and must be applied properly by the underlying software, that must adjust its rendering frustums accordingly.

The issue is gone after reverting SteamVR to stable and doing a fresh DCS installation with a separate saved games folder. I'll try tomorrow with the previous DCS install & saved games to check if this was SteamVR. No!

It may be the case for one particular headset but that's pure luck. On my side it's awful in FS2020 I did a proper calibration using a DIY alignment bench and debug tool (see earlier in this thread) and now it's perfect in DCS. The core issue is more likely Reverbs not properly factory calibrated or the calibration not properly stored/applied by the firmware.

Thanks for the information! So it would seem that resistivity is measured. Do you have any successful use of these switches? I just tried with two brand new ones, without anything else plugged on the BBI-32. I have tried to change the index of the first virtual switch to 33 so that it doesn't overlap with physical switches. The result was always the same : stable button state is correct, but upon switching from a position to the next or previous one, I get around 2-3 short spurious ON/OFF events from other buttons, in a random order. Since all DCS modules seem to work on "ON" events only for multiposition switches, the cockpit button ends up on a random position. Here is for instance what I get when switching from 24 to 25: 6,f,Button 24,UP,2453 7,f,Button 28,DOWN,2453 8,f,Button 27,DOWN,16 9,f,Button 28,UP,16 10,f,Button 25,DOWN,0 11,f,Button 27,UP,0 So I get a 24 UP and 25 DOWN as expected, but also two short pulses for 27 and 28. DCS doesn't like that at all. I contacted LB about this, he suggested me to disable other encoders in the board config tool. I did that and even disconnected anything else but the switch, with no improvement.

Yes, I use it since the beginning. They may have screwed it in a recent update, I'll try downgrading. I'm currently trying without VR, it seems stable.

Hi, Since one week, I have a very painful issue. DCS starts properly, the mission too, but after 10-15 minutes the headset suddenly becomes black. DCS continues running (sound goes on, VR preview is low FPS but goes on). Did anyone encounter this issue? I have my current setup for 6 month and never had such problems. Now it's every time. I have 64Gb RAM, and I don't see any memory leak while playing. GPU is RTX3090. I suspected cooling issues, but GPU is 70°C and CPU 65°C when playing DCS, which is far from awful. NVidia drivers are up to date, I uninstalled and reinstalled SteamVR and WMR plugin. Repared DCS.

No. These LB switches are 12 pos selectors, not encoders. They have 13 pins (12 + 1 common) and you can’t go from pos 1 to 12 and conversely, the movement is blocked. They are modified by LB with an extra round board having the exact switch footprint, converting the 13 pins to a 2-pin signal specifically designed for the BBI32 board, using only a single input, and resulting in 12 logical switches. I suppose the 12 inputs are converted to some binary sequence recognized by the LB firmware

The ILS in DCS is very picky, it's active only when the AI ATC decides to enable it. It will never switch it on in rear wind conditions, and at low/no wind conditions it's messy. This is the case for all aircraft See here for instance :

With frequency only you will have ILS deviations on the ADI (yellow needles). But no or wrong HUD symbology.

Hi, It's not an encoder. I have 4 encoders on the BBI32, configured properly with the ratio. They work perfect. Used for ILS & TACAN. This is a special 12 position switch sold by Leo Bodnar for use with the BBI-32 exclusively. The big advantage, it makes a 12 pos selector, using only one input and two wires. http://www.leobodnar.com/shop/index.php?main_page=product_info&products_id=207 I connected it as documented. It somewhat works, as the "stable" button output is the selected position button ON, and all other buttons OFF. But, when switching position, instead of generating only a OFF event for the old position and an ON event for the new one, many spurious ON/OFF short events are generated for random positions. And as DCS always takes the last event only the corresponding cockpit switch ends up in a random position.

Hi, I recently purchased a BBI-32 Leo Bodnar board with a couple of 12-pos selectors, as they are very interesting to reduce the amount of wire mess in my Mirage-2000 right panel. However, I can't have them to work well. When switching slowly from 1 to 12, other random positions switch on for very short times. Does anyone have any experience with these? Thanks!

I think a Warthog profile was recently added to the aircraft files.

Edit : didn't see the attack profile... See Helljumper's answer below. You are dropping the bomb fully outside its domain of use. You must NOT dive and attack with a low altitude, using the Vz indicator.

The left digit. It goes above 9. Just turn the left knob.

Did you try? Just turn the knob...

What was your altitude?