|
Post by Travis on Nov 15, 2014 18:26:04 GMT -5
It's even in the old FCOM (one of the pages is - there are actually 2 Specify PAX pages in the FCDU... I keep thinking that one's an accident. )
|
|
|
Post by mjl1966 on Nov 15, 2014 18:51:29 GMT -5
Multi-leg flights still not working in ACARS. When I arrive, shut down engines and unload, it still thinks I'm at the origin when I go to select flight. i.e. KMIA-KATL. Arrive KATL, unload, Heidi says everyone is off. INIT/RST to select flight, "no flights from KMIA"
I have to quit FS and come back in, which destroys the whole purpose (immersio) of a multi-leg flight. From a dispatch perspective, the difference between a separate flight and a multi-leg flight is trivial. This feature really should just be abandoned because it doesn't really do anything that contributes to the user experience.MJ, I did not realize this was an ongoing issue. I will put this in the official bug tracker to address. (When I began actual coding on FSCaptain this summer I pulled a list of issues from the forum and the only one that involved "legs" were about running multiple instances of FSCaptain and for users of the demo version. I now see your messages from last December, and realize how patient you are. ) So while I don't make multi-leg flights as an "I don't have the time" rule, I will run a few short-leg flights and gather data. MJL SAYS (Because he doesn't know how to get out of the quote box:
I AM WRONG!
It does work. I just got a proceed page for the next leg from KPHL to KMSP (YAY!) I think the problem is the start time restriction. I have my airline set so I have to show up at least 10 minutes prior to flight time. In the case where a flight arrives late, this may mean that I can't start the next leg until after its actual departure time. In that case, I am not given the option to continue because I didn't start soon enough.
Example:
Leg 1 KMIA - KATL. Scheduled arrival 0734. Actal arriaval 0748. Since 0748 is way later than the 10 minutes prior to flight time required, it doesn't let me continue.
Can we do this? You can start late IF you are on a continuation leg.
Sorry for jumping the gun...
|
|
|
Post by peter on Nov 15, 2014 19:08:37 GMT -5
Hi Lucas,
your images are most interesting. I have never used the EXEC button. The only buttons of the FCDU keyboard that I use are MSGS and INIT RES.
But more importantly: my flow looks quite different. When I log in, I am either presented with a page to select a flight, or for a committed flight I get the same as your "After press LOGIN". When I press proceed, I end up immediately on your "After revise" page with the correct pax number. I cannot remember having seen that "Specify pax page" ..
Peter
|
|
|
Post by Travis on Nov 15, 2014 19:12:42 GMT -5
It does work. I just got a proceed page for the next leg from KPHL to KMSP (YAY!) I think the problem is the start time restriction. I have my airline set so I have to show up at least 10 minutes prior to flight time. In the case where a flight arrives late, this may mean that I can't start the next leg until after its actual departure time. In that case, I am not given the option to continue because I didn't start soon enough. Example: Leg 1 KMIA - KATL. Scheduled arrival 0734. Actal arriaval 0748. Since 0748 is way later than the 10 minutes prior to flight time required, it doesn't let me continue. Can we do this? You can start late IF you are on a continuation leg. Sorry for jumping the gun...
No sweat about that - and you're working in an area where I would like to enhance FSCaptain as we approach a new version - better modeling of turnaround times for airliners, and what part YOU as the Captain would play in any of it. (Do you want to call the Cleaners & Caterers, etc.?)
Short term, we can likely relax starting restrictions on multi-leg flights after the initial leg has started. I haven't looked into this area of the code so I don't know what's really possible, but I have a glimmer of an idea. Worst case, you'll be late a lot.
I would think that if you want to test your theory, make a backup of your schedule and for your next multi-leg marathon, change all of the arrival times from each leg to 0000, and only have a valid departure time for your initial leg. See how that works. And if that seem too blah to work with, then try adding back your arrival times but leaving your secondary departure times as 0000.
Regards,
|
|
|
Post by Lucas on Nov 15, 2014 19:42:43 GMT -5
Peter, I don't know why our flows are different... Travis, help
|
|
|
Post by mjl1966 on Nov 15, 2014 23:31:49 GMT -5
It does work. I just got a proceed page for the next leg from KPHL to KMSP (YAY!) I think the problem is the start time restriction. I have my airline set so I have to show up at least 10 minutes prior to flight time. In the case where a flight arrives late, this may mean that I can't start the next leg until after its actual departure time. In that case, I am not given the option to continue because I didn't start soon enough. Example: Leg 1 KMIA - KATL. Scheduled arrival 0734. Actal arriaval 0748. Since 0748 is way later than the 10 minutes prior to flight time required, it doesn't let me continue. Can we do this? You can start late IF you are on a continuation leg. Sorry for jumping the gun...
No sweat about that - and you're working in an area where I would like to enhance FSCaptain as we approach a new version - better modeling of turnaround times for airliners, and what part YOU as the Captain would play in any of it. (Do you want to call the Cleaners & Caterers, etc.?)
Short term, we can likely relax starting restrictions on multi-leg flights after the initial leg has started. I haven't looked into this area of the code so I don't know what's really possible, but I have a glimmer of an idea. Worst case, you'll be late a lot.
I would think that if you want to test your theory, make a backup of your schedule and for your next multi-leg marathon, change all of the arrival times from each leg to 0000, and only have a valid departure time for your initial leg. See how that works. And if that seem too blah to work with, then try adding back your arrival times but leaving your secondary departure times as 0000.
Regards, . Nope, that's not it either. I just arrived AFTER the scheduled departure time for my next leg and was able to proceed just fine. (nice red -00:21 right of the bat!) So, forget everything I said. Multiple leg flights seem to be working just fine. Carry on.
|
|
|
Post by Travis on Nov 16, 2014 10:47:23 GMT -5
Peter, I don't know why our flows are different... Travis, help I will guess that you have auto-load turned off for that aircraft, and that you have "Prompt for PAX Count" set in your "Options for All Airlines" tab of the Admin. That's what I was missing when I tried to replicate things and burnt up an engine a few days ago. I may have time late in my morning to try again... I'm behind on weekend chores because I was fixing some bugs yesterday afternoon. (You earned a place in the source code comments, by the way. )
|
|
|
Post by Travis on Nov 16, 2014 10:49:42 GMT -5
Nope, that's not it either. I just arrived AFTER the scheduled departure time for my next leg and was able to proceed just fine. (nice red -00:21 right of the bat!) So, forget everything I said. Multiple leg flights seem to be working just fine. Carry on. Roger that. Once you have made several multi-leg flights while using Beta 4, I'd be interested in viewing your FCDU logs... both good flights as well as flights that wouldn't let you proceed. Please email them when you have a few!
|
|
|
Post by robsgam on Nov 24, 2014 8:05:50 GMT -5
Robs, If you were in offline mode, or even logged in but hadn't started your taxi, your FO won't say anything. It is possible for an aircraft to accumulate weight even with structural deice on. If you were in flight and this were to occur, there are some FO cautions that he'll send your way. The calculation for ice is very simple - we check the TOTAL WEIGHT as reported by the simulator, and subtract the aircraft's empty weight, payload and fuel. I suppose its possible the Q400 isn't reporting structural deice to the simulator and so the simulator keeps adding ice to the simulator aircraft. So here's a task for any Q400 pilot who encounters this situation - go to the SIGNALS page of the ACARS, and turn structural de-icing on there. If the ice weight magically disappears, then I'll modify the interface to automagically do this. I found myself in a situation where the HOT time expired and ice began accumulating while on the ground. I turned on all the q400 anti ice and turned on all the anti ice items in the signals page. the ice weight increased the entire time. I also never seem to have any icing happen while in flight. I guess its a good thing since the anti icing doesnt work.
|
|
|
Post by Travis on Nov 24, 2014 11:07:38 GMT -5
I found myself in a situation where the HOT time expired and ice began accumulating while on the ground. I turned on all the q400 anti ice and turned on all the anti ice items in the signals page. the ice weight increased the entire time. I also never seem to have any icing happen while in flight. I guess its a good thing since the anti icing doesnt work. Dutch can correct me, but I believe that there are two mechanisms at play here - the state where an aircraft takes on extra weight as FS9 / FSX / P3D simulator adds its ice, and the FSCaptain simulation of ground icing where we "add our own ice" and apply the consequences should ground de-icing & anti-icing not occur. Your aircraft's anti-icing systems will not affect the FSCaptain-applied ground ice. (I made some tests in the default Caravan recently and this is my conclusion.) The purpose of "ground ice" is to force complance with ground de-icing/anti-icing policies. On the other hand the Q400 is fairly easy to operate - its systems automatically engage engine anti-ice if the ambient temp is below 15C. That protects the aircraft from any FSCaptain-generated flameouts in bad weather. It's still up to each Captain to decide how to manage their structural de-icing while in flight.
|
|
|
Post by captwotan on Nov 24, 2014 13:10:37 GMT -5
Trav'
Any idea when the next release will materialise? I want to start flying the Q400 again.
Thanks
|
|
|
Post by peter on Nov 24, 2014 13:19:22 GMT -5
Hi Captwotan,
are you using the latest 1.5.1 beta version? I now have very good flights with the Q400
Cheers, Peter
|
|
|
Post by captwotan on Nov 24, 2014 16:45:03 GMT -5
Ah Peter, thank you, i must have missed the latest release. Just downloaded Beta 4. I'll do some test flights tomorrow.
Trav, any chance of getting these (very unfair) gear damage penalties removed?
|
|
|
Post by Travis on Nov 24, 2014 17:44:18 GMT -5
Capt WOTAN, I believe that I would either need to manually remove the penalties, or write a standalone EXE that would do so for the period in which the Q400 was dogged by them. Let us get the final 1.5.1 done, and then I can take care of the bad stuff. I have a new possible bug brought to my attention and I will investigate it today and tomorrow. We're currently working with a few Captains who have been experiencing frustrating & ongoing issues and while one Captain has had improvements of late, I need to get an Alpha 5 version out to the other Captain ASAP.
|
|
|
Post by captwotan on Nov 26, 2014 16:12:01 GMT -5
Pleased to report that the new Q400 interface doesn't appear to be giving me any problems.
|
|