Jump to content

Recommended Posts

Posted (edited)

Just a guess where to start searching ,

maybe you can collect enough hints together to find the right commands in following files :

 

Have a close look in DCS A-10C\Scripts\Aircrafts\A-10C\Cockpit\ControlsIndicator

ControlsIndicator_page.lua:




rudder_scale                = Copy(roll_scale)
rudder_scale.init_pos       = {0,-(pitch_stick_movement_positive + rudder_shift)}
AddElement(rudder_scale)

rudder_index             = Copy(roll_scale)
rudder_index.vertices    = {{-2.0*line_width , -line_width},
                           {-2.0*line_width ,  line_width},
                           { 2.0*line_width ,  line_width},
                           { 2.0*line_width , -line_width}}
rudder_index.controllers = {{"rudder",size},{"rotate",math.rad(90)}}
rudder_index.parent_element = rudder_scale.name
AddElement(rudder_index)

local rud_base            = CreateElement "ceSimple"
rud_base.name            = "rud_base"
rud_base.init_pos         = {-(size + rud_base_shift) ,0}
rud_base.init_rot       = {90}
rud_base.parent_element    = base.name
AddElement(rud_base)

for i = 1,2 do
local rud_sz   = pitch_stick_movement_positive + 0.1*size

local rud = Copy(pitch_scale)
     rud.vertices       = {{ 0      , -line_width},
                           { 0      ,  line_width},
                           { rud_sz   ,  line_width},
                           { rud_sz   , -line_width}}
       
     rud.parent_element =   rud_base.name
     if i == 2 then
     rud.init_pos       =   {-rud_sz,-rud_shift}
     else
     rud.init_pos       =   {-rud_sz, rud_shift}
     end
     rud.init_rot       = {0,0,0}
     AddElement(rud)
     


local brakes_pos            = {size,rudder_scale.init_pos[2]}

local sz_wheel_brake       = 1 * pitch_stick_movement_negative

for i = 1,2 do

   local signum = {-1,1}
   local     wheel_brake_mask                = CreateElement "ceMeshPoly"
           wheel_brake_mask.name            = "wheel_brake_mask_"..tostring(i)
           wheel_brake_mask.primitivetype  = "triangles"
           wheel_brake_mask.vertices       = {{0                    ,0},
                                              {0                    ,sz_wheel_brake},
                                              {-signum[i] * 0.3 * sz_wheel_brake ,sz_wheel_brake},
                                              {-signum[i] * 0.3 * sz_wheel_brake ,0}}
           wheel_brake_mask.indices        = {0,1,2,0,2,3}
           wheel_brake_mask.material        = "MASK_MATERIAL"
           wheel_brake_mask.init_pos       = {signum[i] * brakes_pos[1],brakes_pos[2]}
           wheel_brake_mask.parent_element = base.name
           wheel_brake_mask.controllers    = {{"brakes_value",i,sz_wheel_brake}}
           wheel_brake_mask.h_clip_relation  = h_clip_relations.INCREASE_LEVEL
           wheel_brake_mask.isvisible      = false
           AddElement(wheel_brake_mask)
           

           
           


And also have a look in:

\DCS A-10C\Scripts\Aircrafts\A-10C\Cockpit

 

command_defs.lua:

   PlaneLeftRudderStart = 201,
   PlaneLeftRudderStop = 202,
   PlaneRightRudderStart = 203,
   PlaneRightRudderStop = 204,

Edited by PeterP

Posted

Pedals are argument 266 in Max

Depending on how you've set up your pedals model, use a rotation-based-argument as example.

 

Pedals - Arg 266 - Range -1 ... 0 ... 1

Posted

I tried setting it to 266, however had no luck. It is mentioned for the Russian birds in the Ed arguments file as you said, but I am using the a-10 as a template. Just out of interest I tried it with arg 266 as a su-27 but the pedals gave no response.

 

Svksniper, I used arg 31 For the pedals, and this does provide some movement, however the argument is actually for the sliding ball in the turn and bank indicator, which means when you roll it also results in pedal movement. This is not ideal so I think unless we can magically discover the argument which results in the pedals moving I might just have to leave them.

 

Thanks to you both for the suggestions.

[sIGPIC][/sIGPIC]

Find us at http://virtual-roulettes.forumotion.com/

Posted

Argument #266 controls rudder pedals in the Ka-50 pit - don't know about the A-10C(don't have that).

 

However, since earlier lock-on pit models didn't have animated rudder pedals, I doubt any of the flyable aircraft entries in FC2 have this feature coded for them.

 

So the mention of argument 266 in the list is probably just for the Ka-50.

JJ

Posted
Why not assign the rudder pedal to the number that does the actual rudder? or is it different since its a cockpit file?

 

Yes arguments are catagorised.

 

E.g. for the Su-33 argument #0 controls IFR probe inside the cockpit - on the external model the same argument controls nose strut lowering, while IFR probe is under argument #22.

JJ

Posted

The rudder pedal arguments are for the newer aircraft only (A-10C and Ka-50), FC2 cockpits do not have an argument for rudder pedals.

i7 7700K | 32GB RAM | GTX 1080Ti | Rift CV1 | TM Warthog | Win 10

 

"There will always be people with a false sense of entitlement.

You can want it, you can ask for it, but you don't automatically deserve it. "

Posted

Yes, but again to sound like a broken record, FC cockpits do not have a rudder pedal animation!!! Unless you are putting your pit over the A-10C in DCS.....

i7 7700K | 32GB RAM | GTX 1080Ti | Rift CV1 | TM Warthog | Win 10

 

"There will always be people with a false sense of entitlement.

You can want it, you can ask for it, but you don't automatically deserve it. "

Posted

Meh, I wouldn't worry. I don't see how a rudder pedal animation (or lack of) would be a useful thing for form flying, IMHO. You gonna spend the whole time staring at your feet when on wing? :lol:

i7 7700K | 32GB RAM | GTX 1080Ti | Rift CV1 | TM Warthog | Win 10

 

"There will always be people with a false sense of entitlement.

You can want it, you can ask for it, but you don't automatically deserve it. "

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...