Re: [Flightgear-devel] Massive shared objects import webtool now active.

2012-07-10 Thread Harald Johnsen

Olivier a écrit :

Hi everyone,

I'm happy to announce the production status of the massive shared 
objects positions import script.


Please note:

   1. You must only import new objects, not the whole STG file you're
  working on!
   2. Don't add models not present in the FG scenemodels database, nor
  (yet) OBJECT_SIGN nor OBJECT_STATIC.
   3. Don't add forest or other items linked to the landcover. Those
  items have to be generated based on the landcover, not on
  objects! The only trees accepted will be those located within
  airport boundaries, for example.
   4. The data you're asking for import should be based for elevation
  on the terrain shipped with FlightGear/Terrasync, and not on a
  terrain you could have downloaded or compiled yourself. Else,
  your objects could appear floating or sunk in the terrain in the
  current FG scenery...
   5. Finally, the import is limited to 100 lines per submission
  (let's think about the poor scenery maintainer(s)...)
   6. The import is quite sensitive about the data in entry, which
  goes through quite a lot of checkings, including humans, before
  insertion.

Finally, and because I receive many questions about it, the import 
script for 3D models is on its way, finished to approximately 90%. Be 
patient.


Hope you enjoy it,

Oliver



Hi Olivier,

point 4) is problematic ; I regenerated east of France to have 850 
airports and I'm pretty sure that there is a difference of elevation at 
those airports (and perhaps elsewhere, I did not check). How could I 
send object elevations for the old scenery when I'm not even using it 
(for obvious reasons), I use the France regenerated scenery or my own one.


HJ.

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Massive shared objects import webtool now active.

2012-07-10 Thread Martin Spott
Olivier wrote:

> I'm happy to announce the production status of the massive 
> shared objects positions import script.

Very nice !

Martin.
-- 
 Unix _IS_ user friendly - it's just selective about who its friends are !
--

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


[Flightgear-devel] Massive shared objects import webtool now active.

2012-07-10 Thread Olivier
Hi everyone,

I'm happy to announce the production status of the massive 
shared objects positions import script.

Now, for the first time 
in flight simulators history (at least AFAIK), you just have to copy/paste new 
objects 
lines (STG format) directly in a webform to update scenery objects all 
over the world for all FG users using Terrasync. Add your email address 
to be informed of the progress of the update. Import should happen soon 
(let's say between 24 and 72 hours if your submission is fine, but it depends 
on the poor scenery 
maintainers workload!).

The address ? http://scenemodels.flightgear.org/submission/ then choose mass 
import, or via the "Contribute" menu.

Please note:

1. You must only import new objects, not the whole STG file you're 
working on!
2. Don't add models not present in the FG scenemodels database, nor 
(yet) OBJECT_SIGN nor OBJECT_STATIC.
3. Don't add forest or other items linked to the landcover. Those items 
have to 
be generated based on the landcover, not on objects! The only trees 
accepted will be those located within airport boundaries, for example.
4. The data you're asking for import should be based for elevation on 
the 
terrain shipped with FlightGear/Terrasync, and not on a terrain you 
could have downloaded or compiled yourself. Else, your objects could 
appear floating or sunk in the terrain in the current FG scenery...
5. Finally, the import is limited to 100 lines per submission (let's 
think about the poor scenery maintainer(s)...)
6. The import is quite sensitive about the data in entry, which goes 
through 
quite a lot of checkings, including humans, before insertion.Finally, and 
because I receive many questions about it, the import script for 3D models is 
on its way, finished to approximately 90%. Be patient.

Hope you enjoy it,

Oliver--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] FGCom -> cmake

2012-07-10 Thread Martin Spott
ThorstenB wrote:

> Schön wieder Fortschritte bei fgcom zu sehen. Und schön CMake + Git zu 
> sehen ;-). Habt ihr auch mal Holger Wirtz kontaktiert?

Unfortunately Holger is unable to contribute to FGCom any more, but
with a bit of luck he'll probably give access to his latest state of
develoment (which, as far as I know, is different from what's available
on Sourceforge).

