electricaltill

I think you want the "crew contract" menu. I don't have access to the sim right now so it might not be exactly that, but in there is an option to disable Jester. What I don't know is whether that setting survives you entering and leaving the RIO seat. I filed a (acknowledged) bug report last year on much the same issue. I did a cold start in the RIO pit, jumped into the front seat and Jester immediately shut off WCS. Proper red mist moment.

If you're in the UK, switchelectronics.co.uk is where I've been getting mine. Not too pricey and they've got most of the bases covered.

Great, I got your PM as well, thank you.

What do I need to edit to correct an error in a switch definition? There is a switch in the F-14 RIO cockpit (jettison station 8 ) that is defined as a 2-position switch that is actually a 3-position. I have found .json, .jsonp and .lua files for the F-14B in the DCS-BIOS folder in AppData/Roaming and in DCS-BIOS's folder in Program Files. There is another switch in the same bank that is correctly defined in the .json file as a 3-position switch, so I have copied that switch's code over to the incorrect one (except the address and mask of course), changing the switch type from a toggle switch to a '3postumb' in the F-14B.lua files. I restarted DCS-BIOS after each change but the incorrect behaviour remained, and the web interface still only lets me select 2 positions out of the 3. What files do I need to edit to make this correction?

FF gauge does not show AB fuel flow and never has. This is correct behaviour.

Yeah but (from memory) it's on the stick and not clickable, so you will have to look up the key binding for it. Someone correct me if I'm wrong, I haven't flown the Shark in a while.

So you're getting the same thing as us then. For me that's how it's been since DCS-BIOS 10. Don't know why, but I'm glad it still works in game.

I have had the same thing happening since (I think) DCS-BIOS 10. It still works fine in the sim, but it is a pain when I just want to test something without firing up DCS every time.

There is a longstanding bug with the lighting on the Ka-50 since DCS 2.5, the AP lights look off when they are on, and vice versa. It is being fixed in the forthcoming cockpit update, but no date on that yet.

I've been developing a matrix board using the SwitchMatrix library, but it doesn't work with DCS-BIOS so far. Not only that but DCS-BIOS ceases to recognise buttons outside the matrix as soon as any part of the matrix board is connected to the Arduino. There aren't any shorts I'm aware of on the matrix board, and it works fine outside of DCS-BIOS. I tried just connecting a single row and column to the Arduino, and DCS-BIOS stopped recognising other buttons connected directly to the Arduino. The web interface still communicates with DCS-BIOS fine throughout, and the Rx light on the Arduino keeps flickering even after DCS-BIOS stops recognising buttons. Can anyone help me?

I've just moved over to DCS-BIOS 10, and although it's communicating fine with DCS via the web interface, my Arduino sketches are not working. The Rx light on the Arduino is flashing constantly so it seems to be communciating, but not transmitting anything. I'm just trying a basic Switch2Pos command currently. Can anyone help?

Can anyone help me getting a button matrix to work? I have built a matrix which registers button presses correctly in the SwitchMatrix library used by BlackLibrary's fork of DCS-BIOS. But when I try using it for DCS-BIOS functions nothing happens. I have assigned functions to every button using the appropriate Matrix2Pos commands but none of them work in DCS. DCS-BIOS is connected to my Arduino as the LED is flickering when DCS is running and the command prompt window is full of gibberish (DCS-BIOS 0.7.31), but beyond that I can't tell what, if anything, is being sent to DCS. Can anyone help me debug this?

Unlike the Hornet there are no levels of steer for NWS - it's on or off.

Voice attack can be made to give key stroke sequences. There may not be a single key stroke for each command but there is a unique sequence.

That looks like what I need. Thank you very much.

This is a little odd. For my cockpit I have bought a load of SPDT toggle switches, which I was intending to use as analogue multi-position switches with voltage dividers. I didn't realise this was significant when I bought them, but the switches are on-off-on, and this confuses DCS-BIOS about what position corresponds to what control. The centre position is 'off', DCS-BIOS thinks that's the lowest position for the switch, so the outputs to the cockpit don't match the physical position of the toggle switch. SPTT switches are pretty expensive, and I haven't yet been able to think of a way to modify the switches I have. So I want to read the resistances off my voltage divider manually and then command a switch position with DCS-BIOS (e.g. - 'set switch 1 to position 3'), but I can't see how to do that. All of the commands determine the switch position to command based on the hardware inputs. I want to determine the command myself and send it directly. Can I do that?

Nope, there is no link between these systems. You have to copy coordinates from the ABRIS, making sure you've set the correct coordinate format in the config first.

Can confirm, it is a requirement.

The only thing I've found to cause problems is if you jump in the back seat yourself to do anything (align the INS, enter waypoints etc) during startup with Jester disabled. If you enable him again he will immediately switch off WCS and restart the alignment process, regardless of what you did while you were back there. Stupid, but it has been reported and acknowledged.

Yes, that's one of the useful things you can do while you're waiting.

+1

Magnetic variation varies across a region. Does what Jester entered match what's on the knee board?

Posters on hoggit have reported it's not fixed for new tracks either

If anything it's worse. At least, with saved tracks. I don't have a HOTAS right now so I can't make any new tracks, but saved F14 tracks the plane nosedives almost immediately, even if you stay in the cockpit view.

Yes, I would like to see some kind of "state of the Tomcat" post, it feels like HB have been quiet for a couple of months now.