Can I modify control indicator??

[815TooCooL]

Unfortunately I'm using CH Pro throttle, which moves linear slide(not arc!!! it could have been perfect throttle), so I can never feel where my collective is at, control indicator(rCtrl+Enter) is necessary evil.

But that BIG red indicator is really immersion killer.

Can I minimize it by editing something?

 

As it always has been, the almighty .lua file could help me again? :D

[815TooCooL]

OK, you can just tell me it's impossible. (finally, something lua can't edit. :D )

But I fogot to ask this.

What is the blinking B and A at right in control indicator?

I see it of no use and quite hindering.

[Frederf]

Try messing with: Black Shark\Scripts\Aircrafts\Ka-50\Cockpit\ControlsIndicator\ControlsIndicator_page.lua

[JG14_Smil]

B park brake.

 

A auto pilot.

 

H hover mode.

 

quite useful.

[Tiger27]

The B is for your handbrake, slider underneath B is progressive brakes, the A signifies auto route mode

[815TooCooL]

I did it.

Thank you for kind answers and thanks Frederf for picking exact file.

Another .lua edit!! :doh:

Edited January 22, 2009 by =815=TooCooL
pic

[Chillspider]

turn it to sim turn all the kid stuff off.

[815TooCooL]

turn it to sim turn all the kid stuff off.

 

Just by that single bar, I'm becoming a kid again?

As long as I don't have proper collective controller, this is necessary.

(Considering X52 pro throttle but it doesn't have nice button layout it seems.)

Hope you hard core simmers withstand my cheats. :D

[Frederf]

Chillspider probably didn't read that you have a special-case game controller that requires a bit of on-screen feedback. Glad it's working out for you!

[Shrubbo]

Hey if you like it go for it but I think you just need to forget about worrying where your collective is and just fly the thing TooCool.

 

For example...

I have flown various types of planes.

I have driven many types of cars, bikes, trucks, forklifts etc etc etc

 

and not one single one of them had any sort of heads up display of where the throttle was at.

 

Exactly the same can be said of a collective. There is no need to see where exactly it is, the only thing you need to worry about is what your machine is doing.

 

I use CH, personally I love it and my control if very accurate with the collective. I am only concerned with what the aircraft is doing, I have no concern at all for where the control is. (Catastrophic failure aside ok but you get my point:D)

[Shrubbo]

Oh btw a tip. If you need super delicate control of the collective for some reason (Strangely enough I find lots of reasons for this) place the heel of your hand just on the edge of the casing and just use your fingers to push/pull. I am still impressed with the minute power differences I can make doing that.

[docehrenhoefer]

(...) Exactly the same can be said of a collective. There is no need to see where exactly it is, the only thing you need to worry about is what your machine is doing. (...)

 

)

 

 

Well, Shrubbo, in a way you are right, in a way not. I own a Saitek X52 and the Saitek Rudder Pedals, and sometimes after continouus trimming the rudder is so much off-center it is almost impossible to re-trim (see all the posts about Saitek and re-trimming). So this little tool may come handy.

 

...and: American Helos have a cyclic position control inside the cockpit, at least the CH-53 Super Stallion and the Sea Hawk and derivatives afaik so it´s not so far off....

[815TooCooL]

What I do need is NOT super delicate control.

In real a/c, or even with my saitek throttle quad, I can roughly feel where it is without looking at it.

But with CH throttle, using it for 5 years, I can NEVER feel it.

With heel of hand tip, :huh: sorry, I won't buy it. I like to grab it.

 

I DON'T HAVE ANY SINGLE CLUE IF MY LEVER IS UP HIGH OR DOWN LOW WITH CH THROTTLE.

ALL OTHER THROTTLE CONTROLLERS IN REAL & SAITEK, IT'S NOT.

I CAN EASILY FEEL AND CONTROL COLLECTIVE WITH SAITEK THROTTLE WITHOUT LOOKING AT IT OR THOSE CHEAT DISPLAY TIPS! THE DIFFERENCE IS SO MUCH OBVIOUS!

 

I love sturdiness & software of CH but making throttle move complete linear was their big fault, like ball crushing gap of CH rudder, oops and the for-gorilla-hand Fighter stick.

Edited January 22, 2009 by =815=TooCooL
FOR RANT. ARC ARC ARC!! SORRY FOR RANT!! :)

[Jack57]

