|
Post by captwotan on Oct 25, 2014 11:44:04 GMT -5
Trav,
While looking through the log i came across the following message, about 12 a second:
FCDU.GAU:: 12:20:32 ERROR: Unimplemented Avar: (A:AMBIENT TEMPERATURE,celsius)
Makes it difficult to read. Also a got a gear down speed penalty, again in the Q400, i dispute that.
|
|
|
Post by Travis on Oct 25, 2014 12:47:08 GMT -5
I can tell from that error you are using the FCDU.EXE (even though it lists .GAU). That's one Dutch has to tackle, since it's in a core communication area of the code. For the gear speed penalty, was this logged or was it just noted at the end of the flight? If it was logged, what was your altitude & speed? That's a little frustrating, since we're looking at an internal-to-MSFS value - (A:GEAR DAMAGE BY SPEED,bool). If you were flying at a speed that would have damaged your gear... but your Q400 gear was up... it could be that your simulator thought the gear was still down, since the Q400 doesn't use the normal gear signals. If that is the case, I think I could write a condition that checked the gear status if such a damage event were reported and ignore the report if I see the gear were retracted. I could also try to set the MSFS gear signal to the Q400 gear signal if I noticed they were out of sync. But I'd try the former first... simpler to react rather that act.
|
|
|
Post by captwotan on Oct 26, 2014 12:20:45 GMT -5
Hi Trav'
Indeed, using the external FCDU.
I can't say for sure if it was logged, the log is 1000's of lines long, because of the error message. I did do a search for gear within the log, but didn't find anything.
I don't generally lower gear until on the glideslope after flaps 5 which come down around 180.
|
|
|
Post by Travis on Oct 26, 2014 23:09:38 GMT -5
Ian,
That's noted....
|
|
|
Post by peter on Oct 27, 2014 3:51:15 GMT -5
I remember that I had this problem, too. Whenever I exceeded a speed of 260 Kts IAS, FSCaptain announced my gear was damaged, even though it was definitely retracted. I think I simply disabled the corresponding penalty in the options.cfg file. I guess another way would be to raise the damage speed in the Q400'a config file. I wasn't too worried about this because I virtually never forget to retract the gear.
Cheers, Peter
|
|
|
Post by Lucas on Oct 27, 2014 4:48:11 GMT -5
...can I join to the thread...? Friends, first flight PMDG 777 with 1.5.1 and I have 2 problems: 1. before flight, in Dispatch tab, the dispatcher randomly allocated 301 PAX (this is probably due that in Aircraft Characteristic there is „301” in Passengers Seats box) – however, in Load Maps, in Optional Overrides, I have „234” pax. But, when I login to ACARS, it showed 234 pax. Revising it didn’t help. So, why ACARS show 234 pax instead 301 and why I couldn’t correct it? 2. loading error that I hadn’t continue flight with FSCaptain This is the screen: After pressing NORMAL LOAD (then I also tried MANUAL LOAD), doors opened but loading didn’t begin. I have set Suppress Auto-Payload and Suppress Auto-Fuel load and I have set Simulate Load. Manual close and open doors again didn’t help. What is the reason, maybe I do something wrong? – however I did everything as always… Just in case, I attach set of CFG files from this flight. Lucas
|
|
|
Post by peter on Oct 27, 2014 6:04:49 GMT -5
Hi Lucas,
1. I just realized a few days ago that have that, too. I conjecture it is because of some conflicting information in PMDG's aircraft.cfg file (I had this with the PMDG J41 and manipulating that file solved it). I will look into this.
2. I had some issues like that a while ago but they went away. I think it has something to do with the fact that the standard door to open is door 2, but FSCaptain thinks it should be door 1. I will have a look at this as well.
Cheers, Peter
|
|
|
Post by Lucas on Oct 27, 2014 6:42:19 GMT -5
Thanks Peter. Ad 2. I manually opened all four doors in 777 - but it also didn't help...
|
|
|
Post by Travis on Oct 27, 2014 9:45:58 GMT -5
I remember that I had this problem, too. Whenever I exceeded a speed of 260 Kts IAS, FSCaptain announced my gear was damaged, even though it was definitely retracted. I think I simply disabled the corresponding penalty in the options.cfg file. I guess another way would be to raise the damage speed in the Q400'a config file. I wasn't too worried about this because I virtually never forget to retract the gear. Q400 Captains, I'm not able to make a flight over the next few days, so if you can make a test or two for us it can help me decide which fix to attempt. What I'd like for someone to do is to set up a normal revenue flight in the Q400, take off, retract your airplane's gear and then press the "G" key (or whatever key you have mapped to be the key to tell FSX/P3D that you've retracted its gear.) Notice if anything changes in regards to your how your aircraft performs or handles. (Also notice if your Q400's gear extends... I'm hoping it won't!) Assuming your gear stays retracted, level off and push your airspeed over 260 - try to reach Vmax if you can. Pause your flight and check your FCDU log and see if Gear Damage was logged. I'm hoping that it would not be logged and your aircraft would otherwise handle normally. If everything is looking okay, as a final check I'd like for you to resume your flight and then press the "G" key again. I'm hoping that it will not cause your aircraft's gear to extend, but to simply tell your simulator to extend the "default gear." If all is going according to plan, if you refresh your FCDU log, you should now see a gear damaged penalty at the speed you're currently flying. If this test fails - if you still get a gear damaged penalty after pressing the "G" key once, or if the aircraft handles oddly after that first press - I'll have to make a global change. If this test goes according to my hopes, I can make a change in the Q400 interface that would only be executed when the gear lever changes. And if you'd rather not run this test, I will be able to do so perhaps on Wednesday. Thanks!
|
|
|
Post by Travis on Oct 27, 2014 10:13:32 GMT -5
Thanks Peter. Ad 2. I manually opened all four doors in 777 - but it also didn't help... Lucas, FSCaptain looks for an MSFS door to be opened (technically it looks at (A:CANOPY OPEN,percent over 100)) - did you open doors with a PMDG control or with good old "Shift E"? If you used a PMDG control to open your doors, could I ask you to please next time try pressing Shift E and noting any good (or bad) results? Thanks,
|
|
|
Post by captwotan on Oct 27, 2014 13:36:15 GMT -5
I don't mind running the test Trav, but i am a little annoyed at all the unfair penalties, is it possible to remove these, outside the point system?
|
|
|
Post by Travis on Oct 27, 2014 13:59:27 GMT -5
I don't mind running the test Trav, but i am a little annoyed at all the unfair penalties, is it possible to remove these, outside the point system? Ian, When Dutch returns, I'll ask him what needs to be done to modify the logs and if it's possible to do such, one of us would write a small EXE that would look for any Q400 flights conducted before "date x" and remove any such penalties. You could ZIP and email us your logs and we'll modify them, or we may post the EXE in the file sharing area and allow users to adjust their own logs. I am curious about one other thing - did these penalties begin with the last Beta build, or can you pinpoint when they started to occur? For any such test flight, you wouldn't need to finish it or worry about anything else that's outside the envelope of the test... just make a pax flight with one pax (to cut down on the load time), start on the runway (we'll give you Official Aviation Authority clearance to do such ), load, takeoff, do the gear bits, level off, accelerate, check your log, and then do the keyboard gear bit again. Don't worry about signaling for takeoff or your lights or anything else. Once you have the data, you can stop the flight and erase it from your log. However an exciting development (and one which must be kept secret for a while) has forced me to change my RW plans and I will be able to make a test flight myself later in my evening.
|
|
|
Post by captwotan on Oct 27, 2014 14:01:58 GMT -5
Trav, I have run the test, when pressing the 'g' key, originally i didn't have anything attached to this function within FSX. The landing gear extends at all times, why wouldn't it though??? I don't understand what you were expecting to see at that point. Would you like to see the log? Curiously, the log indicates that the passengers were unhappy with my landing? Not sure how, i didn't land? Interestingly, i did have a hard landing in the previous flight, logged within the FCDU, but not present within the Administrator? A fault code is present, not sure what that fault code is 702??? No indication of gear damage at any point.
|
|
|
Post by Lucas on Oct 27, 2014 14:09:49 GMT -5
Yes, I opened doors via PMDG FCDU and didn't check shift+E. No problemo - I'll do the test... ...but I'm courious what is the reason of that? I have never had this issue before Travis, what do you think about my 1st issue described above?
|
|
|
Post by Travis on Oct 27, 2014 14:17:45 GMT -5
Ian,
First, thanks for testing.
Yes, please ZIP and email me your recent logs. I'm the curious type.
The Q400 is the only MSFS aircraft that I know of which does not use the normal landing gear value within the simulator. (I don't know everything, so there may be others... it's that this a/c is the only one I know of.)
So my theory is that when you raise the Q400's gear, your simulator may not know that your gear has been raised. So when you exceed the gear damage speed, your simulator may be setting the (A:GEAR DAMAGE BY SPEED,bool) flag, and that's what FSCaptain is looking at to give you a penalty.
So I see two possible solutions - either use the Q400 interface to keep the MSFS gear setting in sync with the Q400 setting, or to check if the gear is actually down when we spot the (A:GEAR DAMAGE BY SPEED,bool) has been set.
I'd prefer to take the former solution if it works. That's what this test scenario should prove or disprove.
|
|