[Flightgear-devel] Weekly CVS Changelog Summary: FlightGear data

2008-03-16 Thread Curtis L. Olson
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2008-03-09_14:57:07 (abory)
/var/cvs/FlightGear-0.9/data/Aircraft/A-10/Models/Attic/apibullet-tracer.ac

- David Bastien:
Stores repertory cleaning.


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2008-03-09_14:57:08 (abory)
/var/cvs/FlightGear-0.9/data/Aircraft/A-10/Models/Attic/apibullet-tracer.xml

- David Bastien:
Stores repertory cleaning.


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2008-03-09_14:58:10 (abory)
/var/cvs/FlightGear-0.9/data/Aircraft/A-10/Models/Stores/GAU-8A/apibullet-tracer.ac
/var/cvs/FlightGear-0.9/data/Aircraft/A-10/Models/Stores/GAU-8A/apibullet-tracer.xml

- David Bastien:
Stores directory cleaning.


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2008-03-10_08:47:29 (martin)
/var/cvs/FlightGear-0.9/data/Models/Aircraft/737-01.rgb
/var/cvs/FlightGear-0.9/data/Models/Aircraft/737-static.ac
/var/cvs/FlightGear-0.9/data/Models/Aircraft/747-01.rgb
/var/cvs/FlightGear-0.9/data/Models/Aircraft/747-static.ac

Group immovable aircraft, those who are meant to be placed by an
OBJECT_SHARED entry in Scenery .stg files, in a directory separate from
other geometries.


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2008-03-10_09:11:22 (martin)
/var/cvs/FlightGear-0.9/data/Models/Aircraft/ARFF-trainer.ac
/var/cvs/FlightGear-0.9/data/Models/Aircraft/ARFF-trainer.xml


Herewith I declare this skeleton as being an aircraft as well  :-)


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2008-03-15_05:57:18 (vmmeazza)
/var/cvs/FlightGear-0.9/data/Aircraft/seahawk/seahawk-3d-2t-yasim.xml

Remove tanks from the non-tank version


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2008-03-15_15:06:13 (helijah)
/var/cvs/FlightGear-0.9/data/Aircraft/Zlin-50lx/Nasal/Attic/pilot-g.nas

*** empty log message ***


2f585eeea02e2c79d7b1d8c4963bae2d

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


[Flightgear-devel] Weekly CVS Changelog Summary: FlightGear source

2008-03-16 Thread Curtis L. Olson
2f585eeea02e2c79d7b1d8c4963bae2d

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] autopilot u_min and u_max...

2008-03-16 Thread SydSandy
On Sat, 15 Mar 2008 20:51:08 -0700
SydSandy [EMAIL PROTECTED] wrote:

 Hi all , 
   I've been trying to change the xmlautopilot to use prop and value 
 for the u_min and u_max properties , and currently have quite a mess on my 
 hands right now :)
 The idea is to have a min and max property to control bank-limit / pitch with 
 a panel knob ...
 setting the u_min and u_max from a property seems to be working , but I get 
 some strange things happening . The pi-simple controller isnt clamped anymore 
 (so i removed the clamp check )... and the output goes immediately to the 
 u_min value...although u_min and u_max are checked every update... 
 Has anyone else attempted this , with good results ? Or , hopefully , already 
 implemented this ?
 Anyway , I'll keep plugging away at it, the answer is probably staring me in 
 the face and I can't see it.
 Is this something that should be implemented anyway ?
  Cheers 
 
 -- 
 SydSandy [EMAIL PROTECTED]
 


OK it seems the errors were caused by my autopilot config file, u_min and u_max 
work with  prop and value  as expected , but I need to test further , just 
in case ...
Cheers 
-- 
SydSandy [EMAIL PROTECTED]

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Rogue objects at KSQL

2008-03-16 Thread drew
On Sunday 16 March 2008 15:47:15 George Patterson wrote:
 Hi All,

 There are a few objects that have been misplaced at KSQL.
 1. Light tower to the right of Runway 30.
 2. A large building (black and grey at the end of the same runway)

G'day George,