Unfortunately I'm using CH Pro throttle, which moves linear slide(not arc!!! it could have been perfect throttle), so I can never feel where my collective is at, control indicator(rCtrl+Enter) is necessary evil.

But that BIG red indicator is really immersion killer.

Can I minimize it by editing something?

 

As it always has been, the almighty .lua file could help me again? :D

 

I can't understand that you feel that way - I use the CH Pro Throttle mounted vertically on the left side on my chair and it gives a very realistic imitation of a real collective. You should know where the collective is at from the instruments and the feel of what the machine is doing - if in doubt have a glance at the pitch indicator which will tell you precisely where the collective is positioned.

 

Cheers,

Jack :)

[McVittees]

Try messing with: Black Shark\Scripts\Aircrafts\Ka-50\Cockpit\ControlsIndicator\ControlsIndicator_page.lua

 

I was wondering how this was done - thank you Frederf!:thumbup:

[docehrenhoefer]

Position change?

 

I am not used to programming lua files:

Does anybody know how the position of the control indicators is defined?

For example, I want to change the position from lower left to lower right... :huh:

 

Thanks in advance

[Shrubbo]

I don't care if you don't buy it.... I wasn't selling anything. I was just trying to help as I thought clearly you had a problem with something that was not actually a problem and I could offer some advice.

 

Obviously the hardware is at fault and there is nothing for you to learn and I bid you good day sir:thumbup:

 

 

What I do need is NOT super delicate control.

In real a/c, or even with my saitek throttle quad, I can roughly feel where it is without looking at it.

But with CH throttle, using it for 5 years, I can NEVER feel it.

With heel of hand tip, :huh: sorry, I won't buy it. I like to grab it.

 

I DON'T HAVE ANY SINGLE CLUE IF MY LEVER IS UP HIGH OR DOWN LOW WITH CH THROTTLE.

ALL OTHER THROTTLE CONTROLLERS IN REAL & SAITEK, IT'S NOT.

I CAN EASILY FEEL AND CONTROL COLLECTIVE WITH SAITEK THROTTLE WITHOUT LOOKING AT IT OR THOSE CHEAT DISPLAY TIPS! THE DIFFERENCE IS SO MUCH OBVIOUS!

 

I love sturdiness & software of CH but making throttle move complete linear was their big fault, like ball crushing gap of CH rudder, oops and the for-gorilla-hand Fighter stick.

[815TooCooL]

I don't care if you don't buy it.... I wasn't selling anything. I was just trying to help as I thought clearly you had a problem with something that was not actually a problem and I could offer some advice.

 

Obviously the hardware is at fault and there is nothing for you to learn and I bid you good day sir:thumbup:

 

Thank you Shrubbo, what I was ranting at..was CH, not you obviously.

