Re: [Flightgear-devel] C310 Update
Hi Stuart, Thanks! How do you feel is the front-wheel steering (low speed, low rpm)? If I look from outside the wheel points to one direction but the action of the aircraft is very slow. At a little bit higher speed the a/c is sliding forward dispite the wheel direction. Just a hint, nothing more. I also wish you and your family a peaceful and happy christmas time. Georg EDDW Buchanan, Stuart schrieb: --- Buchanan, Stuart wrote: Hi All, I've been working on an update for the civilian Cessna 310R, and my patches are now available for review/check-in. Thanks for all the feedback. I've updated the c310.tar.gz and quadrant.tar.gz file to fix the following issues: - mixture (and prop!) levers the wrong way around - bad top wing surfaces - alpha issues on panel. Work-around by creating a background. Not perfect, but I haven't got to the bottom of the issue. - Transparent cabin when viewed from above. Fixed by re-ordering .ac file. As before, the files are available from http://www.nanjika.co.uk/flightgear/c310/. Finally, I hope everyone has a good holiday season. -Stuart ___ Yahoo! Exclusive Xmas Game, help Santa with his celebrity party - http://santas-christmas-party.yahoo.net/ ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] C310 Update
Thank you Jon, I thought it to be a problem just for this a/c. Now I know better and look forward .. Regards Georg EDDW ... Hi Stuart, Thanks! How do you feel is the front-wheel steering (low speed, low rpm)? ... FYI, the coming version of JSBSim will be having very much improved ground handling. Almost there ... Jon ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] C310 Update
Hi Stuart, I can see the nice screenshot but cannot download the files, anything seems to be broken with the link. Would you please check it? Thank you Georg EDDW Buchanan, Stuart schrieb: Patch files are available from http://www.nanjika.co.uk/flightgear/c310/ .. Feedback is greatly appreciated. Regards, Stuart Buchanan _ ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] C310 Update
Buchanan, Stuart schrieb: Hi Georg, Directory listings were switched off, though I think the files were accessible directly. I've enabled directory listings - should work OK now. -Stuart Thank you, Stuart! Downloaded the files and will give feedback as soon as I tested it (in some hours). Regards Georg EDDW ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Even more Scenery Objects
Martin, thank you for the hint, it is a phantastic work! I post it into the German FlightGear forum. Regards Georg Martin Spott schrieb: http://document.ihg.uni-duisburg.de/bitmap/FGFS/EDDI_01.jpg ... Everything on: http://fgfsdb.stockill.org/models.php Cheers, Martin. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] C310 Update
Buchanan, Stuart schrieb: Hi Torsten, Hi Stuart, as Torsten reported more than I could find out when flying the plane, I just have to say that due to your work this nice plane now got back into my hangar. Thank you for your work! Georg EDDW ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] tile cache reload
Hi, during scenery development I experienced that either the [F2] command (development keys: F2 ... force tile cache reload) nor the Reset command does a reload of the *.stg files (Terrain and/or Object folder) of your actual position :-( I did several tests with the newest FG CVS and FG 0.9.9 but only a complete newstart of FG (or going away a real *long* distance with the UFO and returning ) reloads the position related *.stg file(s). Could it be made that the ...force tile cache reload command also re-reads/reloads the used *.stg files (Object and Terrain folder)? This is *very* important for scenery development (placing objects into the scenery) as you could change the local *.stg file (ie. add an object) while FlightGear is running, press the [F2] key and see how/where it is placed into the scenery. As we haven't got any other visual tools for scenery object placing this is the only method - as I know - without wasting a lot of time due to several restarts of FG. Adding this to the reset command would alternativly also be a help but as reset changes your position, views, etc it is second choice. Regards Georg EDDW ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] CVS compiling error CYGWIN
Hi,
after many!!! new builds without any problem I have got a new one over
the last days when trying to compile the newest CVS under Cygwin.
At last I even made a complete new Cygwin install and complete new
download of SimGear and FlightGear CVS and tried to compile the whole
stuff - same result: SimGear without problems, FlightGear compilation
does not work.
Any ideas? Thank you in advance!
Regards
Georg EDDW
In file included from
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/deque:71,
from
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/queue:74,
from ../FGJSBBase.h:47,
from FGFCSComponent.h:46,
from FGDeadBand.h:40,
from FGDeadBand.cpp:40:
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/bits/stl_deque.h: In
member function `void std::_Deque_base_Tp,
_Alloc::_M_initialize_map(size_t)':
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/bits/stl_deque.h:446:
error: expected unqualified-id before '(' token
In file included from
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/deque:74,
from
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/queue:74,
from ../FGJSBBase.h:47,
from FGFCSComponent.h:46,
from FGDeadBand.h:40,
from FGDeadBand.cpp:40:
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/bits/deque.tcc: In member
function `void std::deque_Tp, _Alloc::_M_reallocate_map(size_t, bool)':
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/bits/deque.tcc:699: error:
expected unqualified-id before '(' token
In file included from
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/streambuf:781,
from /fg-cvs/include/simgear/debug/logstream.hxx:36,
from /fg-cvs/include/simgear/props/props.hxx:34,
from ../FGPropertyManager.h:40,
from FGFCSComponent.h:47,
from FGDeadBand.h:40,
from FGDeadBand.cpp:40:
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/bits/streambuf.tcc: In
member function `virtual std::streamsize std::basic_streambuf_CharT,
_Traits::xsgetn(_CharT*, std::streamsize)':
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/bits/streambuf.tcc:54:
error: expected unqualified-id before '(' token
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/bits/streambuf.tcc: In
member function `virtual std::streamsize std::basic_streambuf_CharT,
_Traits::xsputn(const _CharT*, std::streamsize)':
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/bits/streambuf.tcc:88:
error: expected unqualified-id before '(' token
In file included from
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/locale:47,
from
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/bits/ostream.tcc:40,
from
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/ostream:545,
from
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/iostream:45,
from /fg-cvs/include/simgear/debug/logstream.hxx:37,
from /fg-cvs/include/simgear/props/props.hxx:34,
from ../FGPropertyManager.h:40,
from FGFCSComponent.h:47,
from FGDeadBand.h:40,
from FGDeadBand.cpp:40:
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/bits/locale_facets.tcc:514:57:
macro min requires 2 arguments, but only 1 given
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/bits/locale_facets.tcc:563:57:
macro max requires 2 arguments, but only 1 given
In file included from
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/locale:47,
from
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/bits/ostream.tcc:40,
from
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/ostream:545,
from
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/iostream:45,
from /fg-cvs/include/simgear/debug/logstream.hxx:37,
from /fg-cvs/include/simgear/props/props.hxx:34,
from ../FGPropertyManager.h:40,
from FGFCSComponent.h:47,
from FGDeadBand.h:40,
from FGDeadBand.cpp:40:
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/bits/locale_facets.tcc: In
member function `_InIter std::time_get_CharT,
_InIter::_M_extract_name(_InIter, _InIter, int, const _CharT**,
size_t, std::ios_base, std::_Ios_Iostate) const':
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/bits/locale_facets.tcc:2056:
error: expected unqualified-id before '(' token
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/bits/locale_facets.tcc: In
function `bool std::__verify_grouping(const char*, size_t, const
std::string)':
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/bits/locale_facets.tcc:2499:
error: expected unqualified-id before '(' token
In file included from
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/istream:771,
from
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/iostream:46,
from /fg-cvs/include/simgear/debug/logstream.hxx:37,
from
Re: [Flightgear-devel] CVS compiling error CYGWIN
Hi David, your help did not only save the day but the rest of the week, thank you very much :-) I could compile the CVS and FG is running! Have you tried adding -DNOMINMAX to your CFLAGS and CXXFLAGS? Mmh, this was behind my scope. If you ever have some time then tell me please where I find these flags. Can I find something linke a config file anywhere? Alternatively try adding #ifdef HAVE_CONFIG_H # include config.h #endif as the first include of each cxx or cpp file giving problems. This solved the problem. I just put it into the following 4 files (I hope I did not forget one): FGDeadband.h ../FGJSBBase.h FGFCSComponent.h ../FGPropertyManager.h !! As I have not got the skills until now to create a diff file to the cvs and I am not sure whether I have placed the stuff at the position in the code where it should be in a professional manner I would ask anyone who can do it for changing these CVS files to prevent trouble for other friends using Cygwin/CVS. Thank you in advance! I'm not using Cygwin any more BTW, so I'm posting blind, but I'm pretty sure it will turn out to be the old min/max redefinition problem again. Cheers - Dave Ok, now blind but pretty well remembering the way to go from the days you could see :-) :-) Thank you once again, I am really happy now. Regards Georg EDDW ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Render texture problem - report
Hi, while doing some research work to give help to another FG user I installed one of the latest FG CVS compilation on my daughters PC (which was clean of all Cygwin or FG stuff befored) and ran FG under a minimalistic Cygwin install. FG CVS 0.9.x did start and work *without problems* but I got the following error message which does *not* appear on my PC: Error: Render Texture requieres the following unsupported OpenGL extensions: WGL_ARB_extensions_string Just to report this as I don't know whether it is already known or could be helpful to fix the problem. Regards Georg EDDW ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Disappearing objects - bug???
Hi, after trying a lot of hours to solve the problem myself I am now asking for help. I placed 2 objects into the sea near Bremerhaven (EDWB) which can be seen from distance but when you come nearer they disappear. http://home.arcor.de/vollnhals-bremen/DisappObjects/fgfs-screen-037.jpg http://home.arcor.de/vollnhals-bremen/DisappObjects/fgfs-screen-038.jpg http://home.arcor.de/vollnhals-bremen/DisappObjects/fgfs-screen-039.jpg Until now I had no problems with some objects I placed near EDDW, therefore I am not sure it is a bug or my personal failure. What did I do? 1. Put the objects I want to place into the scenery into the folder ..\data\Scenery\Objects\e000n50\e008n53 (lighthouse.xml/ac/rgb + oilrig.ac, oilrig1.rbg, oilrig2.rgb) 2. Created a file 3089361.stg OBJECT_STATIC lighthouse.xml 8.48 53.57 0.0 10 OBJECT_STATIC oilrig.ac 8.485 53.575 0.0 10 3. Put 3089361.stg into folder..\data\Scenery\Objects\e000n50\e008n53 4. Testflights - see screenshots - with fresh build FG CVS (I defined the objects as static because defined as shared they did not show up at all) I am thankful for any help and hints! Regards Georg EDDW ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Disappearing objects - bug???
Melchior FRANZ schrieb: * Georg Vollnhals ([EMAIL PROTECTED]) [051210 17:36]: I placed 2 objects into the sea near Bremerhaven (EDWB) which can bex seen from distance but when you come nearer they disappear. Why did you choose 3089361.stg? Guessing? :- In scripts/perl/scenery/ there's a script calc-tile: Melchior, I am very sorry for the inconvenience I caused but I was fully *blinded* for the real reason which caused this strange behaviour - it must have been a wrong lat/lon input when I calculated the tile with calc-tile.pl. This was not obvious for me as the objects did show up from the distance, so I did not think of this simple error! Thank you for your help, I already have wasted a lot of hours by trying to solve the problem myself - but failed :-(( Regards Georg ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] 2D-Panel for 707
Hans-Georg Wunder schrieb: Hi all, just for your information. I'm still working on a 2D-panel for the 707: Hi Hans-Georg, looks really impressive, this old style layout with all the clocks :-) Your work will be a good reason to try to fly the old lady and rembering the days when I was young (707 and Caravelle were very impressive for me those days). Georg EDDW BTW: what city is displayed in your screenshot? ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] 2D-Panel for 707
Martin Spott schrieb: Georg Vollnhals wrote: BTW: what city is displayed in your screenshot? According to the buildings this must be Paris (find the large TV set right hand behind the turtle :-) Thank you, next flight from LFPG Charles de Gaulle airport, checking :-) I'm surprised to see such a panel layout - it's almost as flat and straight as your C172's are. Did the early airliners really have such a simple panel layout ? Cheers, Martin. I think he did it in a functional style like many of the old MSFS panels were as I remember. Parts of the side panel (flight ing) also integrated. You may hate this or love it. After my opinion the combination of a nice 3D-panel where you have all the things at the right place and the instruments in sight although you are not looking straight forward and a 2D working panel where you have all necessary information concentrated and readable is the best. The pros and cons of 3D panels with very small instruments have already been discussed in this forum, I don't want to get back again, but although I use a 19' display many instruments (ie. b1900, citation) are not readable without zooming onto them and that is sometimes a real pain if you are flying a more complicated approach. For that purpose a more composed 2D panel with big readable instruments and all necessary information needed is more functional than the 3D variant. If I am not wrong it is already possible to switch between the 3D panel and the 2D panel by the s key??? So you could choose what you want for every flight situation. Regards Georg EDDW ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Airport of Hell?
Joacim Persson schrieb: On Sun, 27 Nov 2005, Mathias Fröhlich wrote: Both work for me. What scenery do you use? Is this the 0.9.9 I am currently downloading? :) ... I still use the 0.9.8 normally. Don't know about Melchior, but I'm using terrasync -- whichever version it's feeding me with, I simply don't know. Ask Curt. =) (just did a fresh reload of the tile in question too check if terrasync is syncing properly -- same result. Now getting a steaming fresh 0.9.9 tile for comparison.) I didn't even know the 0.9.9 scenery was released already. The links on the download page still points at 0.9.8. If we have the same source code version, and the same scenery version, the difference could lie in how our respective computer memory has been used lately, i.e. smells like a case of unitialised memory use (or prematurely freed mem). ...which a mem debugger ought to catch. (last time I had a go with valgrind and efence on fgfs, I ran out on swap. :P Have added some more swap since then. The good news is that this bug is suitable for hunting down in a batch run with a mem debugger -- doesn't need any user input.) Hi, I was curious about this problem and did some tests: Only *one* scenery-folder in [FGCVS]\data\.. 3 FG installs FG 0.9.8 windows binary FG 0.9.9 windows binary FG 0.9.x cygwin CVS (only 2 days old) Parameters (set via FGTools V1.3.4), example for FG 0.9.9 windows binary: --fg-scenery=C:\cygwin\fg-cvs\data\scenery --fg-root=H:\FlightGear99\data --enable-fullscreen --bpp=24 --prop:sim/current-gui=1 --airport=EGLL Results: 1. FG 0.9.8 windows binary works without problems 2. FG 0.9.9 windows binary and FG 0.9.x cygwin CVS either freezes in a black hole or crashes This might be an OpenAL problem as I could copy these outputs from a) 0.9.9 binaries b) Cygwin CVS Regards Georg EDDW - a) Windows 0.9.9 binaries latitude = 7.60387e-316 longitude= 1.79954e-307 OpenAL error (AL_INVALID_VALUE): set_pitch altitude = 18.0925 sea level radius = 1.76081e-264 latitude = 7.60387e-316 longitude= 1.79954e-307 OpenAL error (AL_INVALID_VALUE): set_pitch altitude = 18.0925 sea level radius = 1.76081e-264 latitude = 7.60387e-316 longitude= 1.79954e-307 OpenAL error (AL_INVALID_VALUE): set_pitch altitude = 18.0925 sea level radius = 1.76081e-264 latitude = 7.60387e-316 longitude= 1.79954e-307 OpenAL error (AL_INVALID_VALUE): set_pitch altitude = 18.0925 sea level radius = 1.76081e-264 latitude = 7.60387e-316 longitude= 1.79954e-307 OpenAL error (AL_INVALID_VALUE): set_pitch altitude = 18.0925 sea level radius = 1.76081e-264 latitude = 7.60387e-316 longitude= 1.79954e-307 OpenAL error (AL_INVALID_VALUE): set_pitch altitude = 18.0925 sea level radius = 1.76081e-264 latitude = 7.60387e-316 longitude= 1.79954e-307 OpenAL error (AL_INVALID_VALUE): set_pitch altitude = 18.0925 sea level radius = 1.76081e-264 latitude = 7.60387e-316 longitude= 1.79954e-307 OpenAL error (AL_INVALID_VALUE): set_pitch altitude = 18.0925 sea level radius = 1.76081e-264 latitude = 7.60387e-316 longitude= 1.79954e-307 OpenAL error (AL_INVALID_VALUE): set_pitch altitude = 18.0925 sea level radius = 1.76081e-264 latitude = 7.60387e-316 longitude= 1.79954e-307 OpenAL error (AL_INVALID_VALUE): set_pitch altitude = 18.0925 sea level radius = 1.76081e-264 latitude = 7.60387e-316 longitude= 1.79954e-307 OpenAL error (AL_INVALID_VALUE): set_pitch altitude = 18.0925 sea level radius = 1.76081e-264 latitude = 7.60387e-316 longitude= 1.79954e-307 OpenAL error (AL_INVALID_VALUE): set_pitch --- b) Cygwin CVS: OpenAL error (AL_INVALID_VALUE): set_pitch OpenAL error (AL_INVALID_VALUE): set_pitch OpenAL error (AL_INVALID_VALUE): set_pitch Failed to open file OpenAL error (AL_INVALID_VALUE): set_pitch Failed to open file OpenAL error (AL_INVALID_VALUE): set_pitch Failed to open file OpenAL error (AL_INVALID_VALUE): set_pitch Failed to open file OpenAL error (AL_INVALID_VALUE): set_pitch Initializing Nasal Electrical System OpenAL error (AL_INVALID_VALUE): set_pitch OpenAL error (AL_INVALID_VALUE): set_volume altitude = 1.45429e-231 sea level radius = 1.13021e-317 latitude = 9.93823e-315 longitude= 1.13009e-317 OpenAL error (AL_INVALID_VALUE): set_pitch altitude = 1.45429e-231 sea level radius = 1.13021e-317 latitude = 9.93823e-315 longitude= 1.13009e-317 OpenAL error (AL_INVALID_VALUE): set_pitch altitude = 1.45429e-231 sea
Re: [Flightgear-devel] SimGear CVS error SG_LOG Cygwin
Erik Hofman schrieb: Georg Vollnhals wrote: Hi, with the newest SimGear CVS I get this compiling error (Cygwin, gcc 3.4.4): RenderTexture.cpp:1595:44: macro SG_LOG passed 4 arguments, but takes Bah, conditional compiles don't make life easier. This should be fixed now. Erik Erik, thank you! All works fine now. Georg ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] SimGear CVS error SG_LOG Cygwin
Hi, with the newest SimGear CVS I get this compiling error (Cygwin, gcc 3.4.4): RenderTexture.cpp:1595:44: macro SG_LOG passed 4 arguments, but takes just 3 RenderTexture.cpp: In member function `void RenderTexture::_ParseModeString(const char*, std::vectorint, std::allocatorint , std::vectorint, std::allocatorint )': RenderTexture.cpp:1592: error: `SG_LOG' undeclared (first use this function) RenderTexture.cpp:1592: error: (Each undeclared identifier is reported only once for each function it appears in.) RenderTexture.cpp:1642:72: macro SG_LOG passed 4 arguments, but takes just 3 make[3]: *** [RenderTexture.o] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all] Error 2 make: *** [all-recursive] Error 1 Anyone else with this problem? Regards Georg ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] thesis?
Szabolcs Berecz schrieb: Hi! I'm thinking about my thesis which I have to write next semester. I'm interested in FlightGear, but haven't got the time to dig into it, yet, so I don't know what needs to be done. Is there something which should be done, but you don't have the time for it? Maybe I would be willing to do it, but it shouldn't be too big, because I have to write most of it in a couple of months. It shouldn't be too easy, either. Do I want too much? :) Oh, and usually I'm not too interested in user interfaces and graphics, but I don't say there is no chance to work on something like that... I will have time to go into details and start working on something the next week. I would appreciate if you could suggest something. Thanks, Szabi ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d Hi Szabi, I am only a user and not a developer (and can't therefore of no big help for you when you realize your project) but I want to make a suggestion: At the moment it is not very comfortable to place an object into the FlightGear world. First you have to calculate the tile-number via a separate Perl script (Lat/Lon - tilenumber), then you have to get the right elevation of that place, then you have to think about the angle you want to place the object into the world, then you have to create the *.stg file and write the things into it (or add them). All without any visual control and without the possibility to place a complete set of normally single objects into the scenery at one time. I am inspired by the FLY! object editor and as this always has been created for another (old) flightsim it might collide with what you have to do for your students work, but anyway I want to describe how it works in FLY: You fire the sim, fly/go to the place where you want to put your object/set of objects, press a key-combination. Then you see the scenery from above (bird-view) with a cross-marker (it aims to the point where the object is placed if you want to do so). You can go nearer of farer, to all directions (and even angles) to view the scenery. Then you select an object from a menue (grafical view) and place it into the scenery. You can now move it to the place you want to have it, select the height if other than ground (ie an object you want to place into the air or onto an already existing object), then you may safe your work. (In FLY! it is even more comfortable as you can select *every* object already placed in the scenery, move, scale and put it together, but I think this might a little bit too complicated for a several months work :-) ) When the object is safed, your code should make all calculations, changes or creations of new files - and if it is possible, make an initialisation of the scenery if you go out of the editing mode into normal flight mode, so that the new object is placed in the virtual world and can be seen. An add-on could be a little program outside of FlightGear where you can place several single objects into a fixed set which can be placed into the scenery by your new object-edit-code as described above. (This might be a collection of houses, trees, cars, etc to build some sort of a small generic village, or all other sort of small sceneries (small harbour, power plant, etc) which you want to place more than once into FlightGear. Ok, this was just my thought what could be done by you if interested. Regards Georg ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: [0.9.9] screenshots for flightgear.org
Curtis L. Olson schrieb: Ampere K. Hardraade wrote: Perhaps we can have a weekly screenshot competition? The best screenshot of the week get uploaded to FlightGear's frontpage. Sounds like a great idea. ... Curt. ... Ok, I want to win the prize and stop working :-): http://home.arcor.de/vollnhals-bremen/FGScrSh/FGSrSh0003.jpg http://home.arcor.de/vollnhals-bremen/FGScrSh/FGSrSh0004.jpg http://home.arcor.de/vollnhals-bremen/FGScrSh/FGSrSh0005.jpg http://home.arcor.de/vollnhals-bremen/FGScrSh/FGSrSh0006.jpg http://home.arcor.de/vollnhals-bremen/FGScrSh/FGSrSh0007.jpg http://home.arcor.de/vollnhals-bremen/FGScrSh/FGSrSh0008.jpg http://home.arcor.de/vollnhals-bremen/FGScrSh/FGSrSh0002.jpg http://home.arcor.de/vollnhals-bremen/FGScrSh/FGSrSh0001.jpg If you want to have the original *.ppm, I still have them Regards Georg ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Beaver instrument error
Hi, I recognized instrument display errors with the Beaver (a really wonderful FG plane!!!). Have a look at the screenshots, pics can explain more than words: http://home.arcor.de/vollnhals-bremen/BeaverInErr/InFail0002.jpg http://home.arcor.de/vollnhals-bremen/BeaverInErr/InFail0003.jpg http://home.arcor.de/vollnhals-bremen/BeaverInErr/InFail0004.jpg http://home.arcor.de/vollnhals-bremen/BeaverInErr/InFail0001.jpg The instruments also are too dark if you don't have the sun in the back, you have to switch on instrument lights :-( Anyone else with the same error? I have got the one of the last CVS data and build (source). If it is a problem, can it be fixed before releasing 0.9.9??? Regards Georg ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: [0.9.9] screenshots for flightgear.org
Ralf Gerlich schrieb: can I trust my eyes? This must be from the lake-constance scenery...near Bregenz...cool! ;-) Hi Ralf, you must know better than I :-). To be honest, I started from EDNY to combine your very detailled scenery together with the Citation Bravo aircraft on a screenshot. But from some height it all looked rather odd due to the very few textures we have in FlightGear, and not only we have few - they don't fit together perfectly from colour and shape and look not very European. Therefore I masked it with a nice cloud-layer - but then I got *lost*: flying the aircraft from outside, looking for a nice view and convering the ground with clouds. But I think you are right when I look at the screenshots. Regards Georg ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Buildings ?????
Ralf Gerlich schrieb: Erm, yes...working on the GRASS-HowTo for Scenery Designers ;-) Didn't get far yet... Cheers, Ralf Yes, would be a nice christmas present! :-) :-) I stared work with FGSD and made some smaller corrections but it is not possible to correct a bigger area with that tool in the present state (what does not mean that it is bad, it only needs further development and documentation). As always in life, it is a question whether you have the right tools to make a good job and enjoy it! Thank you in advance, Ralf, for finishing your GRASS-HowTo! Regards Georg ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: [Flightgear-users] Re: FGFS 0.9.9-pre2 shadows...
Georg Vollnhals schrieb: Hi, try --bpp=24 as parameter when starting FG. I had the same problem until I got the idea to try this. Now I have nice shadows and a nice reduction in frame-rate. But it's worth :-) Regards Georg Sorry, just working through my mails. Did not see that Pigeon answered already :-) Georg ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] OT: A380 arrived in EDHI (Hamburg-Finkenwerder)
Torsten Dreyer schrieb: Hi everybody! Last tuesday, the A380 serial number 2 (F-WXXL) came to the airbus site in Hamburg to get a new painting and the interior. They will also do the .. An aerial foto of EDHI is here http://www.eddh.de/info/landeinfo-ergebnisb.php?ueicao=EDHI but it is a few years old. In the meantime, the bay located in the center of .. I took some fotos of the A380 landing on tuesday and put them here http://www.t3r.de/fg/a380/ I also put 2 movies there for those with a fast internet-link, they are 37MB and 60MB. Hope you like this little story and the pics. Cheers, Torsten ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d Hi Torsten, thank you for sharing this with us, very interesting! *Bremen* is very proud that the A380 made a low approach at the local airport to greet the employees of the local airbus facility where they constructed the A380 flaps (size of a little airliner wing!) and other wing-add-on stuff. I could only see some pictures in the local newspapers as I was very engaged in day-work and could not look out though the airport ist pretty nearby and I'll always have a look at the traffic when it is possible :-) Last November (2004) I shot some pics when we passed EDHI. The new terrain has already been built and most of the buildings, as I assume. I put 3 pics on my homepage, if you are interested how it looked from air: http://home.arcor.de/vollnhals-bremen/HHFinkenwerder/hamburg_finkenwerder.htm Regards Georg (EDDW) ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear v0.9.9-pre2
Steve Hosgood schrieb: Seems like the program closes /usr/share/FlightGear/data/preferences.xml and immediately crashes. Hi Steve, I had the same problem today after compiling new SimGear/FlightGear CVS. Although I had downloaded FlightGear CVS data with cvs update -d -P I got the message that preferences.xml could not be read by SimGear XML Browser line 1 column 1 and the program terminated. Same after I deleted Line 1, another XML brower error message came up. This was not really professional but easy (in my job I am trained to follow the KISS principle keep it simple, stupid) - I renamend the data folder and made a complete new download of all FlightGear data - and it worked afterwards. After my opinion it has something to do with an old preferences.xml file (I changed the AI entries to have the carrier and other ai) which could not be read anymore with the new CVS code. But please - I am a FlightGear newbie, this is just my 2 c to try to help you as the problem seems to be similar. Regards Georg ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Which aircraft to include in v0.9.9?
Steve Knoblock schrieb: My first impression of FlightGear on Windows was soured by the first aircraft I choose. It was the Cessna with full IFR panel. The panel was upside down and very strange. It didn't make a good first impression and left me confused. If I had not been persistent I might have gave up on it right there. I remember this very clear, I was the same when I tried V0.9.8! Moreover, I could not figure out why there were so many Cessna's and what the differences were. An aircraft should be operational, not in a state of development if it is to be included in the official distribution. Aircraft in development can be downloaded individually. Aircraft should not be incomplete, missing panels, incomplete instruments, etc. I realize this is not easy given the open source and experimental nature of Flight Gear development. There was a review/test of FlightGear in linux user, November 2005, a very popular German linux magazin. Although they gave FlightGear 4 full pages, scenery on their cover CD and a lot of very usable hints aimed to flightsim beginners they complained about missing panels, missing instruments, missing Transponder (and a lot of other things like bad flightmodel ((due to missing stall characteristics)), missing structural damage, missing red and white-blackout, missing higher-level ATC, missing colleason detection ((they might have proved it with the ... objects)). Their last recommendation was not what we would like to see and we could say simply ignore it but a *lot* of linux user are reading this magazin and potentially flightsim interested people get the wrong impression by this review. :-( This means for me - an official release is always some PR for the FlightGear project and the chance to get some people interested, might be even starting some user development (small projects) or to loose them before they have had the chance to see what FlightGear can offer today! And after my opinion there is a need for people who do some work outside the core development - make some more nice generic models for FG that can be used for scenery design, improve airports, make repaints, even do 3D aircraft modelling. This was the typical work sharing what I experienced when I was active for another flightsim (FLY! II). And even core developers may like it to fly a nice little scenery a pure user was able to create. To be honest, also some *easy* tools are lacking now to enable pure users to do such work without too much knowledge about the internal FlightGear stuff. Just a dream for the future :-) I agree with the idea of removing the UFO in favor of a more useful and complete aircraft. .. I think it's important to keep the most widely used general aviation craft, like Cessna and Piper .. Most users will want a light single engine general aviation aircraft they are familiar with. The Cessna fills this niche and is the most popular. I suggest one classic and one modern Cessna single. Of course the linux user magazine used the Cessna *172* to make the first testflights and (very clever!) they recommended the *ufo* to get familiar with the main functions of FlightGear when the reader had no knowledge of flightsims before taking off with the Cessna (what they described step for step in a really professional manner). So, after having said all this, my opinion is only to add very complete (3D, panel, flightmodel) aircraft to the new release. Interested people can download, it is very easy. Regards Georg ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: FG CVS error report
Melchior FRANZ schrieb:
one more serious problem:
- adjust HUD transparency
does not switch but after you leave the menue ('cancel') the *main*
How is this more serious? This is by *design* and was like that since
ages.
Melchior, you cut off the very *important* part of the sentence:
- does not switch but after you leave the menue ('cancel') the
*main* menue is frozen (no reaction on clicks)
In my eyes something is serious when you make a legal keypress and
afterwards a big part of the programs functions don't work anymore = the
main menu is frozen = you can only use keycodes not the mouse and the
main-menue entries are not accessible anymore.
Ok, if this is by design then all is ok, I just reported an error
which might be a problem for *other* user.
Not for me anymore as I know about these features.
Regards
Georg
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: FG CVS error report
Melchior FRANZ schrieb: I didn't criticize that you reported it -- that was the right thing to do. I just didn't share your opinion that it had to be fixed for the next release. Someone has to spend the time after all. And there will be a release after 0.9.9, or two. ;-) m. This is ok :-) - other priorities and limited time is an important factor! After all, I am really happy with this new GUI style Cheers Georg ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Please upgrade to version: 0.9.8
Josh Babcock schrieb: Or you could run linux, then he could only mess up his own files. Josh Yes Josh, that's my way for the future :-) I already created a second partition for Linux some months ago and tried Suse, Fedora, Kubuntu, Knoppix and Kanopix (Debian version). The last was the best for me - installed all my hardware without problems, runs fine. Only problem is that I cannot get my WLAN/router working (Ethernet no problem). I am playing with that whenever I have some time left. But this is the cutting edge for me: no WLAN, no serious work under Linux :-( But I hope I'll find a solution for that in the next future - working with FlightGear under Linux would be a lot easier, I think. Regards Georg ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Please upgrade to version: 0.9.8
Georg Vollnhals schrieb: Curtis L. Olson schrieb: It sounds like you aren't current with your flightgear source or executable? Could you still be running an older build of flightgear (or not fully up to date with your source code?) Curt. Did you upgrade your data from the cvs? Vassilii Just as a feedback: it seems that the file management system (CVS/compiler) got confused as a I had the system clock set to 2006 for some time and are now back in 2005. Some older files might be considered to be the newest one due to the date of 2006 :-) There was no other way for me than to delete all CVS stuff (FlighGear, SimGear) and make a complete new download and build. Worked then without problems. Thank you once again, Curt and Vassilii Regards Georg ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Please upgrade to version: 0.9.8
Curtis L. Olson schrieb: man touch ? Curt. Yes. My 13 years old son is actually a co-user on my PC. He does not ask, he does not think a lot - just trial and error method. Very good if you have all your important data burned on CD/DVD and have a good firewall, virus-scanner and no possibility to make a dial-up connection from your PC! But only until christmas, then I'll upgrade my PC and I'll build him his own with the parts I don't use anymore and those he gets as presents :-) :-) Joy of fatherhood! Regards Georg ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] FG CVS error report
Hi, if I press [Shift - F10] .. cycle through GUI styles *AND* the Basic keys menu is still opened FlightGear freezes. I had it one time by accident and could reproduce it a second time. (Latest FG CVS under Cygwin) Georg BTW: I like that new GUI style very much. Is there a parameter to have it as default when starting FlightGear? ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Please upgrade to version: 0.9.8
Georg, Even the parents should have the occasional Christmas present :-) George Patterson Thanx, just put your mail into my wife's mail account ;-) Georg ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: FG CVS error report
Can't reproduce that. The dialog closes as it is supposed to. Hi Melchior, just to be sure I updated and recompiled again. Same error as described. Shift+F10 when running FG changes GUI style back and forth without problems, Basic Key Window open + Shift/F10 freezes FG. Tested it several times, all default (KSFO + Cessna) directly after starting FG, CygWin/Windows XP Home. Can you provide a stack backtrace? m. Sorry, I think this is far behind my scope as Windows does not give any stack info back as FG is a Cygwin process. And I have to kill Cygwin with the Windows taskmanager as it freezes too. And my knowledge about Cygwin is very limited :-( May be some other Cygwin user can test whether it is an individual problem (then forget about it) or a general one? Regards Georg ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: FG CVS error report
Melchior FRANZ schrieb:
..
but for now I think we can live with that.
That is ok, I think it should only be fixed before the new version gets
officially out.
I checked some other menues
one more serious problem:
- adjust HUD transparency
does not switch but after you leave the menue ('cancel') the *main*
menue is frozen (no reaction on clicks)
one less serious problem:
- Browse internal properties does not switch, but some (did not test a
lot) submenues do (what is fine) but are frozen in that status (when you
change back to the normal style).
I doubt that many people will
find the themes feature at all. :-)
m.
_
Yes, might be - but we should tell them! It is all a question of
personal taste, but the new style is really nice and my default from
now. Yes, eye-candy somehow - but I also like my house much better after
I have painted it :-)
Thank you, Melchior and Harald.
Regards
Georg
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Please upgrade to version: 0.9.8
Georg I must have missed something?? George patterson Sorry for the not understandable (bad) joke :-/ Georg ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Please upgrade to version: 0.9.8
Hi, after compiling the latest CVS and running the new build this message occurs ***Base package check failed ... Found version 0.9.9-pre1 at: /fg-cvs/data*** I know that Curt did some changes regarding the new version in the CVS and there must be a very simple trick a don't know to get it running right, kann you please help me :-) Thank you in advance Georg EDDW ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Please upgrade to version: 0.9.8
Curtis L. Olson schrieb: It sounds like you aren't current with your flightgear source or executable? Could you still be running an older build of flightgear (or not fully up to date with your source code?) Curt. Did you upgrade your data from the cvs? Vassilii Hi Curt and Vassilii, after I got this error the first time (after downloading the latest CVS source and data) I did a full recompile with ./autogen.sh; configure --prefix=/fg-cvs; make; make install I worked around the problem by just changing the version file but this is not the solution. Trying now to make another CVS download and another recompile with deleting autom4te.cache (what has been a hint some time ago when I had other problems). If it does *not* work I will ask again! Thank you for your very prompt replies Georg ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Erik Hofman - your nice ships
Hi Erik, you have a nice pic on your webside with all your aircraft placed on two medium sized ships and there is also one sailboot and a firetruck: http://www.a1.nl/~ehofman/3dmodels/3dmodels.png If these are models *you* have created I would ask you whether you could place them on Jon Stockill's FlightGear Scenery Object Database http://fgfsdb.stockill.org/. It is my pure egoistic motive to ask you :-) as I am trying to populate my local FlightGear world a little but there might some other simmer interested, too. Thank you in advance Georg ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Erik Hofman - your nice ships
Erik Hofman schrieb: They are already included in the base package in FlightGear/data/Models/Geometry Erik Thank you, Erik .. I didn't notice that - but I'm glad to have them already! Regards Georg ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] New Release of Lake Constance custom scenery
Ralf Gerlich schrieb: Hello all, Ingrid has been working hard on the scenery data and we're proud to release a new version of the Lake Constance custom scenery. In fact it is not only a scenery of Lake Constance anymore. The nearest airport to Fuessen is Reutte (LOIR), a nice little grass airstrip with a challenging traffic pattern. Hi Ralf, thank you and all the Lake Constance Team Members for improving that wonderful piece of (scenery) cake for VFR flyers. I just managed due to lack of freetime to make a freeflight around LOIR (to the south and north) and could clearly see what you improved when passing the borders of the scenery in the south (barrier). Flying further it really looks very odd! Next weekend I'll take out some charts and do some more real flights. Regards Georg (EDDW) ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Winter Textures
Erik Hofman schrieb: Ah, I now see what you mean. Tis is a file permission problem. Martin !! First thank you Erik for that wonderful idea, I am very curious about the new winter clothes. Secondly, I could not download the first file(s) and either the winter.zip. *No* problem with downloading the P51 flight envelope charts of the same folder. Just as a feedback. Regards Georg ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Winter Textures
Erik Hofman schrieb: Hi, Sometimes it's nice to do something rather braindead after a day of hard work. This time it has resulted in a set of snow covered winter textures for FlightGear: Hi Erik, your braindead work resulted in an rather impressive feeling how it will look like here two months later - I just flew around the local area with your textures loaded. There are only two textures (sand and some sort of grass/light green) which have to be improved for winter use as sand might also cover some snow in regions where you have a real winter season. This is the first step towards seasonal textures. Now I will get back to the normal textures until winter season has come. Thank you Georg ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Never ending story: Building SimGear CVS under Cygwin
Ralf Gerlich schrieb: Hi, was this resolved somehow? Hi Ralf, the discussion caused some changes in the CVS files, the last change was due to the HUGE error (HUGE - HUGE_VAL). After that at least Ima and me had no problems compiling SimGear and FG cvs with *gcc 3.3.3* !!! David Luff gave some hints how to change some files to be able to compile FG with *gcc 3.4.4* and Ima Sudonim made a CVS diff already after realizing these changes and compiling all the stuff succesfully with gcc 3.4.4. It is now up to Erik Hofman to put these changes into the actual FG CVS. :-) Your chances are not bad to compile succesfully within the next time! Regards Georg ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] CVS compiling error
Hi Erik/Durk? Since your update of simple.cxx/hxx on the 18.10.05 the newest CVS version does not compile anymore :-( Error: simple.cxx: In member function `int FGGroundNetwork::findNearestNode(double, double)': simple.cxx:1331: error: `HUGE' undeclared (first use this function) simple.cxx:1331: error: (Each undeclared identifier is reported only once for each function it appears in.) make[2]: *** [simple.o] Fehler 1 make[1]: *** [all-recursive] Fehler 1 make: *** [all-recursive] Fehler 1 Any solution? Thank you Georg ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] CVS compiling error
Thank you David, now off to work, I'll try it this evening! Regards Georg David Luff schrieb: BTW, Georg, CVS SimGear should compile on Cygwin 3.4.4 now, and CVS FlightGear will probably compile on it if you add .. Then send the output of cvs diff -u from the FlightGear directory to Erik, and the 3.4.4 problem should be sorted :-) ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] CVS compiling error
David Luff schrieb: Cygwin doesn't have HUGE, so change HUGE to HUGE_VAL and -HUGE to -HUGE_VAL and I suspect this should compile. Changing HUGE to HUGE_VAL in simple.cxx solved the problem! Thank you, thank you :-) Have just made a testflight with the new FG version! I guess that we could do something in compiler.h along the lines of #ifdef __CYGWIN__ #define HUGE HUGE_VAL #define -HUGE -HUGE_VAL #endif I tried this *before* I did the huge-change. I put it between two other #ifdef .. (Microsoft and Borland, as far as I remember) but it caused some other strange errors. May be it was my fault to put it the wrong place or the wrong file (there are two compiler.h files in my Cygwin folder, I changed the one in the SimGear-0.3 .. folder. BTW, Georg, CVS SimGear should compile on Cygwin 3.4.4 now, and CVS FlightGear will probably compile on it if you add #ifdef HAVE_CONFIG_H # include config.h #endif as the first include for every source (cxx or cpp) file where you get the strange error message you reported a while ago. Then send the output of cvs diff -u from the FlightGear directory to Erik, and the 3.4.4 problem should be sorted :-) Ok, this has to be done when I have a little more time than this evening, but I will go for it within the next days and report so that you have some feedback. Thank you once again, David, your help saved the day for me! Regards Georg ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] build break with cygwin and gcc 3.4.4 in FlightGear approach.cxx
Hi Ima, when I tried to build a CVS version of FlightGear I had a *lot* of trouble and errors. Many developers of this list tried to help me but the break-through was an advice of *KEVIN JONES* not to use gcc 3.4.4 (what I had done until then). I followed his detailled instructions as he was just writing a tutorial/manual about building FlightGear 0.9.8/FlightGear CVS under Cygwin and all went fine. Absolute not problems with the build when using gcc 3.3.3 !!! Try it! Kevin will publish his tutorial/manual soon and I hope he is not angry about my answer. But he helped me so much with his advice at a time where I already had given up my trials because I would not show up here with another ask for help and all further hints did not work. So to repeat it, the key-advice for me was to go back to gcc 3.3.3! Thank you once again, Kevin Jones :-) And I hope it will help you too, Ima. Regards Georg Ima Sudonim schrieb: Hi, I am having a problem building flightgear on cygwin (cygwin updated last friday). I am using cvs from this morning. The GCC is cygming 3.4.4 Any ideas what's wrong or how to fix it? ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Microsoft artwork (!) in the 707 panel
Hans-Georg Wunder schrieb: ... - Do we have a place to store aircrafts with uncompliant aircrafts ??? Hi Hans-Georg, there is an AVSIM category in the file library named FlightGear with 4 sub-categories: - base distribution, - source code, -scenery and terrain and miscellaneous files. You could place anything there as it is your problem and risk and not related to FlightGear if there are copyright problems but I think this is not prudent and useful. And you would be pretty lonely there as only 1 (!) file is there, in the wrong category and with obvious copyright infringements as the 747 repaint is a commercial movie theme. Despite the bad place I will upload a tool to AVSIM as the license of the compiler is a non profit and personal one and I don't want any problems for FlightGear. In Germany it is pretty clear that I am allowed to give this *.exe to other people as long as I do not take money with it. But what's about other parts of the world? I don't know. Therefore AVSIM is a good place as long as there are any doubts to protect FlightGear. In your case, I would at least think about not giving your work away as aircraft designers of other flightsims very often copy even panels or sideviews out of other sims via screenshot and make it a basis of their own work. I can give a lot of samples where FLY! II panels and sideviews are taken for aircrafts of other sims (although FLY! isn't sold anymore the stuff is copyrighted!). Some designers don't think about these things or .. Therefore, if you can't get an answer from the author of the original panel, try to get other stuff. This is painful due to the lot of work you spent but on the long run it would be better for you and FlightGear to have a panel which could go into the basic 707 aircraft. Regards Georg EDDW ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] FlightGearTools Version 1.0 now available
FLIGHTGEARTOOLS Version 1.0 for Win32 FlightGearTools is the startup for a tool collection for FlightGear under Win32. The first page is related to MAP, ATLAS and FlightGear+Atlas on one PC. There might be some more pages for other stuff if there is interest from the user-side. My intention is to make things easier for those people who are not interested in the complicated stuff you need to make things working but want to use an alternative and promising flightsim. I put the complete package as a *.zip file today on my homepage before uploading it to the AVSIM filelibrary (FlightGear) within the next week. The reason for this is a) to have some feedback from users which might result in improving something before having it deposited at AVSIM where a change is not easy. USER: Please download the package, read the manual carefully, install FlightGearTools, install Map/Atlas, do some map work and contact me as soon as possible! b) to have some feedback of developers who might not want the package but can read the manual online and give some more hints. DEVELOPER: Please read the manual below. You might skip all stuff regarding FlightGearTools but have a look at those passages regarding ATLAS, MAP and FlightGear Wizard. If you have any idea what could be corrected or improved before the upload, please contact me as soon as possible (eMail or Atlas devel mailing list). Thank you for your cooperation. Here is the link to my homepage: http://home.arcor.de/vollnhals-bremen/FlightGear/HomeFGToolsM.htm I have to thank all those who supported me by answering my questions on the Atlas devel mailing list and with that supported the development of this tool and the manual. Thank you for your interest and (hopefully) feedback, good and bad :-) ) Regards Georg EDDW ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Never ending story: Building SimGear CVS under Cygwin
Erik Hofman schrieb: ... Fixed, what's next? :-) Erik Hi Erik, it was obviously not difficult for you to assume that I have to ask you again and again .. It is strange, it seems for me that these make-errors are due to errors in code - if so, why do *I* get the problems with make and not all other who compile the CVS stuff? Anyway, another request for help, please! NOW IT IS RenderTexter.cpp Sorry for the German warnings and error codes but I don't know how to switch them to English. If I remember right, you told me that you can read German :-) Otherwise I would try to translate, please tell me! RenderTexture.cpp:40: Warnung: ignoriere #pragma warning RenderTexture.cpp:66: Warnung: ignoriere #pragma comment RenderTexture.cpp: In member function `bool RenderTexture::BeginCapture(RenderTexture*)': RenderTexture.cpp:909: Warnung: Variable bContextReset wird nicht verwendet RenderTexture.cpp: In member function `void RenderTexture::_ParseModeString(const char*, std::vectorint, std::allocatorint , std::vectorint, std::allocatorint )': RenderTexture.cpp:1295: Fehler: WGL_SAMPLE_BUFFERS_ARB nicht deklariert (erste Verwendung dieser Funktion) RenderTexture.cpp:1295: Fehler: (Jeder nicht deklarierte Bezeichner wird nur einmal fur jede Funktion, in der er vorkommt, gemeldet.) RenderTexture.cpp:1297: Fehler: WGL_SAMPLES_ARB nicht deklariert (erste Verwendung dieser Funktion) ../../simgear/screen/RenderTexture.h: In constructor `RenderTexture::RenderTexture(int, int, bool, bool)': ../../simgear/screen/RenderTexture.h:334: Warnung: RenderTexture::_bDoubleBuffered wird initialisiert nach ../../simgear/screen/RenderTexture.h:333: Warnung: bool RenderTexture::_bFloat RenderTexture.cpp:2233: Warnung: wahrend es hier initialisiert wurde make[3]: *** [RenderTexture.o] Fehler 1 make[2]: *** [all-recursive] Fehler 1 make[1]: *** [all] Fehler 2 make: *** [all-recursive] Fehler 1 Regards Georg ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Never ending story: Building SimGear CVS under Cygwin
AJ MacLeod schrieb: ... Keep at it, you'll get there eventually! Cheers, AJ Hi AJ, thank you for your encouragement and explanations. I'll try to remember your hint for the time I'll get to FlightGear CVS. I am very motivated to get a working CVS FlightGear version and as far as anyone is willing to assist me on the way I won't give up now. Though I am reading a lot this config-make-stuff is quite another world for someone who coded a lot with Pascal/Delphi. I think I need pretty much time and practice until I will be grown up and can help myself, at least with normal procedures. Until then I have to ask a lot :-( Cheers Georg ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Never ending story: Building SimGear CVS under Cygwin
Vassilii Khachaturov schrieb: Sorry for the German warnings and error codes but I don't know how to switch them to English. If I remember right, you told me that you can read German :-) Otherwise I would try to translate, please tell me! [snip] You can do: $ LANG=C $ export LANG from your shell, and thereafter in the same shell prompt all the programs, including make and gcc, will speak English. V. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d Thank you, Vassilii! This helps very much to communicate in such an international community! The error message in English is: RenderTexture.cpp:40: warning: ignoring #pragma warning RenderTexture.cpp:66: warning: ignoring #pragma comment RenderTexture.cpp: In member function `bool RenderTexture::BeginCapture(RenderTexture*)': RenderTexture.cpp:909: warning: unused variable 'bContextReset' RenderTexture.cpp: In member function `void RenderTexture::_ParseModeString(const char*, std::vectorint, std::allocatorint , std::vectorint, std::allocatorint )': RenderTexture.cpp:1295: error: `WGL_SAMPLE_BUFFERS_ARB' undeclared (first use this function) RenderTexture.cpp:1295: error: (Each undeclared identifier is reported only once for each function it appears in.) RenderTexture.cpp:1297: error: `WGL_SAMPLES_ARB' undeclared (first use this function) ../../simgear/screen/RenderTexture.h: In constructor `RenderTexture::RenderTexture(int, int, bool, bool)': ../../simgear/screen/RenderTexture.h:334: warning: `RenderTexture::_bDoubleBuffered' will be initialized after ../../simgear/screen/RenderTexture.h:333: warning: `bool RenderTexture::_bFloat' RenderTexture.cpp:2233: warning: when initialized here make[3]: *** [RenderTexture.o] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all] Error 2 make: *** [all-recursive] Error 1 Regards Georg ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Never ending story: Building SimGear CVS under Cygwin
Hi Dave, I installed *all* Cygwin stuff after I got the first errors some time ago because I did not really know what I need. I reinstalled it all now before trying again Graphics (one of many entries, but this should it be) 2.2.0-1 169k freeglut: OpenSourced alternative to the OpenGL Utility Toolkit (GLUT) library but the error did not change afterwards. Regards Georg Are you sure you installed openGL support when you installed Cygwin? It's not installed by default, but is definately needed. I think it's hidden away in the graphics section. Cheers - Dave ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Never ending story: Building SimGear CVS under Cygwin
Hi Vivian, hi Erik, hi all! Vivian: Thank you very much, one step further to SimGear (and to a FlightGear CVS version !!!): 1. After you hint I could now activate cut and paste as it is not active by default. I made a little Google search and could solve it :-) 2. I put your bash_profile vars into [cygwin/home/Georg/.bash_profile] (seems to be my special user profile) and it works very well. The epheremis-error disappeared BUT THE NEXT PROBLEM OCCURED IMMEATELY: Erik: //THIS SEEMS TO BE QUITE A SIMILAR ERROR AS I HAD IT ALREADY //IN SWAP_TEST_CPP //AND ERIK HOFMANN FIXED IT (thank you Erik :-) ) //(swap_test.cpp:12: error: not valid conversion of unsigned int* to uint32_t* //swap_test.cpp:12: Fehler: Argument 1 von void sgEndianSwap(uint32_t*) wird initialisiert //(swap_test.cpp:12: error: argument 1 of void sgEndianSwap(uint32_t*) gets initialised) //HERE THE NEW ERRORS IN LOWLEVEL.CXX lowlevel.cxx: In function `void sgReadFloat(void*, float*)': lowlevel.cxx:62: Fehler: Ungultige Umformung von unsigned int* in uint32_t* lowlevel.cxx:62: Fehler: Argument 1 von void sgEndianSwap(uint32_t*) wird initialisiert lowlevel.cxx: In function `void sgWriteFloat(void*, float)': lowlevel.cxx:70: Fehler: Ungultige Umformung von unsigned int* in uint32_t* lowlevel.cxx:70: Fehler: Argument 1 von void sgEndianSwap(uint32_t*) wird initialisiert lowlevel.cxx: In function `void sgReadUInt(void*, unsigned int*)': lowlevel.cxx:106: Fehler: Ungultige Umformung von unsigned int* in uint32_t* lowlevel.cxx:106: Fehler: Argument 1 von void sgEndianSwap(uint32_t*) wird initialisiert lowlevel.cxx: In function `void sgWriteUInt(void*, unsigned int)': lowlevel.cxx:114: Fehler: Ungultige Umformung von unsigned int* in uint32_t* lowlevel.cxx:114: Fehler: Argument 1 von void sgEndianSwap(uint32_t*) wird initialisiert lowlevel.cxx: In function `void sgReadInt(void*, int*)': lowlevel.cxx:130: Fehler: Ungultige Umformung von unsigned int* in uint32_t* lowlevel.cxx:130: Fehler: Argument 1 von void sgEndianSwap(uint32_t*) wird initialisiert lowlevel.cxx: In function `void sgWriteInt(void*, int)': lowlevel.cxx:138: Fehler: Ungultige Umformung von unsigned int* in uint32_t* lowlevel.cxx:138: Fehler: Argument 1 von void sgEndianSwap(uint32_t*) wird initialisiert lowlevel.cxx: In function `void sgReadLong(void*, int32_t*)': lowlevel.cxx:152: Fehler: Ungultige Umformung von unsigned int* in uint32_t* lowlevel.cxx:152: Fehler: Argument 1 von void sgEndianSwap(uint32_t*) wird initialisiert lowlevel.cxx: In function `void sgWriteLong(void*, int32_t)': lowlevel.cxx:160: Fehler: Ungultige Umformung von unsigned int* in uint32_t* lowlevel.cxx:160: Fehler: Argument 1 von void sgEndianSwap(uint32_t*) wird initialisiert lowlevel.cxx: In function `void sgReadFloat(void*, unsigned int, float*)': lowlevel.cxx:247: Fehler: Ungultige Umformung von unsigned int* in uint32_t* lowlevel.cxx:247: Fehler: Argument 1 von void sgEndianSwap(uint32_t*) wird initialisiert lowlevel.cxx: In function `void sgWriteFloat(void*, unsigned int, const float*)': lowlevel.cxx:260: Fehler: Ungultige Umformung von unsigned int* in uint32_t* lowlevel.cxx:260: Fehler: Argument 1 von void sgEndianSwap(uint32_t*) wird initialisiert lowlevel.cxx: In function `void sgReadUInt(void*, unsigned int, unsigned int*)': lowlevel.cxx:397: Fehler: Ungultige Umformung von unsigned int* in uint32_t* lowlevel.cxx:397: Fehler: Argument 1 von void sgEndianSwap(uint32_t*) wird initialisiert lowlevel.cxx: In function `void sgWriteUInt(void*, unsigned int, const unsigned int*)': lowlevel.cxx:410: Fehler: Ungultige Umformung von unsigned int* in uint32_t* lowlevel.cxx:410: Fehler: Argument 1 von void sgEndianSwap(uint32_t*) wird initialisiert lowlevel.cxx: In function `void sgReadInt(void*, unsigned int, int*)': lowlevel.cxx:432: Fehler: Ungultige Umformung von unsigned int* in uint32_t* lowlevel.cxx:432: Fehler: Argument 1 von void sgEndianSwap(uint32_t*) wird initialisiert lowlevel.cxx: In function `void sgWriteInt(void*, unsigned int, const int*)': lowlevel.cxx:445: Fehler: Ungultige Umformung von unsigned int* in uint32_t* lowlevel.cxx:445: Fehler: Argument 1 von void sgEndianSwap(uint32_t*) wird initialisiert make[3]: *** [lowlevel.o] Fehler 1 make[2]: *** [all-recursive] Fehler 1 make[1]: *** [all] Fehler 2 make: *** [all-recursive] Fehler 1 Thank you in advance for your help! Regards Georg ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Never ending story: Building SimGear CVS underCygwin
Hi Vivian, I am very sorry Vivian but due to my bad English there is a misunderstanding: It was just the same error error: not valid conversion of unsigned int* to uint32_t* which once occured in swap_test (was fixed some time ago) and now occures in *lowlevel.cxx*. I actually always delete the whole source folder of SimGear, get the *whole* actual stuff via Cygwin CVS and do it all again at least twice until I ask for help - just to be sure that there is no avoidable error from my side which could cause you to have some work, that would not be fair :-) So, the *new* problem is in *lowlevel.cxx* but with the known problem not valid conversion of unsigned int* to uint32_t*. Thank you for your answer. Regards Georg Vivian Meazza schrieb: The problem in swap_test is corrected in the latest cvs - make sure that you are up to date. Do cvs -z3 update -P -A -d -C In your simgear/source directory Then try again. V. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] RE: Feedback: Building SimGear CVS under Cygwin
Hi all, further help is needed, please! /1. I have experienced exactly the same problem using WinCVS. The solution is /drastic - you have to delete the source directory created by WinCVS and /start over with a clean checkout using the command line cvs provided as part /of Cygwin. Then ./autogen, ./configure etc. /.. /Vivian Thank you Vivian, this helped me to solve the problem but I got another one :-( Might be anyone had the same problem already solved? What I did until now: 1. installed plib-1.8.4 without problems (./configure; make; make install) 2. built SimGear CVS with Cygwin cvs command after deleting all old stuff 3. unpacked and built zlib-1.1.4 (tar xvfz ..; ./configure; make; make install) 4. SimGear/source ./autogen.sh ./configure make - ERROR! ... ... swap_test.cpp: In function 'int main()': swap_test.cpp:12: Fehler: Ungueltige Umformung von unsigned int* in uint32_t* (swap_test.cpp:12: error: not valid conversion of unsigned int* to uint32_t* swap_test.cpp:12: Fehler: Argument 1 von void sgEndianSwap(uint32_t*) wird initialisiert (swap_test.cpp:12: error: argument 1 of void sgEndianSwap(uint32_t*) gets initialised) make[3]: *** [swap_test.o] Fehler 1 (... error 1) make[2]: *** [all-recursive] Fehler 1 (... error 1) make[1]: *** [all] Fehler 2 (... error 2) make: *** [all-recursive] Fehler 1 (... error 1) ANY IDEAS? Thank you very much in advance Georg EDDW ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Another error: Building SimGear CVS under Cygwin
Hi Erik and Vivian, thank you for your quick replies. I am sorry to show up here again with another error message .. but one solved, the next came :-/ Erik: /Anyhow, I have fixed this in CVS now Georg, thanks for reporting this. /Erik This is solved, thank you! but this is the (very long, sorry) error output of make: (BTW: getting this errors is very educational. I had to read nearly an hour until I found out how to redirect the *error* messages under Cygwin bash with 2. But the bash and me get more and more friends :-) ) (not translated, I only changed the German expressions Zeichen = char Fehler = error) In file included from /usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/vector:72, from ../../simgear/math/sg_types.hxx:40, from ../../simgear/misc/sg_path.hxx:36, from ../../simgear/ephemeris/stardata.hxx:31, from ephemeris.hxx:45, from ephemeris.cxx:28: /usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/bits/stl_bvector.h: In member function `void std::vectorbool, _Alloc::_M_insert_range(std::_Bit_iterator, _ForwardIterator, _ForwardIterator, std::forward_iterator_tag)': /usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/bits/stl_bvector.h:522: error: expected unqualified-id vor (-char /usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/bits/stl_bvector.h: In member function `void std::vectorbool, _Alloc::_M_fill_insert(std::_Bit_iterator, size_t, bool)': /usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/bits/stl_bvector.h:823: error: expected unqualified-id vor (-char In file included from /usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/vector:75, from ../../simgear/math/sg_types.hxx:40, from ../../simgear/misc/sg_path.hxx:36, from ../../simgear/ephemeris/stardata.hxx:31, from ephemeris.hxx:45, from ephemeris.cxx:28: /usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/bits/vector.tcc: In member function `void std::vector_Tp, _Alloc::_M_fill_insert(__gnu_cxx::__normal_iteratortypename _Alloc::pointer, std::vector_Tp, _Alloc , size_t, const _Tp)': /usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/bits/vector.tcc:307: error: expected unqualified-id vor (-char /usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/bits/vector.tcc: In member function `void std::vector_Tp, _Alloc::_M_range_insert(__gnu_cxx::__normal_iteratortypename _Alloc::pointer, std::vector_Tp, _Alloc , _ForwardIterator, _ForwardIterator, std::forward_iterator_tag)': /usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/bits/vector.tcc:384: error: expected unqualified-id vor (-char make[3]: *** [ephemeris.o] error 1 make[2]: *** [all-recursive] error 1 make[1]: *** [all] error 2 make: *** [all-recursive] error 1 Is this a gcc-error or error in ephemeris.* ??? Vivian: /If you are using Norman Vines pre-prepared OpenAL stuff there is a further /.. /Vivian If I *only* get to the FlightGear stuff then I'll remember your hint. Erik and Vivian, thank you once again! Georg ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Another error: Building SimGear CVS under Cygwin
Hi Fred, /Does it help to put #include vector *before* #include simgear/compiler.h in /math/sg_types.hxx /-Fred I CHANGED THE POSITION OF #include vector: ... #include vector #include simgear/compiler.h #include STL_STRING //#include vector (original position) #include simgear/math/point3d.hxx ... but the result was the same (error as described) Regards Georg ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] help: making SimGear CVS under Cygwin
Building SimGear CVS under Cygwin Hi, thanks to the help of AJ I solved the OpenAL problem and though the files of Norman do not work with older versions the problems are solved with the CVS version of SimGear and Normans precompiled files (thank you Norman, AJ) Now there is another problem I cannot solve myself at my present stage of knowledge (make files): I installed FlightGearCVS, OpenAL files and I installed the SimGear CVS files under /usr/local/source/SimGearCVS First I made zlib: /usr/local/source/SimGearCVS/src-libs/zlib-1.1.4 ./configure make make: Fur das Ziel all ist nichts zu tun. (make: for the target all is nothing to do make install .. runs through Then I went back to /usr/local/source/SimGearCVS ./autogen.sh Running aclocal /usr/share/aclocal/libsmi.m4:8: warning: underquoted definition of AM_PATH_LIBSMI run info '(automake)Extending aclocal' or see http://... /usr/share/aclocal/cppunit.m4:4: warning: underquoted definition of AM_PATH_CPPUNIT Running autoheader Running automake --add-missing Running autoconf Now you are ready to run './configure' next step: ./configure ... runs through many points without remarkable observations ... but then, at the end: configure: creating ./config.status config.status: creating \ .infig.status: error: cannot find input file: \ next step make make: *** Keine Targets angegeben und keine make-Steuerdatei gefunden. Schluss (make:*** No targets found and no makeconfig(???)file found. End) Please, can someone give a hint what to do, what did I do wrong? I would like to be able to build FlightGear CVS versions as there are some other Win32 users too who would like to do some user-development (texturing, aircraft-work) with an actual FG version. Thank you very much in advance Georg EDDW ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] SimGear and OpenAL files/Cygwin
Hi AJ, thank you for your prompt reply, therefore this as a feedback: I tested it with Normans precompiled version and the (older) stuff I need for building FG 0.9.8 but still got the same error messages when typing ./configure from SimGear-0.3.8. Just downloading all the actual CVS stuff for SimGear and FlightGear I will have another try with the more actual files, hopefully ... :-/ If I am not lucky I will ask again as I started to work seriously with FlightGear this August and though spending a lot of time reading all docs and testing things I am a bloody beginner! Once again, thank you for your help and time Regards Georg EDDW ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] SimGear and OpenAL files/Cygwin
Hi, after many hours trying to solve the problem I give up and ask for help: Problem: When building SimGear under Cygwin OpenAL files are not found. The Readme.OpenAL and other docs are not helpful for two questions: 1. What do I need for Cygwin? Is the OpenAL11BetaSDK sufficient (content folders: dll/Docs/Include/libs/Samples)? Or do I need to install the whole CVS stuff with a lot of folders for different OS? 2. Where is the right place to put the needed OpenAL stuff into Cygwin? (ie. where to put libs, Include or other folder?) I tried a lot of places (trial and error) but I always got the message ... Win32 specific hacks... Will link apps with -lglu32 -lopengl32 -luser32 -lgid32 -lwinmm checking for library containing alGenBuffers... no checking for library containing alutInit... no You *must* have the openal library installed on your system to build SimGear! ... I would be very glad if someone could help me. Building FlightGear 0.9.8 from source would be the first step to building it from CVS. Thank you very much in advance Georg EDDW ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: DHC-6 progress
Hi Thorben, as I like this little island-hopper aircraft very much I immediately flew it in the sim. Very nice, indeed. As it is a work in progress it would be fine if you could have a look at the size of the wheels, especially the front-wheel, and the related steering structure. The model would look a lot more realistic if you could make it much smaller as this is a very important first look element of the original aircraft. Anyway, I thank you very much for developing this wonderful sim-aircraft. Regards Georg EDDW ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] RE...RE: Turbine, Engine (Concorde, Hunter, and Citation Information Needed)
Hi Andi, Message: 2 Date: Tue, 06 Sep 2005 11:13:49 -0700 From: Andy Ross [EMAIL PROTECTED] Subject: Re: [Flightgear-devel] Re: [Flightgear-users] RE: Turbine Engine (Concorde, Hunter, and Citation Information Needed) Heh, fair enough. OK, how about this: if someone can get me reasonable data on a real turbine, I'll do a model for it and check it in such that other engines can use the same interface, even if the numbers are wrong. More than I could expect :-) It doesn't need to be really involved. Basically, what I'd need is stuff like: Nr 1 and 2 + What the RPM curve vs. time looks like the as you hold the starter button down. + The temperature curve vs. time, showing the points where control inputs were made. Nr 3 and 4 Ok, this is the easiest point. I'll have a look into the handbooks within the next days and mail all stuff to you which may be interesting. + The handbook procedures that tell me which numbers are important, and which ones I can fake. + The handbook descriptions of what the failure modes are, how they are caused, and (roughly) what the effects are. I don't think anyone cares if we get this exactly right -- it doesn't matter whether the over-temp condition is exactly the same temperature as you would see on a real engine, so long as the temperature is pointing at the red area of the gauge. This was also my first idea when I read Nr 1 and 2 as all the parallel processes (instrument readings) can be analyzed afterwards with all the time you need for it. This will be done by me with some delay as I first have to get my old and longtime unsed Camcorder working , this means getting a new NiCd storage batterie for it as the old one has only reduced capacity for some minutes. Maybe just a video of the panel during a successful startup would be sufficient. Andy We should notice that these parameters are only valid for a special type of 2-shaft-engines (turbines) but it might be a start and better then nothing! :-) Please give me some time (due to real-life workload). Cheers Georg ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: [Flightgear-users] RE: Turbine Engine (Concorde, Hunter, and Citation Information Needed)
Curt, well argued - our real-world pilots handle these engine startup and shutdown procedures very seriously in helicopters without FADEC, ie. Eurocopter BO105, BK117. Getting the temperatures too high (hot start, ITT++) is a financial desaster. And what not might be generally known - the engines are even cooled by airflow after shutdown for a short time with the electric starter. And combined with that you have to check other important things, ie. batterie-power (if you have not got an external energy supply) for sufficient electric starter function when running the free turbine part up to get enough airflow *before* ignition, otherwise .. :-( Although all these things are no problem with modern turbines with FADEC (ie Eurocopter EC135) it might be a good idea to have these features implemented (together with a random failure generating system) in some future version of FlightGear, all these little things increase reality feeling. Regards Georg ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: Custom Scenery for Lake Constance
First, thank you Ralf for improving your work. I could now fly the VFR routes of the Visual Operation Chart EDNY from IVAO-DE and get clear through the mentioned reporting points. I never before flew such precise procedures just by looking out of the sim window. But when I read your mail I know that it will be a long long way for me to go to get a similar scenery for my local area as there is a lot to learn. Let us know what you think. We're open for (constructive) criticism and suggestions. 1. As all different streets are displayed in the same way it is a luck that you cannot get the smaller streets into the scenery. Yet it is difficult to follow some bigger streets when you come to a big street crossing and have a web of streets all looking the same. It would be nice if TerraGear could render different street-types with different colours (or even better, textures). 2. Is TerraGear able to render railway-lines with a darker colour, ie. dark brown? This would be more how you see older railway-lines from air, at least in Northern Germany. 3. Did you change the size of the streets? They appear too broad, I tested it with a Cessna and landed, it seems they have the width of 3 x Cessna wingspan :-) Regards Georg EDDW ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: Custom Scenery for Lake Constance
Hi Ralf, I am a pure FlightGear user (since very early versions) and scanning the developers mailing list regularly. After your announcement I first flew the scenery from EDNY two days ago and now downloaded, installed your improvements and did several VFR flights with my ICAO chart and a more detailled street chart. Congrats! This is really a big step forward to increase the possibility of realistic VFR flying (next version with modelled NOVEMBER and ECHO :-) ?). I did some improvements of my local scenery the last 2 months with FlightGear Scenery Designer (which works pretty well) but to get instructions how to do it more economicly with GISS tools would be very nice!!! As TerraGear only works under LINUX I also did a Fedora Linux install this morning and will be sweating the next weeks to get familiar with your OS as development for FG seems to be easier with the right basics (there are also other reasons to do some more work under LINUX now :-) ). As I did more then 2/3 of my simming time with FlightGear the last months I already decided to improve the local scenery which is pretty usable but too wrong in detail. With your help (tutorial) and after getting LINUX and TerraGear to a point where I can use it I would like to do so and (naturally) share my work with all interested when there will be a place to put it. Thank you once again for sharing your work with us (vielen Dank, Ralf!) Best regards Georg EDDW Bremen ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] MB-339 PAN aircraft
Just as a feedback as projects like this might help to make FlightGear more popular: http://forums.avsim.net/dcboard.php?az=show_topicforum=127topic_id=28692mesg_id=28692page= Regards Georg ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Some other BO105 pics - Melchior Franz
Hi Melchior Franz, http://www.nord-com.net/vollnhals-bremen/BO105HH/BO105Pol.htm .. Please give me a few days to download them from my Linux workstation.) I let the pics there until you have had a look at them/downloaded them. Would be nice if you give me two words at [EMAIL PROTECTED] so that I can delete the page. These are the outside pics, just an addition http://www.nord-com.net/vollnhals-bremen/BO105PolOuts/PolHHOuts.htm Regards Georg HeliFLYer EDDW BTW: If it is EASY to describe where I can find the source code for the special flightmodel for helos in FlightGear it would be nice if you could give me a hint, otherwise forget about it. Thank you very much! --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.771 / Virus Database: 518 - Release Date: 28.09.2004 ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Satellite textures (Landsat/D-Sat)
Hi Boris, though the price of 100 EUR/$ might be rather fair one should look for other limitations which are not obvious. I don't know the latest D-Sat version but in D-Sat 5 you have that export function for private use for MS-Flightsim (which I used to get the pics out, combined them and get the lat-lon-data for the corners). That sounds really good, but although it is limited for private use, there are a lot of hidden limitations - the area size for export with highest resolution is limited (you have to find your own way) - the given lat-lon coordinates of the corners are rather unprecise (you have to correct. This makes it impossible to adapt some of those BIG pictures automized (at least for me. I wasted a lot of hours searching bugs in my programm until I found out where the bug is. You have to do it manually, very time-consuming.) - the picture quality of the exported pics is limited (you notice if you export with highest resolution and compare with the screen-output of D-Sat5) - outside the big cities you have satellite-pics with limited resolution and rather bad colours (might be changed with Ver 6) - I am not sure they use WSG84 projection for output (bigger areas: if you match one runway at one corner you loose exact position of a runway at the other corner). - This is for D-Sat5, don't know D-Sat6 - For the prof version you should ask whether the size of the area/pics one can use commercially is limited by license. After all, 1 1/2 year ago, when my work started, I was very enthusiastic about satellite textures. My opinion has changed. Until you get a very high resolution neatless for very big areas it is unsatisfying. The better alternatives could be using low-res satellite pics (as Landsat7) to derive information from it: a very precise water-mask (the way FLY! CAN display water areas independent from textures, if you make a mask), land-use (the way MSFS Flightsim IS ABLE to display CUSTOM(!!!) information about displaying irregular shaped landuse from big downto very small areas by using a lot of different high-res standard textures, if you look at AVSIM you'll find out that they use Landsat7 pics that way), part of the basic FlightGear dataset (streets, railways ..) and important obstacles and objects (USER created). This is just a fictional idea for FlightGear but the way how existing flight-sims do it (not bad). And it is NOT an argument against Manuel's work and suggestions - let's see how the result is, another grafic engine with SRTM is not bad. And I'm too go on working with Landsat as I cannot change the grafic engine of FLY!II which is rather obsolete und without further development - FlightGear has a better chance! Regards Georg HeliFLYer EDDW --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.756 / Virus Database: 506 - Release Date: 08.09.2004 ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] BK117: turbine starting procedures, correction
Hi all, after discussing turbine starting procedures with a real-life BK117 pilot I want to give you some corrections and additions which are very interesting after my opinion. I know that Melchior Franz has his own sources but I address all those others who read my last statement and might be misinformed: Some short technical remarks Modern helos are equipped with a two shaft turbine with air compressing part (gas producer, N1) and free-running working part(N2). These two parts are only connected by the airflow through the turbine, there is no gear or any mechanical connection between. EVERY turbine is connected through a free wheel with the main gear (defective turbine, autorotation, ..). The rotor drives main gear and connected tailrotor and hydraulic pumps(!!!, stearing) when autorotating. Rotor brake: BK117 (BO105???): is placed on the tailrotor drive near the main-gear. It is NOT constructed like a car emengency brake (loosen-fasten) but has a hydraulic system with a valve which reduces pressure after some time so there is not permanent fastening of the rotor system. So with the BK117 there is no real danger from the rotor brake when staring the engines as none would apply pressure on the rotorbrake an THEN start the engine. Starting procedure of turbines: [Electrical supply is on, some BK117 have different systems, ie. main power switch, batt switch, shed bus switch] Fuel pumps on (BK117: only as booster pumps until turbines are running, turbines drive own mechanical fuel pumps. BO105: requieres running fuel pumps all the time due to fuel tank construction. Otherwise lacking supply causes abrupt shutdown of turbines if alarms are not recognized - real life proofen, caused autorotation into water and lost of helo/not lifes) BK117: throttle is on 0 position. You use the electrical starter to get the gas producer (air compressing part, N1=Ng) to 10% N1 rpm, then move throttle ca. half way to idle position - trigger for automatic ignition (BK117, BO105 requires manual ignition). Hold starter button, when 25% N1 is reached N2 must increase and rotor movement visible - otherwise failure, stop starting procedure. TOT (T4) can be modified during the turbine running-up procedure by adapting throttle position. Check maximum TOT (turbine outlet temperature, 650 C deg BK117, BO105 might be a little hotter), don't exceed, stop starting procedure. Release starter button when 40% N1 is reached. Move throttle full to idle position, turbine rpm increases automatically to 68% N1 (idle). N2 and rotor rpm follow to normal rpm When turbine rpm has stabilized set generator on (identical starter and generator engine, same switch with pos [starter - none - generator]). If no extern power supply wait until batterie recharge current decreases from ca. 150 to 100 Amps Do same procedure for engine 2. Before flight: Slowly turn throttles to flight position - for each engine Georg HeliFLYer EDDW --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.756 / Virus Database: 506 - Release Date: 08.09.2004 ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Landsat 7 textures - Oliver C.
Hi Oliver, One question, how did you do the color correction when merging the three visual channels (1 blue,2 green and 3 red) of the Landsat data together to get one real looking RGB truecolor picture? I allways get false color pictures. Do you know any tools that do the color correction automatically? Sorry, I still do it manually. I tried some grafic tools with automatic white balance functions for photographic color correction (PaintShop Pro Ver 8). Sometimes the results were good, sometimes bad. I had so much trouble solving other problems, so some sort of automatic colour correction is still on my list but will not be done tomorrow. Georg HeliFLYer EDDW --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.756 / Virus Database: 506 - Release Date: 08.09.2004 ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Landsat 7 textures, Manuel Massing
Hi Manuel, this is great, thank you for explaining your idea! What I mean with procedural texture or geometry. is the creation of detail textures and the addition of geometric models at runtime (on the fly!). This could be e.g. done based on known landuse (possibly by letting a classifier analyze the landsat textures at scenery generation time or runtime), and can be easily integrated with the engine LOD management (so that detail is only generated when necessary). Additionally, as you suggest, it would be great to model roads, rivers, etc. derived from vector datasets. Our posts crossed and you might have seen that we use other words but mean the same. This could really be a big step forward IF a very easy way could be implemented for amateurs like me to add own regional textures, landuse-structures and objects WITHOUT big problems. Just put the textures/geometrical objects and textures/landuse references into a subfolder of a specified folder, FlightGear will read the information at run-up-time and display them with priority to the generic scenery: FLY!II would handle it like that (simplified sample): (AOSTA.SCF in folder [Scenery], AostaEnd.POD in folder [Scenery]. The *.POD-file is the container for all textures you need) (AOSTA.SCF:) bgno BEGIN SCENERY FILE name scenery set name AostaEnd call coverage area lower left 45 30 2.2 N 6 56 20.5 E caur coverage area upper right 45 54 52.0 N 7 51 5.7 E ldll load lower left 44 30 2.2 N 5 56 20.5 E ldur load upper right 46 54 52.0 N 8 51 5.7 E file pod file AostaEnd.POD endo END SCENERY FILE === OR to place an object (which normally is done by an editor anytime you are flying, but you can write or edit the code yourself, still more complicated, so everybody uses the editor or tools) (This is part of a big file for all scenery objects of a specified region) wobj world object type mobj bgno == BEGIN OBJECT == geop geo position lat lon elev 53 04'53.8973N 8 46'59.5820E 13.825202786872708 type object type mobj flag gestalt flags 33077 detl detail level 3 id object id (unique) mobj7 kmmd model manager bgno == BEGIN OBJECT == modl model entry norm YACHT-1.BIN endo == END OBJECT == iang inertial angular position 0.00,4.906706,0.00 endo == END OBJECT == wobj world object type This just as a sample how things could be handled. Anyway, I love your ideas but I am no FlightGear developer. So I hope that they support your work! Thanks a lot for your engagement. Regards Georg HeliFLYer EDDW --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.756 / Virus Database: 506 - Release Date: 08.09.2004 ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] next release - ac that don't work
Hi all, I have to correct a typo of my last message: watching the temperature of the working part (N4).. It should read watching the temperature of the working part (T4). I described in a short way the procedure similar to the BK117. If you want to get more and better information then go to http://www.f2fdesign.com/ (Download section, at the bottom of the page) and get DauphinFM.zip Size: 1.91 MB Description: Flight Manual for Eurocopter AS-365N2 Dauphin II for Fly! II. Read pages (13)-15-16-(17). You will get the very best real-life infos as one of the designers is my Norwegian FLY!-friend Jan M. Herigstad who workes as a helicopter mechanic for Dauphin helicopters in Stavanger/Norway at CHC. He knows what he is talking about. These procedures are a little different to BO105 or BK117 but you will understand more the way a turbine without FADEC is started. If you have a very modern helo like EC 135 just press a button, all is done by electronic. If there are any further questions, please contact me. I will answer with a little delay. Thanks HeliFLYer Georg (EDDW) --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.756 / Virus Database: 506 - Release Date: 08.09.2004 ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] BO105 starting procedure - Melchior Franz
Hi Melchior (and all other helo interested), my knowledge gaps are significant as I was more interested in aerodynamics and flying procedures until now. But I have the chance to discuss some of these questions with a helo pilot (hopefully with BO105 typerating and experience) the next weekend as I am on helo-rescue duty next Saturday/Sunday. Shall I report via eMail to you and protect all the other readers from this very special stuff? Is there any other question you are interested in that I should ask? OK, that explains Martin's and my experience. The AB204 (where I observed engines first, then rotor) is *really* old. (We used it until a few years ago, nevertheless.) Although the Bo105 isn't exactly a modern helicopter, either, I'll now go for the no-clutch version. After my opinion the AB204 = Bell 204 = (military) UH 1D has no clutch (.. one question to ask!). Until 1997 we had a Bell 212 at our base and a UH 1D as a backup. My flightsim interest grew later, so I don't remember exactly, but I think the starting procedure was similar. There is always a delay between the running-up turbine (gas producer, N1) and the rotor movement. As the rotor is coupled with the free-running (secondary) working part of the turbine(N2), there must be a certain pressure (depending on N1) to force movement (air is compressible) and therefore a delay until the rotor movement is visible. That's the way I understand it (.. second question to ask). Once I implement the rotor brake, I'll need to know what I had to expect model in this case. (High temperature in both turbines? Unpleasant noise? Warining light/sound? :-) (.. third question to ask) But I am not sure any of our pilots has real-life experience with this! :-)) I think Martin already gave the answer. Prepare for being abused as a beta tester! ;-) No abuse, no problem, just fun! But be aware - and I tell this very seriously - that my knowledge and skills are very limited. I have no problem to ask the profs - until I have to ride home sitting on the skid. Regards HeliFLYer Georg (EDDW) --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.756 / Virus Database: 506 - Release Date: 08.09.2004 ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] next release - ac that don't work
Some words to the starting procedures with a modern turbine helo as BO105, due to my bad english knowledge I will repeat some technical expressions in German, Melchior Franz will understand it: Modern helos are equipped with a two shaft turbine (Doppelwellenturbine) with air compressing part (Verdichterturbine)(N1) and working part (Arbeitsturbine) (N2). These two parts are only connected by the airflow through the turbine, there is no gear or any mechanical connection between. You use the electrical starter to get the air compressing part up to 10% N1 (Mit dem Anlasser die Kompressorturbine auf 10% Normdrehzahl N1 hochfahren), then you start ignition and carefully set power (10% ..) watching the temperature of the working part (N4). If temperature gets too high you have either to reduce the throttle setting or in the worst case break the start. When the compressor part gets faster (N1 rises) you have to watch the working part (N2) also to turn, otherwise there is a failure and you have to stop turbine-start. (Ein Hochfahren des Kompressorteils bedingt ein Folgen der Arbeitsturbine, andernfalls ist ein Fehler vorhanden. Bereits die Betätigung des Anlassers der Turbine kann in einigen Fällen ein Folgen der Arbeitsturbine verursachen mit leichter Rotordrehung) Normally (modern helos) there is no clutch between working part of turbine and main-gear. So a working turbine will result in a turning rotor disk. The higher N1, the better following of N2. Exception as far as known: Alouette and some other rather older French helos (turbine and clutch). Piston helos do have centrifugal clutches (Fliehkraftkupplung), but I have no experience with this type of copters, just know it from a book. If you lock your rotor brake when starting a turbine you will burn the blades of the working turbine part - good luck! If you have reached ca. 40% N1 you may add the generator to reload the battery for the start of engine 2 (in case you have no extern energy supply). Wait until primary energy flow to the battery (up to 150 Amps) will decrease for the generator hasn't the power to load the battery AND to start engine 2. Rotor RPM should be in the green. Make the same procedure for engine 2. Before take off you have to go from idle to 100% throttle. Stable turbine RPM will be electronically controlled. Only Piston helos require adjustment of throttle - but ie. Robinson has developed some sort of electronic manager for the R22/44. (Robinson hat für seine Kolben-Hubschrauber ein elektronisches Regelgerät für das Gasnachsteuern entwickelt, welches unter normalen Betriebsbedingungen sehr gut arbeitet). If your Rotor is faster then the turbine (naturally gear between) you have a free wheel (Freilauf), also needed for autorotation. Hope that helped a little. Regards Georg (HeliFLYer, EDDW) --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.756 / Virus Database: 506 - Release Date: 08.09.2004 ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
