Finally made a full version of the ZUTF. I didn't plan to do so but previous version seemed to have navdata and terraforming problems when I tried to fly FBW A380 with it. So I made a new one. Since a decent payware ZUTF will be available early next year, I used completely MSFS default assets.

What's available:
1.Most parkings, all runways and taxiways and their lights.
2.Same 3D model (By Hammer Sudio) as before.
3.AI aircraft parking code.
4.Glass jetway from MSFS stock LSZH (2020) EDDM (2024)
5.CAAC standard runway markings.

Known Issue: Jetways are not long enough at some MARS implemented gates. Tower is broken (Caused by LOD logic). Default lighting conflicts with MXIDesign's OTHH Doha Hmad.

What's not available:
1.CAAC standard ground markings.
2.Detailed 3D models.
3.Taxiway signs.
4.Some parkings near SMECO and CES hangars (Not available on charts)

Note: some parkings had been biased to fit the inaccurate 3d model. If you find duplicated runways or no navdata, please make sure the priority of ZUTF is higher than navigraph-navdata-base and lower than navigraph-navdata.

 Different level of rendition explained (freeware applicable) 

Basic: using MSFS default assets to make a flyable airport.

Simple: Using some custom assets to make an airport that recreates some of the most significant elements on the aerial image.

Detailed: Using custom assets, trying to recreate most details in the airport following the aerial image, charts and MH5001 standard.

Please note that this is only for the apron.