Jump to content

After 2.7 cannot mouse click on rocket arm switch, only works with keyboard command or joystick button.


Recommended Posts

  • Miles Vorkosigan changed the title to After 2.7 cannot mouse click on rocket arm switch, only works with keyboard command or joystick button.

Actually ALL switches below covers are not mouse klickable with 2.7 in the Sabre.

 

Fox

  • Thanks 3

Eagle Dynamics, ceterum censeo: dare nobis ME CCLXII!

Spoiler

PC Specs: Ryzen 9 5900X, EVGA RTX 3080 FTW3 ULTRA GAMING, 64GB RAM 3600Mhz, Samsung SSD 970 EVO Plus 1TB, HP Reverb (G1)

Link to comment
Share on other sites

4 hours ago, iFoxRomeo said:

Actually ALL switches below covers are not mouse klickable with 2.7 in the Sabre.

 

Fox

 

Can confirm; 100% reproducible.  Track attached.

 

@BIGNEWY

f86 broken switches.trk

Ryzen 9 5900X - GTX 1080ti - 32GB DDR4 - Samsung 970 EVO SSD - HP Reverb G2 - Thrustmaster Warthog - Logitech Flight Rudder Pedals - JetSeat - PointCTRL

 

Early Cold War Servers

https://discord.gg/VGC7JxJWDS

Link to comment
Share on other sites

Agree, was struggling with this yesterday, couldnt get rockets off while in flight in MP, had to look up keyboard commands to get to work, have since assigned to throttle buttons for work around

Intel i7-10700k, 32GB DDR4, GTX 1080 8GB, 1TB NVMe SSD, LG32GK850G 2560x1440 Monitor, Noctua u12a cooler

Link to comment
Share on other sites

  • 2 weeks later...
  • 3 weeks later...

I have compared old and new clickabledata.lua files for the F-86F as well as compared the F-86F to the similar, but fully functional F-5E. What I see is that ED made substantial changes to their scripting of clickable controls. It appears that they have added more parameters. Perhaps when this was done for the F-86, there were typos on all the red switch covers and/or covered switch definitions.

 

For example, here is are old definitions for the F-86:

elements["Rockets_switch_cover"] = default_red_cover  (_("Rocket Release Selector Switch Cover"), devices.WEAPON_SYSTEM,device_commands.Button_10, 750)
elements["Rockets_switch"] = default_3_position_tumb(_("Rocket Release Selector Switch, SINGLE/OFF/AUTO"), devices.WEAPON_SYSTEM,device_commands.Button_9,  751, false)

 

Here are the same elements in the current openbeta F-86:

elements["Rockets_switch_cover"] = default_red_cover  (_("Rocket Release Selector Switch Cover"), devices.WEAPON_SYSTEM,device_commands.Button_10, 750, {-90,0,0})
elements["Rockets_switch"] = default_3_position_tumb(_("Rocket Release Selector Switch, SINGLE/OFF/AUTO"), devices.WEAPON_SYSTEM,device_commands.Button_9,  751, false, nil, nil, nil, {-90,180,0})

 

Here is are similar definitions from the open beta F-5:

elements["PTR-CVR-LVP-GUM-MSL-CAM-342"] = default_red_cover(_("Guns, Missile and Camera Switch Cover, OPEN/CLOSE"), devices.WEAPONS_CONTROL, weapons_commands.GunsMslCamrCover,    342, nil, {0,90,-90})
elements["PTR-TMB-LVP-GUM-MSL-CAM-343"] = default_3_position_tumb(_("Guns, Missile and Camera Switch, GUNS MSL & CAMR/OFF/CAMR ONLY"), devices.WEAPONS_CONTROL, weapons_commands.GunsMslCamr, 343, nil, nil, nil, nil, nil, {0,90,0})
 

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

Open beta red cover definition for the F-5:

function default_red_cover(hint_,device_,command_,arg_,animation_speed_,turn_box_)
    local    element = default_2_position_tumb(hint_,device_,command_,arg_,animation_speed_,turn_box_)
    element.sound    = {{SOUND_SW3_CLOSE, SOUND_SW3_OPEN},{SOUND_SW3_CLOSE, SOUND_SW3_OPEN}}
    element.side    = {{BOX_SIDE_Y_bottom},{BOX_SIDE_Z_bottom}}
    return  element
end

 

Open beta red cover definition for the F-86:
function default_red_cover(hint_, device_, command_, arg_,turn_box_)
    return  {    
                class         = {class_type.TUMB,class_type.TUMB},
                hint          = hint_,
                device         = device_,
                action         = {command_,command_},
                arg           = {arg_,arg_},
                arg_value     = {1,-1}, 
                arg_lim       = {{0,1},{0,1}},
                updatable     = true, 
                use_OBB     = true,
                sound        = {{SOUND_SW3_CLOSE, SOUND_SW3_OPEN},{SOUND_SW3_CLOSE, SOUND_SW3_OPEN}},
                side        = {{BOX_SIDE_Y_bottom},{BOX_SIDE_Z_bottom}},
                turn_box    = turn_box_ or nil,
            }
end
 

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

Open beta 3-position switch definition for the F-5:

