|
Post by Lucas on Nov 13, 2014 15:06:21 GMT -5
Ahh, I forgot Ok. I'm curious to your report
|
|
|
Post by robsgam on Nov 13, 2014 16:13:23 GMT -5
FSCaptain Version 1.5.1 RC 4, P3D 2.4, ASN build 5410, MJ8Q400 1.0.11.
I just flew from KIND to CYYZ. I was monitoring the FCDU INFO page and ASN debug window and noticed I am not getting turbulence being reported in the FCDU. Turbulence=0 is in my config and when ASN is reporting HEAVY (Cloud) turbulence, I am get nothing.
I was also playing around with ICING conditions in ASN and noticed that none of the anti icing controls in the q400 have any effect. I checked in the interface signals and nothing seemed to work there either.
I don't know if you need logs or more information but please let me know how I can help address this.
Lastly it looks like the gear penalty is no longer a factor.
Thanks!
|
|
|
Post by Travis on Nov 13, 2014 20:13:25 GMT -5
Robs,
Archiving and sending us all of your logs would give us a better look at what was happening, but I can venture that the Q400 may not send turbulence data through the FSX/P3D system, so we may not see anything's happening. Yes, you may see the aircraft pitching and jumping about, but if it's not presented to the ACARS in something that's reliable, we can't know. (It might be possible to check VSPEED and note changes in deltas, but calculating turbulence is more involved than that....)
As for the anti-ice systems, the Q400's engine anti-ice is automatic as long as the TAT is 15C or less. If the engines are running and the airframe anti-ice switch is set to something other than 'off' you should see a "+" on the Interface screen.
(The Signals screen is rapidly losing purpose, btw.)
When you write "none of the anti icing controls in the q400 have any effect," what effect were you looking for? Did your FO continue to nag you? Did your ACARS show ice continuing to build???
Now that we can turn off WX events in the logs, I may begin logging things such as "Ice forming," "Anti-ice on," "Ice gone." But I'd rather give it a little more time to see if we can sort this out.
Still, this is the purpose of a beta session... to gather data and formulate Cool New Stuff that WorksTM.
|
|
|
Post by robsgam on Nov 14, 2014 7:12:58 GMT -5
Robs, Archiving and sending us all of your logs would give us a better look at what was happening, but I can venture that the Q400 may not send turbulence data through the FSX/P3D system, so we may not see anything's happening. Yes, you may see the aircraft pitching and jumping about, but if it's not presented to the ACARS in something that's reliable, we can't know. ( It might be possible to check VSPEED and note changes in deltas, but calculating turbulence is more involved than that....) I wasn't sure if the recent update to .11 of the Q400 broke something. I do recall seeing turbulence displayed in the FCDU before but I don't remember if it was the Q300 or not.
As for the anti-ice systems, the Q400's engine anti-ice is automatic as long as the TAT is 15C or less. If the engines are running and the airframe anti-ice switch is set to something other than 'off' you should see a "+" on the Interface screen. I did see then interface screen displaying the "+".(The Signals screen is rapidly losing purpose, btw.) When you write "none of the anti icing controls in the q400 have any effect," what effect were you looking for? Did your FO continue to nag you? Did your ACARS show ice continuing to build??? I was in offline mode on the ground so I didn't hear the FO say anything but the ACARS showed the ICE weight rising steadily.Now that we can turn off WX events in the logs, I may begin logging things such as "Ice forming," "Anti-ice on," "Ice gone." But I'd rather give it a little more time to see if we can sort this out. Still, this is the purpose of a beta session... to gather data and formulate Cool New Stuff that Works TM. I totally understand that this is BETA and just want to contribute what I can to the effort. I am more than happy with the product and appreciate being able to participate.
|
|
|
Post by Travis on Nov 14, 2014 12:45:35 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.
|
|
|
Post by Travis on Nov 14, 2014 12:48:51 GMT -5
Ok. I'm curious to your report Ummm it had been a while since I stepped into a JS41, and since my default flight is still Friday Harbor my aircraft started with all engines going and within a few seconds Dutch was calling my attention to an engine fire. Flight aborted and I'll try again this weekend.
|
|
|
Post by Lucas on Nov 14, 2014 15:43:39 GMT -5
I hope you are safe and sound ...no problem, I'll be waiting for info...
|
|
|
Post by peter on Nov 14, 2014 16:30:49 GMT -5
The JS4100 is one of my favorite planes, but I do not recall any issues like what Lucas describes. If that's OK with you, Lucas, maybe Travis can share your config files with me so that I can verify the issue.
Cheers, Peter
|
|
|
Post by Travis on Nov 15, 2014 13:49:09 GMT -5
I've sent Lucas' files to Peter, and I hope to have a test load (sans fire) later today. I do have a bucket of gray water handy just in case an engine goes all smoky on me.
|
|
|
Post by mjl1966 on Nov 15, 2014 15:42:30 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.
|
|
|
Post by peter on Nov 15, 2014 16:26:21 GMT -5
In JS41 (only), ACARS, at Specify PAX page, payload and amount of PAX are correct (as in Dispatch set). But after press EXEC (on incoming Flight page), there is only 2 PAX (payload stays correct). Of course I can revise it, however I decided to report it... Hi Lucas, I am just reviewing this, but I am not exactly sure how to reproduce the problem. I created a flight with the admin, committed to it, and then the FCDU shows only this flight (with correct pax). If I do not commit but just select a flight in the FCDU, it also shows correct pax. I must be doing something wrong as I never get an "EXEC" button to push. Can you let me know how you get to that Specify PAX page? Cheers, Peter
|
|
|
Post by Lucas on Nov 15, 2014 17:43:01 GMT -5
Ok, from the beginning... (flight set in Dispatch with 29 pax) Turn on the ACARS: After press LOGIN: After press PROCCED: (and this is Specify PAX page, with 29 pax)After press EXEC (althought EXEC button isn't shining, however it works): (here you see only 2 PAX)After revise: Ps. I don't know why there is an ICE, but after each step what I described above, amount of ICE is decreasing
|
|
|
Post by Travis on Nov 15, 2014 17:48:56 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.
|
|
|
Post by Travis on Nov 15, 2014 17:51:37 GMT -5
Ok, from the beginning... (flight set in Dispatch with 29 pax) I see that you're using the Specify PAX screen (I don't use that normally) so I will factor that into my testing this evening. I've been writing and coding all morning - took time for lunch & some telly - now back at the keyboard.
|
|
|
Post by Lucas on Nov 15, 2014 18:17:54 GMT -5
Hmm, that's interesting... I didn't know that is an option . I have this page from the first day of using FSCaptain (as I remeber well...)
|
|