electricaltill

As I understand the current support for button matrices and voltage dividers: a) You can only have one button matrix per project b) Voltage dividers can only be used for a single control, i.e a rotary switch. Can we have support for more than one button matrix, and for buttons being chained on voltage dividers?

It holds 9 including the named points (IP, HB etc), so while I don't think this is a bug, I'm not exactly sure how these numbered points are supposed to correspond to those named points. Perhaps the same order as they appear on the destination selector in the RIO pit.

My free time is far too sparse and unpredictable for that, unfortunately.

Same. I get the occasional one. The issue is that if your RIO bails you don't get Jester back.

Fantastic, thank you.

Sorry, my terminology probably isn't great here. I'm new at DCS-BIOS. I'm building a button box for the RIO pit of the F-14, and one of the things I want to do is replicate the state of the buttons for the Computer Address Panel, which illuminate under certain circumstances (not necessarily when pressed). Other modules have separate categories in DCS-BIOS for button LEDs and the buttons themselves, but the F-14 doesn't - the 'LED' commands for the CAP buttons just fire when the button is pressed. Does that mean it's impossible to capture the button LED state, or does it mean it just hasn't been added to DCS-BIOS yet? If the latter, is it possible to add it myself? If so, how?

Can anyone tell me if the state of the CAP buttons in the RIO pit of the F14B are exported? They can be illuminated with a green arrow, and I don't see an obvious function in DCS-BIOS that captures this state. The LED function just fires when the button is pressed, and the button LED states are not necessarily related to the button being pressed.

If I remember rightly the switch is just for testing purposes. The emergency flight hydraulics are supposed to activate automatically.

At what point in the mission does it happen? Laser burnout is a thing, and requires repair.

OP didn't mentio 'gyros', and I'm not familiar with the navigation systems of the F/A-18C or the Harrier. Doing a nav fix update makes navigation more accurate, which surely is the objective here.

Yes, you can take a visual fix, use the radar or use a TACAN. The manual describes how.

I guess the answer to your question is "a RIO," then. Once Jester can operate the LANTIRN it hopefully won't be a problem. I'm at work without access to DCS at the moment but I think you have to get into the mode where you enter the laser code (check the manual for that) to be able to turn on auto lasing.

I know this isn't the answer for your question, but it would just manually lase all the way down. I found LGBs unreliable when I used auto lasing as it only illuminates the target from (iirc) 10 seconds before impact. HB have also said that in most LANTIRN recordings they had access to the RIO manually lased as well.

In the process of setting up a button box I found that the INS mode switch bindings don't work. You can set them up, and they respond while in the control options menu, but in the cockpit they have no effect.

I am just starting out with DCS-BIOS. I built a voltage divider with a rotary switch and am trying to use it to control a dial in the F-14. It didn't work, and I wasn't sure if I had set things up right, or if I was understanding the syntax right, so I tried the 'live preview' app to try to interact with DCS via DCS-BIOS. The app does show the status of controls, and they change correctly when the controls are manipulated in DCS, but if I try to manipulate controls using the live preview app nothing happens in DCS. I think this may be related to my problem. Can anyone suggest what might be going on? Here is a sample of my dcs-bios.log: Util.lua: value -1.000000 is too small for address 4624 mask 64 Util.lua: value -1.000000 is too small for address 4652 mask 256 Util.lua: value -1.000000 is too small for address 4652 mask 32768 Util.lua: value -197.000000 is too small for address 4934 mask 65535 Util.lua: value -81.000000 is too small for address 4948 mask 65535 Util.lua: value -1.000000 is too small for address 4624 mask 64 Util.lua: value -1.000000 is too small for address 4652 mask 256 Util.lua: value -1.000000 is too small for address 4652 mask 32768 Util.lua: value -5309.000000 is too small for address 4930 mask 65535 Util.lua: value -566.000000 is too small for address 5024 mask 65535 Util.lua: value -1.000000 is too small for address 4624 mask 64 Util.lua: value -1.000000 is too small for address 4652 mask 256 Util.lua: value -1.000000 is too small for address 4652 mask 32768 Util.lua: value -8061.000000 is too small for address 4930 mask 65535Here's what I get in the command window when I run DCS after running the serial port script: https://imgur.com/jgE3xxF Edit: I omitted the dcsbios init lines, and it works OK now.

I am just starting out with the 0.2.18 Arduino library, but I can't compile my sketch as the IDE is saying there is an error in the library itself: I tried looking for the error message but didn't get anywhere. I have some programming knowledge but this is my first time using whatever language this is so I'm still trying to unpick it. The key bit seems to be 'tryToSendDcsBiosMessage' is not a member of 'DcsBios'. I've tried to usual restart the program, restart windows, remove the library and reinstall but it hasn't helped. EDIT: fixed by adding missing definition for DCSBIOS_DEFAULT_SERIAL

I think Satarosa understands what the difference between the bombs is, but (like me) does not know what technique to use with retarded bombs. If you use the TGT/PLT technique with high drag bombs they will land short.

Yes, I'd like some guidance on technique for dropping the high-drag bombs as well.

Use the utility light (alt+L, I think) until they fix it. I can't believe it was like that in the real aircraft either.

It's the other way around.

You still have to switch it out of standby once it's warmed up to actually use it. I dunno if that's what Jester does.

At what point did you ask Jester to turn it on? It takes about 8 minutes to warm up to a usable state.

The UHF 1 radio in the pilot's seat has an ADF mode. The bearing is shown on the BDHI. I haven't actually tried it though.

Yup. You'll also notice that, as he is a robot, he doesn't need oxygen.

Sorry, you're right. I should have said manoeuvring flaps.