Jump to content

Major Mesh Issue with ENTC


Recommended Posts

Hi guys. 

 

There is a major issue with the accompanying mesh in the package Aerosoft - Tromsø ENTC

While is looks good at the airport, it destroys the terrain at neighbouring airport ENDU, have not check other airports

Rivers and airport seems to be diggin in creating cracks. Perhaps some elevation data is wrong or flattening is in place. 

Removing the mesh fixes the problem, but also flatten ENTC, it works but I bet not as intended. ENDU is situated as the closest airport to ENTC, but still

a distance away from it. Please have a look!!

 

Using X-Plane 11.32r2 and Windows 10 

No other mesh or ortho is installed, pure vanilla. 

 

This is a before and after image showing mesh at ENDU with and without (ENTC Mesh) folder installed in XP

 

ENDU Without "Aerosoft - ENTC Tromso - Mesh"

Please login to display this image.

 

ENDU With "Aerosoft - ENTC Tromso - Mesh"

 

Please login to display this image.

Link to comment
Share on other sites

One could say "works as designed". It's a common problem of sceneries with custom mesh and not only happens with ENTC but all other tiles with multiple airports on it. 

 

Here is what you can try out:

 

1. Create a new ENDU scenery folder and make sure it stays above ENTC mesh 

2. Download the latest gateway version of ENDU into the new scenery folder through WED 

3. Activate "always flatten" in the airport options 

 

If the flattened area is not wide enough try to extent the airport boundary in WED. 

Link to comment
Share on other sites

vor 6 Stunden , Marten sagte:

One could say "works as designed". It's a common problem of sceneries with custom mesh and not only happens with ENTC but all other tiles with multiple airports on it. 

 

In more detail: The Tromsø XP Custom Mesh is based on the UHD Mesh v4 and that UHD mesh has the shown mesh-artifacts at ENDU.
In other words: The base mesh for the custom mesh-version causes the shown issue at ENDU, not the custom edit itself.
See also the attached comparison. Thus I'd like to adapt Marten's comment and say: "works as _initially_ designed".

Please login to display this image.

Link to comment
Share on other sites

Hi, that much I have figured out too.. I will talk to Andras to see if he can fix it. I believe I have narrowed the bug down to "river elevations" or perhaps the tag "streams" 

The coverage is way larger than just ENDU, it also cover the entire +69_018 tile

I have checked ENEV and ENAN which are the nearby airports, but it seems to be only ENDU that have the actual airport effected, again of course due the fact that there is a "river" or a "stream" coming down towards the airport boundary. The cracks can be seen all over the tile as seen in these two images. 

 

Red arrow = Rivers or Streams

Please login to display this image.

 

Please login to display this image.

 

Link to comment
Share on other sites

Thanks Marten

 

Here is what you can try out:

 

1. Create a new ENDU scenery folder and make sure it stays above ENTC mesh 

2. Download the latest gateway version of ENDU into the new scenery folder through WED 

3. Activate "always flatten" in the airport options 

 

Will try this, but if it does not work I think the best solution is then to remove Aerosoft ENTC for good.  Not worth having an FSX converted airport present in XP if neighbouring mesh/airport is ruined. Better then to make the airport from scratch again and edit the default dsf tile. But I think it is important that people know about this problem, just in case they are thinking about buying it, it is in the end a payware product.

 

Fingers crossed though..

 

 

Link to comment
Share on other sites

You are the first reporting the ENDU problem although that might be the more popular airport. I would guess most of the people wouldn't buy ENTC anyway because they prefer flying to ENDU with a better scenery. 

Link to comment
Share on other sites

Though not as trafficated as ENTC with only 242.000 pax in 2017 vs 2.104.861 at ENTC (which is a way larger city), it is still a important airport for both military and domestic travels in this region. While not everybody takes time to report, the fact is that there is an issue that cannot be fixed in this payware scenery and people need to be aware. The correct way is that the thirdparty vendor list this detail in their readme or on the product page as a known bug. That way the end user is informed in a responsible fashion. 

 

From Alpilot's response, too bad he quit doing mesh..

 

Deep, cut-out canyons around narrow rivers
In some very rare cases, the river smoothing / flattening algorithm goes haywire. Yes, riverbeds need to be take care of via some algorithms as the original DEM (elevation) data is rarely optimal along narrow valleys OR the OSM river vector data is not perfectly in sync with the DEM data. An algorithm tries to “correct” these issues, but in some – rare – extreme cases it can be too aggressive in the wrong place. This is very, very hard to take care of thus I accept it “as is”.

 

 

 

Link to comment
Share on other sites

  • Developer
On 8.4.2019 at 13:03, Tom Knudsen sagte:

Not worth having an FSX converted airport present in XP if neighbouring mesh/airport is ruined. Better then to make the airport from scratch again and edit the default dsf tile.

 

Just for the record: This is a mesh problem and has nothing to do with the airport itself - you could create all Tromso content from scratch and it would not change anything here. Further, it's not relevant if any aiport originally was created for FSX and then ported to X-Plane. X-Plane does not have any compatibility modes for FSX sceneries so everything you see in any XP scenery is native X-Plane tech. The objects don't care if you first export them for FSX and then for X-Plane later, doing a so called 'conversion' results in a native XP scenery and is not any better or worse than 'creating a scenery from scratch' - the latter just takes additional time. 

 

 

 

 

 

Link to comment
Share on other sites

  • 9 months later...

@Tom Knudsen Allow me to copy attached FB conversation into this thread: You got already an extensive explanation in this thread regarding the issues you encounter at ENDU. To summarize: The issues are not caused by @Marten' / Stairport Sceneries' ENTC scenery, but the X-Plane scenery architecture – and the fact, that LR doesn't allows us developers (yet) to patch meshes locally. Further reading here and here.

Please login to display this image.

Link to comment
Share on other sites

After reading up on all linked pages my question is this:

Could sceneries such as ENTC be patched with a custom made ortho mesh that would not cover ENDU? Or does a mesh produced by ortho cover the same 

geographical area as the ortho itself.  We made an patched mesh file just for ENKB "made by Didier" (ortho4xp), but that had to be then rendered with ortho4xp to generate the fix.

While the mesh was fixed, not all want to use ortho. I guess you could mask out everyting you wouldn't need, but that seems like a ton of extra work. 

So basically what are the options, wait for a tool by XP or try patching it with ortho mesh and not use an mesh by Andras. 

 

Do we really not have any other choices but to wait for a tool by XP to arrive?

 

Cheers

Tom

 

 

 

Link to comment
Share on other sites

  • Developer

BTW: ENTC ships with winter textures already. There is TerraMaxx compatibility currently available and also a winter mod for JSGME if I remember correctly.

Link to comment
Share on other sites

  • Developer

SAM integration is technically finished but updates usually need some time to release because of testing, preparation and stuff like that.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use