I flew around KSQL in the ufo and, after comparing with GE, that large 
building to the left of the threshhold on runway 30 is most definitely dodgy.
All the AI light aircraft were clipping their wings on final!
You can go to wherever_your_scenery_is/Objects/w130n30/w123n37/942051.stg
and delete the line:
OBJECT_SHARED Models/fgfsdb/generic_skyscraper_03.ac -122.2469440 37.5088890-
490.86 180
That should get rid of the blue building.
I couldn't pin down the light tower in the middle of the taxiway but if you 
do, make it a windsock and place it about 50 metres north-east - it would 
just about match the image in GE.   :)

Regards,

Drew

 It seems that the green and white light from the tower is solid.

 I have take a screen shot or two which I haven;'t attached to this email.

 Assuming that this is not a known bug, any comments on how to fix
 these two artifacts.

 (I though the problem of light being solid was fixed.)

 I am using Flightgear CVS version with glut.

 Regards


 George

 -
 This SF.net email is sponsored by: Microsoft
 Defy all challenges. Microsoft(R) Visual Studio 2008.
 http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
 ___
 Flightgear-devel mailing list
 Flightgear-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/flightgear-devel


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] FG build fails with plib 1.8.5 and SLD

2008-03-16 Thread Alasdair Campbell

On Sat, 2008-03-15 at 14:49 -0600, dave perry wrote:
 Alasdair Campbell wrote:
  So all is OK now except for the hotspots on my c172 radio stack which
  have gone haywire. Clicking on the COM2 swap button switches COM1 radio,
  Clicking the ADF buttons change the COM2 radio, the Autopilot buttons
  are ineffective, etc.etc. Can anyone confirm this behaviour?
 

 Try resizing the window.  I pointed this out more that a month ago, but 
 Tim Moore (who is maintaining osgviewer) was unable to reproduce the 
 problem on his system.  The resize can be dragging a side of the window 
 or minimize/maximize the window.  The mouse coordinates are not properly 
 initialized (I speculate) until this is done.
 
 - Dave Perry
 

Thank You, Dave, you are correct. Min/max the window and the hotspots
behave as expected. Sorry I missed your original post.

Kind regards,

Alasdair
 -
 This SF.net email is sponsored by: Microsoft
 Defy all challenges. Microsoft(R) Visual Studio 2008.
 http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
 ___
 Flightgear-devel mailing list
 Flightgear-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/flightgear-devel


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Till's MP patches /feedback -- WAS:MP forest fire model!

2008-03-16 Thread Georg Vollnhals
till busch schrieb:
 hi georg,

 i am currently working on a patch that adds model-paging. models (ai, 
 multiplayer and, to some degree, scenery) will be loaded in a different 
 thread. this is more or less what you describe.

 some successful testing has been done already. so i hope to get it integrated 
 into cvs soon.

 if you'd like to (beta-)test, feel free to get the latest versions of my 
 patch 
 at: http://flight.bux.at

 currently these are: 
 http://flight.bux.at/0001-model-paging-v0.4.0-beta-simgear.patch
 http://flight.bux.at/0001-model-paging-v0.4.2-beta-flightgear.patch

 note that i'm not pushing for integration yet. the changes still need some 
 clean-up and minimal documentation ;-)

 i'll be glad for any comments (success or regression reports, for the matter)

 cheers,

 -till

   
Hi Till,

I applied your patches after updating my FG OSG CVS version and compiled
it. All went fine without problems.

Then I tried two multiplayer sessions at KSFO this (European) sunday
afternoon. There was a lot of traffic and several logging in and out due
to crashes. I flew outbound KSFO to the south and made a HOGE for round
about 20 Minutes. Trying to hold my position and altitude and observe
the traffic.

Congratulations! There were still short framerate depressions which
caused a little instability but always to manage, some pedal-work to get
the nose into the wished direction and some collective-corrections -
this is really great! And a big, big ,big difference to the old
problematic behaviour when I found myself in some uncontrollable flight
after a 3 second pause.

Not to mention, further flying and a smooth landing at KSFO hangar - ALL
WITH REALLY A LOT OF PEOPLE JOINED!

