RodWan Olds

I'm running 5120x1440 and just was wondering if that is why these haven't been working for me on MT, works just fine on ST. I'm on Beta and other people in the squadron are saying it's working fine for them. Any ideas?

I've noticed that when you are spending a lot of time around the boat the 25-30deg drift can make running the CASE 1-3 downwind confusing sometimes. Switching compass mode to COMP seems to alleviate this and allows running the radial and reciprocal again without the need for head math. Is this the intended behavior? Or should the INS slave mode switch automatically when an excessive drift is detected. Obviously this only matters when doing multiple traps in a row, but still it would be nice to confirm what actual pilots did on qual nights, and how it's suppose to work when inside the CVN bubble.

You can tell because it kind of snaps in place.

Changed wing sweep initialization on spawn: Carrier spawn on catapult: 20deg, AUTO. All other ground spawns: oversweep, handle and cover raised. Air spawn: AUTO, position adjusted to the airspeed.

The Manual wing sweep now has an issue returning to CADC mode. -Wings Auto @ 45deg <450kts -Manual E-sweep to 30deg -Cannot push down handle unless at 20deg -Once handle is down, cover down, MASTER RESET does not drive the wings to the current CADC position. You have to open the cover, manually drag the handle (while in the down position) to catch the spider detent and then close the cover and press MASTER RESET. Or slow down to drive the CADC up to the current wing position. Not sure if this is the intended behavior. Not being able to push the handle down at mid range makes the additional setting in options pointless though as if you went in to e-sweep you'd have to slow to <300kts to return to the CADC program. ~ The obvious way to return to CADC you'd think would be to catch the spider detent, push down the handle, close the cover and hit MASTER RESET. Although it would have been nice QOL to be able to just push down the handle, close cover, hit MASTER RESET and have the wings go to the current computer position like it's always been. I will say that the whole system seems less jank now though, so I can defiantly tell it's been improved, just need to figure out how we're meant to use it now. Counterpoint: You can now control the wings manually by just opening the cover and leaving the handle down. So I've switched to using that instead as it mitigates most of the issue. Just move the slider to the CADC position and close the cover/press MASTER RESET. Additional: I also noticed that with the handle up in E-Sweep, if you align the wings and to the CADC bars and hit MASTER RESET it will connect with the spider detent and start to drive the handle with out closing the cover. Not sure if this is intended either. It all works fine for me. I'd double check your key bindings. I didn't have to change anything and it worked straight away. You will need to set the wings if you are starting on the ground now though. Handle down, cover close, MASTER RESET. Try an air spawn and see if it works like that.

Is the min range on the 7P suppose to be less than the 7MH? Here's a side by side shot first MH second P nullnull

If it was AI then how do you know it was TWS? I was under the impression AI only did STT launches which you would expect to get a RWR warning for.

This is just a binding though yeah? The logic of the mains should still be binary. Also folks can always move the flap lever with the mouse, but as long as the mains are on/off only it won't matter about the axis.

I have yet to get home and look at the files, but you can't get full extension on the maneuver flaps with the flap hadle before the aux extend, so it may be that HB has written a binding that basically is just a second DLC aft binding. In that case my previous statement is incorrect. I am unsure if the computer will override the DLC wheel and continue to sweep if you were actively holding it, but that would be one way to run the binding.

I skimmed this, so pardon me if this has been said. 1: Yes main flaps give you a turn rate advantage. No you shouldn't do that, they will break. 2: Regarding the OP question about using the flaps lever just to the point where the flaps won't break. I write my own keybindings for my pit and have already experimented with this idea. Two things. First the aux landing flaps are binary, so they are either up or down. Second the spot the flap handle would activate the aux flaps has not extended the maneuver flaps fully yet. So the conclusion is that by trying to game the system you are actually getting less flaps.... Just use the DLC wheel for flaps outside of landing.

People wanted a binding for their 3 position switches. As far as the implications are concerned, if you used the flap leaver the flaps will remain in maneuvering mode, if you use the dlc wheel, the computer can operated the flaps still. So for instance if you were in burner the new flap binding will prevent wings from getting past like 45deg or so, where in the old one the computer would collapse them and continue to sweep. AFAIK there isn't anything notable beyond that though. And as HB said, it's unrealistic for pilots to use the flap lever for partial flaps when their thumb is right there.

Can confirm. After AT is engaged, any time AP is on the throttle is unresponsive.

I just jumped in and checked, everything is working correctly for me. Double check that you are on the correct ICLS freq and have the HUD/VDI switches selected to AWL. For ACL make sure you are hooked to the CVN datalink.

Duplicate of https://forum.dcs.world/topic/297082-bug-using-auto-pilot-after-using-auto-throttle/?do=getNewComment

