|
|
Post by philabos on Oct 30, 2012 17:02:43 GMT -5
I have followed the tutorial for 1.4 and flight appears, fuel loads ok but pax never load. I have updated the airport data base.
I am running a new airline and different a/c but all seems to work short of pax ldg.
Any help appreciated.
|
|
|
|
Post by Dutch Owen on Oct 30, 2012 17:17:01 GMT -5
There are lots of possibilities and lots of questions, but let's start with the obvious.
Is the door open? You won't get clearance to load without the main door being open, but we've seen cases where it gets closed after cleared to load status is issued. PAX can't load though a closed door so things just kind of sit there.
If the door is open but the count isn't being updated we call that an "auto-load hang". It sometimes is a rare occurrence and the way out is to use the INTERRUPT function to jog it. You can sometimes then RESUME the load and it'll get going again, or you can STOP the load and go straight to the reconciliation page where you can tell the loader to load what's on the manifest right now and get on with it. (This kind of warps all the PAX into their seats, it's not a permanent solution since it's not realistic, but it will get you to where you can carry on with the flight.)
If the hang is consistent, the question becomes what airplane is this happening with, and does it happen only with that airplane, or with all of them? When we know that we can go ahead with figuring out what the problem with the auto-loader is.
Dutch
|
|
|
|
Post by Guest on Oct 31, 2012 12:33:29 GMT -5
Hi!
I'm having the exact same problem and usually end up using the reconciliation page. Then I have a problem with the FCDU not recognising the different stages of flight. I will have taking off and yet the FCDU will still say Taxi for Departure.
|
|
|
|
Post by Dutch Owen on Oct 31, 2012 13:56:06 GMT -5
For anyone having problems with the auto-loader, please let me know what version of MSFS you are on (FS9, FSX SP1, SP2, etc) and what version of Windows you are using. And whether or not you have a registered version of FSUIPC and what version that is.
Also, very important, does it happen on all airplanes or only certain ones? And if on certain ones, does that airplane simulation have it's own loading process (sometimes an airplane's loading system will flight with FSCaptain for control.)
As an experiment, install the FCDU/FCOM on one of the default airplanes and see if that load will have problems or not. In doing this we're isolating the issue: is it an airplane or is the whole whole system?
Does the Reconciliation page load the payload correctly if you select "MANIFEST" as the correct option? This isolates the auto-load process, or the mechanism by which the loading is done in Flight Sim.
Dutch
|
|
|
|
Post by Dutch Owen on Oct 31, 2012 13:57:58 GMT -5
Also, the devices take a short while to switch from taxi to flight mode, to be sure you aren't just bouncing along the runway. Does it eventually switch to Climb? And about how long is that taking?
Dutch'
|
|
|
|
Post by philabos on Nov 1, 2012 9:15:35 GMT -5
Have been fighting this for several days now.
Tried changing airlines to one of those included in the program with no better result. Did manual load, which seemed to work, but then pushback command drove the plane forward through the terminal, out the other side, for 100 yds before I quit.
Based on latest advice switched to MS default a/c and the auto load DID work.
I have not tried the pushback feature in that plane yet.
The program would not work with the 737-8 a/c and panel as described above.
Am I understanding the take away is that you have to use MS default panels? or aircraft? or both? for auto load to work?
FSUIPC 4.8.5.3 (latest) in FSX.
|
|
|
|
Post by philabos on Nov 1, 2012 9:16:49 GMT -5
Failed to mention using Windows 7.
|
|
|
|
Post by Travis on Nov 1, 2012 13:50:28 GMT -5
First... the pushback that the Communicator calls is the generic FSX pushback. If it's moving an aircraft forwards, that's likely due to the way it sees the parking/taxi structure where you happen to be starting. You could always check by using the standard keypress to start/stop pushback (CRTL+P IIRC.)
As to autoloading....
Default a/c are not a requirement for autoload - the suggestion to try autoload with one of the defaults just confirms (or not) that autoloading is or isn't working on a particular system. Another possibility is that there could be a configuration issue that would have to do with the "load maps" for some aircraft. ("Load maps" are a detailed and specific method by which loading can be customized for specifc aircraft in your hanger.)
What 737/8 is failing for you? PMDG? iFly? Another devleoper I didn't mention?
Autoloading our 737s works for Dutch ane me - Dutch has the PMDG and I have the iFly (I haven't updated to their latest SP yet though). FSCaptain ships with PMDG loadmaps... I don't recall if it does with an iFly loadmap. (I have an iFly737-800 loadmap, but I don't know if it's in the release-to-build gallery.)
|
|
|
|
Post by philabos on Nov 1, 2012 16:43:27 GMT -5
Looks like the default MS 737-8 panel.
Also tried with FCOM - same negative result.
|
|
|
|
Post by Travis on Nov 2, 2012 9:45:42 GMT -5
Hmmm, you can get default a/c to autoload, but not the default 737-800? We may need to look at several files... could you begin by emailing us your default 737-800's aircraft.cfg and panel.cfg files? We may follow up with a request for other FS Captain files. This thread has our less-than-amazingly-cleverly-protected email addresses. |
|
|
|
Post by tamsini on Nov 2, 2012 18:00:43 GMT -5
I posted on another forum but in case this helps, I'll post here as well. The load PAX problem is only on JustFlight's 146-200, running on FSX and Win 7. Shift+E does not work with this aircraft. Could that be a problem?
|
|
|
|
Post by Dutch Owen on Nov 2, 2012 18:23:42 GMT -5
That's a major clue. Since shift-E controls FSX's main door, and FSCaptain monitors this main door, if shift-E doesn't control it the 146 must have another door it considers the "main door". Something we don't know about and aren't monitoring.
It seems there's no end to the way designers defeat and subvert the MS FSX system. And we have to find them all and accommodate them.
Yet ... I think MS by default considers every airplane to have at least one door. Even though shift-E doesn't physically open a door, does it, perhaps, convince FSCaptain that the standard main door is open enough to let in passengers?
But I'm just sure someone here is using the JF 146 ... or maybe that's another brand 146?
Dutch
|
|
|
|
Post by Guest on Nov 2, 2012 20:11:30 GMT -5
Hi Dutch.
The passenger loading seems to be working now but still having the same problem with the Fcom not changing the different stages of flight. It usually stays that way the entire flight. Think there was the only the one time where it changed just before I landed and was able to record the flight results. Been only using the default Cessna Grand Caravan. I also use GSX from FsDreamTeam if that could be causing a problem.
|
|
|
|
Post by Dutch Owen on Nov 2, 2012 21:18:19 GMT -5
Not changing phase is a unique problem, in 3 years of this being out. So, we have something new to figure out  If it never leaves taxi then it's because FSX is reporting it is still on the ground. GSX should not be an issue. Lots of people including me use it with no problems. Dutch |
|
|
|
Post by Travis on Nov 3, 2012 1:21:45 GMT -5
I've only the QW 146s on hand, m'self. Standard doors there. But even the F1 PC-12 uses standard door signals, and I've long wondered why they sometimes don't respond....
I can't see where GSX would affect the stock 208 (nor anything else) to the point where it wouldn't report it was in the air. That's a stumper and a half.....
|
|