And as I was also active with local flights without the mp server
connected I can say that until now I made no negative observation with
this patch.

This is a big step forward, I'm going to log into mp again as the
fun-factor is back again.
A further report will follow after some more testing-time, I hope that I
can validate what I reported today.

Thank you very much!
Regards
Georg EDDW


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


[Flightgear-devel] KLSV add-on is available

2008-03-16 Thread alexis bory
Hi all,

http://croo.murgl.org/fgfs/scenery/KLSV/

Not all the shared models are already in fgfsdb, and the new terrain 
won't be available until next scenery build,

*but* you can already download 2 tarballs from my website and anjoy the 
full Nellis AFB.


Be sure that we do our best so this airport will be fully included in 
the standard scenery with standard process.

I also hope it wont eat too much fps on the weakest PC's...


Enjoy,

Alexis

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Walking around

2008-03-16 Thread Heiko Schulz

--- Detlef Faber [EMAIL PROTECTED] schrieb:

 Hi everybody,
 
 I've just committed a Walk View to the jeep, so a
 virtual passenger
 can get out of the car and walk around in the
 scenery.
 
 The View follows the terrain height and the
 movements gets blocked by
 steep slopes and scenery models (sadly not by random
 scenery models as
 they are insensitve to collisions).
 It is planned to be integrated with the interiour
 movement like in the
 Albatross, so one can seamlessly walk inside and
 outside of the
 Aircraft.
 
 Suggestions and comments are welcome!
 
 Greetings
 
 Detlef
 
I can only say: wow! not yet tested, but this sounds
awsome! Thanks for your work!

Regards
HHS

still in work: http://www.hoerbird.net/galerie.html
But already done: http://www.hoerbird.net/reisen.html


  E-Mails jetzt auf Ihrem Handy.
www.yahoo.de/go

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Walking around

2008-03-16 Thread Georg Vollnhals
Detlef Faber schrieb:
 Hi everybody,

 I've just committed a Walk View to the jeep, so a virtual passenger
 can get out of the car and walk around in the scenery.

 The View follows the terrain height and the movements gets blocked by
 steep slopes and scenery models (sadly not by random scenery models as
 they are insensitve to collisions).
 It is planned to be integrated with the interiour movement like in the
 Albatross, so one can seamlessly walk inside and outside of the
 Aircraft.

 Suggestions and comments are welcome!

 Greetings

 Detlef


   
Hi Detlef,
downloaded and tried this nice feature.
Getting out/in the Jeep works as described - only the walking w (used
also W) does not work here.
I was on a runway, so no terrain blocking or scenery object could
disturb walking free forward.
Any idea?
Regards
Georg


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] autopilot u_min and u_max...

2008-03-16 Thread LeeE
On Sunday 16 March 2008 03:51, SydSandy wrote:
 Hi all ,
   I've been trying to change the xmlautopilot to use prop and
 value for the u_min and u_max properties , and currently have
 quite a mess on my hands right now :) The idea is to have a min
 and max property to control bank-limit / pitch with a panel knob
 ... setting the u_min and u_max from a property seems to be
 working , but I get some strange things happening . The pi-simple
 controller isnt clamped anymore (so i removed the clamp check
 )... and the output goes immediately to the u_min
 value...although u_min and u_max are checked every update... Has
 anyone else attempted this , with good results ? Or , hopefully ,
 already implemented this ? Anyway , I'll keep plugging away at
 it, the answer is probably staring me in the face and I can't see
 it. Is this something that should be implemented anyway ?
  Cheers

Hi Syd,

one way you could do this with the current autopilot controllers is 
to feed the output from your controller through a gain filter to 
get the range you want.

For example, if you've set u_min/u_max to +/- 40 in your controller 
but want to reduce it to +/- 20, you'd set the gain value on the 
gain filter to 0.5.

If you don't mind re-tuning your controller, it would probably make 
more sense to set u_min  u_max to +/- 1.0, then the gain factor 
would be the required bank or pitch angle limit i.e. for +/- 30 
limits you'd use a gain of 30.

