Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 06/19/2019 in Posts

  1. I think I can vouch for that. I purchased FSGRW earlier this evening and after a bit of confusion over what version I received, I believe I got it work and may I say i am rather impressed how the weather (as it was being injected), faded in, instead of popping in, as I was used to before. I don't say this often, but I am very impressed so far with the performance. unfortunately, my evening is coming to a close and I still need to grab the update to SMP, but with running the previous version, the performance and visuals are awesome. :)
    3 points
  2. Just to clarify again, you can set a decision altitude (height above mean sea level) in the Hotstart TBM, but you can't set a decision height (height above ground level). AFAIK the latter would be required for CAT II approaches, for which the TBM 900 is not certified anyway. So IRL it would add bit of safety but that's about it, in Sim it doesn't really matter.
    1 point
  3. I would have to concur that after a couple of months using SMP w/RWC, I see a noticeable difference in my visuals. I admit that I currently use ASXP with it, but I might just go ahead and purchase FSGRW as an alternative, since Cameron shed some light on how well SMP/RWC/FSGRW work together. I have yet to upgrade to the latest build of SMP, but I suspect it'll be the perfect polishing to a great weather add-on. A thank you goes out to the team at Sundog for continuing with great success. Thanks.
    1 point
  4. OK, so I think it's saying that you do indeed have a 2GB video card. It may be that an X-Plane update, an increase in your monitor resolution or anti-aliasing settings, or something else caused X-Plane to start using a little bit more VRAM, and that didn't leave enough for SMP to work with. Laminar recommends 4GB or more for X-Plane 11. Updating your video card would be money well spent, but failing that, there are some things you can try: - Try lowering your monitor resolution, and disable any anti-aliasing your video driver may be set for. - Assuming you can get to X-Plane's graphics settings, turn the quality down such that HDR is not enabled. Also disable any anti-aliasing for now. - If at this point SMP will start up, disable any SMP features you don't need that consume more memory. Mainly, turn down the "cloud area" setting as far as you can tolerate, turn off cloud shadows, turn off cloud reflections, and set terrain blending to zero. If that gets you up and running, you can start re-enabling the features most important to you until stability is impacted.
    1 point
  5. Well that's odd - your METAR.rwx file is actually empty of any data at all! I think maybe ASXP wiped it out before you were able to grab a copy of it. However, I just now tried KPDX with ASXP and fortunately similar conditions still existed there. I think I might know what's going on. Do you have your overcast representation in SMP set to solid or broken procedural? If so, cumulus (broken) cloud layers that intersect the overcast layer are suppressed in SMP, because having these two different representations of cloud types overlapping each other looks weird. The issue isn't that the broken layer is low, it's that it's too close to the overcast layer. If you change your overcast representation to something else, like "Soft HD", you should see both layers appear. Although, they are close enough that they can be difficult to distinguish - but they are there. Our clouds tend to be larger and taller than default clouds, so visualizing distinct layers that are close together can be tricky at times. Anyhow, I hope you just had overcast set to a procedural setting and that's all it is.
    1 point
×
×
  • Create New...