I have the same problem with Main/renderer.cxx. Your solution
(or one very
like it) solves the problem. I guess near/far are reserved
words in Cygwin?
Thereafter, FGFS compiles and runs under Cygwin.
I'm not using Andy's libs, but those built by Norman, with a couple of
tweaks which
Richard Bytheway wrote
I have the same problem with Main/renderer.cxx. Your solution
(or one very
like it) solves the problem. I guess near/far are reserved
words in Cygwin?
Thereafter, FGFS compiles and runs under Cygwin.
I'm not using Andy's libs, but those built by Norman,
Hello Erik,
Erik Hofman wrote:
Update of /var/cvs/FlightGear-0.9/data/Aircraft/fokker100/Models
In directory baron:/tmp/cvs-serv14144
Modified Files:
f70_cabin.ac fokker70.ac fokker70.xml
Log Message:
Some final changes, fixes and updates for some time
The model looks very nice
Vivian Meazza wrote:
Never noticed that; I keep FGFS at a higher level, but now that you mention
it, so it does. It's not a problem, but we ought to record all this
somewhere. We seem to go through some Cygwin drama every major update.
That's what Wiki's are for:
Martin Spott wrote:
The model looks very nice and the handling feels pretty easy. It's only
Thanks.
that I'm missing the cabin door being coupled to the parking brake as
it was in your first version ;-)
No, it's not ...
:-)
Erik
___
Flightgear-devel
Erik Hofman wrote:
Martin Spott wrote:
that I'm missing the cabin door being coupled to the parking brake as
it was in your first version ;-)
No, it's not ...
Hmmm, I don't understand: Did you decouple the cabin door from the
parking brake intentionally because you thing the coupling is
From: Andy Ross
Vivian Meazza wrote:
I have the same problem with Main/renderer.cxx. Your solution (or
one very like it) solves the problem. I guess near/far are reserved
words in Cygwin?
Goodness, that brings back memories. The near and far keywords are
holdovers from 16 bit DOS
Erik Hofman wrote
Vivian Meazza wrote:
Never noticed that; I keep FGFS at a higher level, but now that you
mention
it, so it does. It's not a problem, but we ought to record all this
somewhere. We seem to go through some Cygwin drama every major update.
That's what Wiki's are for:
* Josh Babcock -- Wednesday 30 March 2005 18:34:
Has anyone gotten the viewer program from the plib-examples package running?
When I compile and run it I get:
WARNING: fntLoadTXF: Failed to open 'data/default.txf' for reading.
Works perfectly. And the font is in CVS:
$ grep default.txf
* Erik Hofman -- Thursday 31 March 2005 13:27:
That's what Wiki's are for:
http://www.seedwiki.com/wiki/flight_gear/flight_gear_developer_documentation.html?wpid=123227
That's really where the FAQ should be maintained, too, as long as someone
is regularly archiving the contents. (I tried with
Melchior FRANZ wrote:
* Erik Hofman -- Thursday 31 March 2005 13:27:
That's what Wiki's are for:
http://www.seedwiki.com/wiki/flight_gear/flight_gear_developer_documentation.html?wpid=123227
That's really where the FAQ should be maintained, too, as long as someone
is regularly archiving
Fridtjof Busse wrote:
I'd say the X52 then has exactly this problem. One bit is always on,
since it has a mode-switch (doesn't do anything without the
windows-software) which always has a bit set.
You can write a joystick definition to use that mode switch however
you want; on all systems.
* Andy Ross [EMAIL PROTECTED]:
I'd say the X52 then has exactly this problem. One bit is always on,
since it has a mode-switch (doesn't do anything without the
windows-software) which always has a bit set.
You can write a joystick definition to use that mode switch however
you want; on
13 matches
Mail list logo