function default_3_position_tumb(hint_,device_,command_,arg_,cycled_,animation_speed_,inversed_,arg_value_,arg_limit_,turn_box_)
    local cycled = false
    if cycled_ ~= nil then
       cycled = cycled_
    end
    local    animation_speed_ = animation_speed_ or anim_speed_default
    local    arg_value = arg_value_ or 1
    local   side = {{BOX_SIDE_Z_top},{BOX_SIDE_Z_bottom}}
    if inversed_ then
        arg_value = -arg_value
        side = {{BOX_SIDE_Z_bottom},{BOX_SIDE_Z_top}}
    end
    local    arg_limit = arg_limit_ or {-1,1}
    return  {
                class             = {class_type.TUMB,class_type.TUMB},
                hint              = hint_,
                device             = device_,
                action             = {command_,command_},
                arg               = {arg_,arg_},
                arg_value         = {-arg_value, arg_value},
                arg_lim           = {arg_limit,arg_limit},
                updatable         = true,
                use_OBB         = true,
                cycle           = cycled,
                animated        = {true,true},
                animation_speed    = {animation_speed_,animation_speed_},
                sound            = {{SOUND_SW1}},
                side            = side,
                turn_box        = turn_box_ or nil,
            }
end

Open beta 3-position switch definition for the F-86:

function default_3_position_tumb(hint_,device_,command_,arg_,cycled_,inversed_, arg_value_, arg_limit_,turn_box_)
    local cycled = true
    local arg_limit = arg_limit_ or {-1,1}
    local arg_value = arg_value_ or 1
    
    local side = {{BOX_SIDE_Z_top},{BOX_SIDE_Z_bottom}}
    if inversed_ then
        arg_value     = -arg_value
        side        = {{BOX_SIDE_Z_bottom},{BOX_SIDE_Z_top}}
    end

    if cycled_ ~= nil then
       cycled = cycled_
    end
    return  {    
                class         = {class_type.TUMB,class_type.TUMB},
                hint          = hint_,
                device         = device_,
                action         = {command_,command_},
                arg           = {arg_,arg_},
                arg_value     = {-arg_value, arg_value},
                arg_lim       = {arg_limit,arg_limit},
                updatable     = true, 
                use_OBB     = true,
                cycle       = cycled,
                sound        = {{SOUND_SW0}, {SOUND_SW0}},
                side        = side,
                turn_box    = turn_box_ or nil,
            }
end

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

F-86: function default_3_position_tumb(hint_,device_,command_,arg_,cycled_,inversed_, arg_value_, arg_limit_,turn_box_)

F-5:   function default_3_position_tumb(hint_,device_,command_,arg_,cycled_,animation_speed_,inversed_,arg_value_,arg_limit_,turn_box_)

 

They are the same except for the extra "animation_speed_" in the F-5, but look at the calls for the 3-way switch instances:

 

F-86: elements["Rockets_switch"] = default_3_position_tumb(

_("Rocket Release Selector Switch, SINGLE/OFF/AUTO"), devices.WEAPON_SYSTEM,device_commands.Button_9,

751, false, nil, nil, nil, {-90,180,0})

 

F-5: elements["PTR-TMB-LVP-GUM-MSL-CAM-343"] = default_3_position_tumb(

_("Guns, Missile and Camera Switch, GUNS MSL & CAMR/OFF/CAMR ONLY"), devices.WEAPONS_CONTROL, weapons_commands.GunsMslCamr,

343, nil, nil, nil, nil, nil, {0,90,0})

 

I don't know if there is a difference between how "false" and "nil" are decoded, but that is the only difference I see.

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

Any chance of a fix for this, before it hits Stable?

- Jack of many DCS modules, master of none.

- Personal wishlist: F-15A, F-4S Phantom II, JAS 39A Gripen, SAAB 35 Draken, F-104 Starfighter, Panavia Tornado IDS.

 

| MSI Z87-G45 Gaming | i5-4670K @ 4.3Ghz | 32Gb DDR3 1600 | Asus GTX 1070 Strix OC | Samsung 850 Evo 250 & 500Gb | 40" Sony FullHD | Oculus Rift CV1 | Thrustmaster Warthog Stick (19.5cm extension) & Throttle | MFG Crosswind | Windows 10 |

Link to comment
Share on other sites

It has been reported so the devs are aware

Windows 10 Home ¦ Z370 AORUS Gaming K3 motherboard ¦ i5-8600K oc to 4.3GHz ¦ 48GB Corsair PC4 memory @ 3000MHz ¦ Samsung 960 EVO M.2 SSD for OS, Samsung 860 EVO 1TB SSD for DCS ¦ ASUS ROG GTX 2060 Super 8GB ¦ Virpil WarBRD base with VFX grip, Thrustmaster A10c and F/A-18 grips ¦ VKB Gunfighter Mk2 and MCG ¦ Thrustmaster Warthog Throttle ¦ MFG Crosswinds ¦ Oculus Rift S

Link to comment
Share on other sites

  • 3 weeks later...

Is there a community fix for this? I am thinking about buying the Sabre with summer sale, but I fly only VR and I extensively use mouse clicks, I won't buy a bugged module until there's a fix. Thanks.

Link to comment
Share on other sites

Still worth buying. But do be aware that bugs are a lifetime thing with this module. We are still waiting for the no sound bug to be fixed. And this particular bug has survived through three or four updates so I am not hopeful that it will be fixed any time soon. 

Link to comment
Share on other sites

 Share

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...