While I appreciate the video, kind of unhelpful. You didn't include critical data in your vid. They'd need to see you show in ME that the carrier is commanded with ILS on and what channel, then that you're in AWL and HUD/VDI toggled to AWL. I wonder if DataLink ACL works for the needles? I'll make a video tonight testing this once I'm off work if you don't have time, just trying to be helpful.

Did a fix for the AOA indexer lighting "keybind" make the cut. Noticed this the other day when I thought it was busted after starting at dawn and landing in late morning. I'm also curious when we'll see things like the hand pump and e-flaps / fire bottle get implimented. Are these on the radar at all? Reguarding the seat switching. I had noticed it working for me in the past if the "player seat lock" setting was disabled in the ME. Not sure if this is connected to the issue, but might try it.

The Rio cannon leave their seat from what I've noticed. Only the Pilot can get access to the Rio seat. Also if both the Pilot and Rio are in seat 2 there is some weirdness.

So I've been doing this for a while by disabling player seat lock on the mission. I've tested this in the ME and in Multiplayer on my own hosted server. Might be worth a shot to see if this works for you guys. The option is an Action in the trigger section of the ME. "STOP PLAYER SEAT LOCK()". Should just need to have it activate on mission start. Hope this helps. -Olds

Not working for me, Ai just takes control.

Posting this here as none of those formulas worked for me and I couldn't find any help. F14 VSI Formula for DCS Flightpanels (PLT_VSI_NEEDLE-32767.5) * ifless (PLT_VSI_NEEDLE 32767.5 (ifmore(PLT_VSI_NEEDLE 16000((log10 1.1)*log10 55)(ifmore(PLT_VSI_NEEDLE 7500((log10 1.125)*log10 80)(ifmore(PLT_VSI_NEEDLE 2500(log10 1.4)(.185))))))) (ifless(PLT_VSI_NEEDLE 46800((log10 1.1)*log10 50)(ifless(PLT_VSI_NEEDLE 56000((log10 1.125)*log10 80)(ifless(PLT_VSI_NEEDLE 62000(log10 1.4)(.185))))))))

Got another one { down=device_commands.VDIG_VDI_handle,up=device_commands.VDIG_VDI_handle, cockpit_device_id=devices.HUD, value_down=0, value_up=1, name = _('HUD Filter OFF else ON'), category = _('Lights')}, { down=device_commands.VDIG_VDI_handle,up=device_commands.VDIG_VDI_handle, cockpit_device_id=devices.HUD, value_down=0, name = _('HUD Filter OFF'), category = _('Lights')}, { down=device_commands.VDIG_VDI_handle,up=device_commands.VDIG_VDI_handle, cockpit_device_id=devices.HUD, value_down=1, name = _('HUD Filter ON'), category = _('Lights')}, { down=device_commands.VDIG_VDI_filter,up=device_commands.VDIG_VDI_filter, cockpit_device_id=devices.VDI, value_down=1, value_up=1, name = _('VDI Filter Momentary OFF/ON'), category = _('Lights')}, { down=device_commands.VDIG_VDI_filter,up=device_commands.VDIG_VDI_filter, cockpit_device_id=devices.VDI, value_down=1, name = _('VDI Filter Toggle OFF/ON'), category = _('Lights')}, [/Code] Keybinds for the HUD and VDI filters

To be added to Joystick.lua in the axis section at the bottom {action = device_commands.WINGSWEEP_EmergencySweepLever, cockpit_device_id=devices.WINGSWEEP, name = _('WingSweep')}, Add to both Keyboard and Joystick lua files {down = device_commands.WINGSWEEP_EmergencySweepCover, cockpit_device_id = devices.WINGSWEEP, value_down = 0, name = _('Emergency Wing Sweep Cover CLOSE'), category = { _('Throttle')}}, {down = device_commands.WINGSWEEP_EmergencySweepCover, cockpit_device_id = devices.WINGSWEEP, value_down = 1, name = _('Emergency Wing Sweep Cover OPEN'), category = { _('Throttle')}}, {down = device_commands.WINGSWEEP_EmergencySweepCover, up = device_commands.WINGSWEEP_EmergencySweepCover, value_down = 1, value_up = 0, cockpit_device_id = devices.WINGSWEEP, name = _('Emergency Wing Sweep Cover OPEN else CLOSED'), category = _('Throttle')}, {down = device_commands.WINGSWEEP_EmergencyLeverExtended,up=device_commands.WINGSWEEP_EmergencyLeverExtended, cockpit_device_id=devices.WINGSWEEP, value_down=1.0, value_up=0.0, name=_('Emergency Wing Sweep Handle PopOut else In'), category=_('Throttle')}, This will allow you to toggle into and out of emergency wing sweep mode, and then use the axis to control the wings. BTW you don't actually need to open the cover for this to work.... ~~but ma realism~~