Fly the Maddog landinglights

Please report Bugs and Problems here

Moderator: FSAirlines Staff

Locked
Kirk
Ticket Agent
Posts: 15
Joined: Mon Nov 26, 2007 9:47 am

Fly the Maddog landinglights

Post by Kirk » Wed Dec 05, 2007 2:20 pm

Hi folk, I really like flying the MD82 from Flythe maddog, the only problem I have, is that when I tourn off the Landing Lights on my aircraft, FlyNet client doesn't recognize it, and I have a penalty over FL100, is there anyway to fix it?

Thanks a lot.

Adrián.
Image
Image
AEROTRANS, FLYING HIGH FLYING FUN

sarrisk

Post by sarrisk » Wed Dec 12, 2007 1:39 pm

Hi
i have the same problem with maddog landing lights. I tried to use ctrl+L but nothing happens... This problem seems to be active only in new version of client. I didnt have the problem with the old client.

Any ideas ?

Kirk
Ticket Agent
Posts: 15
Joined: Mon Nov 26, 2007 9:47 am

Post by Kirk » Mon Jan 21, 2008 11:58 am

Still no ideas? :shock:
Image
Image
AEROTRANS, FLYING HIGH FLYING FUN

User avatar
flightsimer
Chief Pilot
Posts: 1815
Joined: Tue Oct 09, 2007 3:35 am

Post by flightsimer » Mon Jan 21, 2008 6:39 pm

does ur lights on that work wierd? mine i have to hit the lights button like 4 times to get all of my light on/off...
Owner/CEO
North Eastern Airways

Image
Image

Kirk
Ticket Agent
Posts: 15
Joined: Mon Nov 26, 2007 9:47 am

Post by Kirk » Thu Jan 24, 2008 12:06 am

