717 Tester
  • Content count

  • Joined

  • Last visited

1 Follower

About ProfessorMadman

  1. Cold and Dark Gnd Pwr Gen switches in On position

    By the looks of it the ENG and APU GEN switches are always left in the on position. Not sure about the external power. This is from the Boeing FCOM under the initial cockpit preparation procedure:
  2. feedback

    @foobar @gamesyns I already logged a bug report for this on Saturday and Joshua acknowledged the issue:
  3. P3D V4 CTD - no errors

    FWIW I'm running @1440p. I've done quite a few Hawaiian hops now at both 4096 and 2048 resolutions and have had successful flights with both resolutions but also crashed with both (and the ones that were successful involved a LOT of view switching). Next try is like Skipy with 1024x1024 but that'll come after a week as I'm off on holiday next week.
  4. Auto Pilot/FD

    I get this too. To work around it I only arm APPR/LAND when established laterally on the final approach course or, in most cases, I fly the entire ILS approach using raw data with FD, AP and ATS off altogether.
  5. VC panels disappear

    It happened again at cruise before T/D into PHNL (ITO - HNL). It seems related to PHNL though as I never got this before flying into this airport. I did a flight after that too HNL - LIH and no such issue. Will report if it happens coming into FSDT HNL again.
  6. Incorrect SID representation on ND and in FMS

    Another example, this time PHTO (Hilo Intl) on the PARIS FOUR departure. I departed off runway 26 but it drew a fix on the east side of the airport for the turn. The F-PLN page looks to be ok (climb out on rwy heading, then r/t heading 45 to intercept the R-355 ITO to SADPE) but the visualisation on the ND is totally wrong.
  7. Data Flickering
  8. feedback

    Agreed, very nice update. Still suffering hangs but it's manageable with the state saving feature and FSUIPC autosave. I have logged a few bugs relating to SID drawing and interpretations but this update is really good. A couple of things that has come to my attention and may be due to my lack of knowledge on the 717 so please do correct me if I'm wrong. 1) The WX radar tests fine on the first flight and you can skip over it if you want to by quickly switching from OFF to WX position, however on subsequent flights (without reloading) the radar tests even if you swiftly switch from OFF to WX position. Is this intended? 2) ILS autotune populates the frequency but not the course on the RAD/NAV page. Not sure if it's supposed to also put in the course or not?
  9. P3D V4 CTD - no errors

    Very, very interesting Ransu. I know that there are people that do not get crashes with the 717 in v4 and others consistently do. I've done further testing doing island hops in the 717 in Hawaii and have had flights where I had hangs and ones where I didn't. Nothing consistent whatsoever and I've debunked my texture resolution theory too lol. I was using AS in P3Dv3 as well with the 717 and never had any problems but that's not to say that some gremlin got introduced in v4 relating to compatibility between these two products. @turbofandude would a forum poll on users experiencing crashes using Acitve Sky or not maybe provide some statistics to strengthen or debunk this theory? EDIT: Ok so I flew HNL - ITO without Active Sky running and still had a crash (again when returning to flight deck after external view).
  10. Incorrect SID representation on ND and in FMS

    @turbofandude @Joshua Che. another example. This is the CRISI ONE RNAV departure out of PHKO. The departure calls for a climb on runway heading then a turn at 560 feet direct CRISI after a departure from either runway 17 or 35. The 717 is drawing the northern climb fix (i.e as if you are departing from runway 35). It should draw a fix south of the field for a runway 17 departure, no? EDIT: Actually, I just tested setting up a runway 35 departure and it's placing the turn fix for that departure south of the field, so it looks like it's reversing the two?
  11. VC panels disappear

    Just had similar visual artefacts spawn with on a Hawaiian island hop from Kona to Honolulu. This is the first time I've seen this happen and I've done quite a lot of flights in the 717. Fortunately nothing obscured so I could complete my flight without reloading EDIT: A reload of the scenario fixed the problem. Maybe a one off problem not worth investigating.
  12. Volunteers for an Internal Test Team

    Count me in, if you'll have me I am going to be away on holiday for a week starting the 18th though. Regards, Daniel
  13. Data Flickering

    Same problem programming an RNAV Z arrival into YBAS rwy 30 (BASEC transition). Flight QJE1798: YBBN - YBAS Flight plan route: N0436F360 WACKO1 WACKO V179 UNVAT DCT 25S145E 25S142E DCT WILLS W344 AS DCT
  14. P3D V4 CTD - no errors

    Okay so here's a synopsis of my test run today. I spent 6 hours with the 717 in sim today and just now had a hang for the first time. I've been experimenting with reducing my texture resolution and set mine to 2048x2048 in the sim. I did a casual flight around NZQN and view switched and performed a takeoff and landing no issues. Without restarting I then went on to doing a YMML - YBBN - YBAS - YAYE run. First leg YMML - YBBN was fine, no issues, perfect flight online. I switched views a lot and the aircraft performed beautifully. It flew the arrival perfectly as well. No ATS issues, not autoflight issues. Long turn at YBBN as I was watching VATSIM traffic land and was switching views to deliberately try and get the sim to lock up. Second leg YBBN - YBAS - all fine for about 2 hours and then a graphical hang in sim (with sound still playing) whilst in cruise inbound WILLS fix (literally in the middle of nowhere so not possibly taxing the sim in any way) in the flight deck not touching a thing. Interestingly, I could still see my aircraft move on ProjectFly and VATSPY - so I decided to use my joystick button mapped to ChasePlane and switch to external view and I could hear the external engine sounds but the visuals remained in the flight deck. I could switch back too and hear the internal sounds again but the visuals were totally "locked up". I had to kill the process and load an FSUIPC autosave to resume. I was so optimistic about the progress of my test with 2048x2048 until the hang occurred that I drafted a long post here and had to delete it Bummed out and still nowhere near to finding the cause. I'll try reducing texture res even further like Spiky suggested (1024x1024) and see if that makes a difference. It's probably a red herring but 6 hours and 2 and a half flights in the 717 without a single CTD/hang/crash is certainly more than I've been able to achieve since P3Dv4 came out.
  15. P3D V4 CTD - no errors

    Hi Collin, Fair enough, I appreciate you looking into this. If you removed all your code and still had the issue then it has to be something specific with the combination of P3Dv4 and the 717. The problem here is that I have nothing to go on to report to LM other than my own anecdotal evidence so far with v4. I get no error messages in the Event Viewer, no debug logs, no mini dumps. Nothing I have now done 64 flights in P3Dv4 using the 717, CRJ (a little unstable at the moment with other CTD issues), PMDG 737, 777 and 747 and the 717 is the only one with this specific issue where no error is logged whatsoever. I can do anything from 16 hour long hauls in the T7 to short hops in the 737 without any issue. As I mentioned previously, before build my sim would simply CTD without a single trace of error in the logs. Now with and up my sim instead just hangs and when I kill it I get this rather useless and generic error in the Application Log in Event Viewer: The program Prepar3D.exe version stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel. Process ID: d848 Start Time: 01d3137125510601 Termination Time: 215 Application Path: D:\P3D\Prepar3D.exe Report Id: 077d0994-ed86-4920-8d9b-0d97ef35ad4b Faulting package full name: Faulting package-relative application ID: I'm going to try and faff around with the model and replace the external with something and do some further testing with graphic settings for now but I don't think LM will appreciate us going to them without any error messages on this illusive issue just yet. If I can find some consistent method of reproducing the crash/hang instead of it randomly occurring I'll post it here and tag you guys. Thanks for your interest and again for acknowledging that a problem does exist. Let's hope we can find the cause soon so that we can all enjoy this amazing creation