electricaltill

I'm trying to add 'nudge' CW/CCW bindings to the 'weapon interval' rotary control in the Viggen. Normally creating new bindings isn't too difficult but in this case the LUA files are using command numbering I don't understand. A comparable example I was trying to copy is the weapon selector knob, which does have 'nudge' bindings. In clickabledata.lua we have: elements["WepSEL-PTR"] = multiposition_switch_limited(_("Weapon Selector Knob - J/A Valjare"), devices.WEAPON_SYSTEM, 3304, 264, 6, 0.1, false, 0) In the default.lua for keyboard commands we have: {down = 3304, cockpit_device_id = devices.WEAPON_SYSTEM, value_down = 0.0, name = _("Weapon Selector 0 SJÖ/PLAN"), category = _("Weapons")}, -- added v0.6 {down = 3304, cockpit_device_id = devices.WEAPON_SYSTEM, value_down = 0.1, name = _("Weapon Selector 1 RB75/MARK/DYK"), category = _("Weapons")}, -- added v0.6 {down = 3304, cockpit_device_id = devices.WEAPON_SYSTEM, value_down = 0.2, name = _("Weapon Selector 2 LUFT/RR"), category = _("Weapons")}, -- added v0.6 {down = 3304, cockpit_device_id = devices.WEAPON_SYSTEM, value_down = 0.3, name = _("Weapon Selector 3 AKAN/JAKT"), category = _("Weapons")}, -- added v0.6 {down = 3304, cockpit_device_id = devices.WEAPON_SYSTEM, value_down = 0.4, name = _("Weapon Selector 4 ATTACK"), category = _("Weapons")}, -- added v0.6 {down = 3304, cockpit_device_id = devices.WEAPON_SYSTEM, value_down = 0.5, name = _("Weapon Selector 5 IR-RB"), category = _("Weapons")}, -- added v0.6 I understand this so far. But this is the key bindings for individual rotary positions. For the 'nudge' CW/CCW commands, on the same control, we have: {combos = {{key = "W", reformers = {"LShift","LCtrl"}}}, down = 3969, cockpit_device_id = devices.WEAPON_SYSTEM, value_down = -1.0, name = _("Weapon selector turn clockwise"), category = _("Weapons")}, {combos = {{key = "W", reformers = {"LAlt","LCtrl"}}}, down = 3969, cockpit_device_id = devices.WEAPON_SYSTEM, value_down = 1.0, name = _("Weapon selector turn counterclockwise"), category = _("Weapons")}, Where does 3969 come from? Why doesn't it use 3304? I've done a text search and the only files where 3969 appears is the default.lua files, there's nothing in clickabledata.lua. I don't understand how it's assigned, or how to establish what the command number would be for a 'nudge' binding for the weapon interval selector.

I don't remember setting this option but turning off resolved the problem. Thanks!

Sure but it's incredibly basic, just one WP and a fix point. F-14B INS fix practice PG.miz

I've made a few SP missions to practice aspects of the Tomcat, with the aircraft already airborne. When I click 'fly', regardless of what speed I've set for the aircraft the flaps deploy and the stick goes to full left deflection. I can catch this before it causes damage, and the stick deflection is overridden by my HOTAS position as soon as I move it, but this shouldn't be happening.

Just discovered this same issue.

The manual has nothing about airstart procedures for the TF30, and the 'A lacks the 'engine mode' panel of the 'B. Can you airstart the TF30, and if so, are the any references for how to do it?

I'm getting this issue with a 10900k, 64GB @3600 and a 3090. The F-14 carrier quals IA mission hovers around 40-50fps when looking at the island. After takeoff it's pinned at 60 (vsync). Do a flyover of the SC deck, it flickers down to 40-50 again. The problem disappears if I change shadows to 'flat only.'

I have a 4k monitor and am experimenting with lower resolutions for a decent framerate. At any res other than 4k, in fullscreen, when I click on something in the GUI the mouse cursor jumps to what looks like where that menu option would be if DCS was in windowed mode. For instance, in fullscreen@1080, if a menu option is centred on the screen (the pause menu, say), when I click on it the first time, the cursor jumps to roughly the centre of the upper-left quadrant of the screen - i.e. where DCS would be if it was windowed@4k. The second time I click on the option (after moving the mouse back) the click registers. This is a PITA, because I have to move twice to click on anything. I've tried repairing the installation. Can anyone help?

All right, you got me! Edit: actually shouldn't have put station 2 in there, there's already bindings for the left and right tanks, just not numbered stations 2 and 7.

