I will give it a try this week.
The one from EatDirt direct Link and Chris torrent are the same ?
and only if Thorsten thinks there an interest, I can indeed work on how implementing a runtime switch-on.
For geo.nas, the interest may be larger than the SpaceShuttle,
If only they had left the sea-ice in there...
then we can use it. There's not much that can go subtly wrong after all.
'move aloing a great circle' method in geo.nas is actually flawed for...
and there was zero interest, so I've been implementing all geometry since as part of the Shuttle private lib.
Do we have to specify the path for normalmap.png and heights.png in some files
<animation>
<type>select</type>
<object-name>dummy_N3</object-name>
<condition>
<property>/earthview/show-dummy</property>
</condition>
</animation>
eatdirt wrote in Sat Feb 08, 2020 3:38 pm:
As an aside remark, I think we could also have a command-line switch to force the loading of all textures all the time for people having a lot of graphics memory. It takes 1 or 2 mn, 7GB of GPU memory for 16K textures. But once loaded, man... That's fantastic and super smooth!
Cheers,
Chris.
<animation>
<type>scale</type>
<x-offset>58030</x-offset>
<y-offset>58030</y-offset>
<z-offset>58030</z-offset>
</animation>
Totally up for that, tell me how you do this
in the property tree, so if you start fgfs with --prop:/earthview/show-force-all=true full texture loading will be done. Mind that if you graphic card or RAM is not enough, you're certainly good for a crash/reboot... Yes, expect minimum 7-8GB on the GPU, between 10 and 20GB on the RAM depending how many 16K textures you're using./earthview/show-force-all
Users browsing this forum: No registered users and 3 guests