Jump to content
The simFlight Network Forums

balus

Members
  • Content Count

    19
  • Joined

  • Last visited

Community Reputation

0 Neutral

About balus

  • Rank
    Member
  • Birthday 01/01/1970

Contact Methods

  • Website URL
    http://
  1. gotta love the support available for this product
  2. If you re-read my post you will notice that I have already stated 1. I always have mytrafficmil.bgl disabled (renamed with an old extension) This issue is related to Mytraffic, or how Mytraffic interacts with the simulator.
  3. Having problems with a flight, only when mytraffic 6.0.a is active. Flight is EHAM to KORD with FlyTampa scenery at origin and FSDT at destination, no other 3rd party scenery is active, aircraft is PMDG 747 QOTS, flight plan is EHAM BERG1S UL602 SUPUR UP1 GODOS UM981 NATEB TLA DCT AVUTI YDP N710A ROUND WYNDE8 KORD About 2/3 of the way through the flight I get the NTDLL.DLL error Faulting application name: Prepar3D.exe, version: 3.4.22.19868, time stamp: 0x588f7cbf Faulting module name: ntdll.dll, version: 10.0.14393.479, time stamp: 0x58256ca0 Exception code: 0xc0000374
  4. I have been able to consistently reproduce a g3d.dll error, preceeded by a .NET error CTD, on a flight between KJFK and PHNL with Mytraffic 6; it happens at around the same location 22 32N 156 48W which is about 110 nm from PHNL. I have traffic set to 10% and no GA, Mytrafficmil.bgl has been renamed, if I set traffic to 0% then I can complete the flight. VAS is fine, aircraft is BBS A330, system is i4790 with 16 GB RAM Windows 7 x64, no antivirus or firewall Where do I start looking to solve this, could it be a corrupt Mytraffic flightplan, aircraft model, or something else?
  5. I have been able to recreate this error consistently and the fix is always to rename mytrafficmil.bgl to mytrafficmil.old Flightplan is KJFK GREKI4 JUDDS DCT MARTN DCT TAFFY N621A LOMSI/M082F350 DCT 55N050W DCT 57N040W DCT 58N030W DCT 58N020W DCT SUNOT DCT KESIX DCT MIMKU/N0467F350 DCT REMSI/N0464F370 UL603 LAMSO DCT TULIP DCT LARET DCT OMELO L620 KOMUR M748 ODNEM DCT ERGOM DCT TEGRI M748 OVDOT/N0474F390 L606 TIMUR/K0878F390 L867 RILEX/N0459F270 L867 ENESU ENES1D LTBA FSDT JFK2, no other scenery, crash happens using around an hour after take off Error is Faulting appli
  6. Thanks Pete, Should I be downloading from http://www.schiratti.com/dowson.html? Regards Scott Edit: to answer my own post, yes even though the download is labelled 4.937 it is actually 4.938 and it installed fine thanks again
  7. thanks to both Pete®s and Andy - hopefully I'll get a chance to try this out today - don't you hate how work interrupts! Have a good holiday Pete. Scott
  8. Thanks for all that info - now to keep testing :) edit: hmmm the sub view seems to work, kind of, but the next and previous views don't seem to do what I expected, the views don't cycle
  9. Didn't want to hijack the other thread. Venturing into the world of using FSUIPC to fully control my yoke and pedals for the first time after having owned FSUIPC for quite some time, back to the real early days :) My CH yoke uses the 2 buttons on the left hand side of the yoke (the red ones) to cycle through the views - this emulates the the S key. I have checked the key assignments in FSX and S is assigned to View (next category). I can't see this option in the control list under Buttons + Switches - is it called something else, or am I in the wrong place? thanks Scott
  10. LOL Thanks Pete, that's why I came to the horses mouth....rather than the other end :)
  11. "Please note that FSUIPC4 is a new release and requires that you purchase a registration key. " http://www.fsflighttracker.com/index.html the other is Flightsim Commander, it's buried somewhere in the documentation.
  12. Why is it that add-ons for FSX are requiring a "registered" version of FSUIPC?
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy 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.