Bruce R

Member
  • Content Count

    18
  • Joined

  • Last visited

Community Reputation

5 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Bruce R

    CG Value

    Just to carry on from what LordWalrus has said - Open up your "TFDI Design Addon Manager" first, scroll down and add your fuel. Scroll back up and add your pax and cargo. Then "Send Payload to Sim" and "Send Fuel to Sim". When entering data into the FMS, the tablet will show your figures. Bruce R
  2. Did a flight from Brisbane to Canberra, Australia today with the 717 V1.1. Flight plan was a real world plan taken from Flightaware - Huugo H62 Admar Q78 Oltin W180 Tesat H65 Razzi Flight took 1hr 31 which is the same as the RW 717 flight took. I had AS weather active (it was a clear blue sky with a few scattered clouds over Sydney), as well as My Traffic Professional and ORBX Australia & New Zealand A1 traffic. Much to my relief there was no CTD. Perhaps V1.1 has done the trick. Bruce R
  3. For your first aircraft in the flightsim world, you've put some more established devs to shame. Yes, I agree with the previous comments. Well done and congratulations. Bruce R
  4. Bruce R

    Nav Data Issue

    My Navigraph FMS Data Manager has my path as: Lockheed Martin/Prepar3DV4/SimObjects/Airplanes/TFDi_Design_717 - is yours? Bruce R
  5. Yes, I have My Traffic Professional and ORBX Australia & New Zealand AI traffic installed. Do you think it 'could be' MTP causing this? Bruce R
  6. I'm starting to suspect the CTD I had in the above thread had nothing to do with the 717. Soon after that crash I did the same flight with similar AS weather in the FSL's 319. This time I had a CTD at 4000'. Again there was no error message. This time there was no Event Error message either. I might hop over to the ActiveSky forums and see if there's any talk over there. Bruce R
  7. I have 717 version 999 installed on W10, P3D V4.3. I had ActiveSky open. I was flying NZCH - NZDN; route Ubdan3P Idara Y814 Mipak Mipak2A. I was in cruise at FL230 and was about 5 miles before TOD. I began winding the altimeter down for the decent. As soon as I did that, the screen froze for about 10 seconds then CTD. There was no error message. Event Viewer shows the following; Log Name: Application Source: Application Error Date: 16/07/2018 1:54:11 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: Description: Faulting application name: Prepar3D.exe, version: 4.3.29.25520, time stamp: 0x5b2c3263 Faulting module name: ai_player.dll, version: 4.3.29.25520, time stamp: 0x5b2c3261 Exception code: 0xc0000005 Fault offset: 0x000000000004f179 Faulting process id: 0x17fc Faulting application start time: 0x01d41c9d51745baa Faulting application path: C:\Lockheed Martin\Prepar3D v4\Prepar3D.exe Faulting module path: C:\Lockheed Martin\Prepar3D v4\ai_player.dll Report Id: b673cb17-6257-470a-8abe-f96703b56c41 Faulting package full name: Faulting package-relative application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2018-07-16T01:54:11.745619200Z" /> <EventRecordID>14581</EventRecordID> <Channel>Application</Channel> <Computer>Bruce-Ross</Computer> <Security /> </System> <EventData> <Data>Prepar3D.exe</Data> <Data>4.3.29.25520</Data> <Data>5b2c3263</Data> <Data>ai_player.dll</Data> <Data>4.3.29.25520</Data> <Data>5b2c3261</Data> <Data>c0000005</Data> <Data>000000000004f179</Data> <Data>17fc</Data> <Data>01d41c9d51745baa</Data> <Data>C:\Lockheed Martin\Prepar3D v4\Prepar3D.exe</Data> <Data>C:\Lockheed Martin\Prepar3D v4\ai_player.dll</Data> <Data>b673cb17-6257-470a-8abe-f96703b56c41</Data> <Data> </Data> <Data> </Data> </EventData> </Event> There was nothing in the 717 log. For your information Bruce R
  8. There' really nothing on the event viewer. The AppCrash doc has got some info that may be of interest to you. If there's anything you want me to do, just sing out. Regards Bruce R AppCrash.docx
  9. Further to my last post above - I did a flight from YSTW to YSSY. Take off Tamworth R30L intended landing at Sydney R25. Flight plan TW W192 Sanad Mepil1. The flight was uneventful until TOD. 1. The aircraft didn't descend at TOD despite a lower altitude entered. I had to use vertical speed. Once on the descent path I was able to click on PERF which seemed to bring it down okay, but in the end I had to intervene to increase descent to meet a restraint. 2. During descent there were a lot of stutters. While manually entering a height restriction P3D paused for a good 3 seconds for each number I clicked on and again when I entered on the waypoint line. At this time FPS went from 30 to 60 in cruise to 5 to 10 and below. 3. Just as I turned onto finals P3D just stopped and then crashed. There was no error message. I had AS for P3Dv4 running at the time. Perhaps I should mention that this behaviour has not happened to me with the 717 before. My specs are; i7-4790 CPU, 32GB Ram, 64 bit, GeForce GTX980Ti. W10, P3D V4.1. I hope this info is useful. Cheers Bruce R
  10. I updated the 717 yesterday, Sat 2 Dec, rebooted and then opened P3D. After about 30 seconds on the opening 'Prepar3d' screen, P3d just closed down. No error message. This happened three times in a row. On the forth time I got to the second screen where I chose the 717 and ORBX's YSTW airport. The aircraft loaded and then after about 10 seconds P3D closed down and stopped working. Once again there was no error message. I probably tried another six times to open P3D but couldn't get past the 'Prepar3d' opening screen before it just stopped working and closed with no error message. This morning, suspecting the 717 update install may have something to do with P3D closing down, I uninstalled the 717, rebooted and re-installed, rebooted again and successfully opened P3D with the 717 at ORBX's YSTW, Gate 1. I've now successfully opened P3D twice. The 717 sits on the tarmac at YSTW, C & D, with the frames running between 43 and 50. My specs are; i7-4790 CPU, 32GB Ram, 64 bit, GeForce GTX980Ti. W10, P3D V4.1. I do have two monitors but run by the one computer. I seemed to have solved my problem so this is is for your info only. Cheers Bruce R
  11. Yes, I have the same issue. If I dial in flaps 13 and then later pull my Saitek flap lever back, it go into flaps 18. Clicking on the cockpit flap lever handle sends it back to flaps 13. Bruce R
  12. I agree with Deltamike172. To begin taxiing I ease the throttles forward slowly, hear the engines spooling up and nothing else happens. Ease the throttles slightly more and the aircraft becomes unstuck and screams away. I usually have to immediately brake to slow it down. Bruce R
  13. Bruce R

    T/C and T/D

    I'm not sure what you mean by proper information. I completed the whole form. Is there something I missed? If so please advise what the missed information is and I'll resubmit. Regards Bruce R
  14. Bruce R

    T/C and T/D

    The active autoflight modes were FMS speed, Nav and Prof. Did the same flight again today and more or less the same as the previous flight. Five miles before T/D I wound the altitude down from 25000' to 3000' . This time the aircraft did not begin a slight decent as it did previously. However, as it flew over the T/D arrow nothing happened. It then dragged the arrow all the way to the next waypoint, LADIS. At LADIS it began descending. Screenshots show overhead the T/D with 25 miles to run to LADIS, and then at 10.6 miles to LADIS with the T/D arrow still underneath. The last screenshot shows 10 miles to touch down and still at 20760'. Bruce R
  15. Bruce R

    T/C and T/D

    Sorry but I was unable to reply to my own topic of today with the same title. New download installed, and flying the same route as previously, the T/C and T/D both showed up in the ND. However, approx 10 miles before T/D I wound the altimeter knob down to the next altitude restraint and the aircraft began immediately descending at about 100 ft per min. It flew over the T/D and failed to descent. It continued on descending at about 100 ft per min. I let it go on for a few more miles then gave up. Bruce R