* Melchior FRANZ -- Tuesday 26 June 2007:
There's no release imminent for fg/osg, and we have time to clear
matters and don't need to rush in a workaround for a (potentially)
long fixed bug.
I guess things are clear now. Read through this thread:
Melchior FRANZ wrote:
So it's now also clear that we have to fix FlightGear's broken
sound ourselves for 0.9.11 (fg/plib branch). If it can be done
in a way that doesn't break the current framework and makes clear
which parts are the workaround (by using #ifdefs and comments,
as is the case
I was getting these errors in FG OSG before Maik made me a new win32 binary for
osg, now I cannot start plib due to similar problems.
Initializing Aircraft structure
Initializing HUD Instrument
Reading instruments from C:/Program Files/FlightGear/datacvs/Aircraft/Generic/ge
Hi all,
I bought a new laptop (intel core 2 duo with nvidia graphics card) and
I'm having problems with the (too high) frame rates (fg/osg).
Whenever I look outside in fg, the framerate skyrockets to values
around 300 which induce stutter in the simulation.
A (partial) solution would be to
wim van hoydonck wrote:
Whenever I look outside in fg, the framerate skyrockets to values
around 300 which induce stutter in the simulation.
A (partial) solution would be to increase /sim/model-hz in the
internal properties browser, so that less time is available to render
the outside
On 6/27/07, wim van hoydonck [EMAIL PROTECTED] wrote:
A (partial) solution would be to increase /sim/model-hz in the
internal properties browser, so that less time is available to render
the outside visuals.
But there is a problem with increasing the FDM update frequency.
If I set it to
On 6/27/07, Martin Spott wrote:
wim van hoydonck wrote:
Whenever I look outside in fg, the framerate skyrockets to values
around 300 which induce stutter in the simulation.
A (partial) solution would be to increase /sim/model-hz in the
internal properties browser, so that less time is
Hi,
Some days ago, we found out in the IRC-chat, that
YASim aircrafts are working with thermals too.
So the description in thermal_demo has to be changed,
the sentcence and AFAIK they only work with the
JSBSim FDM. can be cut out.
The other documentation is o.k. (just checked today)
So
Hi Erik,
Erik Hofman schrieb am 27.06.2007 09:04:
Melchior FRANZ wrote:
So it's now also clear that we have to fix FlightGear's broken
sound ourselves for 0.9.11 (fg/plib branch). If it can be done
in a way that doesn't break the current framework and makes clear
which parts are the
Hello Martin,
just didn't got the point of my posting.
Maik
Martin Spott schrieb am 27.06.2007 01:14:
Maik Justus wrote:
[...] But I only will start to work
on that patch if there is a chance to get it into cvs. Therefore I will
wait, if the windows patch will be accepted.
Anyone has tested this patch? Isn't it interesting? Have I done something wrong?
Thanks.
2007/6/14, woodyst [EMAIL PROTECTED]:
Hello friends:
My name is Eduardo García-Mádico Portabella and I am from Spain, so
English is not my native Language.
I posted some months ago an email because my
2007/6/27, John Denker [EMAIL PROTECTED]:
On 06/27/2007 04:06 PM, you wrote:
... my yoke made interferences
with autopilot because its lack of force feedback. Y
You wrongly describe the problem.
Probably more than 90% (maybe even more than 99%) of
the FGFS users who have joysticks
Melchior FRANZ wrote:
Note that a single offset0.123/offset
does *not* work on fg/plib.
^^^
I was using a single offset in several places... but after specifying
all three axis, it needed fixing.
*fg/plib*! You are using fg/osg, no?
Um, No.
I
Stewart Andreason a e'crit :
Melchior FRANZ wrote:
[snip..]
Of course, if you don't care at all how your model looks in 0.9.11,
then you don't need to change anything. Your models aren't GPL
compatbile, nor part of fgfs, let alone of 0.9.11, so you shouldn't
worry, anyway.
I do
alexis bory wrote:
Any URL for this webpage ?
Oh, sorry. Guess I was trying not to promote it until after I completed
the next step in development.
http://www.geocities.com/sandreas41/flightgear_aircraft.html
Stewart
Martin Spott wrote:
wim van hoydonck wrote:
Whenever I look outside in fg, the framerate skyrockets to values
around 300 which induce stutter in the simulation.
A (partial) solution would be to increase /sim/model-hz in the
internal properties browser, so that less time is available to
16 matches
Mail list logo
