Jump to content


Verified Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About jabloomf1230

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

804 profile views
  1. Thanks. I'm sorry to keep extending this thread, but since I've figured several workarounds for the Flysimware aircraft, I'm not going to worry about it and you can close this thread.
  2. Thanks. I thought that was the way the weather radar gauges worked, but it doesn't hurt to ask. SF must get its built-in map radar display data from some online source, the same way that various online weather forecasting sites (Weather Underground, Windy, Intellicast, etc.) do.
  3. Thanks. As per my previous post, where does the WX Radar gauge get its data from if both ASP4 and SkyForce are running? I assume that if the SF weather engine is disabled, no radar data is available from SF. The reason that I am asking this is that SF still displays radar data on its built-in map even with the weather engine disabled. A number of people use that dual ASP4/SF weather configuration, because SF has better cloud textures/structure and SF changes them dynamically, supposedly even with the weather engine disabled. If that's not the case, then I can try some tests with just ASP4, as any previous offline SF run will cause the sim to use its cloud textures. They just won't change dynamically while the sim is running. I agree that the COUATL Python interpreter causes conflicts, but it appears to affecting only the FlySimWare aircraft with the WX Radar gauge installed in the VC.
  4. With the Falcon 50 and REX Sky Force, everything works correctly, no stutters and no CTDs. Do you think the problem stems from me running ASP4 for weather and SF for cloud textures/changes (weather engine off)? If SF had the in-cloud effect like ASP4, I would dump ASP4 in a minute, since the SF interface is more intuitive.
  5. Doing so indicates that ASP4 is definitely injecting weather. I also tried it in my normal mode (every 15 minutes) and both the ASP4 log file and the green text line indicate every 15 minutes. Here's the interesting thing though. I disabled COUATL from FSDT, which is used by GSX and there was no CTD with the Falcon 50, starting ASP4 first, EXCEPT, the first weather injection created about a 3-4 second stutter where the sim display stalls. But then it recovers. After that, no noticeable stutter occurs on further weather injections. I monitored CPU and temps with AIDA64 and nothing unusual happens during the initial stutter, so I don't think that it has anything to do with heat. I run a modest OC on an i7-6700k (4.4 with water cooling) and it has been stable since I got the computer, so that also seems like it's not the cause. Like I said originally when I said this was "solved", there is some inherent conflict among the add-ons that I'm using that only becomes apparent with the two Flysimware aircraft. I do have one other option. I also own SkyForce, but I only use it for the cloud structures. I could try disabling ASP4 and just using SF and see what happens.
  6. I'll have to turn on the ASP weather update notification window, since generally the weather transitions are so smooth in ASP4, that it's often hard to tell visually if anything has changed at all. I'll let you know in few days, after I do enough tests.
  7. Hey Reed, Maybe here's another clue. I just purchased the new FlySimware Falcon 50 and guess what? It does the same thing as the LJ 35A with the WX gauge in the VC (see above). The Falcon 50 (v2.6) was installed into P3d V4.3, Win 10 (latest updates and nVidia driver). P3d CTDs at almost exactly 15 minutes into the flight, but if I start ASP4 after P3d4, it works fine. The Falcon 50 is brand new, so I can't imagine it wasn't tested with the VC version of the WX gauge.
  8. The gauge DLL file is dated 9/18/2018 and is 140.0.45. The module DLL file is dated 10/5/2018 and is version 1.44.1. I did find another "rogue" older version of the gauge and deleted it, but it was in an aircraft folder that I haven't used in a while. I don't know how the sim would accidently find that over the version that is in a specific aircraft's subfolder. Is there something wrong with my installer file? The msi is wxradar_20181005.msi. Uninstalling and reinstalling made no difference. Editing the gauge for the LJ 35A info via the WX gauge installer made no changes to the panel.cfg file, except the file modified date. Anyway, I have a feeling it something to do with my installation setup of the Flysimware aircraft and P3d4 and not the weather gauge. Other people that were reporting CTDs with the LJ 35A have said that the latest update fixed the CTD problem for them. Besides, the other aircraft that I have that utilize the WX radar gauge in the VC work fine. And prior to the P3d 4.3 update, the WX gauge worked fine in all aircraft. All this, just in time for P3d 4.4.
  9. I got the WX radar to work with this aircraft, but the solution was very odd. All other aircraft with the VC version of the WX radar are working fine for me in P3d 4.3 with the 5.1 update. The LJ35A would CTD after about 15 minutes, which coincidentally is my setting for the weather injection interval. I disabled the 2D version of the WX radar gauge, as some LJ 35A users with the same problem had suggested on AVSim to try that workaround. After experimenting with disabling various add-ons, I discovered that if I start ASP4 before P3d, the CTD happens. But if I start the default P3d scenario, change the aircraft to the LJ 35A and then start ASP4, it works fine and no CTD. It will remain one of the mysteries of flight simming, but there must be some corruption of the LJ 35A's internal variables, although it's not worth worrying about, since the problem is solved.
  10. Michael, I still get a CTD about 10-15 minutes into a flight with the Flysimware LJ 35A. The VC WX gauge continues to work okay in the Milviz 310R Redux and the TDFi B717. This situation is unchanged over the behavior of the last beta that I was sent. The event log shows this: Faulting application name: Prepar3D.exe, version:, time stamp: 0x5b2c3263 Faulting module name: KERNELBASE.dll, version: 10.0.17763.1, time stamp: 0xc3164c39 Exception code: 0xc0020001 Fault offset: 0x0000000000055299 Faulting process id: 0x3c4 Faulting application start time: 0x01d46cc5b6202dd8 Faulting application path: G:\Program Files\Lockheed Martin\Prepar3d v4\Prepar3D.exe Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll Report Id: ecb132f9-0110-4027-8316-1c5a6680ee1a Faulting package full name: Faulting package-relative application ID: I do not get any CTDs when using any other aircraft other than the LJ 35A with the WX gauge. Jay
  11. PM the developer to see if he will provide you with a test version of the WX Radar gauge:
  12. Just to let everyone else know, the most recent version of the WX Radar gauge that I got from Naruto-kun fixed the CTD for me.
  13. Oops. Now I'm getting the same CTD and error. This is with the MV310 Redux.
  14. Just set cloud.fx to "read only" in properties. SC TD 4 still installs the textures but doesn't alter cloud.fx.
  15. cumulus01 is the filename used for the lower cloud layer texture in FSX and P3d. You choose one of the 16 sets and it copies the chosen SC version to your sim and overwrites the previous version of that file. Note that there can be multiple versions of this so-called lower cloud layer, each with its own base elevation and layer thickness.
  • Create New...