Re: [Flightgear-devel] Recent checkins and plans
Hi Tim, On Sunday 22 February 2009 12:37:55 Tim Moore wrote: > Good to hear from you again. You should check out my recent changes to the > groundcache code that changes it to use the OSG PolytopeIntersector. My > thinking was that someone (perhaps you or I) could teach the polytope > intersector to use the kd tree support that is already in OSG to create a > truly fast ground cache. Well, I have something better than that. My original groundcache idea was to use only few huge geometry triangles from the area around the aircraft to do collision test with. This list of triangles is flat. Ok, so far. What works well with this approach: * Rolling on ground tiles with few huge triangles. * Rolling/interacting with the carriers deck with few huge triangles and few cats/wires. What is bad with the current implementation: * When we have many triangles in the cache. This provides bad run time behavior because of lookups in the flat list and the huge amount of work to build that list. To work around that problem in the current implementation almost all fine details in the carrier and the whole set of ai traffic is invisible to the collision code. * Movements of objects is very messy to compute. Nested movements are not implemented and much more messy to compute if we would implement those in the current code base. So what have I done to solve that issues: I have a collision tree implementation that provides: * A very fast collision implementation. * Hybrid approach for kd-trees (sort of) for the leaf geometry and higher level grouping nodes for a scenegraph like high level structure. * The good part of the idea groundcache: Use only a local part of the tree to do frequent lookups, build that local tree once per time frame. But the subtree build time is almost not noticable in contrast to the old groundcache (with or without kd-tree of osg). * Provides motion nodes in the collision tree to provide the groundwork for realistic collisions with the carriers tower for example. Have usable information for nested movement like an elevator on a carrier. Have a simple way to provide such nested movement information. Solve some subtle problems we have with the current 'pivot point' approach for the collisions. * Have now a good way for the FDM part to do faster and more realistic collisions with geometry not to roll on (TBD physics wise). * Have the ability to provide 'collision geometries' for models in the model configuration. * ... (stop here) :) So the fast paths are already very well done. There are still rough edges that I plan to work out before switching to that new implementation. That is currently the angular movement of the carrier is missing - but that is a matter of some cross products with the correct signs in some methods - well in theory :). So all in all, I have up to 10% frame rate improvements on my notebook. Also this adds a code base that opens some doors. Greetings Mathias -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] YASim static friction
On Tue, Feb 24, 2009 at 2:41 AM, Diogo Kastrup wrote: > > Ok, just replacing Gear.cpp:648 as below will do it. Now it is > tested! ;) Yes, this works, thanks Diogo. Next problem: Carrier speed 20kts, start with the bo105, check ATC/AI menu->options->turn into wind and watch the helicopter slide around on the deck. It is already immensely better than without your patch, of course. I am just reporting it in case you have some more tweaks :) -- Csaba/Jester -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] YASim static friction
Em Ter, 2009-02-24 às 01:16 +0100, Csaba Halász escreveu:
> The groundcache fix seems to work fine, thank you.
> The fix for the stationary carrier doesn't because:
>
> (gdb) p _slipping
> $1 = true
>
> To get a stationary carrier edit $FG_ROOT/AI/nimitz_demo.xml and set
> to 0.
Ok, just replacing Gear.cpp:648 as below will do it. Now it is
tested! ;) Thank you Csaba.
Replace this:
Math::unit3(cv, dir);
by this:
Math::unit3(dgear, dir);
Regards,
Diogo
Index: src/FDM/flight.cxx
===
RCS file: /var/cvs/FlightGear-0.9/source/src/FDM/flight.cxx,v
retrieving revision 1.35
diff -u -r1.35 flight.cxx
--- src/FDM/flight.cxx 9 Nov 2007 05:39:13 - 1.35
+++ src/FDM/flight.cxx 24 Feb 2009 01:39:04 -
@@ -705,6 +705,15 @@
return dist*SG_METER_TO_FEET;
}
+void
+FGInterface::get_platform(double t, double pos[3], float *orient)
+{
+ SGVec3d _pos;
+ ground_cache.get_platform(t, _pos, orient);
+ if (pos)
+assign(pos, _pos);
+}
+
// Legacy interface just kept because of JSBSim
bool
FGInterface::get_agl_m(double t, const double pt[3],
Index: src/FDM/flight.hxx
===
RCS file: /var/cvs/FlightGear-0.9/source/src/FDM/flight.hxx,v
retrieving revision 1.18
diff -u -r1.18 flight.hxx
--- src/FDM/flight.hxx 27 Jul 2008 16:25:14 - 1.18
+++ src/FDM/flight.hxx 24 Feb 2009 01:39:04 -
@@ -629,6 +629,9 @@
double end[2][3], double vel[2][3]);
double get_cat_ft(double t, const double pt[3],
double end[2][3], double vel[2][3]);
+
+// Return the position and orientation of the platform
+void get_platform(double t, double pos[3], float *orient);
// Return the altitude above ground below the wgs84 point pt
@@ -642,8 +645,8 @@
int *type, double *loadCapacity,
double *frictionFactor, double *agl);
bool get_agl_m(double t, const double pt[3],
- double contact[3], double normal[3], double vel[3],
- int *type, const SGMaterial **material,double *agl);
+ double contact[3], double normal[3], double vel[3],
+ int *type, const SGMaterial **material,double *agl);
bool get_agl_ft(double t, const double pt[3],
double contact[3], double normal[3], double vel[3],
int *type, double *loadCapacity,
Index: src/FDM/groundcache.cxx
===
RCS file: /var/cvs/FlightGear-0.9/source/src/FDM/groundcache.cxx,v
retrieving revision 1.33
diff -u -r1.33 groundcache.cxx
--- src/FDM/groundcache.cxx 15 Feb 2009 00:56:22 - 1.33
+++ src/FDM/groundcache.cxx 24 Feb 2009 01:39:05 -
@@ -158,6 +158,7 @@
_material(0),
cache_ref_time(0.0),
wire_id(0),
+ platform_id(0),
reference_wgs84_point(SGVec3d(0, 0, 0)),
reference_vehicle_radius(0.0),
down(0.0, 0.0, 0.0),
@@ -198,6 +199,8 @@
gp.vel = SGVec3d(0.0, 0.0, 0.0);
gp.rot = SGVec3d(0.0, 0.0, 0.0);
gp.pivot = SGVec3d(0.0, 0.0, 0.0);
+gp.platform_id = 0;
+gp.platform = NULL;
gp.material = 0;
backfaceCulling = false;
// XXX state set might be higher up in scene graph
@@ -235,6 +238,8 @@
break;
default:
gp.type = FGInterface::Solid;
+gp.platform_id = ud->carrier->getID();
+gp.platform = ud->carrier;
break;
}
// Copy the velocity from the carrier class.
@@ -304,7 +309,7 @@
// Only check if the triangle is in the cache sphere if the plane
// containing the triangle is near enough
double d = dot(n, v[0] - localCacheReference);
-if (d*d < reference_vehicle_radius*dot(n, n)) {
+if (d*d < reference_vehicle_radius*reference_vehicle_radius*dot(n, n)) {
// Check if the sphere around the vehicle intersects the sphere
// around that triangle. If so, put that triangle into the cache.
double r2 = boundRadius + reference_vehicle_radius;
@@ -323,6 +328,10 @@
t.sphere.setRadius(boundRadius);
t.gp = gp;
triangles.push_back(t);
+if (gp.platform_id
+&& (platforms.empty()
+|| dynamic_cast(platforms.back())->getID() != gp.platform_id))
+platforms.push_back(gp.platform);
}
}
// In case the cache is empty, we still provide agl computations.
@@ -414,6 +423,7 @@
triangles.resize(0);
catapults.resize(0);
wires.resize(0);
+ platforms.resize(0);
// Store the parameters we used to build up that cache.
reference_wgs84_point = pt;
@@ -460,6 +470,7 @@
<< ", # triangles = " << triangles.size()
<< ", # wires = " << wires.size()
<< ", # catapults = " << catapults.size()
+ <<
Re: [Flightgear-devel] YASim static friction
On Tue, Feb 24, 2009 at 12:25 AM, Diogo Kastrup wrote: > > I am sending the diff again with the fix for this and the (untested) fix > for the zero-speed problem, just in case someone want to play with it. The groundcache fix seems to work fine, thank you. The fix for the stationary carrier doesn't because: (gdb) p _slipping $1 = true To get a stationary carrier edit $FG_ROOT/AI/nimitz_demo.xml and set to 0. -- Cheers, Csaba/Jester -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] YASim static friction
Em Seg, 2009-02-23 às 17:58 -0300, Diogo Kastrup escreveu:
> The carrier sailing out from underneath is strange, it looks like the
> groundcache can't finding a intersection with the ground for these
> aircrafts and it is using a fallback value. Can someone check if this
> happens without my patch also? I will try to find out why this is
> happening.
Yep, the groundcache can't find a intersection. I think this problem
occurs without my patch also. To fix it just change groundcache.cxx
around line 312 from this:
if (d*d < reference_vehicle_radius*dot(n, n)) {
to this:
if (d*d < reference_vehicle_radius*reference_vehicle_radius*dot(n, n)) {
I am sending the diff again with the fix for this and the (untested) fix
for the zero-speed problem, just in case someone want to play with it.
I am still trying to figure out why the s76c is shaking. This happens
with other helicopters also, like the R22.
Regards,
Diogo
Index: src/FDM/flight.cxx
===
RCS file: /var/cvs/FlightGear-0.9/source/src/FDM/flight.cxx,v
retrieving revision 1.35
diff -u -r1.35 flight.cxx
--- src/FDM/flight.cxx 9 Nov 2007 05:39:13 - 1.35
+++ src/FDM/flight.cxx 23 Feb 2009 23:14:47 -
@@ -705,6 +705,15 @@
return dist*SG_METER_TO_FEET;
}
+void
+FGInterface::get_platform(double t, double pos[3], float *orient)
+{
+ SGVec3d _pos;
+ ground_cache.get_platform(t, _pos, orient);
+ if (pos)
+assign(pos, _pos);
+}
+
// Legacy interface just kept because of JSBSim
bool
FGInterface::get_agl_m(double t, const double pt[3],
Index: src/FDM/flight.hxx
===
RCS file: /var/cvs/FlightGear-0.9/source/src/FDM/flight.hxx,v
retrieving revision 1.18
diff -u -r1.18 flight.hxx
--- src/FDM/flight.hxx 27 Jul 2008 16:25:14 - 1.18
+++ src/FDM/flight.hxx 23 Feb 2009 23:14:48 -
@@ -629,6 +629,9 @@
double end[2][3], double vel[2][3]);
double get_cat_ft(double t, const double pt[3],
double end[2][3], double vel[2][3]);
+
+// Return the position and orientation of the platform
+void get_platform(double t, double pos[3], float *orient);
// Return the altitude above ground below the wgs84 point pt
@@ -642,8 +645,8 @@
int *type, double *loadCapacity,
double *frictionFactor, double *agl);
bool get_agl_m(double t, const double pt[3],
- double contact[3], double normal[3], double vel[3],
- int *type, const SGMaterial **material,double *agl);
+ double contact[3], double normal[3], double vel[3],
+ int *type, const SGMaterial **material,double *agl);
bool get_agl_ft(double t, const double pt[3],
double contact[3], double normal[3], double vel[3],
int *type, double *loadCapacity,
Index: src/FDM/groundcache.cxx
===
RCS file: /var/cvs/FlightGear-0.9/source/src/FDM/groundcache.cxx,v
retrieving revision 1.33
diff -u -r1.33 groundcache.cxx
--- src/FDM/groundcache.cxx 15 Feb 2009 00:56:22 - 1.33
+++ src/FDM/groundcache.cxx 23 Feb 2009 23:14:49 -
@@ -158,6 +158,7 @@
_material(0),
cache_ref_time(0.0),
wire_id(0),
+ platform_id(0),
reference_wgs84_point(SGVec3d(0, 0, 0)),
reference_vehicle_radius(0.0),
down(0.0, 0.0, 0.0),
@@ -198,6 +199,8 @@
gp.vel = SGVec3d(0.0, 0.0, 0.0);
gp.rot = SGVec3d(0.0, 0.0, 0.0);
gp.pivot = SGVec3d(0.0, 0.0, 0.0);
+gp.platform_id = 0;
+gp.platform = NULL;
gp.material = 0;
backfaceCulling = false;
// XXX state set might be higher up in scene graph
@@ -235,6 +238,8 @@
break;
default:
gp.type = FGInterface::Solid;
+gp.platform_id = ud->carrier->getID();
+gp.platform = ud->carrier;
break;
}
// Copy the velocity from the carrier class.
@@ -304,7 +309,7 @@
// Only check if the triangle is in the cache sphere if the plane
// containing the triangle is near enough
double d = dot(n, v[0] - localCacheReference);
-if (d*d < reference_vehicle_radius*dot(n, n)) {
+if (d*d < reference_vehicle_radius*reference_vehicle_radius*dot(n, n)) {
// Check if the sphere around the vehicle intersects the sphere
// around that triangle. If so, put that triangle into the cache.
double r2 = boundRadius + reference_vehicle_radius;
@@ -323,6 +328,10 @@
t.sphere.setRadius(boundRadius);
t.gp = gp;
triangles.push_back(t);
+if (gp.platform_id
+&& (platforms.empty()
+|| dynamic_cast(platforms.back())->getID() != gp.platform_id))
+platforms.push_back(gp.platform);
}
Re: [Flightgear-devel] an idea about dialog-apply command (was: Patch for random system failures)
Hi Melchior, you can find the patch with, I hope, the correct improvement you asked. I wanted to add that I really agree your point of view: "To make listeners work as expected the solution is to make *listeners* work as expected, not to change dialog-apply in a way that makes them not work as expected.". Be sure that I'll be aware and will recall you of this change if one day we run into problems, and no-one remembers about it before ;) thanks for the interest you had about my suggestion. Now I'm going to continue my tries about failures scenarii. I think I've got some nice ideas about it to make them generic but adaptable (using xml) and improving flight experience. I'll expose you them later as it needs more thinking, and a lot more work. :D best regards seb Melchior FRANZ wrote : * Sébastien MARQUE -- 2/20/2009 1:23 AM: This is not new, it was the case with the precedent gui dialog, and I used a Nasal workaround but not really useful as it disallows to come back to a previous state. I've written a lot of dialogs, the most complicated ones among them, and I don't remember that I ever had to work around this sort of issue. That's one of the reasons why I hesitate when someone asks for a change to make his first(?) dialog work. :-P But anyway. I withdraw my objection and don't mind if someone commits this patch with one improvement: the node value shall not be read twice! That's not so much because of the saved nanoseconds, but mostly because of --trace-read (and style). dialog-apply does then no longer mean copy widget data to the tree, but sync tree with the internal widget state. (dialog-update does still mean *copy*, though ... which is another reason why I'm not thrilled by the change. One more inconsistency to remember ...) But be warned: if we run into problems with this modification, I'll be less hesitant before throwing it out again. ;-) m. -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel Index: src/GUI/dialog.cxx === RCS file: /var/cvs/FlightGear-0.9/source/src/GUI/dialog.cxx,v retrieving revision 1.115 diff -u -r1.115 dialog.cxx --- src/GUI/dialog.cxx 10 Feb 2009 22:14:13 - 1.115 +++ src/GUI/dialog.cxx 23 Feb 2009 21:26:32 - @@ -437,11 +437,17 @@ case SGPropertyNode::BOOL: case SGPropertyNode::INT: case SGPropertyNode::LONG: -node->setIntValue(object->getIntegerValue()); +int objectintvalue; + objectintvalue = object->getIntegerValue(); + if (node->getIntValue() != objectintvalue) +node->setIntValue(objectintvalue); break; case SGPropertyNode::FLOAT: case SGPropertyNode::DOUBLE: -node->setFloatValue(object->getFloatValue()); +float objectfloatvalue; + objectfloatvalue = object->getFloatValue(); + if (node->getFloatValue() != objectfloatvalue) +node->setFloatValue(objectfloatvalue); break; default: const char *s = object->getStringValue(); -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] YASim static friction
Csaba, thank you very much for testing. See my comments below. Em Seg, 2009-02-23 às 04:59 +0100, Csaba Halász escreveu: > I tested with the bo105 on solid ground first. It doesn't move an inch > with engines shut down. During startup, it doesn't turn either. The > s76c (which has wheels instead of skids) vibrates during startup (we > can call that realistic ;)) That is weird, I will try to find out why. After a quick look, I am concerned about the values of the spring and compression in the definition file of the s76c. The static friction value is very high also. I will do some tests... (...) > Apparently it happens because I have the carrier stationary. Setting > it into motion, the bo105 starts up fine. With the s76c the carrier > sails out from underneath even with the parking brake on (which is the > default). With the v22, it only happens with the brakes off, which > seems right. Setting the wind so that it cancels out the relative wind > due to motion makes the v22 stay in place even with brakes off. > Haven't tried maneuvering the Nimitz yet. > > The s76c problem might be an aircraft specific issue and the > zero-speed carrier error sounds easy to fix. All in all it looks quite > good so far. How can I set the carrier speed to zero? :) I would like to reproduce it here. Anyway, I think that moving the following lines to inside the "if (_slipping)" loop around line 650 in Gear.cpp solves it: // Get the direction of movement float dir[3]; Math::unit3(cv, dir); The carrier sailing out from underneath is strange, it looks like the groundcache can't finding a intersection with the ground for these aircrafts and it is using a fallback value. Can someone check if this happens without my patch also? I will try to find out why this is happening. Regards, Diogo -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Property System Overview?
On Sun, Feb 22, 2009 at 3:38 AM, Erik Hofman wrote: > > The main reason for implementing the property system is that it can > represent the contents of any XML file in memory quite easily. > I appreciate everyone's response to my questions about describing FlightGear's property system. I've pulled bits and pieces together from just about everyone's comments. Thanks! Curt. -- Curtis Olson: http://baron.flightgear.org/~curt/ -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] northern hemisphere vs southern hemisphere
Hi, Heiko Schulz schrieb am 23.02.2009 14:22: > > >> The bo105 doesn't use Nasal for blade bending. >> > > > noticed, so it is indeed a bug in hardcode. Maik has already a patch and is > in test on helijah. I wait for the results, because this bug could be also > the cause for the sliding. > Meanwhile I have a running flightgear here (with osg 2.8 it works fine). I can confirm helijahs observation, that the bug reportet by helijah is fixed with the patch, but the effect on sliding is smaller than I hoped. Maybe the sliding of helicopters is comparable to other aircrafts now. Fortunately Diogo has a general patch for the sliding issue. Please commit my patch. Thanks, Maik -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Flightgear-devel Digest, Vol 34, Issue 21
In this case you might want to check out the UFO. It has some very fancy code for placing objects in the scenery by clicking on the ground. The basic nasal function doing the trick is geo.put_model() (look in your data/Nasal directory for the file geo.nas). This just places a model into the scenery without adding any intelligence. If you want that model to do some magic, like moving around, that can't be done by just clicking somewhere or by a keystroke. Hope this helps, Torsten BTW: we discourage top posting on this list. > hi > > thanks Torsten it looks so intersting but what I want to do is to create an > object dynamicly when FG is running via the keyboard for example. I did > this before with ESP but in FG I don't know if there's a function in the > source which allows to do this. > > > thanks > > ITAF > > > Subject: Re: [Flightgear-devel] handling AI objects > > To: FlightGear developers discussions > > > > Message-ID: <200902231243.27093.tors...@t3r.de> > > Content-Type: text/plain; charset="utf-8" > > > > > hi > > > > > > I would like to know if flightgear source code has any function which > > > > can > > > > > create/remove/control AI objects ( aircraft, cars etc...) > > > > > > thx > > > > Certainly it has. > > You might want to read this: > > http://wiki.flightgear.org/index.php/AI_Systems > > > > Torsten -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Flightgear-devel Digest, Vol 34, Issue 21
hi thanks Torsten it looks so intersting but what I want to do is to create an object dynamicly when FG is running via the keyboard for example. I did this before with ESP but in FG I don't know if there's a function in the source which allows to do this. thanks ITAF > > Subject: Re: [Flightgear-devel] handling AI objects > To: FlightGear developers discussions > > Message-ID: <200902231243.27093.tors...@t3r.de> > Content-Type: text/plain; charset="utf-8" > > > hi > > > > I would like to know if flightgear source code has any function which > can > > create/remove/control AI objects ( aircraft, cars etc...) > > > > thx > Certainly it has. > You might want to read this: > http://wiki.flightgear.org/index.php/AI_Systems > > Torsten > -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] northern hemisphere vs southern hemisphere
>The bo105 doesn't use Nasal for blade bending. noticed, so it is indeed a bug in hardcode. Maik has already a patch and is in test on helijah. I wait for the results, because this bug could be also the cause for the sliding. -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] handling AI objects
> hi > > I would like to know if flightgear source code has any function which can > create/remove/control AI objects ( aircraft, cars etc...) > > thx Certainly it has. You might want to read this: http://wiki.flightgear.org/index.php/AI_Systems Torsten -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Patch for positioned.cxx
> not subscribed to the flightgear-cvslogs ML ? ;-) No, was not, but am now! Thanks Fred. Geoff. -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] handling AI objects
hi I would like to know if flightgear source code has any function which can create/remove/control AI objects ( aircraft, cars etc...) thx -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: source/src/Navaids positioned.cxx, 1.12, 1.13
On 22 Feb 2009, at 08:23, Frederic Bouvier wrote: > Modified Files: > positioned.cxx > Log Message: > Compile with VS2005 in debug mode Thanks to everyone who's had problems with this for their patience, and to the people who worked out and committed a fix. It's my code, but I have no access to a Win32 build environment, so I've been remaining silent as long as the discussion stayed in MSVC land. As I noted a few weeks ago, I still suspect my use of lower_bound and upper_bound is not quite standard-compliant (though it works in real- word implementations). Thanks again, James -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] an idea about dialog-apply command
* Melchior FRANZ -- 2/23/2009 10:18 AM: > the node value shall not be read twice Disregard! You aren't doing that, and why should you?! But also don't read the widget value twice, please. :-) m. -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] YASim static friction
* Csaba Halász -- 2/23/2009 4:59 AM: > I tested with the bo105 on solid ground first. It doesn't move an inch > with engines shut down. During startup, it doesn't turn either. For testing the bo105 please comment out the line starting with antislide.setDoubleValue(... in $FG_ROOT/Aircraft/bo105/Models/bo105.nas. While this didn't remove all sliding, it reduced it a lot. m. -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] northern hemisphere vs southern hemisphere
* Heiko Schulz -- 2/22/2009 1:41 PM: > Bo105 and S64E Skycrane using Nasal for the blade bending, > the ec135 not! > So it could be that it has to do with the nasal code instead > then rather a bug in the code! The bo105 doesn't use Nasal for blade bending. m. -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] an idea about dialog-apply command (was: Patch for random system failures)
* Sébastien MARQUE -- 2/20/2009 1:23 AM: > This is not new, it was the case with the precedent gui dialog, and I > used a Nasal workaround but not really useful as it disallows to come > back to a previous state. I've written a lot of dialogs, the most complicated ones among them, and I don't remember that I ever had to work around this sort of issue. That's one of the reasons why I hesitate when someone asks for a change to make his first(?) dialog work. :-P But anyway. I withdraw my objection and don't mind if someone commits this patch with one improvement: the node value shall not be read twice! That's not so much because of the saved nanoseconds, but mostly because of --trace-read (and style). dialog-apply does then no longer mean copy widget data to the tree, but sync tree with the internal widget state. (dialog-update does still mean *copy*, though ... which is another reason why I'm not thrilled by the change. One more inconsistency to remember ...) But be warned: if we run into problems with this modification, I'll be less hesitant before throwing it out again. ;-) m. -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
