mmogahed

That is fair, so let me explain it more clearly. I am the original creator of this OEJN work: https://forums.x-plane.org/files/file/69509-king-abdulaziz-international-airport-2021-oejn/?_fromLogin=1 The current MSFS product I am referring to is this one: https://secure.simmarket.com/double-t-king-abdulaziz-international-airport-msfs.phtml During the dispute, the developer side sent me the MSFS airport-layout XML for that product, and that file was then compared against my original OEJN source. I am not here to create drama or turn AVSIM into a legal thread. I am putting this on record because I do not want my original work to be quietly buried or ignored, and I do want the community to understand why this matters. AVSIM has long been one of the places where flight sim users actually follow developers, products, and what happens around them. That is why I felt it was the right place to explain the issue and ask for fair understanding and community support.

I’m referring to the current OEJN product for MSFS, sold under Double T on simMarket: https://secure.simmarket.com/double-t-king-abdulaziz-international-airport-msfs.phtml I’m putting this on record because, during the dispute, the developer side sent me the MSFS airport-layout XML for that product. That file was then compared with my original OEJN source. So this is not just a generic “same airport” argument. The issue is the repeated structured correspondence found in the developer-supplied layout data. I’m keeping this limited to the current MSFS matter, the XML they supplied, and the completed technical findings.

I am posting this here because the technical review is now complete, and I want to explain the issue clearly and without exaggeration. This concerns the current OEJN MSFS matter only. During the dispute, the developer side supplied the MSFS airport-layout XML themselves. That file was then compared against my original OEJN source. The issue is not a generic “same airport” overlap, and I am not claiming a literal 100% unchanged copy of every asset. The point is narrower and more specific than that: the completed technical findings identified repeated structured correspondence between the developer-supplied MSFS XML and my original OEJN source in stand layout, gate naming and numbering, headings, taxiway geometry, and related jetway-location patterns. One report found 235 of 249 parking entries within 50 m, 2811 of 2909 taxiway points within 50 m, and related jetway-location correspondence. A second report found 145 shared named gate positions, with 115 aligning within 50 m and 10 degrees. Both reports also state their limits clearly. They are technical comparisons, not legal opinions, and they do not claim that every 3D asset is identical. My point is simply that the underlying layout structure shown in the developer-supplied MSFS XML materially corresponds to my original OEJN source in a repeated and documented way. That is why I am putting this on record here.

I’m truly saddened by how things turned out. For a long time, I reached out to this community, asking for 3D design collaborators to help me bring this project to life as a high-quality, free gift for everyone. My goal was 100% engineering realism, but I didn't even receive a simple response or a single offer to help. It hurts to see engagement only now, after I've decided to keep it private. I wanted this to be 'our' project, but since I had to finish the engineering journey alone, I’ve decided to keep the final result for my private hangar. I wish it had been different. Happy flying, everyone.

Hello everyone, I am writing to share a final milestone regarding the Hamad International Airport (OTHH) project. I am proud to announce that the engineering and structural design is now 100% complete, covering all new expansions and intricate architectural details across the 15 main objects. Having developed over 80 airports throughout my career, I aimed to bring this world-class hub to the simulation community with the highest standards of accuracy. However, observing the lack of engagement and interest in this specific project, I have made a firm decision: The OTHH project is now transitioned into a "Private and Exclusive Build" for my personal use only. It will not be released to the public or distributed on any forums. I believe that when a demanding technical effort doesn't resonate with the community's interest, it is best kept for the creator who values the magnitude of the work. Thank you to those who showed support. Safe flights.