Today!! Hornet updates?

Yup, TDC returns to top left on undesignate. Sweep bar still sticks at 140 degrees. Bombs still seem super inaccurate unless dropped at like a 50 degree dive.

I can't get the speedbrake to extend/retract either by my WH HOTAS or the keyboard --- anyone else having this problem too?

Edit: I even put the config files from a backup I made before the update - no joy.

I cant lock a target after update....anyone has same issue?

I can't get the speedbrake to extend/retract either by my WH HOTAS or the keyboard --- anyone else having this problem too?

 

Edit: I even put the config files from a backup I made before the update - no joy.

I haven't had a chance to test yet, but the mappings had changed so that the Speed brake switch had been remapped to Chaff. Have changes these back and will try later

I can't get the speedbrake to extend/retract either by my WH HOTAS or the keyboard --- anyone else having this problem too?

 

Edit: I even put the config files from a backup I made before the update - no joy.

I had this problem...solved after restarting PC and re-bind...hope it helps!

Also my monitor start blinking after update. Never did that before...and fixed by itself after few minutes. Wtf?

Maybe it couldn't believe its pixels when it saw the MiG-29 update?

also, additional commands that i really used (2 position switches) don t work anymore..

{down = SMS_commands.MasterArmSw, up = SMS_commands.MasterArmSw, cockpit_device_id = devices.SMS, value_down = 1.0, value_up = 0.0, name = _('Master Arm Switch 2-Pos ARM/SAFE'), category = {_('Instrument Panel'), _('Master Arm Panel')}},

{down = hotas_commands.THROTTLE_EXTERIOR_LIGTHS, up = hotas_commands.THROTTLE_EXTERIOR_LIGTHS, cockpit_device_id = devices.HOTAS, value_down = 1.0, value_up = 0.0, name = _('Exterior Lights 2-Pos ONOFF'), category = {_('Throttle Grip'), _('HOTAS')}},

{down = iCommandPlaneGearUp, up = iCommandPlaneGearDown, name = _('Landing Gear Control Handle 2-Pos UP/DOWN'), category = {_('Left Vertical Panel')}},

{down = gear_commands.HookHandle, up = gear_commands.HookHandle, cockpit_device_id = devices.GEAR_INTERFACE, value_down = 1.0, value_up = 0.0, name = _('Arresting Hook Handle 2-Pos UP/DOWN'), category = {_('Right Vertical Panel')}},

{down = HUD_commands.HUD_AltitudeSw, up = HUD_commands.HUD_AltitudeSw, cockpit_device_id = devices.HUD, value_down = 1.0, value_up = 0.0, name = _('Altitude Switch 2-Pos BARO/RADAR'), category = {_('Instrument Panel'), _('HUD Control Panel')}},

{down = cpt_commands.CanopySwitchClose, up = cpt_commands.CanopySwitchOpen, cockpit_device_id = devices.CPT_MECHANICS, value_down = -1.0, value_up = 1.0, name = _('Canopy Control Switch 2-Pos OPEN/CLOSE'), category = {_('Right Wall'), _('Systems')}},

{down = oxygen_commands.OBOGS_ControlSw, up = oxygen_commands.OBOGS_ControlSw, cockpit_device_id = devices.OXYGEN_INTERFACE, value_down = 1.0, value_up = 0.0, name = _('OBOGS Control Switch 2-Pos ON/OFF'), category = {_('Left Console')}},

{down = cptlights_commands.HookBypass, up = cptlights_commands.HookBypass, cockpit_device_id = devices.CPT_LIGTHS, value_down = -1.0, value_up = 1.0, name = _('Hook Bypass 2-Pos Switch CARRIER/FIELD/CARRIER'), category = {_('Left Vertical Panel')}},

{down = gear_commands.LaunchBarSw, up = gear_commands.LaunchBarSw, cockpit_device_id = devices.GEAR_INTERFACE, value_down = -1.0, value_up = 1.0, name = _('Launch Bar Control 2-Pos Switch RETRACT/EXTEND'), category = {_('Left Vertical Panel')}},

