Board index FlightGear Release candidates 3.2

3.2rc1 KAUS terminal is sunk  Topic is solved

This is the archive of topics about the 3.2 release candidates.

3.2rc1 KAUS terminal is sunk

Postby wlbragg » Tue Aug 26, 2014 5:46 am

The wheels of the terminal are below ground at KAUS. I've seen this with buildings at one other airport, so far. But most of the USA terminals are correct. I've checked about half of them.
Kansas and Ohio/Midwest scenery development.
KEQA, 3AU, KRCP Airport Layout
Intel i7/GeForce RTX 2070/Max-Q
User avatar
wlbragg
 
Posts: 7588
Joined: Sun Aug 26, 2012 12:31 am
Location: Kansas (Tornado Alley), USA
Callsign: WC2020
Version: next
OS: Win10/Linux/RTX 2070

Re: 3.2rc1 KAUS terminal is sunk

Postby f-ojac » Fri Aug 29, 2014 7:50 am

Scenery and Terrain are very mostly independant of the version of FG: there has been no terrain regeneration for this version, so it probably was the same with 3.0.
f-ojac
 
Posts: 1304
Joined: Fri Mar 07, 2008 10:50 am
Version: GIT
OS: GNU/Linux

Re: 3.2rc1 KAUS terminal is sunk

Postby wlbragg » Fri Aug 29, 2014 5:18 pm

Maybe, but my custom scenery is doing the same thing when running under 3.2. Nothing had changed with it other than using 3.2 FG. There may be some bug there,
Kansas and Ohio/Midwest scenery development.
KEQA, 3AU, KRCP Airport Layout
Intel i7/GeForce RTX 2070/Max-Q
User avatar
wlbragg
 
Posts: 7588
Joined: Sun Aug 26, 2012 12:31 am
Location: Kansas (Tornado Alley), USA
Callsign: WC2020
Version: next
OS: Win10/Linux/RTX 2070

Re: 3.2rc1 KAUS terminal is sunk

Postby Tomaskom » Fri Aug 29, 2014 7:44 pm

I think there is some way to somewhat reduce complexity of terrain (recomputing to lower poly count on the fly) in the new version, do you have it turned on? It's supposed to improve framerates for those who wish to sacrifice a bit of eye candy.
"There are no problems in the air. The only problem is hitting the ground"

Get my L-159 ALCA from the FGUK hangar. If you crash it, things gonna go boom!
User avatar
Tomaskom
 
Posts: 132
Joined: Sun Dec 02, 2012 9:03 pm
Location: Czech Republic
Callsign: OK-TomK
Version: git
OS: openSUSE (Linux)

Re: 3.2rc1 KAUS terminal is sunk

Postby adrian » Fri Aug 29, 2014 8:34 pm

Tomaskom wrote in Fri Aug 29, 2014 7:44 pm:I think there is some way to somewhat reduce complexity of terrain (recomputing to lower poly count on the fly)


I highly doubt that. I've been working on this since two years and never got any solid results. Knowing a bit about the the terragear object format, this is going to be a problem as long as the storage model doesn't change.
What's likely to happen though, is the models in the database can be updated with the wrong coordinates and end up underground or above ground.
adrian
 
Posts: 362
Joined: Wed Sep 15, 2010 3:15 pm

Re: 3.2rc1 KAUS terminal is sunk

Postby F-JJTH » Fri Aug 29, 2014 8:46 pm

Adrian,

We use osg::Simplifier which reduce complexity of terrain: https://gitorious.org/fg/simgear/commit ... 1099851225

Regards,
Clément
User avatar
F-JJTH
 
Posts: 696
Joined: Fri Sep 09, 2011 12:02 pm

Re: 3.2rc1 KAUS terminal is sunk

Postby Johan G » Fri Aug 29, 2014 8:52 pm

adrian wrote in Fri Aug 29, 2014 8:34 pm:What's likely to happen though, is the models in the database can be updated with the wrong coordinates and end up underground or above ground.

I was under the impression that the scenery database does not use an elevation, only elevation offset, since the generation of the new world scenery. I might be wrong though. In various places it is stated that the elevations are recomputed, but I am not 100% sure if that means that the elevations are fixed or if only elevation offsets are used.
Low-level flying — It's all fun and games till someone looses an engine. (Paraphrased from a YouTube video)
Improving the Dassault Mirage F1 (Wiki, Forum, GitLab. Work in slow progress)
Some YouTube videos
Johan G
Moderator
 
Posts: 6629
Joined: Fri Aug 06, 2010 6:33 pm
Location: Sweden
Callsign: SE-JG
IRC name: Johan_G
Version: 2020.3.4
OS: Windows 10, 64 bit

Re: 3.2rc1 KAUS terminal is sunk

Postby wlbragg » Fri Aug 29, 2014 10:27 pm

The other area of question is KEQA, of which I have custom scenery. With 2.0 scenery (terrasync) the buildings are correct depth, it's only my custom that is wrong. That might be on me, although I don't think I changed anything from 3.0/3.1. But I might have. I'll have to check that out.
I'm pretty sure my objects were submitted as -999 or whatever the code is for on ground and no offset.
so it probably was the same with 3.0

per f-ojac, may be correct.
Kansas and Ohio/Midwest scenery development.
KEQA, 3AU, KRCP Airport Layout
Intel i7/GeForce RTX 2070/Max-Q
User avatar
wlbragg
 
Posts: 7588
Joined: Sun Aug 26, 2012 12:31 am
Location: Kansas (Tornado Alley), USA
Callsign: WC2020
Version: next
OS: Win10/Linux/RTX 2070

Re: 3.2rc1 KAUS terminal is sunk  

Postby f-ojac » Sat Aug 30, 2014 8:49 am

In fact we don't allow users to imput custom elevation data as it has no sense. The elevation depends on elevation data input, which is not user dependant, but terragear input data dependant.
So the elevation is always set to -9999, which means: compute the elevation yourself. It is done on export, based on fgelev.
Users only have to say if the object has to be sunk or above the ground with the offset setting.
And elevations should change only when a new world scenery is out.
f-ojac
 
Posts: 1304
Joined: Fri Mar 07, 2008 10:50 am
Version: GIT
OS: GNU/Linux


Return to 3.2

Who is online

Users browsing this forum: No registered users and 1 guest