module is up go get it here

 

Thanks! will check it out this weekend.

 

Here are some scripts that I've written. Currently working on VRS Superbug. Let me know if you have any questions or comments.

 

http://1drv.ms/1vQMr5f

Thanks! will check it out this weekend.

 

Here are some scripts that I've written. Currently working on VRS Superbug. Let me know if you have any questions or comments.

 

http://1drv.ms/1vQMr5f

 

Thanks Henry,

 

i guess the T45 is from Dino, the Douglas A-1H is the Razbaam, the OV-1D is Aerosoft and the Trojan is Ants, right? I have all these aircraft. The VRS is also in my hangar but it will stay there as i only fly P3D2. I will check out the other modules.

T-45 from Dino (tested with v2.66 but not with 2.70)

A-1H by Tim Conrad

OV-1D by Tim Conrad (the OV-10 by Aerosoft is included with LINDA)

T-28 was destined for Ant's but I think maybe be empty right now.

 

There is a function call Trim Reset in the PC-21 that really should be in the default FSX set. I have been lazily just copying it to new aircraft.

 

 

Is the HUD usable with TrackIR or is this a static overlay?

 

HUD is static ... made some screenshots in my thread here: http://forum.avsim.net/topic/453103-day-4-19-aircraft-in-19-locations-in-19-days/

 

Cheers, Rob.

Thanks for the extra shots and info, Rob. Seems like it's still usable, albeit not as nice and lined up like on the NGX. Well, the NGX doesn't have the night vision though. ^_^

Version 1.2 has fixed a lot, especially engine startup is now wway better. Not that´s it´s perfect, but it´s way better than it was.

Seems like they are reacting to the constructive critique. Nice trait. Thanks for the information, Steffen.

Let me know if you have any questions or comments.

 

I'm a bit of a Linda novice.

Don't these scripts usually have a linda-cfg folder as well?

 

Thanks,

gb.

I'm a bit of a Linda novice.

Don't these scripts usually have a linda-cfg folder as well?

 

Thanks,

gb.

 

Hi gb,

 

yes you´re right but in the linda-cfg folder is the definition file of your controllers. As you can see below this is the content of the config-hid.lua found in the folder of the airlifter

 

-- ## TM Warthog Stick ## (044F04020) ##############

 

 

 

-- ## TM Warthog Throttle ## (044F04040) ##############

 

JSTK["044F04040"][4]="MFD_Toggle"

JSTKrp["044F04040"][4]="MFD_Toggle"

JSTK["044F04040"][11]="HUGS_Toggle"

JSTKrl["044F04040"][11]="Do_nothing"

JSTK["044F04040"][16]="LH_Fuel_Pumps_On"

JSTKrl["044F04040"][16]="LH_Fuel_Pumps_Off"

JSTK["044F04040"][17]="RH_Fuel_Pumps_On"

JSTKrl["044F04040"][17]="RH_Fuel_Pumps_Off"

JSTK["044F04040"][18]="ENG_1_Off"

JSTKrp["044F04040"][18]="Do_nothing"

JSTKrl["044F04040"][18]="Do_nothing"

JSTK["044F04040"][19]="ENG_2_Off"

JSTKrp["044F04040"][19]="Do_nothing"

JSTKrl["044F04040"][19]="Do_nothing"

JSTK["044F04040"][20]="APU_On"

JSTKrl["044F04040"][20]="APU_Off"

JSTK["044F04040"][24]="TRU_1_On"

JSTKrl["044F04040"][24]="TRU_1_Off"

JSTK["044F04040"][25]="APU_Generator_On"

JSTKrl["044F04040"][25]="APU_Generator_Off"

JSTK["044F04040"][26]="Yaw_Damper_Sys_Toggle"

JSTKrp["044F04040"][26]="Do_nothing"

JSTKrl["044F04040"][26]="Do_nothing"

JSTK["044F04040"][27]="AC_Source_GEN1_ON"

JSTKrl["044F04040"][27]="AC_Source_APU_ON"

JSTK["044F04040"][28]="AC_Source_APU_OFF"

JSTKrl["044F04040"][28]="AC_Source_APU_ON"

JSTK["044F04040"][31]="ENG_1_On"

JSTKrl["044F04040"][31]="ENG_Starter_1_Off"

JSTK["044F04040"][32]="ENG_2_On"

JSTKrl["044F04040"][32]="ENG_Starter_2_Off"

JSTK["044F04040"][301]="HUGS_BRT_BRT"

JSTKrp["044F04040"][301]="HUGS_BRT_BRT"

JSTKrl["044F04040"][301]="Do_nothing"

JSTK["044F04040"][303]="FLIR_BRT_BRT"

JSTKrp["044F04040"][303]="FLIR_BRT_BRT"

JSTK["044F04040"][305]="HUGS_BRT_DIM"

JSTKrp["044F04040"][305]="HUGS_BRT_DIM"

JSTKrl["044F04040"][305]="Do_nothing"

JSTK["044F04040"][307]="FLIR_BRT_DIM"

JSTKrp["044F04040"][307]="FLIR_BRT_DIM"

 

 

-- ## Saitek Rudder ## (046DC02C0) ##############

 

 

 

-- ## Komodo VBS ProCyclic ## (16C005BA0) ##############

 

 

 

-- ## Saitek Yoke ## (06A30BD30) ##############

 

 

 

-- ## Saitek Pro Flight Switch Panel ## (06A30D670) ##############

 

JSTK["06A30D670"][5]="Engine_Prop_Ice_Prot_On"

