Cameron

Glad you're all set!

Your log shows Gizmo not installed. Did you remove it? This would be the source of your problem. Re-run the installer.

Agreed, and we'll add it in!

Thanks, guys. The problem has been identified and will be shipped in the coming update.

It's quite a bit more complex. I'm not at a computer to create a tutorial, but in short you need to feed command line info to the app, and you need to get elevation source data to cut a whole new tile. You cannot simply use a shp file because MeshTool needs to literally cut into mesh data you feed it for the water to get placed. Also keep in mind that MeshTool cuts version 9 style dsf tiles. It won't look like a smooth transition in 10.

Hi, Guys, We'll look into this. If I had a quick guess it may be out of our control if I think I know what's causing this. SkyMaxx Pro disables X-Plane's cloud art assets, and it's possible Laminar tied these textures in with that kill switch for us. The kill switch is in place to prevent X-Plane from rendering clouds while we do, which saves big time in performance.

...and what John said!

Hey, there, Thanks for the report. Simply as a matter of curiosity, can you check to see what happens in this scenario with HDR off? We 'll definitely look into this!

I have to wonder if this is overload with that GPU and CPU. How much VRAM is in that GPU? Can you remove all plugins except Gizmo and SilverLining as a test?

Correct!

Yes.

Understood! There's no better time than now! (semi joking)

Glad you got it sorted!

I'm mobile today, so sigs don't show. I'll be looking into this for you over the next day. Thanks!

We do not plan 32-bit, but please do further explain your need for 32-bit. Ears are open!

Hi, Can you tell us more about your computer setup please? Thanks!

Run the X-Plane updater.

Use the user interface to tone these down to your liking! X-Plane controls where clouds appear, not SkyMaxx Pro. It simply renders nicer clouds where X-Plane tells it to. Should not cause an issue.

Tbh, those fps worry me. Add a custom airport and what happens? 33 fps on a bare runway, outside the 3d pit...... Sounded too good to be true anyway, again. This is precisely why the test was conducted in an area with a massive amount of objects. The autogen, trees, and roads were set to extreme for good reason, and show a case of settings most people do not even use. As SkyMaxx relies more on CPU to do its job rather than GPU, I don't see much an issue for concern as you bring up.

Shane, Those lines in the log are perfectly normal. If this is the very latest version of XSB then it's possible they still have some sorting out to do. Most people I have seen appear to have their issues solved in the latest build of XSB though. Did you try this without the JAR aircraft as well?

The work in progress section has a thread with information on this. John likes to call it the grey screen of death, and it has been adjusted in this product to not do this.

The problem appears to be an issue with perhaps some DLL files trying to load in 64bit as 32bit. It may be that your computer is missing what it's looking for. Please check your PM box to handle this further.

I understand, dron420, but we have absolutely no interest or even a thought at this point for 32-bit support. I do apologize for the inconvenience!

That's a receipt, and not what I was looking for. Please re-read my reply.

Technically shader tweaking is not condoned by Laminar and is considered a very unsafe move in a commercial product. We'll need to work out a more fail safe measure than this (or Laminar will, anyhow). Thanks for the compliments though!