Jump to content

flynman33

Members
  • Content Count

    304
  • Donations

    $0.00 
  • Joined

  • Last visited

Posts posted by flynman33


  1. I have this same issue "AFTER installing AIG-OC" on my hard drive.

    [20:27:10.243] INFO SODE.FSLOOP :  - SimObject 'Flightbeam_KPDX:Jetway 1 GATE_C 5' [kpdx_jetway]. ID: 135
    [20:27:10.243] INFO SODE.FSLOOP :  - SimObject 'Flightbeam_KPDX:Jetway 1 GATE_C 3' [kpdx_jetway]. ID: 136
    [20:27:10.243] INFO SODE.FSLOOP :  - SimObject 'Flightbeam_KPDX:EDP KPDX' [12bPilot_SODE_Environmental_Data_Probe]. ID: 133
    [20:27:10.243] INFO SODE.FSLOOP : ### FILTERING OBJECTS: R=40000m, Bubble Lat/Lon: 45.742366, -122.596179 ###
    [20:27:10.346] INFO SODE.FSLOOP : ### Active SimObjects: 63; Active Wind Data Probes: 1 ###
    [20:27:51.285] FATAL SODE.WATCHDOG : Sim Process running test failed!
    [20:27:51.298] DEBUG SODE.FSPROCESS : Cleaning up Memory...
    [20:27:51.315] DEBUG SODE.FSPROCESS : Removing Top-Menu structure...
    [20:27:51.315] DEBUG SODE.FSPROCESS : Closing Connection to FS.
    [20:27:51.425] INFO  : Terminate SODE.

    I was flying the PMDG 737-7 out of Flightbeams KPDX to CYVR. When the aircraft crossed the BTG VOR 10 miles north of PDX the screen would freeze and then CTD.

    I disabled my AIG AI aircraft and deactivated SODE and was able to fly 15 minutes before I terminated the flight. Then I disabled the AI function of SODE and enabled AIG and had the same freeze over the BTG VOR again. I also deactivated SODE and activated AIG with the same CTD at the same point.

    Sounds like 12bpilot has some work cut out for them.

     

     

    Randy

     

     


  2. So I'm going to throw this back out for another discussion. My current system has an Intel 6700k OC'd to 4.7.Asus z170-P MOBO, 6GB 3200 DDR4 Crucial RAM, 750 WT PSU and a EVGA GTX 1080FTW2 GPU.

    I have been looking at building a new system to facilitate P3dV5 and MSFS 2020. My thoughts were to buy a I7 9700k CPU and OC it to 4.7/4.9 and an Asus Z390 MOBO and bring my PSU/RAM/SSDs and GPU over to the new system.

    Would I be better to UPGRADE to an EVGA GTX1080ti and sell my current GPU or go for a new CPU and MOBO. I am reading the 2080 GPU are really not worth the extra cost. What would you do?


  3.   The time has come to move to Windows 10 so I can consider MSFS 2020 and have better security. I will be using the Media Creation tool.

    Do I need to delete everything P3dv4.5 related off of my hard drive and reinstall everything all over again after the upgrade.

    If you know of an easier way to complete this task I am all ears. If you have any recommended Youtube videos please provide the link.

    Thanks

    Randy Smith
     


  4. 7 minutes ago, vgbaron said:

    Your best bet is to uninstall P3D from the C drive and reinstall to E;  Depending on how your addon scenery was installed you should have no real issues just mapping in the scenery library. It really depends on the scenery, if they have registry entries that point to the old location, you'd have to modify those. Maybe a simple reinstall. 

    I'd say try it without reinstalling your addon scenery first but knowing that if it doesn't work you will have to reinstall.

    Vic

    I will keep the scenery files in tact and see if I can map them successfully  throught the scenery library. I am though going to delete my 3rd party aircraft and reinstall them to the new ssd.

    I gather I will need to keep my C/Program Files/LM/P3d folder and not delete it until I know what I can do.


  5. Last night I installed my SSD. I then downloaded P3dv4.5 and tried to install it to my SSD which I have labeled my E/Drive. I pointed the P3d install to the e/drive and commenced the install. It did not install to the SSD but did a sort of repair to the current P3d on C/drive. I now understand that I cannot have 2 versions of P3d on the same drive.

    So if I were to remove the Client/Content/Scenery installers off my C/drive along with my 3rd Party aircraft. Could I leave my 3rd party scenery files on the c/drive and then map them through the scenery library to the ssd and still get fast loading times. Is there anything on the P3d Forums about this.

    How would you move P3d to a SSD if it was you. I want the SSD to be a dedicated P3d Drive...


  6. On 4/27/2019 at 9:09 AM, Farlis said:

    Rob McCarthy wrote on the 16th about a hotfix in the "next couple of weeks".

    The 16th was Tuesday last week.

    Certainly you see that "a couple of weeks" hasn't past.

    Today is 2 weeks,

    I have heard that Orbx is part of the problem.

    I went back to 4.4 but the reversal has brought the same issues with it.


  7. I have all the sudden without touching anything on my settings or PC have lost all ability to have input with my Thrustmaster Rudder pedals and P3dv4.5.

    I am able to re-calibrate and save through the P3d settings but no response is the SIM and they are operating correctly inside  the device and printer menu.

    Does anyone have a good starting point to resolve this. I have tried to re-calibrate with no luck. Thanks


  8. On 4/10/2019 at 5:11 PM, Bert Pieke said:

    If you are experiencing fps drop..

    1. Did you delete your Shaders folder?

    2. Are you using speedtrees?

    In my case fps are unchanged and smoothness is better.

    (Shaders deleted, and no Speedtrees in use).

    What are Speed Trees. How do you disable them?

    Thanks

    Randy


  9.  

    Last night I was doing a KLAX/ZSPD filght with the PMDG 747-800.

    About 6 hours in the PC and P3dv4.5 crashed. The below is my AppCrash report. It logged 6 errors before it CTD.

    Any ideas how to fix this. It happened under P3dv4.4 as well recently.

     

    Thanks

    Randall Smith

     

     

    Version=1
    EventType=WindowsWcpStoreCorruption
    EventTime=131994458764446067
    ReportType=1
    Consent=1
    UploadTime=131994458768502067
    ReportIdentifier=0726d6f8-5c36-11e9-8512-2c4d544ed578
    Response.BucketId=2116719330
    Response.BucketTable=515412878
    Response.type=4
    Sig[0].Name=OsVersion
    Sig[0].Value=6.1.7601
    Sig[1].Name=Type
    Sig[1].Value=MissingWinningComponentKey
    Sig[2].Name=Path
    Sig[2].Value=x86_policy.14.0.avg.vc140.mfc_f92d94485545da78_14.0.27012.0_none_d411c77bf2be0a74
    DynamicSig[1].Name=OS Version
    DynamicSig[1].Value=6.1.7601.2.1.0.768.3
    DynamicSig[2].Name=Locale ID
    DynamicSig[2].Value=1033
    State[0].Key=Transport.DoneStage1
    State[0].Value=1
    State[1].Key=DataRequest
    State[1].Value=Bucket=2116719330/nBucketTable=515412878/nResponse=1/n
    FriendlyEventName=WindowsWcpStoreCorruption
    ConsentKey=WindowsWcpStoreCorruption
    AppName=Windows Modules Installer
    AppPath=C:\Windows\servicing\TrustedInstaller.exe

     

     

     


  10. 19 hours ago, Jim Young said:

    I tried to replicate but did not get a crash enroute.  Used the following route -

    KSEA COGLE V349 HOWSE J528 YQU J526 YOJ V321 YHY J526 YZF ZF J477 CB BR84 LT 8300N05500W 8300N05000W 8300N04500W 8300N04000W 8300N03500W 8200N02500W 8100N02000W 8000N01500W 7900N01000W 7800N0500W EXITA UP190 INSEP UP65 SDA P65 VANOS A74 PELOR G476 ULWC B958 BD UUEE

    This is my FSUIPC log of the flight -

      Reveal hidden contents

    20594 Initialising SimConnect data requests now
        20594 FSUIPC Menu entry added
        20594 ... Using Prepar3D with Professional License
        20609 C:\Users\JimY\AppData\Local\Lockheed Martin\Prepar3D v4\Prepar3D_Default.fxml
        20609 G:\Prepar3D v4\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air
       157687 G:\Prepar3D v4\SimObjects\Airplanes\QualityWings 787-8\Boeing 787-8 RR.air
       291453 Loading Complete ...
       292140 User Aircraft ID 1 supplied, now being used
       292140 Aircraft loaded: running normally now ...
       292203 System time = 12/06/2018 13:14:53, Simulator time = 10:11:02 (17:11Z)
       292203 Aircraft="QualityWings 787-8 Boeing Dreamliner 8 -Exp_CP"
       293187 -------------------- Starting everything now ----------------------
       293187 ASN active function link set
       293187 Ready for ActiveSky WX radar with additional data
       293281 Using "G:\Prepar3D v4\Modules\GFDEV64.DLL", version 2.2.8.0
       298594 Advanced Weather Interface Enabled
       304969 Weather Mode now = Theme
      3202344 Sim stopped: average frame rate for last 2910 secs = 44.0 fps
      3202344    Max AI traffic was 176 aircraft (Deleted 0)
      3223531 **** Restarting traffic scanning due to non-reception ****
      3339625 Sim stopped: average frame rate for last 116 secs = 39.5 fps
      3339625    Max AI traffic was 176 aircraft (Deleted 0)
      3525047 Sim stopped: average frame rate for last 169 secs = 37.6 fps
      3525047    Max AI traffic was 176 aircraft (Deleted 0)
      5670828 Sim stopped: average frame rate for last 2128 secs = 44.0 fps
      5670828    Max AI traffic was 176 aircraft (Deleted 0)
      5673094 === Closing session: waiting for DLLStop to be called ...
      5688109 === DLLStop called ...
      5688109 === Closing external processes we started ...
      5689109 === About to kill any Lua plug-ins still running ...
      5689250 === Closing global Lua thread
      5690265 === About to kill my timers ...
      5690469 === Restoring window procs ...
      5690469 === Unloading libraries ...
      5690469 === stopping other threads ...
      5690469 === ... Button scanning ...
      5690562 === ... Axis scanning ...
      5690672 === Releasing joystick devices ...
      5690672 === Freeing macro memory
      5690672 === Removing any offset overrides
      5690672 === Clearing any displays left
      5690672 === NOTE: not calling SimConnect_Close ...
      5690672 === AI slots deleted!
      5690672 === Freeing button memory ...
      5690672 === Closing my Windows ...
      5690672 === Freeing FS libraries ...
      5691672 === Closing devices ...
      5691672 === Closing the Log ... Bye Bye! ...
      5691672 System time = 12/06/2018 14:44:50, Simulator time = 11:59:21 (09:59Z)
      5691672 *** FSUIPC log file being closed
    Minimum frame rate was 20.0 fps, Maximum was 81.6 fps
    Average frame rate for running time of 5324 secs = 43.7 fps
    Maximum AI traffic for session was 176 aircraft
    Memory managed: 2504 Allocs, 2503 Freed
    ********* FSUIPC Log file closed ***********

    Activated UTLive and ASP4. Flew at FL350.  The first part of the flight to YOJ, I flew normally but used 4x's acceleration until YZE.  I then jumped to EXITA using QW's awesome Jump To feature.  I then Jumped TO ULWC where the TD began and then into UUEE on 24L.  Beautiful Orbx PNW scenery outbound from KSEA.

    When you installed the update 1.1.1, did you update 1.1.0?  Or, did you completely uninstall, download 1.1.1, and install?  Did you install with Admin Privileges?

    Did you use FSUIPC's Autosave feature - known cause of freezes.  Try flying w/o that feature if so.  If you want to get to your destination over 4600 nm's away, use the Jump To feature in QW.

    Strange the problem does not occur with the PMDG 747 but I have seen that happening before.  You do know there are two dll.xml's, one in the same folder as the p3d.cfg and the other, the default, in the same folder as your scenery.cfg.  When P3D loads to the setup screen, it loads all of the modules in the these two xml's.  Many are not needed but they load anyway.  There could be a conflict between one of these modules and your QW 787 but I have about every module known to mankind loading when I start the sim.  Crashes do not occur immediately if there is a conflict.  Sometimes there is no crash whatsoever so it happens randomly.  This is why the AVSIM CTD Guide recommends you disable these two dll.xml's just to see if one of the modules is causing the freezes.  You won't be able to use some features like the FSUIPC.dll or ActiveSky but you are just testing to see if this fixes your freezes. 

    As you know, if there were freezes caused by the QW787, it should be happening to everyone and so far we have not seen that.  So there is something external that only you have that is causing the crashes.  For instance, some own Carenado aircraft and that program loads the CMeteoXml.dll into one of the dll.xml's.  It evidently is used to display weather in their aircraft but not entirely sure.  Sometimes it causes a freeze or crash and it happens randomly.  I never had a problem with it until I loaded some really nasty weather and tried to fly the CS757.  The sim crashed almost as soon as I loaded the scenario.  Disabled Active Sky and the crashes stopped.  So I uninstalled/reinstalled AS several times but always got a crash which I have never seen before in calm or clear sky type weather.  Only in heavy weather.  I disabled the CMeteoXml and the problem was gone.

    In P3DV4, you can also run into periodic freezes/crashes when the .xml's and .cfg's in P3D are not encoded properly.  If you use Lorby_Si's Addon Organizer, open it up and click on the icon in the upper right corner to see.  If so, just click save and that will fix them all.

    Best regards,

    Jim

    Jim,

    I was on the BETA team for the 787 and did not have issues till the release version

    I did a full uninstall of the RC2, the last beta version and full install of 1.1.1 with ADMIN PRIV.

    Again, when the 787 software is installed I can not fly any aircraft without a CTD. Without it.....no issues,

     

     

    19 hours ago, Jim Young said:

     

     


    • 29 minutes ago, Jim Young said:

      I cannot replicate.  Moving to CTD Forum.  You need to provide an AppCrashView or EventViewer report showing the faulting module, if any.  If no faulting module, then disregard.  I will try to replicate by flying the KSEA/UUEE flight.

      I had no Fault Module report. Just a CTD and strange noise. With the 787 software uninstalled I do not have the issue. I believe it is with the QW software.


  11. I discovered that I could not fly other developers aircraft as well without the same problem.

    So I removed the 787 from my hard drive and loaded up the PMDG 747-4 and did a KSEA/UUEE flight without an issue. This is the same flight I had been trying to complete with the 787.

    There seems to be an issue with the QW V1.1.1 787 software.


  12. This happens no matter what aircraft I fly

     

    When I fly the QW 787I have not checked the WXR box so I am not running weather.

     

    The model will CTD on the runway before T/O roll, after T/O roll, during climb and any point along the flight, it happens at random and it also freezes my PC. It can happen when clicking on any gauge. Generally before 90 minutes of flight.

     

    When it freezes it makes a strange audio noise that sounds like cards clicking on the spokes of a bike. Also just a hum.

     

    I don't believe it is GPU driver related. I have no event viewer or APP crash report to share

    tmpt-M.jpg

     

    Thanks

    Randy

×
×
  • Create New...