Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 02/05/2021 in all areas

  1. It is normally not as bad as it looks. But thanks to you I found a problem. I have Xorganizer and normally I start that first, choose only plugins I need for the plane or just because I want them, only sceneries I need (and global scenery improvements) and often also only one plane or some type of flying (I have a bunch of preset-profiles). But even fully loaded my FPS is good and everything works fine. But I think I know now what went wrong. I used the wrong profile (for bushflying/heli) But to be sure I now tried my "big tour africa in airliner" profile. Same fault but now no errors in the log file. Only one error and that is the Gizmo error. This is my "minimum" set-up. These are enhancement I will not fly without because they make my Xplane almost as good looking as MSFS2020. (see log.txt ) But to be sure, after that I used my vanilla Xplane profile and only the 737. Still the same problem. (see log2.txt) But again, not a real problem. I can live with that. Log.txt Log2.txt
    1 point
  2. Version 1.51

    16 downloads

    This is a livery for the BN2T. It is fictitious but sports an indian head logo on the tail for any name you want. I use Iriquois Air in my fictitious world but any indian based name would work - Blackhawk, Cheyenne, Shawnee, etc in your world. I cleaned up one of the stock liveries although not perfectly as every plane that flies isn't showroom pristine. Hope you like this. It is JUST the object file.
    1 point
  3. On a Mac, it's usually not RAM that is the issue but video memory. I don't see any indication of you flying through storms in the log, so I think you're just exhausting video memory. That's very common on Macs as they typically don't have much of it. And when X-Plane crashes due to running out of video memory, it typically does so in this fashion where it just stops without writing any diagnostic information into the log first. If you're flying through custom scenery, that's likely consuming quite a bit of it. Disabling HDR can also help. Or, you can lower SkyMaxx Pro's cloud draw area setting. The new volumetric clouds in SkyMaxx Pro 5 also use more video memory than the non-volumetric options do.
    1 point
  4. Holds / VNAV are in our current sights. What kind of progress we make remains to be seen, but we are actively focusing on it now. -tkyler
    1 point
  5. +1 for a P-Factor option and more realism.
    1 point
  6. It's ironic that a few of you are wanting it back. I was getting quite a few DM's on Facebook, and I think a few here, also, asking for it to be lessened or removed. That it was too hard to land and take off. I'll discuss with Saso and ask him if it can be made as an option or just to bring it back as before.
    1 point
×
×
  • Create New...