Bardia

Members
  • Content Count

    97
  • Joined

  • Last visited

Community Reputation

9 Neutral

Profile Information

  • Gender
    Male

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Bardia

    P3D 4.1 CTD near Labrador

    The first case does not explicitly state that he doesn’t have GSX installed. And the second one is self-explanatory, GSX installed and used but later terminated. So still a trace of your software in the mix. The simple question that you fail to even come close to answering is, why on earth don’t other addons crash the whole sim when loading the faulty data? Surely they deal with exactly the same sort of data your software deals with. Why is it only GSX that not only fails to deal with corrupt data but also causes the entire sim to crash? You got to answer this question clearly to the whole community of simmers that are paying you hard earned cash only to have their sims CTD mid-atlantic.
  2. Bardia

    P3D 4.1 CTD near Labrador

    Gosh this is basic logic mate, if you don’t get the crash with X installed it does not mean X is not at fault. But if you do get the crash with X not installed it does mean X is not a fault. Really really simple stuff.
  3. Bardia

    P3D 4.1 CTD near Labrador

    Wrong - this CTD is only happening when GSX is installed. If the “Cause” was faulty sim data, we would be witnessing at least a handful of CTD reports without GSX installed or running because as you said other addons look up sim data all the time. But that is very simply not the case. No reports of that so far. And I’m not confused at all to be honest...
  4. Bardia

    P3D 4.1 CTD near Labrador

    Nope, earlier there were reports of CTD without vector even installed.
  5. Bardia

    P3D 4.1 CTD near Labrador

    “We” is all the users reporting this issue on this thread.
  6. Bardia

    P3D 4.1 CTD near Labrador

    The least GSX dev could do is clearly explain what exactly the module is up to when in cruise altitude. We need to know in full detail what it loads, processes or tries to access. Has he already done that?
  7. Bardia

    P3D 4.1 CTD near Labrador

    Perhaps it gets too fast beyond x16 for coualt (or maybe the sim itself) to load the faulty element.
  8. This is the results of my findings after thorough testing of each individual slider in P3D, in case you’ve wondered which settings affect CPU usage and which ones affect GPU usage. CPU: Water quality and all water reflections Texture resolution, mesh resolution, LOD radius Special effects (detail and distance) Scenery complexity, autogen draw distance, vegetation and building density, dynamic 3D vegetation Cloud layers, density and draw distance All types of AI traffic GPU: Anything to do with shadows and light (quality, distance, boxes ticked, dynamic lighting and reflections) Tesselation Anti-aliasing Texture filtering Screen resolution
  9. Bardia

    P3D 4.1 CTD near Labrador

    As a paying customer, I don’t remotely consider this to be good customer service. We went through vector, navaids, etc. etc. many pages ago and they all got affirmatively eliminated through verifiable means. GSX remains the only plausible offender. Devoper must be held accountable by the community. Lousy excuses dished out by the dev make very little sense.
  10. Bardia

    P3D 4.1 CTD near Labrador

    Umberto, do you recall telling us only a few months ago that this issue has zero to do with GSX?
  11. Bardia

    Grass textures showing through taxiway / apron

    Absolutely nothing to do with AFCAD, it’s a well-known ESP bug and you just need to decrease the texture resolution in P3D menus by a notch or two. That’s all.
  12. Bardia

    Prepar3D v4.3 has been released

    Mate this is not just another random tweak, LM itself has stated that you need to lower this value until you hit the optimal balance unique to your own PC setup. Trust me I’m no fan of nonsensical tweaks either especially post v4 but this one is an exception.
  13. Bardia

    Prepar3D v4.3 has been released

    Yeah I can confirm this issue persists with ProATC, though limited to certain circumstances but definitely still there.
  14. Bardia

    Prepar3D v4.3 has been released

    Then why no mention of it in the 4.2 release notes either? Yeah might be the case that I’ve failed to notice this till now.
  15. Bardia

    Prepar3D v4.3 has been released

    Didn’t really pay attention, updated the shaders using Envshade straight away.