On Thu, Mar 28, 2002 at 10:29:13PM -0800, Alex Perry wrote:
> > ATI Technologies Inc 3D Rage IIC AGP (rev 122), 8 MB vram.
>
> PCI id is 1002:4757 or 1002:475a according to
> http://pciids.sourceforge.net/iii/?s=1&i=1002
>
> According to the X headers (in the GLX source tree) that is a GW or GZ
/fgfs/cockpitsg-update-20020328.tar.gz
http://www.spiderbark.com/fgfs/cockpitsg-update-20020328.diffs.gz
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> ATI Technologies Inc 3D Rage IIC AGP (rev 122), 8 MB vram.
PCI id is 1002:4757 or 1002:475a according to
http://pciids.sourceforge.net/iii/?s=1&i=1002
According to the X headers (in the GLX source tree) that is a GW or GZ chip.
The Utah-GLX project, from CVS, does not accelerate this under XFr
> Are there any tricks to getting the CH Pro Pedals USB working under
> Linux 2.4? I tried plugging them in and got a regular message on the
> console (as with my existing gamepad), but I get a no such device
> error when I try to access them. All of the required modules are
> loaded, etc. etc.
Norman writes:
> Andy Ross writes:
> > Uh oh, we're going in circles again. Last words, I promise. :)
> I do not have a linux box to play with but I am almost willing
> to bet that a full screen undecorated window would have a
> somewhat similar speedup under X compared to drawing in
> a 'X' deco
> In Britain, as far as I know, we always use two-digit numbers
Nope, not in the US. Dunno about elsewhere.
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> *connects to http://www.uk.research.att.com/vnc/ and downloads VNC for the
> PC and Mac*
> *installs VNC in both computers*
Buys the second license to the appropriate version of Windows
> *does the 'happy dance'*
... it's the Microsoft tax dance.
Every computer that runs, or remotely contro
On Thursday, March 28, 2002, at 06:41 PM, Andy Ross wrote:
> Jonathan Polley wrote:
> > *trundles downstairs to PC*
> > *makes edit*
> > *compiles*
> > *says dirty words*
> > *trundles back upstairs to Mac*
>
> *ssh's into home machine from 7 miles away at work*
> *sips coke*
> *cvs update's Fli
Bernie,
I just made your change and now input.cxx compiles fine.
/**
* Settings for a mouse.
*/
struct mouse; // This is new code
friend struct mouse; // This is new code
struct mouse {
mouse ();
virtual ~mouse ();
int x;
int y;
SGP
The joystick axis "squared" mode seems to default to on, and is applied at the centre
of the axis, not the zero-point of the output value. In the default joysticks.xml,
the throttle bindings do not explicitly set it false, so the throttle movement is very
odd, so I edited my joysticks.xml.
Ho
In Britain, as far as I know, we always use two-digit numbers for the runway direction
- e.g. "09" or "09L" or "09R", not "9L". Is this not the case in the USA and
elsewhere?
- Julian
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.f
The recent 3D work is absolutely lovely.
With Jim's view manager work, can we re-instate the F5-F8 keys so that they move the
pilot's head up/down/left/right relative to the airframe? The effect would be
equivalent to the old 2D panel moving around the screen. In particular, moving the
pilot
Jonathan Polley wrote:
> *trundles downstairs to PC*
> *makes edit*
> *compiles*
> *says dirty words*
> *trundles back upstairs to Mac*
*ssh's into home machine from 7 miles away at work*
*sips coke*
*cvs update's FlightGear source*
*compiles*
*makes edit*
*debugs*
*sticks out toungue*
*deci
Gene Buckle writes:
> Andy, wouldn't even a mild optimization be of benefit when you're looking
> at things like poloygon budgets and such? Keep in mind that the more you
> can improve frame rate, the more you can throw in eye candy to keep it
> constant. *huge grin*
The point is that you'd
Andy Ross writes:
>
>Uh oh, we're going in circles again. Last words, I promise. :)
OK me too but
Win2k pIII 733 gForce2 fastest NVIDIA reference drivers available
for my machine, and I do test them all as they are released
startup location brakes on no hud no panel
windowed mode 56 f
I believe this was the height above ground level of the original
LaRCsim navion view point.
Curt.
Jim Wilson writes:
> Norman Vine <[EMAIL PROTECTED]> said:
>
> > Jim Wilson writes:
> > >
> > >Norm, where did you get that "magic" number? I know its got
> > >something to do
> > >with the near
Gene Buckle wrote:
> Andy Ross wrote:
> > ballpark). But it's just not like that anymore; really. It's a mild
> > optimization at best.
>
> Andy, wouldn't even a mild optimization be of benefit when you're looking
> at things like poloygon budgets and such? Keep in mind that the more you
David Megginson wrote:
>
> Jonathan Polley writes:
>
> > I reverted input.hxx back to what was in CVS and moved the enumeration
> > from being private to public and MSVC now likes using an enumeration
> > element to define an array. Why the compiler cares about an enum being
> > private vs.
On Thursday, March 28, 2002, at 04:14 PM, David Megginson wrote:
> Does it still work if the enum is protected? I'd like to keep things
> as well encapsulated as possible.
*trundles downstairs to PC*
*makes edit*
*compiles*
*says dirty words*
*trundles back upstairs to Mac*
MSVC gives a simil
> ballpark). But it's just not like that anymore; really. It's a mild
> optimization at best.
>
Andy, wouldn't even a mild optimization be of benefit when you're looking
at things like poloygon budgets and such? Keep in mind that the more you
can improve frame rate, the more you can throw in e
Andy Ross writes:
> The c.g. isn't a fixed location. It moves when you burn fuel, load
> cargo or drop bombs, sometimes quite significantly. When I looked,
> actually, all of the model stuff was relative to the airfame. I can
> promise that YASim's position output is that of the aircraft n
Norman Vine wrote:
> Andy Ross writes:
> > [* What, exactly, does game mode do? My impression was that it simply
> > set the video mode through GDI before creating the OpenGL context.
> > This isn't an optimization, per se. Can someone more familiar with
> > GLUT comment?]
>
>
> In Wi
/fgfs/cockpitsg-update-20020328.tar.gz
http://www.spiderbark.com/fgfs/cockpitsg-update-20020328.diffs.gz
Best,
Jim
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Tony Peden writes:
> Yes. Commenting out the test right at the top of joydev.c in the
> kernel sources will allow them to work.
Tony:
Would it be possible to send me the change? I've having trouble
finding it. The CVS $Id$ at the top of the file is
* $Id: joydev.c,v 1.19 2001/01/10 19:49
Norman Vine wrote:
> Andy Ross writes:
> > What I'd really like to see is for the panel's draw() method to be
> > called with a pre-built matrix stack that transforms model/aircraft
> > coordinates (back/left/up, with the origin at the nose) into screen
> > space.
>
> I realize that this is
Jonathan Polley writes:
> I reverted input.hxx back to what was in CVS and moved the enumeration
> from being private to public and MSVC now likes using an enumeration
> element to define an array. Why the compiler cares about an enum being
> private vs. public, I will never know (althoug
Norman Vine writes:
> Which is the FAST lane to the underlying video in that the Win32
> Windowing manager is bypassed for this window < ie all the region
> clipping code etc. > so the speedup is not a driver bug !
Under X11, DRI's approach seems to be to allow the window manager to
recalcula
Andy Ross writes:
> What I'd really like to see is for the panel's draw() method to be
> called with a pre-built matrix stack that transforms model/aircraft
> coordinates (back/left/up, with the origin at the nose) into screen
> space. Then we just store corner locations for the panel and dr
Andy Ross writes:
>
>What I'd really like to see is for the panel's draw() method to be
>called with a pre-built matrix stack that transforms model/aircraft
>coordinates (back/left/up, with the origin at the nose) into screen
>space.
I realize that this is jsut a translation but why at the nose
Its ALIVE!!!
I reverted input.hxx back to what was in CVS and moved the enumeration
from being private to public and MSVC now likes using an enumeration
element to define an array. Why the compiler cares about an enum being
private vs. public, I will never know (although I have seen this beha
Andy Ross writes:
>
>[* What, exactly, does game mode do? My impression was that it simply
>set the video mode through GDI before creating the OpenGL context.
>This isn't an optimization, per se. Can someone more familiar with
>GLUT comment?]
In Windows it does
status = ChangeD
David Megginson wrote:
> Are there any tricks to getting the CH Pro Pedals USB working under
> Linux 2.4? I tried plugging them in and got a regular message on the
> console (as with my existing gamepad), but I get a no such device
> error when I try to access them. All of the required modul
David Megginson wrote:
> For the record, if anyone wants to fix that, they are welcome too.
> The 2D panel was my very first OpenGL project, written as a learning
> exercise, and I do not deny that it is sloppy and poorly-integrated in
> its current state.
Actually, for the 2D panel this beha
Norman Vine wrote:
> I have always thought that FGFS development has been primarily aimed
> at a RAW OPENGL SURFACE which is considerably different then any
> Window !
This isn't the case, even in windows. OpenGL rendering (or DirectX,
for that matter), is always directed at a window. There'
Hi,
> OK my wording was a little strong :-)
>
Not really, the idea behind the glass displays is for the development of
full scale cockpit simulators. so things like framerate and fidelity are
major design objectives to achieve the highest level of realism and
performance.
Right now you can get g
--- David Megginson <[EMAIL PROTECTED]> wrote:
> Are there any tricks to getting the CH Pro Pedals
> USB working under
> Linux 2.4? I tried plugging them in and got a
> regular message on the
> console (as with my existing gamepad), but I get a
> no such device
> error when I try to access them.
Are there any tricks to getting the CH Pro Pedals USB working under
Linux 2.4? I tried plugging them in and got a regular message on the
console (as with my existing gamepad), but I get a no such device
error when I try to access them. All of the required modules are
loaded, etc. etc.
I remembe
On Thu, 28 Mar 2002 08:20:09 -0800 (PST),
Alex Perry <[EMAIL PROTECTED]> wrote in message
<[EMAIL PROTECTED]>:
> > Danie Heath asks:
> > > I've got a friend who publishes an aviation magazine, and I was
> > > wondering what you outlook is on publicity ? Will it be alright
> > > for me to organ
--- Norman Vine <[EMAIL PROTECTED]> wrote:
> Alex Perry writes:
> >
> >> I could care less about those folks running FGFS
> in a window
> >> this is a FlightSIM and the operative word is
> FRAMERATE
> >> which any windowing system KILLS.
> >
> >I'm sure the glass cockpit people will disagree
> wi
Andy Ross writes:
> Not only should the panel not be going to the viewer for this
> information; it shouldn't be going *anywhere* for the information. It
> should simply spew vertices in the aircraft's coordinate frame at
> OpenGL, and expect that everything should work. That way, you can d
Norman Vine writes:
> As I said it is 'nice' that we can run in a window and I also use windowed
> mode alot esp. when debugging etc., and we certainly want to keep this
> capability, but IMHO 'windowed mode' should not be our 'primary target'..
Nearly every Linux (and probably FreeBSD) user
Alex Perry writes:
> > I could care less about those folks running FGFS in a window
> > this is a FlightSIM and the operative word is FRAMERATE
> > which any windowing system KILLS.
It does in Windows, when I've tried it, but it doesn't seem to hurt
under X11 with DRI. Back when I had a Vood
hello.
any macintosh developers here? maybe you can help me.
i'm looking for a book or something to learn PowerPC assembly
language (preferably for the G4). is there such a book? unfortunately
i don't have the money to fly to the USA and visit an Apple seminar
(don't even know if they do that k
Andy Ross writes:
>
>If you see a significant boost to frame rate in game mode, my
>suspicion is that what you're seeing is the horrifically slow updates
>to the windows text console, and not the lack of a page flip
>optimization.
game mode, on windows at least, is still significantly faster
and
Norman Vine wrote:
> I could care less about those folks running FGFS in a window this is
> a FlightSIM and the operative word is FRAMERATE which any windowing
> system KILLS.
This really isn't true anymore. It used to be that a big part of the
rendering time in windowed mode was the blit of
Erik Hofman writes:
>
>David Megginson wrote:
>.
>>
>> What does everyone else prefer -- should the mouse get stuck on the
>> window edges in constrained mode, or should it wrap around?
>I have no
>> strong preference either way. There are good arguments in favour of
>> both: with wrap-around,
David Megginson wrote:
> With Jim's latest patches, the 3D model is drawn in its own scene
> graph; if we're in 3D cockpit view, the model also has a different
> clip plane.
>
> Currently, we set the near/far clip plane for the scenery to
> 0.5/12000.0 on the ground and 10.0/12000.0 in the a
Jim Wilson wrote:
> Well I haven't done that. Ideally (perhaps not a good word :)) the
> panel code would get the orientation from the FGModel class and a
> panel XYZ from the model's xml file. We really don't want anything
> to be dependant on the viewer for that kind of data.
Sure we do (
> >> I could care less about those folks running FGFS in a window
> >> this is a FlightSIM and the operative word is FRAMERATE
> >> which any windowing system KILLS.
> >I'm sure the glass cockpit people will disagree with you.
> >Certainly I do; I have a bunch of instrumentation in other windows.
Alex Perry writes:
>
>> I could care less about those folks running FGFS in a window
>> this is a FlightSIM and the operative word is FRAMERATE
>> which any windowing system KILLS.
>
>I'm sure the glass cockpit people will disagree with you.
>Certainly I do; I have a bunch of instrumentation in ot
David Megginson wrote:
.
>
> What does everyone else prefer -- should the mouse get stuck on the
> window edges in constrained mode, or should it wrap around? I have no
> strong preference either way. There are good arguments in favour of
> both: with wrap-around, you still see cursor movement
> * Norman Vine -- Thursday 28 March 2002 17:16:
> > I could care less about those folks running FGFS in a window
> > this is a FlightSIM and the operative word is FRAMERATE
> > which any windowing system KILLS.
>
> Huh ... forget my other (arrogant) reply. I guess you are right.
> I just didn't
David Megginson <[EMAIL PROTECTED]> said:
> I have no problem with adding them to the property tree, but I suspect
> that they will be both model- and view-specific,
Well I hope not. I've got an idea, hang on a bit.
Best,
Jim
___
Flightgear-devel
* Norman Vine -- Thursday 28 March 2002 17:16:
> I could care less about those folks running FGFS in a window
> this is a FlightSIM and the operative word is FRAMERATE
> which any windowing system KILLS.
Huh ... forget my other (arrogant) reply. I guess you are right.
I just didn't manage yet to
* Norman Vine -- Thursday 28 March 2002 17:16:
> Nah
>
> I could care less about those folks running FGFS in a window
> this is a FlightSIM and the operative word is FRAMERATE
> which any windowing system KILLS.
Hehe, you are obviously a windows kind of guy, which explains that
you don't know mu
> Jim Wilson writes:
> > Would it be ok with everyone to add the values for the two near and
> > far plane settings to preferences.xml? I'd like to be able to use
> > them in makeing eyepoint and model origin translation adjustments.
> I have no problem with adding them to the property tree, b
Norman Vine <[EMAIL PROTECTED]> said:
>
> I could care less about those folks running FGFS in a window
> this is a FlightSIM and the operative word is FRAMERATE
> which any windowing system KILLS.
>
If you got a real operating system ;-) that runs X you'll find there's a very
small difference
Jim Wilson writes:
> Would it be ok with everyone to add the values for the two near and
> far plane settings to preferences.xml? I'd like to be able to use
> them in makeing eyepoint and model origin translation adjustments.
I have no problem with adding them to the property tree, but I sus
David Megginson writes:
>
>What does everyone else prefer -- should the mouse get stuck on the
>window edges in constrained mode, or should it wrap around? I have no
>strong preference either way. There are good arguments in favour of
>both: with wrap-around, you still see cursor movement while
David Megginson <[EMAIL PROTECTED]> said:
>
> fgfs --aircraft=c172-3d
>
> the use the mouse to scroll the view downwards. At first I thought
> that the model was just sitting too low on the runway, but the problem
> vanishes when I make the 3D model clip plane the same as the scenery
> one.
Norman Vine <[EMAIL PROTECTED]> said:
> Jim Wilson writes:
> >
> >Norm, where did you get that "magic" number? I know its got
> >something to do
> >with the near value, or length of depth vector, but if you can
> >give me the
> >formula it'd save my wee little brain the effort :-)
> >
>
> Jus
* David Megginson -- Thursday 28 March 2002 15:59:
> with the cursor stuck at the edges, you're less likely to loose
> track of it.
... and you don't lose track of the whole fgfs window when using a window
manager with automatic desktop switching. (fvwm2, KDE with that feature
enabled, ...) Of co
* David Megginson -- Thursday 28 March 2002 16:01:
> We can patch up Navaids/default.fix.gz, but be warned that the file is
> autogenerated and that all changes will be blown away the next time we
> get an update from Robin Peel. Your best bet is to submit the changes
> to Robin as well, to make
* Melchior FRANZ -- Thursday 28 March 2002 16:50:
> ... and you don't lose track of the whole fgfs window when using a window
> manager with automatic desktop switching.
Hehe ... nonsense. Either version would cause problems with such a window
manager.
m. :-]
_
Melchior FRANZ writes:
>
>* David Megginson -- Thursday 28 March 2002 15:59:
>> with the cursor stuck at the edges, you're less likely to loose
>> track of it.
>
>... and you don't lose track of the whole fgfs window when using a window
>manager with automatic desktop switching. (fvwm2, KDE with t
Norman Vine <[EMAIL PROTECTED]> said:
>
> The default use to be wrap in horizontal and not be able to go pass
> straight-up or down. I am assuming that this behaviour was generally
> acceptable as there was VERY little < or none > discussion as to it's
> short comings on the list
>
Yes, actua
Jim Wilson writes:
>
>Norm, where did you get that "magic" number? I know its got
>something to do
>with the near value, or length of depth vector, but if you can
>give me the
>formula it'd save my wee little brain the effort :-)
>
Just a WAG inspired by the value of
alt_adjust_ft
which is
Jim Wilson writes:
> This patch creates a seperate scene graph for the cockpit. The
> near plane is only moved up when in the interior (pilot) view.
> This is because with rounding (I presume) it the visible ground is
> a bit up higher than it is with the older nearplane setting. Not
> muc
Norman Vine writes:
> > if (mode.constrained) {
> >bool need_warp = false;
> >if (x <= 0) {
> > x = xsize - 2;
> > need_warp = true;
> >} else if (x >= (xsize-1)) {
> > x = 0;
>
> should be x = 1;
Oops -- I missed this one. It looks like I guessed Norm
Jim Wilson <[EMAIL PROTECTED]> said:
> Andy Ross <[EMAIL PROTECTED]> said:
>
> > Your changes to put the panel in a scene graph are the big part of the
> > solution. Really, the panel should be drawn immediately after the
> > aircraft model, with the same matrix environment. If you can get thi
Melchior FRANZ writes:
> There are some bugs in the Navaids/default.fix.gz file.
Gazillions of them.
> Here are the
> most obvious ones:
>
> lat lon
>ORTAC 49.595700-20018.00
>PEPIS 51.114800-11437.00
>PERLA 13.765000-88695.
Norman Vine writes:
> Here is a start at a 'positionable' mouse that I find makes the new
> mouse MUCH easier to deal with when switching modes and a
> doMouseMotion() that is MUCH closer to what we had
Great, thanks.
> if (mode != m.current_mode) {
> m.current_mode = mode;
> gl
* [EMAIL PROTECTED] (Danie Heath) [2002.03.29 00:16]:
> I've got a friend who publishes an aviation magazine, and I was wondering
> what you outlook is on publicity ? Will it be alright for me to organize
> an article for you guys ?
>
> Regards
>
> Danie Heath
I don't call the shots aroun
Julian Foad writes:
> I experimented with the effect of inlining on code size and compile
> times (but not run-time performance) on the src/FDM/JSBSim tree
> within FlightGear CVS as of about a week ago. I did this by
> supplying different compiler options with "make
> CFLAGS=... CXXFLAGS=.
Would it be ok with everyone to add the values for the two near and far plane
settings to preferences.xml? I'd like to be able to use them in makeing
eyepoint and model origin translation adjustments.
Norm, where did you get that "magic" number? I know its got something to do
with the near valu
Jonathan Polley wrote:
>
> On Thursday, March 28, 2002, at 06:12 AM, David Megginson wrote:
>
>> Jonathan Polley writes:
>>
>>> .\src\Input/input.hxx(321) : error C2248: 'MAX_MOUSE_BUTTONS' : cannot
>>> access private enumerator declared in class 'FGInput'
>>> .\src\Input/input.hxx(250)
Jonathan Polley writes:
> This brings about the philosophical question, Is is possible to work
> around ALL MSVC bugs?
I'm pretty sure that people are successfully building FlightGear
already with MSVC 6.
> I also don't like the name space problems that #defines cause, especially
> when i
Doh! I just had a thought. Could MSVC be having a problem because the
enum containing MAX_MOUSE_BUTTONS is *private* rather than public? I have
seen some compilers apply different rules to private vs. public data in
that they take an 'ignorance is bliss' approach to private data (i.e.,
sinc
On Thursday, March 28, 2002, at 06:12 AM, David Megginson wrote:
> Jonathan Polley writes:
>
>> .\src\Input/input.hxx(321) : error C2248: 'MAX_MOUSE_BUTTONS' : cannot
>> access private enumerator declared in class 'FGInput'
>> .\src\Input/input.hxx(250) : see declaration of
>> 'MAX_MOU
Andy Ross <[EMAIL PROTECTED]> said:
> Your changes to put the panel in a scene graph are the big part of the
> solution. Really, the panel should be drawn immediately after the
> aircraft model, with the same matrix environment. If you can get this
> put together (forgive me if you already have
On Thu, 28 Mar 2002 08:14:43 +0200,
"Danie Heath" <[EMAIL PROTECTED]> wrote in message
<[EMAIL PROTECTED]>:
> Hi All
>
> I've got a friend who publishes an aviation magazine, and I was
> wondering what you outlook is on publicity ? Will it be alright for
> me to organize an article for you gu
* way lee -- Thursday 28 March 2002 13:34:
> I want to ask where is the definition of class c4_FloatRef or c4_FloatProp ?
In the metakit library which you have to install. You find a copy of the
sources in the SimGear directory: metakit-2.4.3-33.tar.gz
m.
__
When I compile flightgear in Microsoft Visual C++ 6.0, it shows following imformation:
runways.obj : error LNK2001: unresolved external symbol "public: class c4_FloatRef __thiscall c4_FloatProp::operator()(class c4_RowRef const &)const " (??Rc4_FloatProp@@QBE?AVc4_FloatRef@@ABVc4_RowRef@@@Z)simple
Danie Heath writes:
> I've got a friend who publishes an aviation magazine, and I was wondering
> what you outlook is on publicity ? Will it be alright for me to organize an
> article for you guys ?
As far as I'm concerned, go for it.
All the best,
David
--
David Megginson
[EMAIL PROTE
Jim Wilson writes:
> It looks like somehow the panel is locking the the offset adjustments. So
> that if you move into the back seat the panel comes with you.
Right -- Andy is not yet using the x/y/z view offsets for the panel
transform. Andy?
All the best,
David
--
David Megginson
[EM
Norman Vine <[EMAIL PROTECTED]> said:
> >This patch creates a seperate scene graph for the cockpit. The near plane
> is
> >only moved up when in the interior (pilot) view. This is because with
> >rounding (I presume) it the visible ground is a bit up higher than it is
> with
> >the older nearpl
Jonathan Polley writes:
> .\src\Input/input.hxx(321) : error C2248: 'MAX_MOUSE_BUTTONS' : cannot
> access private enumerator declared in class 'FGInput'
> .\src\Input/input.hxx(250) : see declaration of 'MAX_MOUSE_BUTTONS'
>
> Changing the enumeration to a series of #defines solve
There are some bugs in the Navaids/default.fix.gz file. Here are the
most obvious ones:
lat lon
ORTAC 49.595700-20018.00
PEPIS 51.114800-11437.00
PERLA 13.765000-88695.00
RIBOS 13.95-87651.00
SOMBU 5959.31 000
Andy Ross wrote:
>
> Julian Foad wrote:
> > Code size:
> >secondsbytes options
> > Smallest:203 761360 -g -O1 -finline-limit-6 -finline-functions
> > Smallest O2: 233 767064 -g -O2 -finline-limit-6 -finline-functions
> > Default: 3881328284 -g -O2
> >
89 matches
Mail list logo
