Worth noting that it appears some older XP11 aircraft sucessfully modified to work in XP12 (not overly complex etc) have hit a major hurdle with the latest update to the beta (12.08.b2) not sure why and cannot find out why but the FPS which was fine for previous versions just hits the wall with a couple of these older aircraft - e.g RW Design DHC-6 Twin Otter worked fine until 12.08 still works but the FPS went from 60 as normal on my system to 30 (but only for a default livery) change the livery and the FPS dropped to below 20 effectively a 60% plus loss of performance.

Another carryover bites the dust until it is updated (If it will be which I doubt). 

Others report same issue with some models various causes ascribed; LUA Scripts Plugs ins etc - no these are all working fine for me it is the graphics display and the livery display that has the issues. Why this would be I have no idea and no logical explanation. 

@coastaldriver I have the same issue with the RWD DHC6. The SASL code needs updating apparently. Check your PluginAdmin and you'll see it is eating about half of the plugin load.  I know zero about SASL.

The Pedrovl model still flies great. Not SASL equipped.

2 hours ago, dolph98 said:

@coastaldriver I have the same issue with the RWD DHC6. The SASL code needs updating apparently. Check your PluginAdmin and you'll see it is eating about half of the plugin load.  I know zero about SASL.

The Pedrovl model still flies great. Not SASL equipped.

Thanks will just have to let it go, like a lot of XP11 stuff it falls into the abandoned category. (Not abandoned enough though for them to still be getting something back via sales via the Org Store!) Seems lot of talented people had time on their hands during Covid but since then merciless realities of life outside of computers has dictated otherwise. especially the one man band developers quite disappointing but not the end of the world. I have tinkered with a few but reach my limits on a lot of stuff because either of stuff like SASL about which I know zero or you hit the need the model and have to use and be a master with Blender to alter or repair something. 

Doph thanks for that. As a matter of interest I got an update for the older XP11 Beechcraft D50 or Twin Bonanza with a new XP12 version which has been parked for months waiting for an update. Exactly the same problem. Load the default livery FPS and performance is brilliant (60-80FPS)  change the livery and it just grinds to a halt (no more than 20FPS). I have submitted a bug report to LR! I could have expected the RW Twin Otter but a brand new out of the box XP12 model via the Org store?

Initial response over at XPlane.org that it appears something is happening when the relevant or a dataref is accessed to change a livery! What is going on they are not sure! I might add that for me it is affecting all models but for most including Laminar the loss was not great but still present (lets say 70 back to 46 for example). See where it goes.

This is becoming a real can of worms at the moment. XP12.08b3 clearly fixed the issues in pure XP12 models and some XP11 updates but only some! For aircraft that were designed and built for XP11 that have not been gone over by the developer with a fine eye and carefully or not all! It is showing that some (not all) developers model builders need to update SASL and revist the underlying datarefs as well. 

I cite the example of an updated product for XP12 (that shall remain nameless - the vendor just said well thats what you get your using the Beta version! in other words bad luck for you) that now has some really crazy behaviour with the power and mixture levers if moved will not resynch and just freeze in the wrong position. Exactly the same thing for an non updated product that worked fine until 12.08 and is now basically busted with both the livery issue and the crazy power lever issues as well. Sigh! 

I still don't see a problem on my system when changing the livery on my planes, but I do have a SASL problem on some planes, including a particular store-bought plane for XP12 which shall also rename nameless because it is a great airplane with older betas.

I filed a bug report with LR, with good pictures and the logs and all that, proving the difference between v12.0.7r1 and v12.0.8.3. They changed something under the hood and according to my notes, it started with v12.0.8.1.

Updated XP to v12.0.8rc1 and the SASL issue is fixed. Holy cow! Thanks LR, but why did this happen and why no mention of it in the patch notes? Seems like it was a pretty big deal to me.

Agree, it is fixed with what I can only call a Hot Fix. Yes it was a big deal. Another gent has spent several days recoding the word not allowed thing and SASL - not yet released or made it available, guess he will not be impressed either!

4 hours ago, dolph98 said:

Updated XP to v12.0.8rc1 and the SASL issue is fixed. Holy cow! Thanks LR, but why did this happen and why no mention of it in the patch notes? Seems like it was a pretty big deal to me.

You were most likely seeing

Quote

XPD-14774 – Performance Regression reading “sim/aircraft/view/acf_livery_path”.

which affects any plugin trying to access it.

Edited November 28, 20232 yr by Bjoern

@Bjoern Agreed. I noted it on the first beta 12.0.8.1 and watched it with all my SASL planes. Yet I couldn't find anybody else saying something about it. I never did see anything negative happen when I changed liveries or anything like that. Believe me, I tried. I try all complaints I read about to see if I am affected and this one was strange.

So when I reported it, it was at a point where I couldn't fly any SASL aircraft, even with my lowered settings especially for SASL planes.

I have one aircraft that uses SASLfree and it has zero FPS hit. Why would that be? I don't know SASL but I will be wary of buying any planes that use it from now on.

4 hours ago, dolph98 said:

I will be wary of buying any planes that use it from now on.

Welcome to the club. Granted, commercial SASL has always taken up ~15% of XP's performance, likely because of copy protection and encryption checks. Additional performance bugs in XP12 plus the "dead in the water" rissk when the dev calls it quits makes me avoid all sorts of DRM by now.