Cheers,
Martin.
-- 
 Unix _IS_ user friendly - it's just selective about who its friends are !
--

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] FGCom -> cmake

2012-07-10 Thread ThorstenB
Ah well. You guessed the obvious... This was mainly meant for HB-GRAL.
Anyway, an opportunity to learn some German! ;-)

cheers,
Thorsten

Am 10.07.2012 20:52, schrieb ThorstenB:
> Am 10.07.2012 15:27, schrieb HB-GRAL:
>> The last weeks Geoff McLane and me forked fgcom temporary at gitorious
>> (http://www.gitorious.org/fgcom) and made some significant changes.
>> Origin source is still available at
>> http://sourceforge.net/projects/fgcom/
>
> Schön wieder Fortschritte bei fgcom zu sehen. Und schön CMake + Git zu
> sehen ;-). Habt ihr auch mal Holger Wirtz kontaktiert? Wäre vielleicht
> ganz gut. Er ist beim LinuxTag in Berlin immer mit dabei - hat aber
> ansonsten wohl viel anderes zu tun.
>
>> - In CMakeLists you can see that is possible now to set paths to
>> positions and frequencies files with:
>> -DSPECIAL_FREQUENCIES_FILE="fgcom-data/special_frequencies.txt"
>> -DDEFAULT_POSITIONS_FILE="fgcom-data/positions.txt"
>
> Super wäre es, wenn diese auch als CMake Optionen von außen gesetzt
> werden können - damit man das an sein System anpassen kann, ohne an den
> Sourcen zu schrauben. Siehe Patch im Anhang.
>
> Ansonsten habe ich für Linux noch die "pthread" Library hinzufügen
> müssen. Eine saubere Lösung wäre wohl das irgendwie zu detektieren -
> ggf. mal in die FG CMake Files reinschauen, und irgendwie abkupfern.
>
> Mit dem Patch im Anhang hat es bei mir direkt funktioniert und fgcom
> läuft einwandfrei. Das alte fgcom konnte ich nur auf meinem alten
> Rechner laufen lassen (lansgsamer single core) - auf meiner modernen
> 6core Maschine lief das alte fgcom irgendwie nicht.
>
> Gruß,
> Thorsten



--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] FGCom -> cmake

2012-07-10 Thread ThorstenB

Am 10.07.2012 15:27, schrieb HB-GRAL:

The last weeks Geoff McLane and me forked fgcom temporary at gitorious
(http://www.gitorious.org/fgcom) and made some significant changes.
Origin source is still available at http://sourceforge.net/projects/fgcom/


Schön wieder Fortschritte bei fgcom zu sehen. Und schön CMake + Git zu 
sehen ;-). Habt ihr auch mal Holger Wirtz kontaktiert? Wäre vielleicht 
ganz gut. Er ist beim LinuxTag in Berlin immer mit dabei - hat aber 
ansonsten wohl viel anderes zu tun.



- In CMakeLists you can see that is possible now to set paths to
positions and frequencies files with:
-DSPECIAL_FREQUENCIES_FILE="fgcom-data/special_frequencies.txt"
-DDEFAULT_POSITIONS_FILE="fgcom-data/positions.txt"


Super wäre es, wenn diese auch als CMake Optionen von außen gesetzt 
werden können - damit man das an sein System anpassen kann, ohne an den 
Sourcen zu schrauben. Siehe Patch im Anhang.


Ansonsten habe ich für Linux noch die "pthread" Library hinzufügen 
müssen. Eine saubere Lösung wäre wohl das irgendwie zu detektieren - 
ggf. mal in die FG CMake Files reinschauen, und irgendwie abkupfern.


Mit dem Patch im Anhang hat es bei mir direkt funktioniert und fgcom 
läuft einwandfrei. Das alte fgcom konnte ich nur auf meinem alten 
Rechner laufen lassen (lansgsamer single core) - auf meiner modernen 
6core Maschine lief das alte fgcom irgendwie nicht.


