Jump to content

Sabretooth78

Members
  • Posts

    283
  • Joined

  • Last visited

Posts posted by Sabretooth78

  1. 15 hours ago, DaveCT2003 said:

     

    After seeing your post, I tested the A318 today and on departure the commanded Indicated airspeed was down to around 145 knots when it should have been much higher.  The A/TH wanted to keep this speed, so I manually commanded the airspeed to 250 knots and eventually put the speed back into Managed Mode and it worked fine after that.  I will include this into our bug tracking system.

     

     

     

    That sounds like the same issue - when the issue appears during climb, Managed Mode will still honor the correct speed (that shown on the MCDU) but while in cruise it will honor the incorrect PFD-displayed speed.  Selected Mode and manual flight will work perfectly OK of course, you just need to have your speed target in mind since the bug will not be correctly set.  This all seems to go away when the descent phase is entered - I don't believe I've ever encountered the issue then, while it seems to occur quite frequently especially during climb.

  2. Another takeoff from KJFK, and another instance of the managed speed issue immediately on climb out and persisting through cruise.

     

    This again occurred on another departure from KJFK on the JFK5 departure.  I followed the same procedure as in the previous flight, excepting that I did not change the acceleration height this time (kept it at the default 1500' AGL).

     

    Flight Plan:  KJFK F360 DCT WAVEY DCT EMJAY J174 SWL DCT CEBEE DCT WETRO DCT ILM AR15 HIBAC DCT ORL DADES6 KTPA

     

    Commanding 204 kts on climb - MCDU PERF calling for 306/0.79 as appropriate.speed1.thumb.jpg.c5255b7541270610c2470fb1af60199f.jpg

     

    Commanding 106 kts during cruise:

    speed3.thumb.jpg.3c9dac6e6c78d066a62ea032f5f82163.jpg

     

    Logs attached.

    Logs3.zip KJFKKTPA_PDF_18Jan20.pdf

  3. On 12/15/2019 at 7:51 AM, Secondator said:

    @Sabretooth78do you have by any chance FSUIPC autosaves enabled? If so, when you next time see the speed to drop, post the autosave files that you have taken before the speed dropped and test if it happens again at the same point with the saved flight. If so post us here the saved files and let us know exactly where it happens and we'll try to fix the case. We believe we have been able to solve most of these conditions but there are still few out there which will come out by trial and error.

     

    I did have this error recur with the A330 on a recent flight and I've captured logs and a save made before the error but haven't had the opportunity to test repeatability from the save.  I'll follow up on that later.

     

    Back to the A320 - I just had every flavor (that I've ever experienced so far) of this error both during climb (invalid but ignored target) and cruise (invalid but honored target) I was able to repeat on the same flight plan.  (I only repeated because an unrelated issue prompted me to just want to start the flight over.)

     

    Flight Plan:  KJFK F360 DCT WAVEY DCT EMJAY J174 SWL J121 ISO AMYLU2 KCHS

     

    The issue occurred very quickly on initial climb when I lost my managed speed target - I don't recall the exact moment but it seemed to be at the same time each flight after reaching about 4000 feet.

     

    Process:

     

    • Created a custom waypoint (PBD01) before WAVEY - "JFK/156/10" to give me an intercept target per the JFK5 SID.  (Call it "self-vectoring")
    • Takeoff runway 04L - JFK5 departure - manual climb out and turn to 99 degree heading per SID - instructed FO to set selected heading.
    • Acceleration height 3000 ft, command FO to set selected speed 240 kts (I like to do this to prevent overshoots); follow procedure to 4000 ft then turn to PBD01.
    • (Error began somewhere around here.)
    • Continued manual tracking to PBD01 and then turn to WAVEY, set managed NAV.
    • Continue manual flight to TOC.  (I wanted to fly manual to test new null zones on my "sidestick" controller.)
    • Upon reaching cruise phase, the error persisted and became of the type where setting managed speed would cause an engine rollback to 100-something knots.

    Attached are some pictures, logs captured after each error instance (numbered per flight) and some pictures.  Also attached is my SimBrief OFP in case you want to recreate the exact time and setting with AS historical weather.

     

    Fortunately she does fly beautifully manually, and even better with a FO that saves you the work with the FCU!

     

    EDIT:  The error disappeared upon entering the descent phase.  Those logs which had modified times after activating descent are attached.

     

    Logs2.zip Logs1.zip Pictures.zip KJFKKCHS_PDF_31Dec19.pdf

    LogsDesc.zip

  4. 1 hour ago, RALF9636 said:

     

    ...The EFOB goes constantly down in the first half of the flight and goes constantly back up again in the second half of the flight.

     

     

    Not to pile on a dead horse, but I've seen this behavior as well (using KGS) with the MCDU fuel remaining at destination.  Generally speaking, though, the actual fuel burn is consistent and within a few percent of SimBrief from what I've experienced.

     

    For instance, on a CYYZ-CYVR flight (with 1.0.0.2 IIRC), my block fuel (from SimBrief with a 1.10 fuel factor) was 33400 kgs.  The screenshot was captured 1:16 into the flight (3:15 to go) with a SimBrief EFOB prediction of 21.7k-23.2k kgs. As you can see, the ECAM FOB is slightly high but nearly dead on, while the MCDU is way off.  It finally started to correct around Calgary.  A quick sanity check by summing the upper ECAM engine fuel flows divided into the FOB shows there is plenty of fuel remaining (almost 5 hours!)

     

    2019-12-13_21-30-35-560.thumb.jpg.3e1423053bf258e3048f83b161b5ef01.jpg

     

    Upon arrival at the gate at 20:59 (3.5 hours later), the ECAM reported FOB was 7950 - compared to a SimBrief prediction of 5.3k-6.7k kgs.

     

     

    • Like 1
  5. 15 hours ago, Secondator said:

    @Sabretooth78do you have by any chance FSUIPC autosaves enabled? If so, when you next time see the speed to drop, post the autosave files that you have taken before the speed dropped and test if it happens again at the same point with the saved flight. If so post us here the saved files and let us know exactly where it happens and we'll try to fix the case. We believe we have been able to solve most of these conditions but there are still few out there which will come out by trial and error.

     

    Lately I haven't been using autosave but I'll turn it on for my next A330 flight.  Should be sometime this week.  Way back (somewhere earlier in this thread probably) when I was having these issues on the A320 I seem to recall doing just that and finding it wasn't always repeatable.  Could it be a simple PFD issue?  The actual autoflight does not honor it (at least not in these instances, as opposed to the instances during cruise where it does) and the correct data always shows in the MCDU PERF pages.

  6. I experienced the erroneous "magenta" PFD speed again sometime after the IAS/Mach crossover, this time with the A333.  Identical to my experience when it appears on the A320, the aircraft maintained the "correct" speed and the magenta number declined with altitude and simply vanished after reaching cruise.

     

    pfd1.thumb.jpg.da9354bb28b267a766ab84c74f929ff7.jpg

     

    pfd2.thumb.jpg.8d4a0e770ef376c14fd603e704d5860c.jpg

  7. I had this issue occur last night for the first time in a long time.  Shortly after reaching cruise, I noticed the throttles rolling back and the PFD speed target was indicating "107".  I then tried going back into managed speed at various times during the flight and the problem persisted, right through descent where it was still calling for an unreasonably low "213".  At all times, the MCDU PERF was showing the correct speeds (for CI 35).

     

    Flight plan:

     

    KMCO/36R F370 MCOY2 GUANO DCT FEMON MCOY2 GUANO Q87 JROSS DCT FLO Q87 JROSS J207 RDU DCT NEAVL J207 RDU DUCXS4 KRIC/34

     

    I'm not at my sim PC so I don't have the log files but I do believe I have logging turned on so I can post them later.  This is running the latest version with experimental updates enabled.

     

    An interesting note is that I did a full reinstall of the PC about a month ago, so everything should be relatively "clean".

  8. I still see this "magenta" rollback during climb at or near crossover altitude/speed on almost (if not) every flight (commanding something like 166 kts) but the a/c still follows the correct speed (usually 280-300 kts) and the problem goes away either at TOC or by just playing with the altitude knob (push or pull).  Haven't seen it occur at cruise in some time.

  9. I don't recall having encountered this issue since upgrading to 1.2.3.0 and with any of the subsequent point releases (despite experiencing it quite regularly earlier), but today it has come back with a vengeance!  Flight in progress as I post this:

     

    Plan:  TLPL N0469F340 GEECE Y331 FERNA MACOR L455 SKPPR L455 SAVIK YAALE YETTI MOUGH DONAA OWENZ CAMRN KJFK

     

    Aircraft:  A320 IAE

     

    While climbing, somewhere around FL230, the commanded speed changed to 215.

    • This was not reflected by PERF CLB, which still displayed the correct 320/.79 (CI 35).  Interestingly, PERF DES displayed (and continues to display) .79/214, which is clearly incorrect for CI 35.  Not sure if there's a relationship with that setting.
    • Unlike before, where the a/c would still maintain the correct speed (320) in managed mode, this time it attempted to reach the incorrect (215) speed by pitching up.  Nothing drastic, the speed trend arrow was between 5-10 kts long.
    • Unlike before, this commanded speed didn't seem to decay with increasing altitude, nor did it seem to indicate any correlation with crossover altitude.
    • Unlike before, toggling the FCU altitude pushbutton didn't clear/reset the speed target.
    • Around crossover altitude, the SPD MACH button seemed to be acting funny.  The FCU speed window seemed to be rapidly changing between IAS and MACH before eventually (after a second or so) settling on one of the settings.

    I stayed in selected mode for some time, before trying managed speed for cruise (which by now I had adjusted to FL360).

    • For a brief period it behaved, before suddenly commanding 110 about FL340.
    • This behavior has since persisted every time I toggle between selected and managed speed.
    • Every time after re-entering selected speed, the FCU speed window will be in IAS.

    Logs attached; I can reattach them later upon completion of the flight as well.

     

    As a sort of disclaimer, I have not made any hardware or software changes since my last flight, aside from minor SimStarter scenery library configset changes.  Nor have I (that I am aware of!) done anything different procedurally during this flight (including those points mentioned by C525B). 

     

    Logs.zip

  10. I haven't been using the checklist/copilot and I have had the bug several times (though not since updating to 1.2.3.0).  However, I do have those features turned on in the MCDU3 Options, I just haven't been initiating them at any time (I use FS2Crew).  I don't believe I've changed options settings since the update.

  11. 54 minutes ago, DaveCT2003 said:

    See, if we were to perform development like some people think we should, then one Airbus product would either take 15 years to develop and it would sell for between $1800 and $3600 USD per copy.

     

     

    In the field I work (civil engineering) there's a saying that basically goes "if you have a perfect set of plans, you paid too much for them."  The punch line being, of course, that there's no such mythical creature.  I would expect software development is much the same.

    • Upvote 1
  12. On 1/21/2019 at 2:42 PM, haroldeh said:

    ...

     

    Here is the "New" process.  I'm sure a few of the steps are totally unnecessary ... but this is what I did.

     

    ...

     

    I've reinstalled several times in the past several weeks and at least one of those times I tried deleting those "User" folders (and then restarting) but to no avail in stopping the problem, so apparently it's one of those "your mileage may vary" things that happened to work for you...

     

    I also don't run A/V - I don't use my sim PC for anything besides simming (and the attendant downloading that goes with it) so unless SimMarket, ORBX, Aerosoft, etc. get hacked; well, suffice it to say I haven't used A/V on any of my PCs (Mac and Windows) in at least 15 years and haven't got burned; I'm tech savvy enough and back up early and often enough that if I did get a virus I'd just assume wipe clean and restart.  But I digress...

     

    One area where I differ from your process is that I tend to run P3D and load up whatever particular add-on (particularly in the case of aircraft) immediately after running the installer and rebooting.  I'm not sure if that makes a difference.  I guess I do it as sort of a holdover from the FSX days, where you had to run FSX on the clean install in order for the sim to create its cfg files and such before installing the service packs, otherwise you could potentially run into problems.

     

    All that said, I now almost ALWAYS get the managed speed bug on climb when hitting crossover altitude.  Always, as in, at least the last 7-8 flights (beginning around New Year's Day).  Before that, it hadn't been happening at all (in that situation).  Fortunately, George still seems to obey the "proper" climb speed, and the bug is easily eliminated by either pushing or pulling the altitude knob.

     

    As for the random occurrence of the bug during flight, I still get that only sporadically.  Say maybe once every 5 flights.  For instance it happened to me last night fairly early in cruise on a 4:45 flight; it seems to have a propensity to occur on longer flights (which makes sense; longer flight = greater chance of it happening eventually) at some random point in between waypoints.  The first time it ever happened to me was on November 5; about midway through a 5 hour flight.  Naturally, that was while running P3D v4.3, and the problem has persisted through the P3D update to v4.4 (for which I updated all components and have since reinstalled the Bus a number of times).  Also consider I just performed a clean install of Windows in mid-August 2018 when I effectively rebuilt the PC.  I don't know if that rules out the state of my P3D install as a cause or not.  My virtual money is on it being an unintended side effect caused by a VNAV update to the Bus sometime in late October/early November, but that's just a hunch and I don't intend that as a dig at the developers; --it happens.

     

    So, regarding the upcoming update.  The change log for 1.2.2.2 said that the logging would be triggered when the managed speed dropped below 120 kts.  Unfortunately, this would not trigger in the vast majority of my situations where it is occurring during climb, where it typically shows up at about FL260, calling for a speed of 180 kts and slowly decaying as the climb progresses.  Could I make the suggestion that the logging instead be triggered say when the managed speed drops below 200 while in climb or cruise phase?  Or perhaps any situation above say FL200? Naturally it would have to be coded in some way so as best to avoid instances in initial climb with lower speeds such as SIDs with speed restrictions, etc.  Of course I may well be the only one having this issue during the climb.

     

    At this point I'm sick to death of reinstalling things and I'm content just to throw it into selected speed until the issue is teased out and squashed, which will happen eventually.  I have no problem doing some investigative work as part of my normal flying, but I'm done with the reinstalling for now.  There's enough to do as it is just in the normal course of updating, regardless of trying to tease out bugs.  I have no regrets jumping ship to P3D, but this is why I clung to FSX for as long as I did, why I would still be using FSX were P3D still only 32-bit, and why with most gaming I've usually been a hold out; I appreciate the maturity and stability in the platform!

  13. Just happened to me again - flight plan:  KJFK/31L N0456F350 SHIPP JETZZ BLUUU DUMPR ISLES SQUAD DARUX L459 KEEKA L459 ODUCA SLUGO ULUBA1 TNCM

     

    Heading out over the ocean so frames/performance is in no way an issue.
     

    Occured somewhere before ISLES.  I did not notice it immediately because the funny thing was that it was still maintaining the proper speed, perhaps because I was in Open Climb (as opposed to managed climb?  Also, as the altitude increased, the target speed decreased.  It was 170+ +/- around FL250 or so, gradually decaying into the 140s as I approached my clearance of FL340.  Upon climbing to cruise at FL350, the problem disappeared.

     

    Another observation - when I select speed at cruise when the speed target is working properly, the window displays a mach value.  When it's not working properly, it displays a speed value and I have to hit SPD/MACH to dial in the desired value.

     

    2019-1-7_13-15-1-890.thumb.jpg.8bf196e7e8a724036048c55fe16bb9cc.jpg

     

    2019-1-7_13-12-9-120.thumb.jpg.05eff66820089b82fe99c489dc8687be.jpg

     

    To supplement my earlier info:

     

    Add-ons in use:  Active Sky (v6909), REX SkyForce 3D (textures and real time sync only; no weather engine), PF3 (ATC), EnvTex, FSX Tracker, ORBX (various), FSDT KJFK, FT KBOS and TNCM.

  14. Operating System:  Windows 10 Professional

    Simulator Version:  4.4.16.27077  (updated client, content and scenery from 4.3)

    Airbus Version:  1.2.2.1

     

    System Specs:

    MB:  ASRock X470 Gaming-ITX

    CPU:  AMD Ryzen 7 2700X 8-core 3.7Ghz 4.3 Ghz Max Boost Socket AM4 (Hyperthreading is turned off)

    Video:  EVGA GeForce GTX 1070 Ti (Driver Version 416.94)

    RAM:  G.SKILL Ripjaws V Series 16GB (2 x 8GB) 288-Pin DDR4 SDRAM DDR4 3000 (PC4 24000)

    Storage:  Samsung 970 EVO 256 GB SSD (Boot), Samsung 850 EVO 500 GB SSD (Add-ons and Utilities), Samsung 860 EVO 500 GB SSD (P3D), Apple 500 GB HDD (Backup)

     

    Description:

    Same as reported previously, managed speed target (as displayed on the PFD) changes apparently randomly, to an apparently random speed in mid-flight.  Most often seems to happen after passing a waypoint, but not always.  MCDU speed target sometimes changes as well, and not necessarily to that given by the PFD.

     

    Reproducibility:

    Not sure if it's reproducible (seems to occur randomly); next time it occurs I will isolate the last prior FSUIPC autosave and see if it continues to happen at the same location.  Occurred twice on my most recent flight:  Once during climb (was flying manually, so it didn't cause any problems) and apparently corrected itself prior to TOC until recurring somewhere between waypoints (don't exactly remember where).  Speed target was 216 if I recall correctly.  Flight Plan was:

     

    KPSP/31L N0458F350 CATH1 PSP V370 TNP EED HBU TXC HCT FOD KG75M DAFLU J70 BROKK/N0461F370 J70 LVZ LENDY6 KJFK/22L

     

    It does not appear to be only a performance issue as both instances occurred at 30 FPS (lock) with no texture loading latency (blurries).  (The worst performance I usually get is 21-24 FPS at FSDT KJFK in overcast conditions.)

    • Upvote 1
  15. 14 hours ago, Osman48 said:

    Hello I don't know who I'm talking to right now because I'm new but I really hope a member of Aerosoft staff listens to me. So it wasn't long ago that Airbus bought the CSeries aircraft from Bombardier. And Airbus named these new planes: A220-100 (for CS100), and A220-300 (for CS300). And I just think these planes are beautiful! The cockpit, the cabin, the engines, the wings, everything is really beautiful on this plane! 

     

    So I would like to know if Aerosoft could make an A220-100/300 because Aerosoft products are of very good quality! If someone reads this text and also wants an A220 on FSX/P3D, then share my text so that it is the most likely to be seen by an Aerosoft Staff. Thank you all. Goodbye :D

     

    Agreed.  I would like to switch my previous allegiance for the E190 to the new A220-300 as I'll be wanting a good one for my VA flights come 2020.  Please make it happen!  ;)

    • Upvote 4
  16. On 1/1/2018 at 4:25 PM, Adamthepilotkid said:

    I want to make the case for aerosoft doing the Embraer 170/5 - 190/5. Right now their is no company that supplies a good e jet that is up to date. Feelthere has one their package which is now available for p3dv4 but they haven’t updated it to make it modern.

     

    I'll continue to piggyback on this request and the others for a rebooted E190, or perhaps the new E2 series. The E190 is going to be the reason why FSX will remain on my PC once I do eventually make the switch to P3Dv4*.  It's unfortunate feelThere doesn't seem to have a desire to update it because it really would seem to have an excellent foundation as it is a great model even today once you get past the fact that it is (and looks) 10 years old.  That said, I drool at the prospect of an E190 that has the polish and practicality of an Aerosoft Airbus.

     

    (Of course, my tune could change if jetBlue (my preferred VA routes) dumps their E190s and switches to the C-Series.  But that probably wouldn't be until the mid-2020s and hopefully by then somebody will have at least done one of those justice as well.)

     

    * Editorial note:  I haven't made the upgrade yet because I [by no small effort, finally] have FSX running like a well-oiled machine and while most of my scenery add-ons are finally P3Dv4 compatible, none of my aircraft are.  Yeah, I could pull the trigger anyway, but I fly a lot of VA with specific planes on specific routes and I like it that way; having something better that I can't fully use to its potential is just going to damp the experience of both simulators for me.

    • Like 1
    • Upvote 3
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use