Please add these weapon jettison bindings to the RIO seat: {down = device_commands.WEAP_Jett_Station1, cockpit_device_id=devices.WEAPONS, value_down = 1, name = _('Jettison station 1: B'), category = _('Weapons')}, {down = device_commands.WEAP_Jett_Station1, cockpit_device_id=devices.WEAPONS, value_down = 0, name = _('Jettison station 1: SAFE'), category = _('Weapons')}, {down = device_commands.WEAP_Jett_Station1, cockpit_device_id=devices.WEAPONS, value_down = -1, name = _('Jettison station 1: SW'), category = _('Weapons')}, {down = device_commands.WEAP_Jett_Station3, cockpit_device_id=devices.WEAPONS, value_down = 1, name = _('Jettison station 3: SEL'), category = _('Weapons')}, {down = device_commands.WEAP_Jett_Station3, cockpit_device_id=devices.WEAPONS, value_down = -1, name = _('Jettison station 3: SAFE'), category = _('Weapons')}, {down = device_commands.WEAP_Jett_Station4, cockpit_device_id=devices.WEAPONS, value_down = 1, name = _('Jettison station 4: SEL'), category = _('Weapons')}, {down = device_commands.WEAP_Jett_Station4, cockpit_device_id=devices.WEAPONS, value_down = -1, name = _('Jettison station 4: SAFE'), category = _('Weapons')}, {down = device_commands.WEAP_Jett_Station5, cockpit_device_id=devices.WEAPONS, value_down = 1, name = _('Jettison station 5: SEL'), category = _('Weapons')}, {down = device_commands.WEAP_Jett_Station5, cockpit_device_id=devices.WEAPONS, value_down = -1, name = _('Jettison station 5: SAFE'), category = _('Weapons')}, {down = device_commands.WEAP_Jett_Station6, cockpit_device_id=devices.WEAPONS, value_down = 1, name = _('Jettison station 6: SEL'), category = _('Weapons')}, {down = device_commands.WEAP_Jett_Station6, cockpit_device_id=devices.WEAPONS, value_down = -1, name = _('Jettison station 6: SAFE'), category = _('Weapons')}, {down = device_commands.WEAP_Jett_Station8, cockpit_device_id=devices.WEAPONS, value_down = 1, name = _('Jettison station 8: B'), category = _('Weapons')}, {down = device_commands.WEAP_Jett_Station8, cockpit_device_id=devices.WEAPONS, value_down = 0, name = _('Jettison station 8: SAFE'), category = _('Weapons')}, {down = device_commands.WEAP_Jett_Station8, cockpit_device_id=devices.WEAPONS, value_down = -1, name = _('Jettison station 8: SW'), category = _('Weapons')}, Thanks!

If you need negative trim downwind you need to lose more speed on the break. Once I'm downwind I always need to start adding positive trim to stay level. Idle, speed brakes, break (3-4g), wings to auto (~280), gear down (250), flaps & DLC out (220), then you can start bringing the throttles back up and trimming like crazy.

I recall seeing here somewhere that this instrument is unreliable in the Tomcat, though whoever that was didn't say whether it's a bug or accurate simulation.

I believe in the jet it's comparable to an analogue axis, but it is spring-loaded, so on release it will return to centre. I think most of us with a HOTAS (except those with the F-14 sticks of course) have DLC bound to forward/aft on a hat switch and "blip" it during the approach with small activations as required. Same as what you're doing with the keyboard. I think you're suggesting toggling DLC in a particular direction, for it to remain there until change, and iirc there is not a binding for that. The solution might be outside of DCS, virtual joystick software or something.

There is a GR video with an example of 4A and 4C in MP.

Wow, that is surprising. I thought that it was just a case of setting a common frequency and non-clashing link IDs. Thanks, again that is useful information.

Yes, thanks very much! So I don't need to change anything except the datalink switch to aux, and it should work?

This is a side effect of the "rudder trimmer" option. I sometimes forget about it too if I'm honest.

Your OP screenshotted the options screen. That is the trimmer mode I'm talking about, but sounds like you are using the trim correctly. Not sure what the problem is, sorry. Edit: are you also releasing the rudder? Because you have to do that too in this mode.

In the trimmer mode you have selected, following trimming, the joystick has to be returned to the neutral position before any further input will register. If you keep the trimmer pressed, inputs will still register.

Can I establish a 4C link with an AI F-14? I want to try the datalink nav fix functionality, but I can't see anywhere in the mission editor that would let me set the link code or datalink frequency on the AI aircraft. Sent from my Pixel C using Tapatalk

That's really cool! Thank you.

Yes, it's been reported but not resolved yet.

No problem, fly safe

It's on the knee board, Rshift+K. You have to go forward or backward a couple of pages. Sometimes it bugs - if Jester didn't tell you which wire you caught, the kneeboard won't show anything either.

What do you mean by silent? Are you talking about the RWR?