"Joshua W. Keane" said: > Hello everyone, > > I'm working on a simulation project using a simulink model. > Currently, I'm running an interface using the Aerosim blockset for > matlab/simulink, but the program "steps"/"chops", especially when the > sun/moon position is updated (and when other info is output to the cmd > window). I'm currently running both on a single computer, but this computer > is a pretty high-end machine. So the question really is: can I stop those > updates from occuring, or should I just try using a network with 2 computers? > > Another thing i've seen is the fact that after a minute of running my > simulation, the simulation suddenly turns to night. Can anyone tell me why > this is? and how can I stop it from occuring? > > One last thing: there is a command to "do not advance time of day" > (--enable-clock-freeze) and if i've read the documentation correctly, this > should keep the time of day constant while letting the simulation run, > right? But when I go and set that - it pauses the simulation and i can not > do anything. Do i have the wrong idea about this?
I would guess that the effect you are seeing is actually from loading scenery data. Have you built flightgear configured --with-threads? The turning to night sounds like an old bug that has been fixed in CVS. My guess is that the --enable-clock-freeze issue you describe is a bug. Same thing happens here. Best, Jim _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
