|
Post by Svilen Vassilev on Feb 12, 2013 9:38:53 GMT -5
Hey, Terry! I don't have the Wilco Airbus, but here's a suggestion (guesswork) that tends to fix similar issues with other planes: try putting the FDR gauge reference in the 2D window which is used for the ACARS, instead of the Virtual Cockpit window. Regarding the transition altitude, there's no way to change FSX default ATC behaviour. Some 3rd party ATC engines support realistic transition altitudes/levels, but I guess the easiest solution for the time being would be to disable the altimeter penalty in FSCaptain: open the Options.cfg file in your FSCaptain/Config folder and change the line: DISABLESTD=0 to DISABLESTD=1 May be Dutch or Travis will chime in with better suggestions, but there's something to try in the meantime
|
|
|
Post by Dutch Owen on Feb 14, 2013 12:07:58 GMT -5
Dutch and Travis have been a bit under the weather but are seemingly recovering now. The timing is odd since we live 2,000 miles apart.
We'll test this but for now I'd suggest following the disable procedure above.
Dutch
|
|
|
Post by J R C on Apr 8, 2014 18:19:45 GMT -5
this probably has been answered already, but I noticed that people were getting really in depth with the responses to this post, but I realize that it tells you on me ACARS to start your engines as the packs are loading, but they will stop once your engine starts. If you shut down your engines, they will start loading again. is that a flaw in the acars?
|
|
|
Post by jimpadgett on Apr 9, 2014 3:09:53 GMT -5
I don't remember seeing the start engines info until after loading is complete.... ??
|
|
|
Post by J R C on Apr 13, 2014 5:50:59 GMT -5
I realized that it was telling me to power up the avionics not the engines..my bad. Any know why it wont let me resume pax service after stopping it? It just repeats the FO making the FAs stop it
|
|
|
Post by Harry on Oct 30, 2014 21:50:05 GMT -5
I am sure that this issue has been solved, but I can't find how to do it. I recently downloaded an airplane (MD-80) and not only passengers won't load but FSCaptain does not work properly (FO voice is not there, the music doesn't start either, there is a signficant delay when communicating with ground services when I start pushing back the airplane and the ACARS stucks and stops working after that). I am using Windows 8 and FSX. If somebody can help me, great! Otherwise I can still go on using the default airplanes that work ok (even though I wanted to change a little bit). Rgds.
|
|
|
Post by Travis on Oct 31, 2014 13:43:19 GMT -5
Harry,
ZIP and email your \FSCaptain\Data\Logs\ folder to Dutch & me. I'll take a look at what's going on with your new a/c.
Regards,
|
|
|
Post by Harry on Nov 1, 2014 12:58:33 GMT -5
Thanks! I just did it. Rgds,
|
|
|
Post by Harry on Nov 6, 2014 10:04:08 GMT -5
Travis, did you have any chance to take a look to the files I sent you? No rush, I´m just checking if you received them alright.
|
|
|
Post by Travis on Nov 6, 2014 11:04:07 GMT -5
Harry, I did. I see that you're still on 1.5.0 which is okay, but I am trying to wrap up work on 1.5.1 Beta 4 which will log many more events in a flight's lifecycle... hopefully enough to let us spot problem areas in more depth as they appear. I hope we can get this Beta release out by the upcoming weekend. Until then stay on 1.5.0, and if you're only having the loading problem with your new MD aircraft, could you please ZIP and email us the panel.cfg file and the aircraft.cfg file from the aircraft's \SimObjects\Airplanes\ folder?? I'm thinking there may be another reason. Until then, could you try a simple "ferry flight" with that aircraft, and see if everything else works fine? Does it detect you've taken off & landed, etc.? A test flight doesn't have to be far... one of my favorite "test flight routes" is to takeoff from KSJC on one of the 29s, climb to around 3000 feet while flying the runway heading, and then intercept the ILS 28R signal from KSFO. Such a flight may take all of 20 minutes if you start on the runway. Another favorite route (one that has less VAS usage), is to take off from KMER 31, climb to 2000 while flying the runway heading until you intercept ILS 28R at KMOD. That's only a 5900ft runway, so be advised. ILS 29R at KSCK (which is just a few miles further north on highway 99) is 10K if you need the stopping length.
|
|
|
Post by Harry on Nov 8, 2014 23:22:55 GMT -5
Great! I am sending you te files by email. Also I'll try a ferry flight and let you know if it works ok. Thanks!
|
|
|
Post by Harry on Nov 9, 2014 22:21:11 GMT -5
The ferry flight showed the same problems that I mentioned above: it stucks when it tries to update flight status after taxiing. I've just sent you the files you requested by email. Thanks again!
|
|
|
Post by Travis on Nov 10, 2014 13:47:13 GMT -5
Harry, Thank you for the files... at least I think that I should thank you... it refuses to load PAX for me too, and I am annoyed to figure out why it is not happening. But this is actually a good thing because now after years of user complaints we have something to work against. I'm busy with real world stuff today and tomorrow, but this is now something that I hope I can work on... I will confer with Dutch later this week as my super-duper logging is showing me that the loading process simply stops soon after it starts. I will take this to email with you very soon....
|
|
|
Post by Travis on Nov 10, 2014 14:32:45 GMT -5
"Heavens to Murgatroyd!"
In answering the F1 DC-9 topic, I had a brainstorm (or brain#@^!) and with a small change to my panel.cfg, I just loaded this aircraft.
Harry, could you try moving your FDR gauge to your ACARS gauge window - like so:
[Window03] size_mm=191,445 position=8 visible=0 ident=24477 gauge00=FCDU!ACARS,1,1,191,445 gauge01=FCDU!FDR,1,1,1,1
|
|
|
Post by Harry on Nov 12, 2014 9:32:50 GMT -5
Travis, you are a wizard! That change in the panel.cfg file actually did the trick. The only thing I noticed is that when I landed the aircraft the "80 kts" announcement by the FO was made after a while (when I was leaving the runway). Just a tiny detail, not even a problem, but I thought that you should know about it. Thanks for everything!
|
|