Changing the output clamps does change the overall behaviour of the 
controller, however.  I found that I got more desirable behaviour 
from a pitch controller (output is a hstab deflection) when I set 
the u_min  u_max limits to +/- 0.25 and then passed it through a 
gain filter with a factor of 4 to restore the required +/- 1.0 
range, as opposed to setting the clamps directly to +/- 1.0.

Heh - I'm still not entirely sure why this is, actually having 
fiddled with the code myself, but it came about through an 
experiment where I was trying to increase the effective bandwidth 
through parallelism.  I started off with four identical controllers 
running in parallel, the outputs of which were summed but then I 
realised that I could get the same effect with a single controller 
using the gain filter technique.

LeeE

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Walking around

2008-03-16 Thread Detlef Faber
Am Sonntag, den 16.03.2008, 21:55 +0100 schrieb Georg Vollnhals:
 Detlef Faber schrieb:
  Hi everybody,
 
  I've just committed a Walk View to the jeep, so a virtual passenger
  can get out of the car and walk around in the scenery.
 
  The View follows the terrain height and the movements gets blocked by
  steep slopes and scenery models (sadly not by random scenery models as
  they are insensitve to collisions).
  It is planned to be integrated with the interiour movement like in the
  Albatross, so one can seamlessly walk inside and outside of the
  Aircraft.
 
  Suggestions and comments are welcome!
 
  Greetings
 
  Detlef
 
 

 Hi Detlef,
 downloaded and tried this nice feature.
 Getting out/in the Jeep works as described - only the walking w (used
 also W) does not work here.
 I was on a runway, so no terrain blocking or scenery object could
 disturb walking free forward.
 Any idea?

I forgot to mention you need to be in mouse view mode to walk around.
The walk direction is steered by the direction you look to.

If it still doesn't work for you, please tell me where you tested it.

 Regards
 Georg
 
 
 -
 This SF.net email is sponsored by: Microsoft
 Defy all challenges. Microsoft(R) Visual Studio 2008.
 http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
 ___
 Flightgear-devel mailing list
 Flightgear-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/flightgear-devel


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Walking around

2008-03-16 Thread Georg Vollnhals
Detlef Faber schrieb:


 I forgot to mention you need to be in mouse view mode to walk around.
 The walk direction is steered by the direction you look to.

 If it still doesn't work for you, please tell me where you tested it.

   
Hi Detlef,

thank you for the fast reply!

Works like a charm now. You know already (Albatross walk around) that I
like this feature very much.
From now I can explore nice sceneries walking around - gives sometimes a
surprising impressing perspective

http://home.arcor.de/vollnhals-bremen/Walkaround/Walkaround01.jpg

By the way, as my mouse modes have been reduced ever since to two
(click-mode and lookaround-mode) I changed the nasal script to

 if (getprop (devices/status/mice/mouse/mode) == 1)

This just as a reminder to some lurkers who also  changed their mouse
modes and  might be surprised that  the walk-around  does not  work.

Regards
Georg

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Walking around

2008-03-16 Thread Georg Vollnhals
Melchior FRANZ schrieb:
 * Georg Vollnhals -- Monday 17 March 2008:
   
 By the way, as my mouse modes have been reduced ever since to two
 (click-mode and lookaround-mode) I changed the nasal script to
 

 Better do not remove mouse mode 1, but just advise mode 0 to switch
 straight to mode 2. Then the indices remain the same and you don't
 have to modify scripts like walk.nas. Putting the following in your
 ~/.fgfsrc does the trick, while mice.xml remains unchanged:

   --prop:input/mice/mouse/mode/button[2]/binding/value=2

 m.

   
Thank you Melchior, good point as other (future) scripts might be
affected, too.
I'll change it tomorrow as you suggested :-)
Georg

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Walking around

2008-03-16 Thread Georg Vollnhals
Heiko Schulz schrieb:
 But it seems to me, that I can't get under objects-
 even than they are not massiv. I can drive under
 Static-aircrafts, but not walk. 

 But that's peanuts
 Detlef- a lot of thanks

 HHS

   
But what is even better - you can walk ON an object if it has a RAMP to
the earth.

