Jump to content

OPabst

Developer
  • Content Count

    12983
  • Joined

  • Days Won

    73

OPabst last won the day on June 14

OPabst had the most liked content!

Community Reputation

1785 Excellent

About OPabst

  • Rank
    Developer

Contact Methods

  • Website URL
    http://www.aerosoft-shop.com/products/aes/aes.html

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. stop P3D and wait one minute, then run the SODE-ON batch again.
  2. Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.
  3. Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.
  4. Same as for Tennerife, no FSX or P3D V3 version planned.
  5. There is no FSX or P3D V3 Version planned.
  6. Damit es nicht noch eines Threads bedarf, hab ich es mal verschoben.
  7. Da dieser Thread beantwortet wurde haben wir ihn geschlossen. Wenn Sie weitere Fragen haben können Sie jederzeit einen Neuen öffnen.
  8. Es ist keine Scenery von Aerosoft und ja, andere haben auch nicht den Service wie Aerosoft. Aber, genau deswegen ist das Aerosoft Supportforum für dieses Produkt (und andere des Entwicklers) nicht zuständig. Daher hier der falsche Ort für eine Diskussion über Fremdprodukte.
  9. Thanks for the positiv feedback. Regarding the „flying“ houses I made several test to find a fix or workaround, but looks like an internal problem of the sim engine. I as developer can only define where on the photoground is a building and its size, not the altitude, this will be calculated by the FS based on the mesh of the ground. We see such issues in all island with a extrem rugged terrain (hope that is the correct translationen). Maybe when the autogen visible distance is high, the building will be visable first, when the mesh is in a low density (LOD). In flat areas no issue, as the change of the mesh altitudes are small. In such an area as in the canary islands maybe the recalc of the position fails at the next LOD level, so the building keep the position while the mesh goes down. We only see the issue, when flying into the area, not when the scenery is reloaded there.
  10. Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.
  11. Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.
  12. First: Gran Canaria (GCLP) has no holdingpoint R01L Second: Take care to set the Mesh to 2m or less (see manual) and check the „Hill“ again.
  13. First, the issue is independed of the Version, it is in issue was already existing in the older Versions (FSX/P3D) and is also in the Professional version. Why is there problem, I will try to explain: In the special case of entrypoints to the runway here at the RW27L, the calulation of the way to the Runwaydepature Position at the runway is source of the issue. The FS (all versions) will go always to the first Node of the Runwaylinks on the runway (blue cycle) and place the aircraft to the first path of the runwaylinks (blue arrow). All traffic from the south has a clear way to the first node, but traffic from the north is depending on which taxiway is entering this area. All traffic via TW B (1) will calc the shortest path correct via L28 to Entry NB1 (green). Traffic entry via A from the west (2) will calc way via NB2E and SB1, because it is shorter then via A to the north and then right via L28 to NB1. The calc is too simple and takes only the pathlenght is count. Solution 1 is, to remove the connection to the south taxiway link like this: In this case the Entry NB2 will not anymore used for depature traffic, as it is not the first note on the runwaylinks. All traffic will go to NB1 Solution 2 is, to change the first Runwaylinke to a apron link: But in this case, NB1 is not used from the north anymore, because the pathlenght to NB2 is always shorter. I will look into it, but there are several other issue, that can be optimized, so it will take some time.
  14. This is not the Professional Version in this case, only the old for FSX/P3D until V3. In the Professional Version no Runwaylights in the Afcad. But the issue is, as Jürgen said, the situation at this end of the runway. The way via the south is shorter then the way Holdpoint NB1. We will change that in the Professional version with the next update. Workaround until then is as Jürgen explain it.
  15. Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.
×
×
  • Create New...