Hi all,
RE: FG MAC OS 10.3 binary
Can anyone help with such a beast? Have tried the 0.9.3 (from
Wally's World) and 0.9.4 binary (FlightGear-0.9.4.tgz) with
the current 0.9.6 scenery base, thank you for these, but no
go ... even when the 'version' file is altered to match!
Says missing
I'm trying to build FlightGear 0.9.1 on Windows 98 using MSVC 6.0.
However, I get a series of operator is ambiguous errors in mk4.inl
from
Compiling...
runways.cxx
e:\flightgear\src\flightgear-0.9.1\src\include\config.h(5) : warning
C4005:
'ENABLE_PLIB_JOYSTICK' : macro redefinition
msvc6 update - 23 Jul 2003
Wow! What a difference a few months can
make ... there's oodles more to see - the
terminal buildings, sf tower, bridge, etc,
etc, etc ... fantastic ...
The fgfs base 0.9 data cvs download was around
6 hours on my ISDN (56K V120) dial up line,
some 140 MB, but the
miss-quote-seen-here-recently -
And before I'm pointed at FGSD, 'the-free-source',
I've looked - but with almost no documentation it is
not usable.
IMHO, if you can download the 100% of the 'free' SOURCE,
you already have 100% of the 'free' 'documentation'? What
more can you 'want' from the
I too maintain my own, and if you read a little way
back in the achives I mentioned you have to also
update FG/src/include/config.h, which arrives as
config.h-msvc6, with something like -
#ifndef GLUT_H // per MSVS install directory
#define GLUT_H GL\glut.h
#endif // #ifndef GLUT_H
Wow :-)) Although I continue to read here, almost daily, I
had not actually run FG since abt mid-Nov-02, and
again WOW! What improvements there have been.
I had noted back in Nov. that the file $FG_ROOT/system.fgfsrc,
where I keep 'my' default start-up, is no longer supported -
only it seems
Dear All,
oops, pardon moi ... RE:MSVC6 Update - continued ...
This i added, explicily, to fg_init.cxx
// Next check the 'root' for a system.fgfsrc file
if ( aircraft.empty() ) {
// Check for $fg_root/system.fgfsrc
SGPath config( globals-get_fg_root() );
Success at last!
Added one more fix in plib -
In ssgContext.cxx, added the line
ssgContext::ssgContext () {
...
ovCullface = FALSE ;
ovState = NULL ;
and re-built plib (Debug and Release)
And i was up and flying. Well not quite. Running the Debug
version under the default
Excuse my in-attention to important CaSe detail ...
read -dP instead of -Dp. Pardon moi (the stupid idiot) :-) ...
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: MSVC6 compile - WIN98 SE crash -
IMHO, looking at new_gui.cxx, mildly suggests -
NewGUI::init ()
{
#ifdef FGFS
SGPath path = globals-get_fg_root();
path.append(/gui);
readDir(path.c_str());
#else // !FGFS
char path[1024];
ulMakePath(path, getenv(FG_ROOT), gui);
Strange Scenery Bug! is NOT a bug at all
around 36D 59.981N -122D 11.236W. As i passed
this point the OCEAN dropped about 25 feet!
Sounds like maybe there are two versions of scenery installed
FGFS used to distribute 'ocean tiles' but the newer versions
manufacture these.
This sounded
Did cvs updated plib, simgear, flightgear, and of course
fgfsbase ... built in 1, 2, 3 order ...
3. FlightGear\FlightGear.dsw
First copy FlightGear\src\include\config.h.msvc6
to config.h, and manually change the version
to 0.7.10 ... just like someone had to do in
config.in ...
Twas i that
However, I do think we could clean it up a bit with a pre-processor
#define AEROINTFUNC double (FGAerodynamics::*)(int) const
or typedef ...
... renaming ... to remove the ambiguity any better?
As someone - i think - mentioned, IMHO it would be
better to have single getter functions, like
Hi,
I'm back, actually already for a few weeks ...
Latest cvs plib, SimGear, FlightGear, fgfsbase ...
I now choose the debug default of plib, and
metakit, namely 'Debug Multithreaded', thus must
'remember' to check this setting is consistant for
each msvc build ...
1. JSBSim - Tie()
Richard Bytheway - perf. ... RAM and/or Video Card
Things to check: ...
all checked and thanks for the tips n info.
Tried to add the 256 MB, but ran into 'real' problems, and
must leave that until later ...
Still must find the 'Unika' book to find out what 'video' this is. In
this fr. system
Windows 98 SE ... stock standard stuff.
Tell me about the display car dyou have, how much memory there?
Must search for the 'book' that came with the machine for the actual
'card'
but i remember something like AGP something. The driver is the Intel
810e Chipset Graphics Driver PV 2.1 (as Alex
Geoff:
It appears that your machine may not be capable of running FlightGear
properly. This stuff should not be happening. ...
... I ran into similar things to what you are seeing a year ago when I
had a seriously underpowered machine/display card.
SUMD = 'seriously underpowered
JSBSim (def), YASim and 'magic' - zlib
Note: JSBSim config files allow the user to specify a log file to be
generated
Wow! Yes, when I looked around after the
'flight' I saw this abt 6 MB csv file,
and wondered - 'where did that come
from?'. I had a quick peek inside and
deleted that first one
It's in FG CVS now.
fix it forever ... death to QNAN = bliss :-))
JSBSim - ok, got the new FGInitialCondition.cpp
with vers 1.33 2002:01:24 ... I certainly 'like'
the few added protective if( vt 0.01 ) return 0;
Let's see if that helps ... Also some other
small updates - httpd.cxx,
A sg/fg (DEBUG) build on yesterdays/todays simgear/flightgear trees
worked well with --fdm=magic.
JSBSim stops after the QNAN's,
There is a fix for the FGInitialCondition problem in JSBSim
CVS, don't think it has migrated its way into FG, though.
If you want it, you should be able to
I asked for --tile-radius, because I don't get enough tiles if I
fly at good visibility (--fog-disable or hitting 'Z' a few times).
only schedules tiles for loading when you cross a tile boundary
Is this out of line ... using --fdm=magic ... rise to say 15,000 feet,
clear fog and clouds, no
Geoff McLane wrote:
YASim, and it all went well ... I had a 'reasonable' flight,
'stuttering' along, but some moments when it came together ...
Andy asked:
YASim shouldn't be stuttering, certainly. Which aircraft were you
using? What were the symptoms?
I was using the c172-yasim
ok, have now tried the c310 - added
--aircraft=c310
to my system.fgfsrc file ...
The log ends almost identically ...
In amongst it all I can see -
[36m
Reading Flight Control[39m
Control System Name: FGFCS:c310
so it was with the c310 ...
Geoff McLane wrote:
When running your fgfs.exe the log ends abruptly with
* Before globals-saveInitialState()
... first thing ... is delete initial_state; but initial_state ... 0
Q Can you delete a NULL pointer?
A ... deleting a pointer with a value of zero...
is guaranteed
Have you tried my Windows binary
http://www.vso.cape.com/~nhv/files/fgfs/fgfs.exe.gz
Initially JSBSim went crazy during the cfg xml read
( JSBSim Flight Dynamics Model v0.9.1 [cfg v1.57])
but this is caused by the cvs update adding things
like the following to %FG_ROOT%\Aircraft\c172\c172.xml
re: AVOID #QNAN
I changed FGAuxilary.cpp in the following -
Uhmm... what problem were you having with this, there shouldn't be any
name clashes here. (There is only one global variable in JSBSim:
debug_lvl)
None. No 'problem' as such. I was chasing down an ellusive FPU 'explosion'
I got
a 'appy new yrrr ta ya all ...
I am overjoyed my Yasim c172 took off with ease. I
was surprised that so much 'leveling' was required. I have
flown 152, 172 and 182, and none seemed so 'skitish' as
I remember ...
Just an observation - I now jump for Crtl+H to stabalize
the heading as I gather
Have not had any success with JSBsim. :-( My engine RPM
stays 'stuck' at ZERO, despite multiple Page-Ups,
Did you start the engine (click twice on the panel to activate both
magnetos and then use the middle mouse button to activate the starter)?
Ok, will try that and advise ... may be a
28 matches
Mail list logo
