Page 6 of 9

Re: World Scenery V2.3

Posted: Tue Dec 13, 2016 10:25 pm
by laserman
Jan helped me to debug this.
Bad news:
The taxiway & apron polygons for some airports are not in apt.dat anymore :-(
They can be found in the .dsf file.

I made a tool for that, but it's still experimental:

https://github.com/mherweg/d-laser-fgto ... 2aptdat.py

It reads dsf files, which are in plain ascii text, not binary dsf files.

Re: World Scenery V2.3

Posted: Wed Dec 14, 2016 5:09 pm
by IAHM-COL
that's quite some bad news :shock: :shock: :shock: :shock: :shock:

Re: World Scenery V2.3

Posted: Wed Dec 14, 2016 11:03 pm
by laserman

Code: Select all

dsf2aptdat.py -i EDDS
reading...
30 polygon type definitions found in  EDDS.txt
inserting into EDDS .dat  (please do this only once per file)
inserted 107 polygons and 1916 nodes into EDDS.dat
wrote 38 buildings to EDDS.osm
done.


result looks like this:
http://www.23hq.com/laserman/photo/27054488
http://www.23hq.com/laserman/photo/27054486
http://www.23hq.com/laserman/photo/27053946

the wrong triangles might be caused by my converter or by genapts850.
With EGLL I had a similar effect - without using my converter.

Re: World Scenery V2.3

Posted: Wed Dec 14, 2016 11:32 pm
by IAHM-COL
that's certainly an interesting solution.
Do you think it would be expandable as more and more airports apt.dat loose this specifications?

(specially since it is a solution that needs to be applied each ICAO.

Re: World Scenery V2.3

Posted: Thu Dec 15, 2016 1:46 am
by laserman
IAHM-COL wrote:Do you think it would be expandable as more and more airports apt.dat loose this specifications?


I don't know. maybe.
Maybe Pete is interested in integrating it in genaps850,
maybe we have to keep our own collection of .dat files for affected airports.

I found a new issue with World Scenery V2.3:
The elevations of the project3000 buildings fit to senery 2.0
I can make a terraGIT edition of project3000, but I'd like to wait for a version
where the elevation=0 bug will be hopefully fixed.
If you are interested then you can run the project3000 scripts on Marvin.


Someone on the german forum asked where to downlaod the apt.dat
that fits to World Scenery V2.3

Re: World Scenery V2.3

Posted: Thu Dec 15, 2016 1:59 am
by IAHM-COL
laserman wrote:
IAHM-COL wrote:

Someone on the german forum asked where to downlaod the apt.dat
that fits to World Scenery V2.3


The apt.dat is on X-plane 10.50 release
Alternatively they can obtain a NavDat directory here:

https://github.com/FGDATA/Navaids/tree/c1a66af09f46ed86577d9453103a5256aee367c8
(+using that exact commit)

For the first point. No. There's no reason to mislocate objects in airports due to an elevation error. The correct fix is address the elevation issue. I am still null on figuring out what's creating it. I am not great at modifying C++ -- which I already knew.

Re: World Scenery V2.3

Posted: Thu Dec 15, 2016 2:06 am
by IAHM-COL
laserman wrote:Maybe Pete is interested in integrating it in genaps850,



The Pete that already destroyed genapt850?

https://forum.flightgear.org/viewtopic. ... 07#p301001


You seem not to understand the really critical problems that terragear now has at the core-developers level.

Re: World Scenery V2.3

Posted: Sun Dec 18, 2016 11:27 pm
by laserman
KDEN has elevation issues.

Re: World Scenery V2.3

Posted: Sun Dec 18, 2016 11:45 pm
by IAHM-COL
yes. I saw that one too :S

Re: World Scenery V2.3

Posted: Wed Dec 21, 2016 1:25 am
by iksni
heh. pete here. Just joined and checking out ws 2.3.

Don't worry - I didn't destroy genapt850. it's still stable in scenery/ws2.0 branch :) Papillon81 and I discussed which way to move forward and decided master would be development, much as next is in fg/sg. We regret it a bit now, as it's 3 years, now - with no real proof of concept...

What is in master branch, I think will benefit your project as well - eventually. genapt now uses a texture atlas for all taxiway and runway markings. This reduces draw calls significantly. But the texture atlas has not been committed to fgdata yet - so it looks like crap :)

It is also only creating a 2D airport layout, that can be draped on top of terrain instead of cutting holes, so you can update airport layouts without rerunning tg-construct - but tg-construct isn't ready for this yet, either.

It hasn't been updated in a while because I've been helping the next gen terrain experimentation. Which will also help 3rd party scenery. If it goes well, terragear may be dropped completely for a couple shell scripts to run GDAL tools. All scenery development would then be in QGIS.

goals of mine for nextgen scenery:

1) Arbitrary mesh resolution - meshes completely independent of landclass. - you can update landclass, without updating mesh, and vice versa.

2) Ability to support multiple mesh directories - in fg_scenery path priorities. i.e. whole world at 3", but some area in the mountains at 1"

3) no more exact matching / gaps at tile boundaries - tiles generated from same DEM will match ok - but if they don't each tile has a skirt to hide gaps.

4) no more airport holes - drape airport on top of smoothed terrain.
also, the terrain smoothing is at runtime after reading airport boundary - so new airport layouts should be able to be tested in flightgear immediately after running genapt850.

I have this in a simgear branch, and I will be making a second commit soon once I have the landclass rasterization done. We'll then need new shaders to render the terrain.