So because you are unable to fix KMEM's problems, you say go back to default jetways LOL
If these "KMEM problems" go away by disabling it...it's best having static jetways than a crash. Several developers made airports with static jetways for years and they still do, and nobody complained about it.
But since this doesn't obviously happens to everybody, but just a bunch of users, it would be wrong to not have that feature in the first place.
In any case, I just had a Teamviewer session with another user today. He was affected by a crash in G2D.DLL happening 100% of the times at KMEM.
The first thing I did, was to disable *every* 3rd party module in the DLL/EXE XML files. And guess what, the crashes went away.
Next step was to enable each module, one by one, test KMEM, until it started to crash again. What we found was:
- With EZDOK camera enabled, the GD2.DLL crash happened 100% of the times.
- With SODE, but no EZDOK camera, the crash happened only once in a while, like 25% of the time.
Without EZDOK or SODE, but with all the other 3rd party modules re-enabled (PMDG, FSRecorder, ASN, Squawkbox), no crashes.
I tried everything, including sending him the next (still unreleased) version of GSX, which comes with a new Addon Manager and Couatl, but the ONLY way I could stop the crashes, was to disable EZDOK and SODE.
I'll try to discuss this with EZDOK and SODE authors, maybe they have some ideas and, perhaps, we might be finally able to reproduce it, which we haven't so far.