Actually I was messing with one of CH throttle remodelling for arc move and broke one at the time. (I had 2 of em, oh, now it's only one.)

[Lightning]

I did it.

Thank you for kind answers and thanks Frederf for picking exact file.

Another .lua edit!! :doh:

 

 

It would be nice if you could share with us, what exact part of the .lua file you edited and what changes you made to it.

 

Thank you !

[815TooCooL]

dofile(LockOn_Options.common_script_path.."elements_defs.lua")
SetCustomScale(1.0)
function AddElement(object)
object.screenspace = ScreenType.SCREENSPACE_TRUE
   object.use_mipfilter = true
   Add(object)
end
local aspect        = LockOn_Options.screen.aspect
local size          = 0.30 --default value was 0.15
local tex_scale     = 0.25/size
local line_width    = (4.5/512)/tex_scale
local roll_stick_movement           = 130
local k                             = size / 130
local pitch_stick_movement_positive = 115 * k  --default value was 115 * k
local pitch_stick_movement_negative = 190 * k
--[[
   CURR_SCREENSPACE_NONE = 0,
   CURR_SCREENSPACE_HUD_ONLY_VIEW = 1,
   CURR_SCREENSPACE_ARCADE = 2,
--]]
local ds           = 0.05 * size
local collec_shift = 0.3*size
local rud_shift    = 0.1*size
local orange_mat   = MakeMaterial("",{255,100,0,0}) --default transparency value was 50
base          = CreateElement "ceMeshPoly"
base.name      = "base"
base.primitivetype  = "triangles"
base.material       = orange_mat -- "GREEN_TRANSPARENT"    
base.vertices       = {{-(size + collec_shift + rud_shift + 3.0*line_width + ds), -(size + ds)},
                      {-(size + collec_shift + rud_shift + 3.0*line_width + ds),  pitch_stick_movement_negative  + ds}, 
                      { size  + ds                            ,  pitch_stick_movement_negative  + ds},
                      { size  + ds                            , -(size + ds)}}        
base.indices        = default_box_indices
base.init_pos       = {0,-(1 - 1.5*size)}
base.controllers    = {{"show"},{"screenspace_position",2,-(aspect - 2*size),0},
                               {"screenspace_position",1,0,0}}
base.h_clip_relation  = h_clip_relations.REWRITE_LEVEL
base.level        = DEFAULT_LEVEL
AddElement(base)

pitch_scale                = CreateElement "ceTexPoly"
pitch_scale.name     = "pitch_scale"
pitch_scale.vertices       = {{-pitch_stick_movement_positive   , -line_width},
                             {-pitch_stick_movement_positive   ,  line_width},
                             { pitch_stick_movement_negative   ,  line_width},
                             { pitch_stick_movement_negative   , -line_width}}
pitch_scale.indices     = default_box_indices
pitch_scale.material    = "ARCADE_3_RED"
pitch_scale.init_rot       = {90,0,0}
pitch_scale.tex_params    = {256/512,176.5/512,0.5*tex_scale,2*tex_scale}
pitch_scale.parent_element = base.name
--AddElement(pitch_scale)
roll_scale                = CreateElement "ceTexPoly"
roll_scale.name        = "roll_scale"
roll_scale.vertices       = {{-size   , -line_width},
                            {-size   ,  line_width},
                            { size   ,  line_width},
                            { size   , -line_width}}
roll_scale.indices    = default_box_indices
roll_scale.material       = "ARCADE_3_RED"
roll_scale.tex_params   = {256/512,176.5/512,tex_scale,2*tex_scale}
roll_scale.parent_element = base.name
--AddElement(roll_scale)
local stick_index_sz           = 0.1 * size
stick_position                  = CreateElement "ceTexPoly"
stick_position.name             = "stick_position"
stick_position.vertices         = {{-stick_index_sz, -stick_index_sz},
                                  {-stick_index_sz,  stick_index_sz},
                                  { stick_index_sz,  stick_index_sz},
                                  { stick_index_sz, -stick_index_sz}}
stick_position.indices          = default_box_indices
stick_position.material        = "ARCADE_3_RED"
stick_position.tex_params    = {330/512, 365.5 / 512, 2*tex_scale, 2*tex_scale/0.8}
stick_position.controllers    = {{"stick_pitch",-pitch_stick_movement_positive,
                                               -pitch_stick_movement_negative},
                                {"stick_roll",size}}
stick_position.parent_element = base.name
--AddElement(stick_position)
rudder_scale                = Copy(roll_scale)
rudder_scale.init_pos       = {0,-(pitch_stick_movement_positive + 0.1*size)}
--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 collective_size = pitch_stick_movement_negative --originally there was no positive value!!
collective_scale             = Copy(pitch_scale)
collective_scale.vertices    = {{0, -line_width},
                               {0,  line_width},
                               {collective_size  ,  line_width},
                               {collective_size, -line_width}}
collective_scale.init_pos    = {-(size + collec_shift),0}
AddElement(collective_scale)
collective_index             = Copy(roll_scale)
collective_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}}
collective_index.controllers = {{"collective",collective_size}}
collective_index.init_rot    = {-90,0,0}
collective_index.parent_element  = collective_scale.name
AddElement(collective_index)

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 = collective_scale.name
     if i == 1 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 tick_50 = Copy(roll_scale)
     if i == 2 then tick_50.vertices    = {{0, -line_width},{0,  line_width},{3.0*line_width ,  line_width},{3.0*line_width , -line_width}}
     else           tick_50.vertices    = {{-3.0*line_width, -line_width},{-3.0*line_width,  line_width},{ 0 ,  line_width},{ 0 , -line_width}}   end
     tick_50.parent_element = rud.name
     tick_50.init_rot       = {90,0,0}
     tick_50.init_pos       = {(50/120)*rud_sz,0,0}
     --AddElement(tick_50)