Gruß,
Thorsten
diff --git a/CMakeLists.txt b/CMakeLists.txt
index d599aae..63fd5dc 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -298,8 +298,11 @@ add_definitions( -DSVN_REV="261" )
 add_definitions( -DLIBVER="SVN 261" )
 
 # for now follow like in OSX, in fgcom-data in the 'install' directory
-add_definitions( -DSPECIAL_FREQUENCIES_FILE="fgcom-data/special_frequencies.txt" )
-add_definitions( -DDEFAULT_POSITIONS_FILE="fgcom-data/positions.txt" )
+option( SPECIAL_FREQUENCIES_FILE "Path to 'special frequencies' file." "/usr/share/fgcom/special_frequencies.txt" )
+option( DEFAULT_POSITIONS_FILE "Path to 'default positions' file." "/usr/share/fgcom/positions.txt"  )
+add_definitions( -DSPECIAL_FREQUENCIES_FILE="${SPECIAL_FREQUENCIES_FILE}" )
+add_definitions( -DDEFAULT_POSITIONS_FILE="${DEFAULT_POSITIONS_FILE}" )
+
 
 if(ADD_DEBUG_OUTPUT)
add_definitions( -DDEBUG )
@@ -358,6 +361,7 @@ else(WIN32)
 # DYNLIB=libiaxclient.dylib
 else(APPLE)
 if(UNIX)
+set( win_LIBS pthread )
 # CFLAGS:= $(CFLAGS) -Iportaudio/src/os/unix
 # DYNCFLAGS=-fPIC
 # DYNLIB=libiaxclient.so
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] FGCom -> cmake

2012-07-10 Thread Christian Schmitt
Awesome! I waited for just that, because current fgcom has not seen any 
change for a long time. Alreadey did a quick test and I think you will get 
some merge requests soon :)

Cheers,
Chris


HB-GRAL wrote:

> Hi all
> 
> The last weeks Geoff McLane and me forked fgcom temporary at gitorious
> (http://www.gitorious.org/fgcom) and made some significant changes.
> Origin source is still available at http://sourceforge.net/projects/fgcom/
> 
> - Most important change is moving fgcom to cmake build and trying to get
> fgcom compiling on all platforms again.
> 
> - updated perl scripts to generate positions and freqs files with recent
> apt.dat/nav.dat
> 
> - In CMakeLists you can see that is possible now to set paths to
> positions and frequencies files with:
> -DSPECIAL_FREQUENCIES_FILE="fgcom-data/special_frequencies.txt"
> -DDEFAULT_POSITIONS_FILE="fgcom-data/positions.txt"
> 
> - Some minor changes for OSX: clenaing here and there, 10.5/6
> i386/x86_64 universal support, individual (or macports) plib
> 1.8.5/PLIB.framework support, skipping osx 10.4 support, update
> iaxclient thread policy etc.
> 
> Most work have been done by Geoff McLane with this cmake support now,
> many thanks to Geoff working on all this stuff and help to incorporate
> my osx changes to ONE single branch for all platforms. fgcomx as another
> fork on gitorious have been deleted.
> 
> Now we need some testers and reporters for all platforms. When you want
> to help please checkout master and compile fgcom for your platform,
> install it and make echo tests or use it with your flightgear version.
> You will need current simgear and other dependencies of course (see
> readme, cmake 2.8, plib, OpenAL and current simgear needed).
> 
> Thanks a lot, Yves
> 
> PS. For next macflightgear release I would recommend to skip the old and
> buggy fgcom shipped with and replace it with a new build from this fork.
> After successful testing of course.
> 
> 
> 
--
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


[Flightgear-devel] FGCom -> cmake

2012-07-10 Thread HB-GRAL
Hi all

The last weeks Geoff McLane and me forked fgcom temporary at gitorious 
(http://www.gitorious.org/fgcom) and made some significant changes. 
Origin source is still available at http://sourceforge.net/projects/fgcom/

- Most important change is moving fgcom to cmake build and trying to get 
fgcom compiling on all platforms again.

- updated perl scripts to generate positions and freqs files with recent 
apt.dat/nav.dat

- In CMakeLists you can see that is possible now to set paths to 
positions and frequencies files with:
-DSPECIAL_FREQUENCIES_FILE="fgcom-data/special_frequencies.txt"
-DDEFAULT_POSITIONS_FILE="fgcom-data/positions.txt"

- Some minor changes for OSX: clenaing here and there, 10.5/6 
i386/x86_64 universal support, individual (or macports) plib 
1.8.5/PLIB.framework support, skipping osx 10.4 support, update 
iaxclient thread policy etc.

Most work have been done by Geoff McLane with this cmake support now, 
many thanks to Geoff working on all this stuff and help to incorporate 
my osx changes to ONE single branch for all platforms. fgcomx as another 
fork on gitorious have been deleted.

Now we need some testers and reporters for all platforms. When you want 
to help please checkout master and compile fgcom for your platform, 
install it and make echo tests or use it with your flightgear version. 
You will need current simgear and other dependencies of course (see 
readme, cmake 2.8, plib, OpenAL and current simgear needed).

Thanks a lot, Yves

PS. For next macflightgear release I would recommend to skip the old and 
buggy fgcom shipped with and replace it with a new build from this fork. 
After successful testing of course.


--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Cocoa/SDK10.5 support, small merge request

2012-07-10 Thread HB-GRAL
Am 08.07.12 16:27, schrieb HB-GRAL:
> Hi
>
> I sent a small merge request here to flightgear next:
> https://www.gitorious.org/fg/flightgear/merge_requests/36
>
> This small addition makes it possible flightgear still compiles with
> older osx development tools (cocoa/sdk10.5). I checked this change also
> with newer SDKs and it will/should not affect any other setting.
>
> Maybe James has to check and merge it in, or comment the request.
>
> Thanks a lot, Cheers, Yves
>
>

This merge request is obsolete now and have been removed. James reviewed 
and worked in relevant changes. Thanks a lot, Cheers, Yves

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


[Flightgear-devel] FlightGear/Simulink/LabVIEW Interface

2012-07-10 Thread Andrew Tudor
Hi,

I have a thread here:
http://www.flightgear.org/forums/viewtopic.php?f=42&t=16853 where I
was directed to contact this email with questions. First, let me
explain my goal with FlightGear. I would like run FG and take
real-time data from it. I do not want to provide my own model, I would
like to use one already established (the P51D was suggested to me).
The data I would like to get is position (x,y,z), orientation
(pitch,yaw,roll) and control surface information (elevator, ailerons,
throttle, rudder). Modifying the control surface data is also
important. With that data inside Simulink I will feed that to LabView
using the Simulation Interface Toolkit (SIT) provided by NI which will
then be interfaced with our hardware. I have had a few questions and
it might be better to ask here rather than the forums.

- From what I understand control surfaces can be modified using this
block: 
http://www.mathworks.com/help/toolbox/aeroblks/packnet_fdmpacketforflightgear.html
?
- How can I get position and orientation information? I can instead
use the velocity of the aircraft with respect to the wind if that is
available? In general I want a way to define a level flight path.
- I have been trying to find these two blocks in Simulink:

http://www.mathworks.com/help/toolbox/aeroblks/receivenet_ctrlpacketfromflightgear.html
http://www.mathworks.com/help/toolbox/aeroblks/unpacknet_ctrlpacketfromflightgear.html

but I can't find them. I have the other 4 blocks but not these. I
initially was using 2.6.0 but noticed that the web page was referring
to 2.0 so I switched versions with no success. I have been looking in:
Simulink Library Browser > Aerospace Blockset > Animation > Flight
Simulator Interfaces.

-Do you think it is possible in FG to get the variables I need? I am
not worried about interfacing the programs once I can access the
variable in Simulink (or for that matter LabView) that I need. This
whole interfacing and project set up is new to me so any help you can
give would be great. Please forward this to anyone you think can be of
help.

Thanks!
Andy


Andrew W. Tudor
University of California, Los Angeles
Graduate Student in Mechanical and Aerospace Engineering
University of Illinois, Urbana-Champaign
B.S. Aerospace Engineering

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel