Cameron

An update on the situation... We have made contact with the developer of XPRealistic, and we feel we have a handle on why this is occurring. XPRealistic is writing to some required view monitoring datarefs every frame which SkyMaxx Pro also monitors. This is causing numerous allocations of depth buffers until things eventually explode. We are discussing how to deal with this. There are talks of us creating a workaround, and XPRealistic coming out with an update. As we get more information we will let you know.

Hi there, It's an unavoidable issue with "volumetric" clouds that there is no depth to the clouds themselves, only to the volume they are drawn within. That's why you're seeing terrain artifacts like that. It is another thing that is less of an issue with RWC because the volumes are smaller. Thus far we have not found a way around this. Luckily it is not "always" happening.

Glad you're enjoying it @pdg17!

Sounds about right!

@Noksi was responding to this post: Not sure on yours @simnut. We'll keep digging, but right now you're still alone in the trenches so to speak.

ADMIN NOTE: SkyMaxx Pro v5.0.1 has been released and supersedes this post for the time being: ------------------------------------------------------- We have received numerous reports of insanely high RAM usage up to the point X-Plane eventually crashes and/or FPS are simply unsustainable. In every one of these instances, XPRealistic has been in use and the culprit of the issue. Our best guess at the moment would be that they are somehow changing the format of the depth buffer, which would mess up our attempts to copy it for our shadow and soft particle effects, and ultimately causing terrible memory leaks. The fix on this is potentially going to need to come from their side. As of this writing I have reached out to the main developer to offer him a copy of SMP v5 so we can work together. In the meantime, you have a couple of options: 1. Remove XPRealistic entirely. or try... 2. Unticking "Natural movements" and "Ground Shakings" in XP realistic v2. We have received a report that #2 does work, but in all cases option #1 does for sure resolve the insane memory leak. I will do my best to keep everyone updated here on how the XPRealistic developer works with us.

When RWC is in use vs not, how things are rendered are done differently, all the way down to the actual appearance of the clouds. Needless to say, RWC is the way to go.

Enjoy!

Are you using RWC in this situation, or not? Have you moved the draw distance slider full right?

Hi @Fab10, This has been narrowed down to XPRealistic being the culprit.

Hi there, We have narrowed this down to XPRealistic being the culprit, which you have installed. Please remove this and try again.

@Motosuwa Than YOU! Your help was greatly appreciated!

I hear you. Just letting you know what others are saying. We're on day one here, and quite known to do updates. Whatever we can gather and find we will. I'm off to have a chat with XPRealistic now. Thanks to all for helping us out!

See reply above.

@simnut we have now had over ten people confirm this. We just have to face realities and try to work on it from here.

@sundog will know best on that one. Does your FPS go up? Now getting numerous reports that disabling it DOES go up. If so, I'll be contacting the developer to get him a copy of SMP 5 and see what we can do to resolve this. Just need more confirmations.

Haha! I get you have your preferences. Right now we're just narrowing down who we need to talk to to fix this.

Can you corroborate @OuterMarker @Motosuwa?

We'll certainly take a look at this! It may not be an issue on our end though. We'll certainly reach out to the developer.

@Motosuwa, Thanks much! Please do as I described one post up as well. Pain in the butt, I know.

Okay, we're getting somewhere! That tells me this is not related to aircraft at least. Unfortunately the only way to narrow this down will be to move plugins one at a time from the _bak folder to the new plugins folder. I would love to know what the culprit is here, and really appreciate your time!

@Fab10, Thanks for the report! Can you please try the same with a default aircraft in the cockpit? Like the Cirrus Jet.

All great information, guys. Thanks! @Motosuwa and @OuterMarker, While we test, can you both do me a favor here? Let's rename your plugins folder to plugins_bak, then create a new folder called 'plugins'. Move SilverLining and Gizmo64.plugin from plugins_bak to plugins. Now start X-Plane. Does this in any way improve the situation? Can you both also tell me which version of Gizmo you opted for?

Hi, yes. I'm not saying this is permanent. We're on day one here and I don't know what in ASXP was causing to flip out. Mind you, this was on ONE machine. While we diagnose, I just need to make sure we gather common problems and get this all noted. Can you please try without ASXP active/on at all?