I walked the whole bridge, first driving on the ramp with the jeep, but
then I walked from the ramp onto the earth and back on the ramp and over
the bridge:
http://home.arcor.de/vollnhals-bremen/Walkaround/Walkaround02.jpg

I should be sleeping already but I had so much fun testing the
walkaraound ...

Regards
Georg



-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Walking around

2008-03-16 Thread Heiko Schulz

--- Georg Vollnhals [EMAIL PROTECTED] schrieb:

 Heiko Schulz schrieb:
  But it seems to me, that I can't get under
 objects-
  even than they are not massiv. I can drive under
  Static-aircrafts, but not walk. 
 
  But that's peanuts
  Detlef- a lot of thanks
 
  HHS
 

 But what is even better - you can walk ON an object
 if it has a RAMP to
 the earth.
 
 I walked the whole bridge, first driving on the ramp
 with the jeep, but
 then I walked from the ramp onto the earth and back
 on the ramp and over
 the bridge:

http://home.arcor.de/vollnhals-bremen/Walkaround/Walkaround02.jpg
 
 I should be sleeping already but I had so much fun
 testing the
 walkaraound ...
 
 Regards
 Georg
 
 
Me too :-)

Yes- Nice feature, very nice- I'm waiting for the
first FlightGear Ego-Shooter! 

When can we guess with your scenery on svn?

Cheers
HHS


still in work: http://www.hoerbird.net/galerie.html
But already done: http://www.hoerbird.net/reisen.html


  Lesen Sie Ihre E-Mails jetzt einfach von unterwegs.
www.yahoo.de/go

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Walking around

2008-03-16 Thread Georg Vollnhals
Heiko Schulz schrieb:
 Me too :-)

 Yes- Nice feature, very nice- I'm waiting for the
 first FlightGear Ego-Shooter! 
   
Ok, there might be a lot of people thinking that FlightGear is a
FLIGHTSimulator and not a WALKING or DRIVING Sim.
But this nice add-on gives a lot of FUN - and if you could leave your
aircraft in the future and do a preflight check, what's wrong with that?
:-))

And to be honest - I personally like using a scenery in some other way.
This walking feature reminds me at Sim Copter I used a long, long time
ago. I always liked to have this other view groundnear between the
objects, especially if there was/are a lot of them.
 When can we guess with your scenery on svn?

   
Just working a lot to re-place the objects for EDDW and EDDV as so much
has changed with the new v 1.0 scenery. Hopefully ready after Easter
time as I get some more sparetime then to finish the task.
 Cheers
 HHS


   
Georg

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


[Flightgear-devel] Building fails cannot find plib library from CVS

2008-03-16 Thread Cleber Santz
Hi, 

 i have some problems to compile Flightgear from CVS. I have plib (1.8.5 from 
CVS) successful installed and headers under /usr/include/plib but the 
compilation fails and say that getting undefined reference for puaList and 
puaComboBox.

Compilation log in attached file.

Any help ??

Regards,
Cleber Santz.




  Abra sua conta no Yahoo! Mail, o único sem limite de espaço para 
