|
Post by captwotan on Oct 27, 2014 14:28:21 GMT -5
I have sent the logs as requested.
The 'G' key, i set within FSX (was blank previously) retracted and lowered the gear as expected. So did my joystick mapping.
I am very interested in why my passengers where complaining about a hard landing when i hadn't landed in the test flight. It's like the penalties are being applied retrospectively, or in the next flight.
|
|
|
Post by Travis on Oct 27, 2014 14:40:54 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 I'm unsure. Have you flown the PMDG777 with FSCaptain before without a door problem?? Did this start with the 1.5.1 Beta 3 build??
I'd like to wait for Peter's assessment of this. As he wrote, he reported a similar issue with the JS41 a few weeks ago, and quickly was able to correct it with a simple edit. I like to have at least three bits of confirming data before I commit to a course of action for something I'm clueless about. (That's entirely related to a quote from the novel/movie villain Auric Goldfinger: "Once is happenstance. Twice is coincidence. Three times it's enemy action.")
|
|
|
Post by Lucas on Oct 27, 2014 15:07:59 GMT -5
Beta 3?! Hmm, I missed it. This issue appeared on Beta2. And Yes, I have flown many times PMDG777, since I bought FSCaptain
|
|
|
Post by peter on Oct 27, 2014 17:32:18 GMT -5
Hi Lucas, several things: 1) Check you messages 2) Loading the 777 seems to work fine after I've done the following: - go to FSX\Simobjects\Airplanes\PMDG777-200LR - open the aircraft.cfg file in this folder - change _all_ instances of atc_model=... to atc_model=B77L That solved all issues for me. Let us know if that worked for you as well. Cheers, Peter
|
|
|
Post by Travis on Oct 28, 2014 13:30:55 GMT -5
I have sent the logs as requested. The 'G' key, i set within FSX (was blank previously) retracted and lowered the gear as expected. So did my joystick mapping. I am very interested in why my passengers where complaining about a hard landing when i hadn't landed in the test flight. It's like the penalties are being applied retrospectively, or in the next flight. I have the logs and I have an idea or two about what's going on, but I need to have Dutch cross check me.
The "hard landing" signs are my biggest clue. They shouldn't appear until after you've landed obviously, so the fact that they did certainly means something important.
And it appears that I'll have to make a global workaround for the phantom gear problem. Yes, it's likely another external flight model gremlin that we'll deal with.
|
|
|
Post by Travis on Oct 28, 2014 13:36:04 GMT -5
- change _all_ instances of atc_model=... to atc_model=B77L That solved all issues for me. Let us know if that worked for you as well. I really don't like having to change the aircraft.cfg file... when there's a new version, the developer will likely change things back to what they want, and suddenly you'll have a mysterious new bug. What was the atc_model value in your PMDG 777? That B77L.cfg file in the \Aircraft\ folder was one that I created for my CS-777. I can put 301 sardines in mine. I'd suggest you change your aircraft.cfg back to what it was originally, make a "TYPE".cfg file to place in the \Aircraft\ folder, and if you need specific Override cfg files for different models, make those based on the \SimObjects\Aircraft\ folder name(s).
|
|
|
Post by peter on Oct 28, 2014 13:56:45 GMT -5
Hi Trav,
the problem is that PMDG planes sometimes come with an inconsistent aircraft.cfg file. The [General] section contains a different value for atc_model than the individual livery sections. When I played with the new economic model, this was a major obstacle for FSCaptain to recognize a plane. Without the economic model the plane would show up in the dispatcher, but the FSCaptain cfg file can be inconsistent.
So the only proper solution would be to have a very close look at how exactly FSCaptain picks the config file for a plane and make sure that it doesn't get confused by the mess that other developers create in their aircraft.cfg files. For the moment, editing the file seems to be the only solution to me. I agree that it is not a great solution.
Cheers, Peter
|
|
|
Post by Travis on Oct 28, 2014 15:01:25 GMT -5
Lucas,
I'll defer to Peter on this, so please make a backup of your original PMDG aircraft.cfg file and follow his instructions for now. Although you may want to invest in making an Override file for your PMDG aircraft that doesn't have the 301 PAX listed.
|
|
|
Post by Lucas on Oct 28, 2014 15:43:05 GMT -5
So, I installed BETA 3... for now (without doing anything, besides installing beta3) pax loading works, however still have max 234 instead 301, so I'm going to check peter's solution...
...ok peter - your solution doesn't work for me. I change all atc_model values to "B77L" but still have max 234 pax. To be more precisely: - just after LOGIN there are number of flight and both ICAO airports codes - after PROCEED, there are payload weight and 301 pax (looks good) - and after press EXEC (and flight page appeares) I see only 234 pax (and there is no possibility to REVISE it)
One more - please tell me guys, what for the OPTIONAL OVERRIDES [in Load Maps tab] options are? I have 234 pax in it - maybe this is the reason?
|
|
|
Post by Travis on Oct 28, 2014 16:17:15 GMT -5
One more - please tell me guys, what for the OPTIONAL OVERRIDES [in Load Maps tab] options are? I have 234 pax in it - maybe this is the reason? Lucas, Can you email me two things, and then answer me a question? 1. A screenshot that shows the Windows Explorer names of the PMDG 777 folders in "\SimObjects\Airplanes\" 2. Any / All of your PMDG 777 load map files? (If you have one or a dozen, send them all! ) Q: How many PAX do you want to be the maximum in your PMDG 777? Is it 301 or 234, or something else?
|
|
|
Post by Lucas on Oct 28, 2014 16:39:18 GMT -5
Hi Travis, 1. sent 2. sent (only four ) Q. I want 301 because it would be more realistic then in PMDG . I know that PMDG programmed 777 that only takes 234, but I have Suppress Auto-Payload set, so I operate only by weights. For example: FSCaptain generate randomly 301 pax, I add 40000lbs more cargo, so final payload is about 105000 lbs - and this is ok. Then, in PMDG FCDU I set just 449000 lbs ZFW (105000 + 344000 empty weight) and that's it. By the way, I edited my previous post (peter's method doesn't work for me) And one more thing which interested me, look: When I manually enter amount of pax above 234 (here 301), there is this error, although in characteristic there is 301.
|
|
|
Post by Travis on Oct 28, 2014 17:55:00 GMT -5
Ah Lucas my friend... I just received your email and in reading your last message you are doing something that we had never intended to support.... But I will see if we can accommodate. I will need to run some tests tonight to see if it's possible.
If I am correct, you want the aircraft to load one thing, while FSCaptain thinks you are loading another. If I can arrange to have the "totals" both come out to be the same, we may be able to work something out.... I will respond to you in email later either very late in my evening or very late in my morning - we may be "trading load maps" for a while.
The reason is, I will need a few hours offline starting very soon. My wife's beloved San Francisco Giants are going for their third Major League Baseball Championship in the last five years tonight (and again tomorrow night, if they do not win tonight.)
So with the wife in control, I must consider tonight as an ATC declaration of "ALL AIRPORTS CLOSED"
|
|
|
Post by peter on Oct 28, 2014 18:42:06 GMT -5
So, I installed BETA 3... for now (without doing anything, besides installing beta3) pax loading works, however still have max 234 instead 301, so I'm going to check peter's solution... ...ok peter - your solution doesn't work for me. I change all atc_model values to "B77L" but still have max 234 pax. To be more precisely: - just after LOGIN there are number of flight and both ICAO airports codes - after PROCEED, there are payload weight and 301 pax (looks good) - and after press EXEC (and flight page appeares) I see only 234 pax (and there is no possibility to REVISE it) One more - please tell me guys, what for the OPTIONAL OVERRIDES [in Load Maps tab] options are? I have 234 pax in it - maybe this is the reason? OK, when you open the FCDU and go off-line, what does it say? Inparticular, the pax number and the cfg ID (e.g., B77L, or PMDG 777-200LR). Similarly, what does it say when you log in? I presume you have a B77L.cfg file. If you send it to me I can check it out. Cheers, Peter
|
|
|
Post by Travis on Oct 29, 2014 18:06:48 GMT -5
I have sent the logs as requested. The 'G' key, i set within FSX (was blank previously) retracted and lowered the gear as expected. So did my joystick mapping. I am very interested in why my passengers where complaining about a hard landing when i hadn't landed in the test flight. It's like the penalties are being applied retrospectively, or in the next flight. I have the logs and I have an idea or two about what's going on, but I need to have Dutch cross check me.
The "hard landing" signs are my biggest clue. They shouldn't appear until after you've landed obviously, so the fact that they did certainly means something important.
And it appears that I'll have to make a global workaround for the phantom gear problem. Yes, it's likely another external flight model gremlin that we'll deal with.
I just made a short test flight with my early build of Beta4, and no gear penalties were applied. That's a good sign. I believe the multiple "Landed too hard" entries in the logs are a result of my attempt to "log everything," which has become in this instance "log too much!" It's currently still writing this out for me, but now that I've had a few new views of things, I think I can apply a new conditional check that would stop this from being written unnecessarily. The errant logging doesn't affect your scores, so for now... just ignore them.
|
|
|
Post by peter on Oct 29, 2014 18:10:41 GMT -5
Lucas,
one more question: in your coptions.cfg file, what is the value of NODETAILLOAD ?
|
|