Nope, four times five times... still Ldglights on for the fllynet :(
Image
Image
AEROTRANS, FLYING HIGH FLYING FUN

User avatar
Quantum
FSAirlines DB Admin
Posts: 1439
Joined: Sat Apr 29, 2006 8:23 pm
Location: UK

Post by Quantum » Thu Jan 24, 2008 2:59 pm

Hi,

I am not familiar with the Maddog but some aircraft do have problems where landing light changes are not recognised by the client immediately, particularly if there is a seperate switch for landing light retract/extend. You should be able to get the client to recognise the landing lights if you make sure you have a key assigned to lights - default = L. When you change the lights, wait a few seconds then pause your game, minimise flightsim and check the client window to see if it recognises your landing light position 1 = on, 0 = off. If its showing the wrong position, go back to your cockpit and try again. I am sure you will get the client to recognise it at some point. As long as you are aware of the problem you can double check. I have a dual monitor setup in FS9 and have FSNav on second monitor with the client on the same monitor. Hiding FSNav shows me the client so I can check without pausing/minimising the sim. On the AW Argosy there is a separate retract switch as well as one for the light itself. Somehow the coding gets the client confused so you have to cycle the switches and use keystroke L to get things back in snyc.

Regards

John
CEO - Classic British Flight Services
Classic aircraft on Classic routes
ImageImage

User avatar
flightsimer
Chief Pilot
Posts: 1815
Joined: Tue Oct 09, 2007 3:35 am

Post by flightsimer » Thu Jan 24, 2008 8:04 pm

quantum, its a problem with the plane... to turn off/on the lights by hitting l about 5 times. and once you hit it once only a certain light will turn off then hit it again, 3 lights turn off but one diff. one comes on... its just really wierd how they have it set up??? and i have a button on my joystick assigned just for landing lights, but even sing that doesnt work... so i just switched back to another easier model to fly...
Owner/CEO
North Eastern Airways

Image
Image

gpap316

Fly the Maddog landinglights

Post by gpap316 » Thu Jan 24, 2008 9:53 pm

I have the same problem with the MADDOG and I have notice that the landing lights appear to be ''on'' for the flynet client, the moment that the aircraft is powered up. If you check the client with the plane in ''cold and dark'' condition, then the landing lights appear to be ''off''. And it does'n matter if you power up the plane with APU GEN or external power. I hope this may help anyone to find a solution.

vknierim

Post by vknierim » Fri Jan 25, 2008 9:25 pm

Hi folks,

this is not directly related to the maddog, but I know that the PSS A330/340's have a similar problem. The reason for that is that there is a 'bug' (or better call it a 'fault') in the coding, which causes addon programs (such as the flynet client or FS Passengers) not to recognise the state of landing lights correctly.
I think for the PSS aircraft the light goes 'off' as soon as the gear is retracted, although the switch is still on...

Has any of you guys that have the problem tried FS Passengers and sees the same problem there? If so, my assumption is that the fault lies with the plane, not the client.

Greetings

Volker

P.S.: Unfortunatly, for the PSS Airbus there is no fix for this problem. :(

gpap316

Post by gpap316 » Fri Jan 25, 2008 10:57 pm

Yes mate,
I had fspassengers running and it detected the same problem. I received the message "check landing lights off" from fspassengers copilot.
I have also noticed that in the Aircraft.cfg file of the MADDOG2006 in the field [LIGHTS] there is not an assignment for the landing lights, though there is such assignment for all the other aircrafts i use. So i am convienced that the problem is there, but i don't know how to fix it. Any ideas ???

Miikoyan
Chief Pilot
Posts: 831
Joined: Mon Feb 12, 2007 5:33 am
Location: Canada
Contact:

Post by Miikoyan » Sat Jan 26, 2008 2:47 am

If you paste the contents of the MADDOG aircraft.cfg file and any fs default aircraft.cfg file then I will help you.
GoUS Executive Chairman
World Alliance Board of Directors
Image
Image

gpap316

Post by gpap316 » Sat Jan 26, 2008 6:44 pm

I have never use FS default aircraft with FLYNET but i send you the specific fields of add-on aircarfts so you can see the difference


MADDOG2006
[LIGHTS]
//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing
light.0 =3, -17.467, -53.796, -0.085, fx_navred,
light.1 =3, -21.224, -54.163, -0.174, fx_navwhi,
light.3 =2, -18.179, -54.209, -0.085, maddog_strobe,
light.4 =2, -21.207, -54.619, -0.174, maddog_strobe,
light.5 =3, -17.467, 53.796, -0.085, fx_navgre,
light.7 =3, -21.224, 54.163, -0.174, fx_navwhi,
light.8 =2, -18.179, 54.209, -0.085, maddog_strobe,
light.9 =2, -21.207, 54.619, -0.174, maddog_strobe,
light.10 =1, 0.000, 0.000, -4.665, fx_beacon,
light.11 =1, 4.797, 0.000, 8.353, fx_beacon,
light.12 =4, 64.324, -1.683, 5.882, fx_vclight,
light.13 =4, 64.324, 1.683, 5.882, fx_vclight,


ATR72-500
[lights]
//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing
light.0=3, -3.60, -43.00, 5.90, fx_navred_F1ATR
light.1=3, -3.60, 43.00, 5.90, fx_navgre_F1ATR
light.2=2, -3.28, -42.85, 6.00, fx_strobe_F1ATR
light.3=2, -3.28, 42.85, 6.00, fx_strobe_F1ATR
light.4=2, -51.95, 0.02, 3.05, fx_strobe_F1ATR
light.5=3, -51.95, -0.25, 3.42, fx_navwhi_F1ATR
light.6=1, -49.56, 0.00, 18.40, fx_beacon_F1ATR
light.7=1, -2.15, 0.00, -5.54, fx_beaconsm_F1ATR
light.8=4, 27.60, -1.80, 3.50, fx_vclight_f1atr
light.9=4, 27.60, 1.80, 3.50, fx_vclight_f1atr
light.10=5, 4.35, 2.75, -4.20, fx_landing_F1ATR
light.11=5, 4.35, -2.75, -4.20, fx_landing_F1ATR

Matt_Matt

Post by Matt_Matt » Sun Jan 27, 2008 11:39 am

The problem is not in the aircraft.cfg, because I use the 737-200 of TinMouse and it doesn't have lights of "landing" in the .cfg. I have test all the lights in the maddog and sitll have the problem, but if i cut the electrical power, i see that the landings are off. I really don't know what the client see to defines that the lights are on, if we know that, maeby we can find a solution to this problem with the maddog.

Locked