local tick_35 = Copy(tick_50)
     if i == 2 then tick_35.vertices    = {{0, -line_width},{0,  line_width},{1.5*line_width ,  line_width},{1.5*line_width , -line_width}}
     else           tick_35.vertices    = {{-1.5*line_width, -line_width},{-1.5*line_width,  line_width},{ 0 ,  line_width},{ 0 , -line_width}}   end
     tick_35.init_pos       = {(13/120)*rud_sz,0,0}
     --AddElement(tick_35)

local tick             = Copy(tick_50)
     tick.init_rot    = {-90,0,0}
     tick.init_pos    = {0,0,0}
     tick.controllers = {{"throttle",i,rud_sz}}
     --AddElement(tick)   
end

local brakes_pos = {-size,0.85*pitch_stick_movement_negative - ds}
txt_brakes                 = CreateElement "ceStringPoly"
txt_brakes.name            = "txt_brakes"
txt_brakes.material        = "font_ARCADE_RED"
txt_brakes.init_pos     =  brakes_pos
txt_brakes.alignment       = "LeftBottom"
txt_brakes.stringdefs      = {0.0035, 0.0035,0,0}
txt_brakes.value           = "B"
txt_brakes.controllers     = {{"parking_brake"},{"blinking"}}
txt_brakes.parent_element  = base.name
--AddElement(txt_brakes)


local sz_wheel_brake       = 0.5 * pitch_stick_movement_negative

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

wheel_brake                = CreateElement "ceMeshPoly"
wheel_brake.name     = "wheel_brake"
wheel_brake.primitivetype  = "triangles"
wheel_brake.vertices       = {{0 ,0},
                             {0 ,sz_wheel_brake},
                             {0.3 * sz_wheel_brake ,sz_wheel_brake}}
wheel_brake.indices     = {0,1,2}
wheel_brake.material    = "RED"
wheel_brake.init_pos       =  wheel_brake_mask.init_pos
wheel_brake.parent_element = base.name
wheel_brake.h_clip_relation = h_clip_relations.COMPARE
wheel_brake.level      = DEFAULT_LEVEL
--AddElement(wheel_brake)
AUTOPMODE_NONE    = 0
AUTOPMODE_ROUTE   = 1
AUTOPMODE_DESCENT = 2
AUTOPMODE_HOVER   = 3
txt_autopilot                 = CreateElement "ceStringPoly"
txt_autopilot.name            = "txt_autopilot"
txt_autopilot.material        = "font_ARCADE_RED"
txt_autopilot.init_pos    = {size,brakes_pos[2]}
txt_autopilot.alignment       = "RightBottom"
txt_autopilot.stringdefs      = {0.0035, 0.0035,0,0}
txt_autopilot.value           = "A"
txt_autopilot.controllers     = {{"autopilot_engaged",AUTOPMODE_ROUTE}}
txt_autopilot.parent_element  = base.name
--AddElement(txt_autopilot)
local delta  = 6*ds
txt_autopilot_hover                 = CreateElement "ceStringPoly"
txt_autopilot_hover.name            = "txt_autopilot_hover"
txt_autopilot_hover.material        = "font_ARCADE_RED"
txt_autopilot_hover.init_pos  = {size,brakes_pos[2] - delta}
txt_autopilot_hover.alignment       = "RightBottom"
txt_autopilot_hover.stringdefs      = {0.0035, 0.0035,0,0}
txt_autopilot_hover.value           = "H"
txt_autopilot_hover.controllers     = {{"autopilot_engaged",AUTOPMODE_HOVER}}
txt_autopilot_hover.parent_element  = base.name
--AddElement(txt_autopilot_hover)

This is what I did.(so long time ago huh)

You can compare it with original one and figure out what's what.

I didn't fully comprehend whole things.(and you don't need to)

Edit it with Notepad++ and think about what you have to comment out or change values.

I added some comments so hope it helps you.:pilotfly:

[GregP]

So I'm trying to simply move the controls indicator a little further up on the screen ... any quick ideas about how exactly to do this? I've looked thru that lua file and it looks like I could sink whole day into experimenting with different values, as it's not at all obvious to me which parameters would affect the position.

[bn880]

Old thread, but I was just trying to do the same and it helped me save some time. Answer is modify

\DCS World\Mods\aircrafts\Ka-50\Cockpit\Scripts\ControlsIndicator\ControlsIndicator_page.lua

 

line which contains definition of

 

base.init_pos

You can change the XY position there, for example this puts it somewhere in the middle and very bottom of the screen: (good if you want to place other panel on left bottom where it used to clash)

 

base.init_pos       = {(1  + size),-(1 - size)}