Blaming each other doesn't bring a solution to this problem.
As I've said, after our Teamviewer session, we found that double jetways in THAT case, were caused by AES.
So it has certainly to do with how FSX handles jetways
Sure.
The question is, what is different about the jetways at JFK. Opening the afcad in ADE9X doesn't show anything special. Maybe Umberto has an answer to this.
The issue is, this thread is very confusing, because there are people that posted with DIFFERENT issue, that doesn't have anything to do with each other, and are caused by very different things:
1) JFK jetways mixed with *default* jetways and double control towers, double buildings, etc. This is SURELY caused by another AFCAD in conflict.
2) JFK jetways mixed with copies of *JFK* jetways in slightly different positions. No other double objects. This is caused by AES, because the double jetways are created by AES, but they look like JFK jetways too, and they are misplaced because their positions were based on JFK V1 so AES must be updated to support V2 to fix this.
3) JFK jetways that looks correct, but split in two ONLY after they start to move, and no other double objects around. This is really a mystery, and it's likely another FSX jetways bug similar to the sinking wheels problem, it doesn't happen only at JFK, we saw it at other airports too, and it appears randomly without a clear pattern, the same jetway that used to work in a session, splits up in the next one, and this leads to believe it has something to do with a problem with graphic resource handling in FSX.
So, to sum it up, of the 3 causes that were discussed here (even if the thread's subject was really about #3), two are caused by external products, and the 3rd one is an FSX bug, the only sure thing, it's nothing *specific* to JFK V2. It's possible this bug is triggered if jetways are more complex of x polygons, but they are the same model we used in JFK V1, just moved to slightly different positions, so we really don't have a firm idea of the possible causes, other than being an FSX bug.
Sooner or later, we'll finally have to tackle the jetway issue once and forever in GSX, and stop relying on FSX for their handling.