I haven't had the chance to look at your fix beyond viewing the diffs, but at
first glance I'm slightly surprised it works across multiple
machines/instances.
I would expect that differences in initialization time would mean that at any
given moment in time some instances would have made more
Really nice to read about that. I got the chance to look at a similar install
of flightgear in Tübingen very close to where I live. And You may remember me
-
I believe we have talked about the problems you have at the fsweekend.
I definitely remember. Apologies for waiting so long to get in
On 09/10/2012 10:33 AM, Jan Comans wrote:
My first try was to just switch to a fixed seed with the default
random number generator during initialization. But for some reason,
this didn't really work out so well. I can't exactly remember, but I
think it seemed to work on my home machine, but
On Mon, Sep 10, 2012 at 11:03 AM, Erik Hofman wrote:
We should have a random number generator in simgear that returns the
same random number within the same period of time (I believe it was set
to 1 second) to prevent short time quirks between different machines.
This was specially added for
I'm sure someone will put me straight if I am talking rubbish, but aren't you
using a sledgehammer to crack a nut here?
There are only 6 .xml files which contain these 'global' settings:
Models/Airport/Jetway/jetway-737-ba.xml
Models/Airport/Jetway/jetway-747-ba.xml
We should have a random number generator in simgear that returns the
same random number within the same period of time (I believe it was set
to 1 second) to prevent short time quirks between different machines.
This was specially added for (random) clouds.
I have looked at this, but as far as
6 matches
Mail list logo
