TerraGIT 3.4

[SkyBoat]

KBOS: Logan Int'l Airport, Boston on a Chilly November Sunrise using terrGIT 3.2.



Screenshot by SkyBoat

[laserman]

Thank you for creating an updated edition of Project3000.

I'm not sure it it's a good idea to merge it into TerraGIT in a way that the user can not easily remove or disable it.
I prefer to use Project3000 as a custom scenery layer so that I can enable and disable it in the FG launcher.
Turning on & off during runtime would be even better. There are some "Scenery Layers" check boxes in FG but I don't know what they do
or if they do anything at all.

The reason for my doubts are those already developed airports in FG where Project3000 objects can enhance the experience but may also disturb e.g.
duplicate, different looking static jetway bridges or generic buildings (from P3000) mixing with hand-made buildings.

[IAHM-COL]

Thank you for creating an updated edition of Project3000.

And thanks to you for developing the code that made it all possible

I'm not sure it it's a good idea to merge it into TerraGIT in a way that the user can not easily remove or disable it.
I prefer to use Project3000 as a custom scenery layer so that I can enable and disable it in the FG launcher.

It is a difficult problem indeed. TerraGIT has P3000 installed since 2016. It is the simpler way to distribute to everyone in a simple --not complicated-- manner.
Using it as a custom layer means the user needs to be informed well in how to add more an more layers via --config,
See this case scenery:

https://github.com/FGMEMBERS-SCENERY/Pr ... 0/issues/2

You can see what happens when user is unaware, and the project exists as a standalone (which already does).

On the other hand terraGIT including it makes a simple --one go solution-- to have all scenery ready to go. No additional technical knowledge needed.

This is why my approach is: install.

Turning on & off during runtime would be even better. There are some "Scenery Layers" check boxes in FG but I don't know what they do
or if they do anything at all.

This is the ideal solution for a project such as P3000 (and OSM).
The way to get this solve is not at the scenery path level. It's at the rendering level. Which requires coordinating with the core team
(or hostile-forking flightgear and make custom configurability)

It's a problem "above my paycheck" [or so, Americans say]

The reason for my doubts are those already developed airports in FG where Project3000 objects can enhance the experience but may also disturb e.g.
duplicate, different looking static jetway bridges or generic buildings (from P3000) mixing with hand-made buildings.

Never seen that happen. Including airports well developed like Frankfort, where the shared P3000 objects enrich significantly the hand made scenery, instead of conflicting.
This is because most hand made objects are statics like terminal buildings and similar, while P3000 brings life to the project by populating the shared objects.

See the screenshot of KBOS by Skyboat above,too.
The P3000 and custom scenery interaction is virtually seamless, and the P3000 just enhances the scenery.

The other false information spreading around this topic is that P3000 is a frame rate killer. I had never seen that happening either. The reality is that the model is loaded to memory only once and rendered at need on their location. The rendering has GPU and GRAM cost, but not RAM cost. A limited number of models rendered in an array-like manner is actually computationally cheap, but visually rich.

My conclussion?
Your idea is correct. Enabling/Disabling features would be great to have. But they are not to be made on the scenery side of things, but on the render side.
The scenery just presents the objects (shared and statics) to the rendering engines. And thus, the scenery package has the objects and positions installed.
FG can't still handle this, but maybe on the next eon will

[IAHM-COL]

@D-laser

Forgot mentioning other reason why P3000 is better updated than not.

The new TerraGIT v3.2 has scenery elevation errors fixed. Old P3000 object elevations are no longer correct, and this update brings--not only many more airports definitions-- the correct elevations.

IH

[123apple]

The other false information spreading around this topic is that P3000 is a frame rate killer. I had never seen that happening either. The reality is that the model is loaded to memory only once and rendered at need on their location. The rendering has GPU and GRAM cost, but not RAM cost. A limited number of models rendered in an array-like manner is actually computationally cheap, but visually rich.

You've never tried the car parks at Manchester then?

[IAHM-COL]

I've been in Machester (EGCC) many times over with terraGIT (prev. version)

Have you run tests over RAM and GRAM usage?

[IAHM-COL]

Project3000 implemented

https://github.com/FGMEMBERS-TERRAGIT/t ... a4bde7cb5e

TerraGIT v3.2 now implements the P3000 updates

Code: Select all

git pull
git submodule update --progress
git submodule foreach git checkout origin/master #if previous command does not bring content


[123apple]

I've been in Machester (EGCC) many times over with terraGIT (prev. version)

Have you run tests over RAM and GRAM usage?

No, on simulator performance - the cars absolutely killed it. To be fair, there were quite a lot of them.

[IAHM-COL]

the cars absolutely killed it. To be fair, there were quite a lot of them.

I can't reproduce. My FPS remains fine

I just also did my first flight with the new Project3000 (or P15000)

I traveled to KMCO based on object density:

http://www.jafva.com/flight/1691/
https://raw.githubusercontent.com/FGMEMBERS-SCENERY/Project3000/master/populate.log/Objects.log

Code: Select all

...
KMCO: 8012 Objects
...(vs)
EGCC: 3163 Objects


The result is quite immersive. My framerate didnt floor.

Best,
IH

[123apple]

OK - was wrong about Manchester. IT was my own scenery, not project3000, where I had to remove cars to prevent unacceptable performance. I see terraGit has no cars at Manchester, which is good.

However, case in point: Warton airport EGNO.















https://github.com/terrasync/main ---> btw, an up to date /Airports/ data source is found here, I see yours is not updated since 2017.