armazenamento!
http://br.mail.yahoo.com/../../src/GUI/libGUI.a(dialog.o): In function `fgList':
/home/cleber/FGFS/src/Flightgear/source/src/GUI/dialog.hxx:210: undefined 
reference to `puaList::puaList(int, int, int, int, char**, int)'
../../src/GUI/libGUI.a(dialog.o): In function `fgList::update()':
/home/cleber/FGFS/src/Flightgear/source/src/GUI/dialog.cxx:1006: undefined 
reference to `puaList::setTopItem(int)'
../../src/GUI/libGUI.a(dialog.o): In function `puaList::RTTI_vinfo() const':
/usr/local/include/plib/puAux.h:889: undefined reference to `puaList::RTTI_obj'
../../src/GUI/libGUI.a(dialog.o): In function `~fgList':
/home/cleber/FGFS/src/Flightgear/source/src/GUI/dialog.hxx:207: undefined 
reference to `puaList::~puaList()'
/home/cleber/FGFS/src/Flightgear/source/src/GUI/dialog.hxx:207: undefined 
reference to `puaList::~puaList()'
../../src/GUI/libGUI.a(dialog.o):(.rodata._ZTV6fgList[vtable for fgList]+0x40): 
undefined reference to `puaList::RTTI_cast(ulRTTItypeid)'
../../src/GUI/libGUI.a(dialog.o):(.rodata._ZTV6fgList[vtable for fgList]+0x80): 
undefined reference to `puaList::getIntegerValue()'
../../src/GUI/libGUI.a(dialog.o):(.rodata._ZTV6fgList[vtable for fgList]+0x98): 
undefined reference to `puaList::getStringValue()'
../../src/GUI/libGUI.a(dialog.o):(.rodata._ZTV6fgList[vtable for fgList]+0xd0): 
undefined reference to `puaList::setSize(int, int)'
../../src/GUI/libGUI.a(dialog.o):(.rodata._ZTV6fgList[vtable for 
fgList]+0x100): undefined reference to `puaList::setColourScheme(float, float, 
float, float)'
../../src/GUI/libGUI.a(dialog.o):(.rodata._ZTV6fgList[vtable for 
fgList]+0x108): undefined reference to `puaList::setColour(int, float, float, 
float, float)'
../../src/GUI/libGUI.a(dialog.o):(.rodata._ZTV6fgList[vtable for 
fgList]+0x130): undefined reference to `puaList::init(int, int, short)'
../../src/GUI/libGUI.a(dialog.o):(.rodata._ZTV6fgList[vtable for 
fgList]+0x138): undefined reference to `puaList::newList(char**)'
../../src/GUI/libGUI.a(dialog.o):(.rodata._ZTV6fgList[vtable for 
fgList]+0x140): undefined reference to `puaList::getValue(char**)'
../../src/GUI/libGUI.a(dialog.o):(.rodata._ZTV6fgList[vtable for 
fgList]+0x148): undefined reference to `puaList::getValue(int*)'
../../src/GUI/libGUI.a(dialog.o):(.rodata._ZTI6fgList[typeinfo for 
fgList]+0x28): undefined reference to `typeinfo for puaList'
../../src/GUI/libGUI.a(dialog.o):(.rodata._ZTV10fgComboBox[vtable for 
fgComboBox]+0x100): undefined reference to `puaComboBox::setColourScheme(float, 
float, float, float)'
../../src/GUI/libGUI.a(dialog.o):(.rodata._ZTV10fgComboBox[vtable for 
fgComboBox]+0x108): undefined reference to `puaComboBox::setColour(int, float, 
float, float, float)'
../../src/GUI/libGUI.a(dialog.o):(.rodata._ZTV11fgSelectBox[vtable for 
fgSelectBox]+0x100): undefined reference to 
`puaSelectBox::setColourScheme(float, float, float, float)'
../../src/GUI/libGUI.a(dialog.o):(.rodata._ZTV11fgSelectBox[vtable for 
fgSelectBox]+0x108): undefined reference to `puaSelectBox::setColour(int, 
float, float, float, float)'
../../src/GUI/libGUI.a(AirportList.o): In function `~AirportList':
/home/cleber/FGFS/src/Flightgear/source/src/GUI/AirportList.cxx:20: undefined 
reference to `puaList::~puaList()'
/home/cleber/FGFS/src/Flightgear/source/src/GUI/AirportList.cxx:20: undefined 
reference to `puaList::~puaList()'
/home/cleber/FGFS/src/Flightgear/source/src/GUI/AirportList.cxx:20: undefined 
reference to `puaList::~puaList()'
../../src/GUI/libGUI.a(AirportList.o): In function `AirportList':
/home/cleber/FGFS/src/Flightgear/source/src/GUI/AirportList.cxx:12: undefined 
reference to `puaList::puaList(int, int, int, int, int)'
/home/cleber/FGFS/src/Flightgear/source/src/GUI/AirportList.cxx:15: undefined 
reference to `puaList::~puaList()'
/home/cleber/FGFS/src/Flightgear/source/src/GUI/AirportList.cxx:12: undefined 
reference to `puaList::puaList(int, int, int, int, int)'
/home/cleber/FGFS/src/Flightgear/source/src/GUI/AirportList.cxx:15: undefined 
reference to `puaList::~puaList()'
../../src/GUI/libGUI.a(AirportList.o):(.rodata._ZTV11AirportList[vtable for 
AirportList]+0x18): undefined reference to `puaList::RTTI_cast(ulRTTItypeid)'
../../src/GUI/libGUI.a(AirportList.o):(.rodata._ZTV11AirportList[vtable for 
AirportList]+0x58): undefined reference to `puaList::getIntegerValue()'
../../src/GUI/libGUI.a(AirportList.o):(.rodata._ZTV11AirportList[vtable for 
AirportList]+0x70): undefined reference to `puaList::getStringValue()'
../../src/GUI/libGUI.a(AirportList.o):(.rodata._ZTV11AirportList[vtable for 
AirportList]+0xa8): 

Re: [Flightgear-devel] autopilot u_min and u_max...

2008-03-16 Thread SydSandy
On Sun, 16 Mar 2008 21:59:18 +
LeeE [EMAIL PROTECTED] wrote:

 On Sunday 16 March 2008 21:52, LeeE wrote:
  On Sunday 16 March 2008 03:51, SydSandy wrote:
   Hi all ,
 I've been trying to change the xmlautopilot to use prop and
   value for the u_min and u_max properties , and currently have
   quite a mess on my hands right now :) The idea is to have a min
   and max property to control bank-limit / pitch with a panel
   knob ... setting the u_min and u_max from a property seems to
   be working , but I get some strange things happening . The
   pi-simple controller isnt clamped anymore (so i removed the
   clamp check )... and the output goes immediately to the u_min
   value...although u_min and u_max are checked every update...
   Has anyone else attempted this , with good results ? Or ,
   hopefully , already implemented this ? Anyway , I'll keep
   plugging away at it, the answer is probably staring me in the
   face and I can't see it. Is this something that should be
   implemented anyway ? Cheers
 
  Hi Syd,
 
  one way you could do this with the current autopilot controllers
  is to feed the output from your controller through a gain filter
  to get the range you want.
 
  For example, if you've set u_min/u_max to +/- 40 in your
 
 Oops - that should have said u_max/u_min to +/- 40
 
  controller but want to reduce it to +/- 20, you'd set the gain
  value on the gain filter to 0.5.
 
  If you don't mind re-tuning your controller, it would probably
  make more sense to set u_min  u_max to +/- 1.0, then the gain
 
 and again above - u_max  u_min to +/- 1.0
 
  factor would be the required bank or pitch angle limit i.e. for
  +/- 30 limits you'd use a gain of 30.
 
  Changing the output clamps does change the overall behaviour of
  the controller, however.  I found that I got more desirable
  behaviour from a pitch controller (output is a hstab deflection)
  when I set the u_min  u_max limits to +/- 0.25 and then passed
 
 Sigh...  u_max  u_min to +/- 0.25
 
  it through a gain filter with a factor of 4 to restore the
  required +/- 1.0 range, as opposed to setting the clamps directly
  to +/- 1.0.
 
  Heh - I'm still not entirely sure why this is, actually having
  fiddled with the code myself, but it came about through an
  experiment where I was trying to increase the effective bandwidth
  through parallelism.  I started off with four identical
  controllers running in parallel, the outputs of which were summed
  but then I realised that I could get the same effect with a
  single controller using the gain filter technique.
 
  LeeE
 
 Doh!
 
 LeeE
 

Hi LeeE,
Thanks for the tips.
Still I think it would be a good idea to make these two settings modifiable 
with a property , don't know if any one else agrees . It turns out that the 
problems I was having was my autopilot config file , it's been working fine so 
far   it simply checks for value or prop like the recent Kp update, and 
uses the u_min and u_max value if no prop or value tag is present ...
now, the fun part, to try to create an lnav /vnav flight profile  :)

Cheers

-- 
SydSandy [EMAIL PROTECTED]

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel