electricaltill

You don't really need a track. You only need to run the cold start mission, turn on the batteries then turn on the landing light and hit F2 to see what we're talking about. The landing light used to illuminate a big cone ahead of the aircraft. Now it only illuminates a tiny circle directly below the light, regardless of where it's pointing.

Sorry, I didn't mean to sound like a dick! I just thought I'd add that it does do something, but not what it's supposed to.

The examples are not my code, they are existing, working bindings. I am asking if there is anything else needed to make bindings like this work. Mainly I don't understand what gives significance to the 'leftright' commands in command_defs.lua.

Actually it does, but only a tiny circle vertically beneath the aircraft (visible when on the ground).

I'm not renaming anything, I am adding bindings using the same format as other controls of the same type. Those added bindings have unique names. What file are you referring to?

I'm making a button box for the F-14. There are several rotary elements that have 'nudge' CW/CCW key bindings. Some don't have these bindings, I would like to add them and I can't quite grasp from the LUAs how they work. For instance, the azimuth center knob in the RIO cockpit (which DOES have these bindings). In clickabledata.lua: elements["PNT_82"] = default_axis(_("Radar azimuth center"),devices.RADAR, device_commands.RADAR_azimuth_center_knob, cockpit_args.RADAR_azimuth_center_knob, 0.0) Fine. But in default.lua for the keyboard commands we have: { combos = {{key = 'D', reformers = {'LAlt'}}}, up = device_commands.RADAR_azimuth_leftright, down = device_commands.RADAR_azimuth_leftright, cockpit_device_id=devices.RADAR, value_down = 1, value_up = 0, name = _('Radar azimuth right'), category = _('Radar Control Panel')}, { combos = {{key = 'A', reformers = {'LAlt'}}}, up = device_commands.RADAR_azimuth_leftright, down = device_commands.RADAR_azimuth_leftright, cockpit_device_id=devices.RADAR, value_down = -1, value_up = 0, name = _('Radar azimuth left'), category = _('Radar Control Panel')} In default.lua for the joystick commands we have: { up = device_commands.RADAR_azimuth_leftright, down = device_commands.RADAR_azimuth_leftright, cockpit_device_id=devices.RADAR, value_down = 1, value_up = 0, name = _('Radar azimuth right'), category = _('Radar Control Panel')}, { up = device_commands.RADAR_azimuth_leftright, down = device_commands.RADAR_azimuth_leftright, cockpit_device_id=devices.RADAR, value_down = -1, value_up = 0, name = _('Radar azimuth left'), category = _('Radar Control Panel')}So there's extra 'leftright' commands which seem to make this work. I can see in command_defs.lua that there are two lines for this control: RADAR_azimuth_scan_knob = counter(), RADAR_azimuth_leftright = counter() I have tried to add 'leftright' bindings for the DDD erase control by editing all of the files above. The bindings appear in DCS, but don't actually do anything when mapped. In clickabledata.lua both of these controls ("Erase" and "Radar azimuth center") are default_axis commands, so no changes needed there. What am I missing?

Have you tried pressing backspace?

I haven't had chance to use the updated module yet but the old one had an option in the "special" menu which affected the HMS position. Have you looked at that?

+1 Didn't change any settings after the update. Significant FPS drop going from the front to back seat. On the take-off IA mission, 60fps in the front seat, 38-40 in the back. It's day time, so no lights being used.

I mean, looking at that scale on the right side it looks like you need somewhere between 75-80%. Well above idle.

You don't seem to have looked in the manual. http://www.heatblur.se/F-14Manual/general.html?tid-symbology#tid-symbology Search for 'launch zone vectors'

I don't know, but one of the other inconsistencies I remember being pointed out about the engines was that idle power was sufficient for taxi in the real jet, and isn't here. Might be related?

Replays have never worked for the F-14. It's a DCS issue I think.

It doesn't automatically. If you want that you have to mark it using the CAP after you see the results of the IFF interrogation on the DDD.

The target only changes on the DDD. A sort of "=" appears in the centre of the DDD if the target is IFFing.

You're right, thanks for the correction.

ED have said there will be a discount for owners of BS2. As far as rudder pedals go, I personally found it better with pedals, but the majority of reports I've seen have said they flew it fine with a twist grip. :shrug:

Have you done the training missions for the RIO? That aside, and because I did this when I started RIOing: is WCS (the switch to the left of the HCU) on? If it's just in standby you don't see any targets on the DDD.

Encoders, not potentiometers. Same deal?

They are virtual com ports over USB, so surely the speeds will be uniform?

As I said, I connected all of the Arduinos to DCS-BIOS at once. That DCS-BIOS web interface certainly implies that devices can be connected through multiple com ports at once. It works but extremely slowly. Unusable.

Can DCS-BIOS communicate with multiple com ports at once? If so, what is needed to make this work properly? I have just finished a button box that uses four Arduinos. I can connect them all to DCS-BIOS together, but the sim takes up to 20 seconds to respond to commands from any of them. This happens if more than one device is connected at once. If only one of the Arduinos are connected DCS responds fine. I understand there is RS-485 support but I can't find anything to say whether this is the only way for multiple Arduinos to communicate with DCS-BIOS together. But what I'm trying is not working.

Good question, and you may ask it. That's a good idea, it's exactly what I was going to do. But I thought I'd first ask if there's some reason he has to do it "his" way so I'm not wasting both of our times with an explanation. Indeed, I am one of them!

Turn off the HUD, I find it distracting.

Why do you need on-on-on? If you set up an on-off-on as a voltage divider it can behave the same way.