Input profile not being used for new aircraft

[swither]

Hi!

 

I'm playing around with making an aircraft mod and everything seems to be working fine excep that the input profile i've created isn't used. It shows up in the control configuration but when i run a mission it defaults back to the su-25t profile!?!?. The array indices and such all seem to be the same so i'm somewhat clueless here.

 

Any ideas of what could cause an error like this? I've been searching the forums with no luck!

[predattak]

You inserted the wrong name in the imput line.

 

EXAMPLE :

 

F-5E mod line from the entry.lua

 

BAD EXAMPLE (YOU WILL GET THE SAME su-25T problem when you want to change controls)

 

InputProfiles =

{

["F-5E"] = current_mod_path .. '/Input/F-5E',

},

 

 

CORRECTED :

 

InputProfiles =

{

["f-5e tiger"] = current_mod_path .. '/Input/F-5E',

},

 

You need the correct imput name (in this case f-5e tiger NOT F-5E.)

 

Tell me what aircraft you wanted to make.

Edited August 26, 2015 by predattak

[indiadamjones]

Thanks

 

I've been looking for this info for at least 4 hrs. Thanks a ton. Just curious if there's a list of these aircraft names that make this function? For now it's enough to know I had to put phantom ii on my F-4E experimental craft. I searched and searched through system files and never was able to find the file that lists these.:thumbup: NM, found it. PM me if you want it.

Edited March 24, 2016 by indiadamjones
found it

[SkateZilla]

["<Aircraft Name<"] = current_mod_path .. '/Input/<AircraftName>/',

 

 

<AircraftName> = The name Given To the Aircraft in the DATA LUA and under the Entry LUA Make Flyable Line:

 

ie:

make_flyable('<AircraftName>'  , <path to cockpit scripts> ',{<Declare Type>}, Path to Cockpit Comms.')