sundog

Actually I just tried it here (SMP 4.7.2 + XP 10.30b7), with an overcast layer over Seattle with SMP in "HD Puffs" mode, and the lights do not show through the clouds at all. Even broken cumulus seem to be doing the right thing. Perhaps it depends on your graphics settings? HDR vs non-HDR might make a difference. Another possibility is that your cloud layer was thinner than mine.

I wasn't aware that this was addressed in the 11.30 beta. We can certainly look at it for a future update. You might want to try selecting different overcast representations, as they may behave differently.

Whoah, haven't seen that before. If you can make it happen again, please send us your log.txt file after ending your flight so we can see what exactly you did.

Well, that log does seem to be implicating the TBM. SMP 4.7 does use more system resources than 4.6 did in terms of memory, but I don't know if that might be affecting it.

A brief update - we think we have a fix for Mac users who found that SMP 4.7 caused a crash when starting a flight. Fundamentally 4.7 used more video memory on the Mac than 4.6 did, and this pushed some systems over the edge. We found some ways to reclaim that memory, and another update is on the way to help those affected. Sorry for the trouble this caused anyone. We did test on several Mac systems prior to releasing, but none of them exhibited this problem.

No. Real Weather Connector is a connector between detailed weather data, either provided by X-Plane or external add-ons such as FSGRW, and SkyMaxx Pro. It does not generate its own weather data; it parses the data it finds and transforms it into cloud formations that SkyMaxx Pro can represent.

It would be really helpful if you could provide any crash log your Mac may have written after this, as well as your metar.rwx file. I am seeing a few reports of crashes from Mac users, but we can't reproduce them here, so we're not really sure what's going on yet. It looks like running out of memory, but you should have plenty.

Yes, I as well as a few users I've seen on Facebook have reported it working with ASXP.

Yeah, actually we just heard from them. They've identified the issue and we're working with them on a solution.

Thanks for providing the crash log. As Cameron said, I don't think that crash has anything to do with RWC. But it's puzzling - I just tried our final release on my Mac here and it loads up and works fine, nor did any crashes arise at all during our beta testing. Your log suggests the crash happened while MacOS was trying to allocate memory internally while compiling our shaders. However, it looks like you have 32GB of RAM and an 8GB video card, which should be plenty. It's possible it is some issue specific to your OS version or configuration, which would make it difficult for us to track down. I did however look at all of the code that changed in the area that crashed for you, and made a few changes in it for our next minor update (expected soon). It's nothing that would explain a crash really, but sometimes the Mac video drivers can be very particular about things.

Please open a support ticket with X-Aviation if you haven't already (they produce and support the installers, not us - otherwise I'd try to help.)

You should probably start with the TBM900 support forum and see if they've seen this before. You're right that the log isn't very telling, but it seemed to crash immediately following the load of one of their plugins, so they might at least know what it's a symptom of. SMP has no direct interactions with aircraft, so whatever is going on is probably more complicated - such as running out of memory, or some add-on writing outside of its memory bounds. I'm just starting to go through SMP 4.7 support issues this morning, so if I find any evidence that we're writing outside of our memory bounds I'll update this post.

This sounds like a question for FSGRW and not us. SMP / RWC does not play a role in temps or pressure.

Sounds like you were running out of memory or video memory, from just having one add-on too many - or one custom scenery package too many.

No, the seasons you see in the settings box are the only ones available.

It shouldn't really matter - TerraMaxx just overrides default scenery assets. It doesn't really fit any of those categories. Just the let installer put it where it wants. I would recommend putting it at the top, however, to ensure other packages don't interfere with it and create confusing results.

It's close! There are just some issues in the current X-Plane 11.30 beta run affecting it, that we want to be sure won't be a problem in the long run.

It's based on the month and your latitude. As it's December and Seattle is pretty far North, its best guess is "winter" since we don't model micro-climate effects, such as how Seattle's temperatures are moderated by the Pacific Ocean. We don't have any data available on actual snowfall to work with. So the short answer is - yes, just set it to autumn if that's the conditions you want to see. We don't claim that automatic mode is a faithful rendition of what's actually on the ground right now in real life, it's just a best guess based on the latitude and time of year.

Opening a ticket was the right thing to do. Please give X-Aviation a few days to respond; if you send follow-up messages, it'll just move you to the back of the line again. The installer is made by X-Aviation and we don't really have any insight as to what might cause this. But they should.

FYI we do seem to have finally cracked the nut on VR support for SkyMaxx Pro - at least it's working here with our Vive Pro. We're waiting to get a build into beta testers' hands. Stay tuned!

This issue is in X-Aviation's hands - it appears to be a problem with their licensing system, and not with TerraMaxx itself as far as we know. The last I heard, they were hoping the latest TBM update would fix it - but it sounds like it didn't.

That haze color is not coming from us; all we draw are the clouds - so I doubt re-installing SMP would have any effect. Really not sure what might be going on there.

I've seen a few more posts on this topic this morning, and there's a theory that the TBM900 is somehow interfering with Terramaxx's ability to verify its license through Gizmo. That would be a plausible explanation. But it's something X-Aviation will have to sort through. At any rate, do open a ticket on the issue so it gets their attention.

Please open a support ticket with X-Aviation on this - whatever is going on has to do with the specifics of your licenses, and we have no way of looking into that.

We are currently testing a 4.7 release with VR support and some performance improvements. It hasn't gone into beta testing yet, so no estimate as to a release yet.