Hi,
On Thursday, August 30, 2012 07:27:45 Renk Thorsten wrote:
Computing constant values at runtime is bad design and we should not do
that. No matter if we notice a significant increase in load time now or
not. The ground elevation at a specific point is well known at scenery
generation
Computing constant values at runtime is bad design and we should not do
that. No matter if we notice a significant increase in load time now or
not. The ground elevation at a specific point is well known at scenery
generation time and that is where the vertical position of an object has
to be
Computing constant values at runtime is bad design and we should not do
that. No matter if we notice a significant increase in load time now or
not. The ground elevation at a specific point is well known at scenery
generation time and that is where the vertical position of an object has
to be
Hi,
On Monday, August 27, 2012 10:57:57 Torsten Dreyer wrote:
If that feature helps scenery developers to _temporary_ place objects,
may I suggest that this code is enclosed in #ifdef's and only enabled
during compile time with a special CMAKE switch and never enabled for a
release?
That's
I have done some test. Here is the result :
Nb of objectWithout _AGLWith _AGL
0 20.4s
20.4s
500 21.4s
21.4s
5 000
On Sunday, August 26, 2012 21:04:53 Clement de l'Hamaide wrote:
I have done some test. Here is the result :
Nb of objectWithout _AGLWith _AGL
0 20.4s
20.4s 500
6 matches
Mail list logo