main modes bindings (A/A, A/G) are not working even the keyboard binds are not working, wth?¿?¿?, they look redish in the controls page...what does that means???

thanks!

I think it means this whole update is FUBAR , nothing but complaints across the board.

after update, my radar froze many times during online play. didn't have this problem before or i didin't noticed it

today i notice the aim 120C is available, has been for awhile or just the B?

main modes bindings (A/A, A/G) are not working even the keyboard binds are not working, wth?¿?¿?, they look redish in the controls page...what does that means???

 

 

thanks!

I found with the red ones if I cleared all bindings for that 'key' I could bind a new button press. It seems like the red ones denote a double assignment of sorts.

today i notice the aim 120C is available, has been for awhile or just the B?

They have been available for over a month.

Worst case scenario, if you can't get your key bindings to work, bin the relevant lua file in the Saved Games set up for the module and input device affected, and it will re-create one when you restart DCS World. Then you'll have a clean file to start re-mapping with.

The problem is due to ED wanting to rationalize the key inputs across all modules. It's not a huge drama to re-set things. Long term, it apparently will make life easier.

I am hanging out for AGMs and JDAMs. I bought the Hornet for the air to air...but I play it for the air to ground.

I can't select radar altimeter, seems to be stuck in baro. Is it something I'm not doing or is it a bug from today's update?

Also noticed they've added all the joysticks and throttles for each module in the main input folders. Not seen that before (pretty sure it was just default.lua in there so if it was done previously then I didn't know). Probably why people are seeing changes in their keybindings? I found some of the Virpil joystick had been pre-programmed with keybindings I don't use so had to remove them. Same with Warthog throttle settings. Had to adjust some analogue settings too.

Not only did none of the supposed fixes listed in the change log take hold, they're worse. To add insult to injury, a lot of my bindings got mixed up/deleted. Can we roll back the radar already until it's been properly QA'd?

The only binding issue I’m having is “Arresting Hook - Cycle” default is “H” and it doesn’t respond to the H key or HOTAS binding. The “Down” I set to “H” and the “Up” I set to “LShft+H”. All other “highlighted” bindings have been corrected. It only took me a few minutes to fix.

So, I’m assuming this is a bug. Unless I’m the only one to have this issue.

Ok - good! Then its not just me. I agree it “should” be easy to fix.

All this was fixed in this patch:

 

Hotfix B-sweep no longer renders outside the radar tactical area.

Corrected the drag value of TCTS Pod.

TDC cursor position maintains location after target breaks lock.

Aerial refuelling Instant Action missions have been corrected.

B-Sweep no longer hangs when radar loses lock. This issue is still being worked on for an undesignated button break lock.

 

The controls issues are due to us starting to standardize and clean up the controls and how they are done in the sim, it makes for some extra work now, but down the road, it will be easier to have controller-based profiles supplied with the sim, that assign most controls for you, as well as have auto settings that make more sense and not so daunting.

 

No rollback is required, also this is Open Beta, if you don't like things like this, that can come with little to no notice, it's better to stick with the release version.

Are you saying these control binding problems will Not be released to stable at any point ? I would much prefer that ED leave my bindings alone :)

All this was fixed in this patch:

 

 

The controls issues are due to us starting to standardize and clean up the controls and how they are done in the sim, it makes for some extra work now, but down the road, it will be easier to have controller-based profiles supplied with the sim, that assign most controls for you, as well as have auto settings that make more sense and not so daunting.

 

No rollback is required, also this is Open Beta, if you don't like things like this, that can come with little to no notice, it's better to stick with the release version.

Had this game since Lomac days, it's what, 15 years down the road and we still push out updates that clobber everyones key bindings ?

How about an 'opt-in' approach on your profiles rather than a 'we will clobber your settings, so good luck try again' approach

Had this game since Lomac days, it's what, 15 years down the road and we still push out updates that clobber everyones key bindings ?

 

How about an 'opt-in' approach on your profiles rather than a 'we will clobber your settings, so good luck try again' approach

Hmmm....called early access!!

Hmmm....called early access!!

They were broken on all ED & Belsimtek modules. Not everything is in EA.