Jump to content

Recommended Posts

Posted

It in Juneau, Alaska.

 

You are right, it is caused by the date, in November the sun is no so high at this location.  But for my point of view, they are too dark for this time of year.

 

When I changed the date, the clouds remain dark evens after I redraw them.   I had to switch back and forth to an other location for the cloud to appear normal.   Maybe some code missing to detect date change in x-plane ??

 

Thanks for your response.

  • 2 weeks later...
Posted

I'd agree the clouds are a tad bit too dark, I cranked the cloud shadow slider control length down to about 30%. Also turned cloud reflections off, I didn't think they were too realistic, and could use less hit on the graphics. Speaking of which I received a hard to believe warning the first time I ran this update saying my settings (out of the box) were dangerously high. I'm running a 6-core processor with 2 GB of graphics VRAM.

Posted
2GB of vram is borderline very small these days. I'm not surprised of this in the least! On a 27 inch display, for example, X-Plane will eat that for lunch without much of any modification.

Hell on my 1080p monitor I use up almost all 6GB of my VRAM.

Posted (edited)

You can get away with 4GB of VRAM with 1080p/1200p and still have decent rendering settings, but of course it depends on the scenery and the plane. I used a GTX 770 with 4GB until recently, which was ok.

 

I changed to a Titan X woth 12GB, which of course is a bit overkill for X-Plane 10 (a 980ti is more than adequate), so there aren't any VRAM issues to be expected.

Edited by mgeiss
Posted (edited)

I received a hard to believe warning the first time I ran this update saying my settings (out of the box) were dangerously high.

 

Any custom scenery installed? That can eat memory alive. If you got this message with our default settings, it means you were running close to the edge beforehand.

Edited by sundog
Posted

Any custom scenery installed? That can eat memory alive. If you got this message with our default settings, it means you were running close to the edge beforehand.

The only variable changed before getting this warning was the skyMaxx update itself.

Posted

The only variable changed before getting this warning was the skyMaxx update itself.

 

And that makes sense since it's a SkyMaxx feature to give you such a warning! You didn't really answer Frank's question at all.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...