JSTKrl["06A30D670"][5]="Engine_Prop_Ice_Prot_Off"

JSTK["06A30D670"][6]="Pitot_System_On"

JSTKrl["06A30D670"][6]="Pitot_System_Off"

JSTK["06A30D670"][7]="Formation_Lights_On"

JSTKrl["06A30D670"][7]="Formation_Lights_Off"

JSTK["06A30D670"][8]="Panel_Lights_On"

JSTKrl["06A30D670"][8]="Panel_Lights_Off"

JSTK["06A30D670"][9]="Beacon_Lights_On"

JSTKrl["06A30D670"][9]="Beacon_Lights_Off"

JSTK["06A30D670"][10]="Pos_Lights_On"

JSTKrl["06A30D670"][10]="Pos_Lights_Off"

JSTK["06A30D670"][11]="Anti_Coll_Lights_On"

JSTKrl["06A30D670"][11]="Anti_Coll_Lights_Off"

JSTK["06A30D670"][12]="Taxi_Lights_On"

JSTKrl["06A30D670"][12]="Taxi_Lights_Off"

JSTK["06A30D670"][13]="Landing_Lights_On"

JSTKrl["06A30D670"][13]="Landing_Lights_Off"

 

 

-- ## Pro Flight Multi Panel ## (06A30D060) ##############

 

JSTK["06A30D060"][8]="AP_Mstr_On"

JSTKrp["06A30D060"][8]="Do_nothing"

JSTKrl["06A30D060"][8]="AP_Mstr_Off"

JSTK["06A30D060"][9]="Hdg_On"

JSTKrp["06A30D060"][9]="Do_nothing"

JSTKrl["06A30D060"][9]="Hdg_Off"

JSTK["06A30D060"][10]="NAV_On"

JSTKrp["06A30D060"][10]="Do_nothing"

JSTKrl["06A30D060"][10]="NAV_Off"

JSTK["06A30D060"][11]="IAS_On"

JSTKrp["06A30D060"][11]="IAS_Off"

JSTKrl["06A30D060"][11]="Do_nothing"

JSTK["06A30D060"][12]="Alt_On"

JSTKrp["06A30D060"][12]="Alt_Off"

JSTKrl["06A30D060"][12]="Do_nothing"

JSTK["06A30D060"][14]="APR_On"

JSTKrp["06A30D060"][14]="Do_nothing"

JSTKrl["06A30D060"][14]="APR_Off"

 

 

-- ## VBS ProStart Collective ## (16C005BA1) ##############

 

 

It basically tells the buttons which function is defined in the module. LINDA will create this file as soon as the module will be loaded and a function is aplied to a button or switch. 

 

BTW i found a way to dim the brightness of the combiner for FLIR and HUGS!!!

 

 

Thanks for the extra shots and info, Rob. Seems like it's still usable, albeit not as nice and lined up like on the NGX. Well, the NGX doesn't have the night vision though. ^_^

 

I will up a HUGS night and day ops demonstration vid. ASN and EZDOK is in use in this vid.

Here we go HUGS demonstration.

 

 

I find it quite realistic with the dynamic head movement. In real life you will also lose focus while turning the head or encountering turbulences.

 

I just checked the PMDG HUGS on youtube. Gotta say i wish the HUGS would be that steady in real life :blink:

Wow, that's really good. Do you guys know if the FLIR works in FSX too?

 

I think I can make room for the plane but I might add the RXP GPS in the background to allow for some proper flight plan handling and things. Should work, no? Wouldn't be the first time. ^_^

 

I also like the sounds. Could it be that the ones in the video are slightly delayed? I had the feeling that the touchdown happened at "20", hence my thought. Excellent video again, thanks for your work, Michael.

Wow, that's really good. Do you guys know if the FLIR works in FSX too?

 

I think I can make room for the plane but I might add the RXP GPS in the background to allow for some proper flight plan handling and things. Should work, no? Wouldn't be the first time. ^_^

 

I also like the sounds. Could it be that the ones in the video are slightly delayed? I had the feeling that the touchdown happened at "20", hence my thought. Excellent video again, thanks for your work, Michael.

 

Thanks for the comment. I dont know if the FLIR FSX compatible i would say yes. Unfortunately i cant test it as i retired my FSX a year ago. AFAIK RXP GPS isnt working in P3D2.

 

Yeah the touchdown varies sometimes its 20´ and sometimes 10´. Im a HUGS pilot and i did the same as im doing normally. It might be a small bug.

 

Got a question to the Spartan drivers, i tried the approach mode. Few things i noticed as soon as i engage the APPR mode HDG and ALT mode becomes inactive. Furthermore the autopilot trys to capture the glideslope in a aggressive climb that leads to a stall instead of flying into and follow it while descending.

 

 

Furthermore the autopilot trys to capture the glideslope in a aggressive climb that leads to a stall instead of flying into and follow it while descending.

Might not help you on the actual issue but I saw this behaviour in quite some default based AP renditions. They follow it "up" first and pitch up quite rapidly and the only way to avoid this (and the corresponding speed loss) is to engage GS or APP at tad bit too late.

 

 

Here we go HUGS demonstration.

 

Very nice video.

 

Cheers, Rob.

Has anyone got the autopilot to work in approach mode? I noticed APR will not work if HDGi is on or ALT is on. No glidslope indication on the HSI either. I have yet to successfully complete one ILS landing using the autopilot. The Iris forum always shows an error, always. It is useless.