Jump to content

Recommended Posts

Posted

Despite most of the aircrafts working perfectly fine as flyables with FC3 cockpits, there are a few that ignore the input folder assigned to them and instead show & use the su-25T controls.

 

Could anyone share some light on why this happens and how to fix it? :smilewink:

[sIGPIC][/sIGPIC]

Posted

But if someone wants to fly the -25T pit instead them from FC3? :( Iberian can you explain me that? Thanks

Bye, SU

 

AMD FX-8350 @ 4.0 GHz, GIGABYTE (AMD) Radeon R9 280X Series @ 3GB Video, ATI Radeon / Realtek HD SoundCard, GIGABYTE FX-990GAUD Motherboard, Samsung 840EVO SSD @ 120GB, WD Caviar Blue @ 1TB

Posted

That depends on the Self_ID and old= parameters at make_flyable in the entry.lua

Old= is for the avionics -> 54 or a nil is the Su-25T, 16 is the a-10a (could be wrong, I have no PC here ATM )

  • 3 weeks later...
Posted
That depends on the Self_ID and old= parameters at make_flyable in the entry.lua

Old= is for the avionics -> 54 or a nil is the Su-25T, 16 is the a-10a (could be wrong, I have no PC here ATM )

 

Correct, so for example I'm using old=49 and regardless it uses su-25T avionics.

So it error is most likely in the bold and underlined area, ["F-16C"] = current_mod_path .. '/Input/F-16C',

 

I have tried F-16C which is the old ID used by DCS until a few months ago, and F-16C Bl.50, neither of those work

[sIGPIC][/sIGPIC]

Posted

So if i want to fly an l39za with su25t cockpit what should i write? :D

Bye, SU

 

AMD FX-8350 @ 4.0 GHz, GIGABYTE (AMD) Radeon R9 280X Series @ 3GB Video, ATI Radeon / Realtek HD SoundCard, GIGABYTE FX-990GAUD Motherboard, Samsung 840EVO SSD @ 120GB, WD Caviar Blue @ 1TB

  • Recently Browsing   0 members

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