But tried to go to Challenger 300 with new sasl and had CTD, so the new sasl does not work with every plane and this was totally clean install. Also could switch to non sasl planes and switch back with no CTD. Do not know what LR did for this drop in fps, but they sure did something.Įdit: Just checked the following planes and they all worked with the new sasl with no CTD when switching: 172/185/F33/C337/C340/PA34/PA32/M20J and Alabeo D17/C188 Sukhoi26/R66. To compare, started 10.36 with 152 at KSEA had 21fps with extreme res and 2258 meg textures, with SkyMaxx Pro 3(the clouds do look better than stock) and other plugins and lots of custom scenery. Using the 152 had fps of 20 with 255 meg of textures, this with 2GB video card. Using El Capitan.ĭisappointed in 10.41, used the settings that it starts with, high res. So it appears that the 2.4 sasl works most of the time. The DA40 had no sound and the prop artifact that shows up. GNOME Commander, Yes, Yes, Yes, No, Yes, Yes. The following planes I put the new 2.4 sasl in plugins folder and they started and I could switch with no CTD. The following tables compare general and technical information for a number of notable file. Earlier posts had suggested we may have to wait for Apple to sort out, but it now appears that the SASL developers were able to do the fix Here, I may wait for the official update, or try it on a duplicate folder. I have no idea whether this will work in the Flyjsim and others' airliners, which do have DRM, but they usually use key files. The only ones that won't work are the G-1000 altered C206 - Dan already mentioned that one - and my REP equipped Centurion. Not worried if it goes wrong, because I always have the original zip files saved. I'll correct the others over the next few hours/days. The most advanced dual pane file manager and file transfer client for macOS. I wouldn't have thought it matters if the particular plane doesn't call for it, but I suspect Dan will put me right on that! With CRAX Commander you can manage your local and remote files easily using multitabbed, dual-pane and user-friendly interface. I noticed an extra file in the components directory under the data folder, but I copied it over anyway. I think the critical changed files are in the "64" folder - the. I had a look inside the folders of 2.4 and the earlier ones, and decided to just overwrite the older SASL (or just delete the folder and copy in the new). Maurice, I copied the new SASL into a couple of Carenado's planes last night, and the planes performed as before, but HOORAY! - no crash on exit, and I could change between them and exit XP without a crash.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |