• Content count

  • Joined

  • Last visited

Community Reputation

489 Excellent

About sundog

  • Rank
    Advanced Member

Contact Methods

  • Website URL

Profile Information

  • Gender Male
  • Location Orlando, FL
  • Interests Real-time environmental effects

Recent Profile Visitors

5,508 profile views
  1. Not setting correct textures.

    The current system just uses latitude and the month to estimate the season, and can't account for micro-climates such as England's. Keep mind 51 degrees latitude is the same as Canada and some pretty cold parts of Russia too. In the US it's even north of Maine, where it's still quite wintry.
  2. Any News on updates?

    We have some more performance improvements ready to go here, and some small bug fixes. The main thing we're working on is VR support; right now we're waiting for Laminar to look into some things on their end, as it seems as though X-Plane's SDK isn't behaving as it should in VR mode. But that's why VR is still in beta. Right now I'm calling it 4.7, but we haven't really talked about a release plan for it yet.
  3. Not setting correct textures.

    If you examine the seasons.txt file inside TerraMaxx's plugin folder, it will answer any questions you have about how seasons are chosen for a given location and time. If your simulated date in X-Plane is in April, you would have to be flying above 50 degrees North for TerraMaxx to consider it "Winter" in auto mode.
  4. Not setting correct textures.

    What date was being simulated in X-Plane? In April, the cutoff latitude for winter is defined to be 50 degrees North.Perhaps X-Plane was set up for a different time of year where the cutoff is further South. " considering there is no snow where I live it should not be deep winter. " Again bear in mind the weather data available to X-Plane tells us nothing about whether there is snow on the ground. We make no claims that what we represent will automatically match what you see out the window at all times. All we can do is make a best guess based on your location and the time of year. The temperature will affect just how "frozen" things looks when we do think there may be snow on the ground. You can easily change the season manually using TerraMaxx's configuration screen if you want to.
  5. CTD En Route

    Thank you owine... I loaded up your METAR files at the location you specified, and nothing crashed - so I'm cautiously optimistic this won't happen again after our next release.
  6. Does MaxxFx work in naitive V.R ..?

    I think I remember seeing a report that it does not, but bear in mind VR is still in beta with Laminar and they are still working out the kinks involved with supporting third party add-ons with VR. We are actually working pretty closely with Laminar on VR integration with add-ons. I expect we'll get it working but it is all a work in progress still.
  7. CTD En Route

    Sure, if you can provide your metar.rwx along with the location you were flying at when it crashed, I can use that to make sure the fix I wrote yesterday actually works. Thanks.
  8. Yes, I think some unusual weather conditions triggered this. Presumably the issue has already passed. But, I'm working on making this part of the code more robust for our next release right now.
  9. CTD En Route

    You're right, that does look like the same issue. Given that it seems to have happened around the same time, I think there were some unusual weather conditions being reported that found a case that triggers this crash. I'm looking into it to see if there's anything we can tighten up for our next release.
  10. CTD En Route

    About the only explanation I can come up with is that something corrupted the memory that our internal clouds use, which led to a crash when we tried to sort them. Looking at your log, I think we were trying to process new weather data at the same time that your Flight Factor aircraft was trying to do something as well, so it's possible there was some sort of bad interaction there. You do have a large amount of third-party add-ons and scenery in the mix so it's hard to say what might be causing trouble. Has this crash ever happened to you before, or since? If it does start to become a problem, see if running without other third party aircraft or plugins makes a difference. Re-installing SMP 4.6 might not be a bad idea as well, in case you still have some older components of SMP 3 installed somehow. SMP 3 did have an issue that would explain this behavior more readily. The version SMP thinks it is can be seen in its configuration menu.
  11. CTD En Route

    Hi, what version of SMP are you using? This does indeed look like our crash, but it looks like something I thought we fixed a long time ago.
  12. TerraMaxx fails to operate

    Just to make sure we're barking up the right tree, it might be a good idea to open up your Custom Scenery/SeasonsXP/library.txt file and see if it is in fact corrupt. It should start with: A 800 LIBRARY If it doesn't, then that supports the corrupt download theory and would explain the error you're seeing.
  13. Ah, I misunderstood. I see now there are some small and grass airfields that use .pol resources that we missed. I'll talk to John about how we want to deal with it.
  14. TerraMaxx does work with default scenery out of the box. This thread is just for people modifying their custom add-on scenery to work with TerraMaxx.
  15. [TERRAMAX] Automatic Mode does nothing?

    In March, our cutoff for "winter" is at 45 degrees North. EDDL is above that latitude. The temperature only controls whether we display "mild winter" or "deep winter" textures. The temperature alone can't tell us if there is accumulated snow on the ground or not, so we just give it our best guess. We make no claims to emulate the current snowfall conditions at a given location and time; we just try to make a reasonable representation of the seasons given the information X-Plane has.