|
Post by tomkrist on May 13, 2010 4:35:17 GMT -5
Everytime in my flight i get a error because my light was not set correclty.However, with my 737-800 and other planes i always set it correctly off/on at 10000 foot, but i still get this error. I also very often get a error that the high altitude standard was not set, though i always press b after climbing 18000. What i am doing wrong here?
|
|
|
Post by Dutch Owen on May 14, 2010 8:14:45 GMT -5
The most often cause of this problem is that the light switch you are using isn't actually toggling the landing lights signal. As an experiment, try using the keyboard shortcut CTRL-L to toggle on and off the landing lights.
Let me know if that reveals anything, Dutch
|
|
|
Post by darcyc on May 21, 2010 14:33:21 GMT -5
I get the same light error also. I have tried Ctrl L but nothing seems to work. It always tells me I do not have Nav lights on.
Darcy
|
|
blue
Trainee
Posts: 39
|
Post by blue on May 22, 2010 11:07:25 GMT -5
Hi,
Yes me too with fokker of digital aviation....
Christian
|
|
|
Post by Dutch Owen on May 23, 2010 8:33:16 GMT -5
You can disable the light penalty on the airline definition tab of the administrator.
Does this happen with all airplanes?
I wish I knew why this doesn't work for some people but does for most.
FSCaptain is just using the signals it gets from FS9/FSX to determine whether the lights are on or not, and the altitude from FS. It's really quite simple.
Dutch
|
|
|
Post by crashcontinental on May 23, 2010 9:24:29 GMT -5
My issues with things like lights, speed calls and the like is that if you're flying - like I do - in the miniscreen or no mainpanel mode (by hitting the 'w' key) the FCOM gauge does not immediately pick up on things. Often, when I've hit my TOGA button on the runway for take off power, I'll move to the minipanel screen for improved viewpoint. After I rotate, verify positive rate and retract the gear, I'll quickly flip back to the mainpanel to visually it over. FSCaptain usually gives you the '80 knots' call at this point.
I've noticed this too with my "lights penalty". Also, if you have changed some of your announcements to mirror the length of real world ones, like I have, and they have become longer, they'll often run over the events like climbing through 10k. The co-pilot call for check landing lights has to wait for the announcement to finish before executing (too many soundfiles?)
- daniel
|
|
|
Post by darcyc on May 23, 2010 10:56:24 GMT -5
My warning happens every time I pushback. I have disabled it but it the warnings under Flight concerns stays there. Overall I love using this product, just trying to help make it better.
Darcy
|
|
|
Post by darcyc on May 23, 2010 10:57:11 GMT -5
Sorry forgot to say that it is with the default 737.
Darcy
|
|
|
Post by Dutch Owen on May 27, 2010 14:30:12 GMT -5
There's apparantly come communications issues with the FS signals getting to the FCOM promptly. Which is weird, and I'm not sure what I can do about it.
Requires investigation...I personally haven't experienced these kinds of problems which makes it frustrating to try and fix.
Dutch
|
|
|
Post by capp on May 27, 2010 23:16:22 GMT -5
About signals getting to FCOM promptly.
I had some issues lately where announcements come in really late, like pressing the welcome announcement in the F4-menu and it started to play like 3 minutes later. At the same time I had some issues with FSX freezing under 64bit Windows 7 for 10 minutes before resuming now and then. Trying around a lot I recently updated to the newest FSUIPC version (IVAP from IVAO installs a quite old one) and the freezing problem was gone. Surprisingly the announcements now come in as fast as they should. No idea if this is related to this in any way.
|
|
|
Post by Dutch Owen on Jun 3, 2010 13:58:36 GMT -5
It sounds like maybe the older version of FSUIPC was interfering with SimConnect somehow. Glad it's fixed and thanks for the good info.
Which version was the problem related to? Other may have the same difficulty and want to know.
Dutch
|
|
|
Post by capp on Jun 4, 2010 2:54:34 GMT -5
Was the one provided with IVAOs "Squawkbox"-application IVAP. Like v4.2 or something.
|
|
blue
Trainee
Posts: 39
|
Post by blue on Jun 5, 2010 8:58:23 GMT -5
Hi, How to desactivate "lights set not proprely" because with some planes I have problem with this penality always -5 . I look into the options config but I don't see this option fo landing lights. Thank you Christian
|
|
|
Post by kelvyn on Jun 7, 2010 6:51:16 GMT -5
blue,
In FSCaptain Administrator go into the "Airline Definitions" tab and load the "Airline" you signed up with and you'll see that on the left side towards the middle... a checkbox next to "Landing Lights on < 10,000 ft?", this is where you can disable "Landing Lights" requirements.
|
|
blue
Trainee
Posts: 39
|
Post by blue on Jun 7, 2010 18:56:50 GMT -5
Thank you Kelvyn...
|
|