Re: [Flightgear-devel] Hires runway effect
Thorsten Sent: 07 June 2013 12:40 To: FlightGear developers discussions Subject: [Flightgear-devel] Hires runway effect After a fresh pull and recompile today (I've not had much time for FG the last weeks...) I've noticed that the hires runway effect of ALS appears to have been partially broken by something - I now see a checkerboard pattern when I look at runways and taxiways which hasn't been there before. Is anyone else observing this? Since I've not done anything for the last weeks, something other than the shader must have caused this (coordinate mapping? altered normal?). Can anyone perhaps shed light on this? Unfortunately I still don't have much time right now for a long investigation :-( I can't see a problem here with today's pull of fg/sg/fgdata. The tree wind effect is nice. Vivian -- How ServiceNow helps IT people transform IT departments: 1. A cloud service to automate IT design, transition and operations 2. Dashboards that offer high-level views of enterprise services 3. A single system of record for all IT processes http://p.sf.net/sfu/servicenow-d2d-j ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Base fgdata
On 8 Jun 2013, at 02:28, Saikrishna Arcot saiarcot...@gmail.com wrote: Is it just me, or has the base fgdata package size increased since 2.10.0? Do you mean some substantial change in size? That might indicate a bug in the rsync rule which generates the base package. Some comparison of contents would be useful. The one thing I'm aware of is the addition of poi.dat.gz, which is a few megabytes I think. Regards, James -- How ServiceNow helps IT people transform IT departments: 1. A cloud service to automate IT design, transition and operations 2. Dashboards that offer high-level views of enterprise services 3. A single system of record for all IT processes http://p.sf.net/sfu/servicenow-d2d-j ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Base fgdata
The primary increase seems to be in Textures.high/Terrain. In 2.10.0, the size of the folder was 181 MB, while in the current git version, the size of the folder is 300 MB. Some of the increases seem to be png versions of dds texture files and to autumn versions of the textures. The next big increase seems to be in Textures.high/Terrain.winter, with folder sizes of 36 MB vs 51.6 MB. The poi.dat.gz is 11 MB. The Models folder seems to have actually decreased in size by 7 MB (234 MB vs 227 MB). On Sat 08 Jun 2013 04:37:03 AM CDT, James Turner wrote: On 8 Jun 2013, at 02:28, Saikrishna Arcot saiarcot...@gmail.com wrote: Is it just me, or has the base fgdata package size increased since 2.10.0? Do you mean some substantial change in size? That might indicate a bug in the rsync rule which generates the base package. Some comparison of contents would be useful. The one thing I'm aware of is the addition of poi.dat.gz, which is a few megabytes I think. Regards, James -- How ServiceNow helps IT people transform IT departments: 1. A cloud service to automate IT design, transition and operations 2. Dashboards that offer high-level views of enterprise services 3. A single system of record for all IT processes http://p.sf.net/sfu/servicenow-d2d-j ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Saikrishna Arcot -- How ServiceNow helps IT people transform IT departments: 1. A cloud service to automate IT design, transition and operations 2. Dashboards that offer high-level views of enterprise services 3. A single system of record for all IT processes http://p.sf.net/sfu/servicenow-d2d-j ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear voice communication
Hi all, With help from Geoff and James I've successfully added FGCom feature to FlightGear. Therefore I'm facing to 2 limitations from IAXClient library. 1) Simultaneous calls IAXClient library has not be designed to handle simultaneous calls. So it's not possible to listen COM1 and COM2 at same time, or COM1 and NAV2... For NAV12 it's not dramatic because fgcom-server (Asterisk) is simply sending morse code, since FlightGear is already providing this feature we just need to admit taht FGCom feature is only used for COM but not NAV. For COM12 it's more problematic since we should be able to listen to COM12 at same time (at least for aircraft equipped by 2 COM stations) The question is: can we agree that FGCom is operating _only_ on COM1 ? If someone want to expand IAXClient library in order to manage simultaneous calls, please raise your hand ! 2) OpenAL context In order to avoid context conflict I've merged FGCom sound into global FG sound system. This mean that we can choose to redirect FGCom sound into our headphone and FG sound into our speaker. The question is: can we agree that FGCom sound is played on the same output than FG sound ? Again, if someone is ready to investigate OpenAL deeply, raise your hand. Let me know if these 2 limitations are not a sine qua non condition for FGCom integration into FG. IMO, I think that FGCom integration - even if it's limited to COM1 - is already a good step forward. I've also added record feature to FGCom (only for standalone binary) which make possible to record an ATIS message. That way, pilots can listen ATIS message from ATC like it's done in real life (at least in France, but I'm now aware that UK ATIS are TTS messages) If this feature is accepted, we need to disable ATIS messages generated by FG (only if FGCom is enabled) For information, on server side it works as follow : - If a record is present = play the record - Else = play a TTS (via Festival in Asterisk) containing current metar For those you want to test the current state, you need to compile FG from https://gitorious.org/~f-jjth/fg/f-jjths-flightgear/ = topics/fgcom branch Then run FG like : fgfs --enable-fgcom --airport=LFMV --com1=125.35 For now, my personal Asterisk server is used (clemaez.dyndns.org) and he is designed for testing only. I'm ready to manage an Asterisk server, also a new subdomain name could be welcome (e.g fgcom.flightgear.org). If someone is ready to provide a public server receiving Asterisk, so raise your hand. Any opinion/feedback are welcome. Cheers, Clément -- How ServiceNow helps IT people transform IT departments: 1. A cloud service to automate IT design, transition and operations 2. Dashboards that offer high-level views of enterprise services 3. A single system of record for all IT processes http://p.sf.net/sfu/servicenow-d2d-j___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] download_and_compile.sh and CMake Superbuild discussion
Pat Callahan and James Turner had an irc converation today about building flightgear. Here is Pat's summary of the main points Ongoing changes to Download_and_compile.sh Pat's goal is to increase the functionality of the script without changing the way it is used for simple builds of master/next or stable builds. these changes can be seen on the team clone Pat is using for download_and_compile.sh maintenance. Let Pat or Francesco know if you want to join the team in any capacity. https://www.gitorious.org/+fg-download-and-compile/fg/fg-download-and-compile-fgmeta The changes on the team clone are pretested, but may still contain bugs. 1.9.10 is very well tested. 1.9.11 is ready for has only minor changes. next has had some testing but could use a serious workout. Francisco will approve all changes that are to be merged with the main fgmeta tree. Francesco has approved 1.9.10 and 1.9.11 for merging into the master fgmeta tree, but has yet to see and approve next next has additional details on pat's future versions beyond next starting at line 54. download_and_compile.sh version number: James thought the version numbers for download_and_compile might be confusing. They're different from the versions for flightgear. Pat thinks we could put a working version on each branch that is tested to work with that specific branch, with a version number to match the flightgear version on the branch. We might want to make a rule that next should always support next, master and the previous 2 releases. Pat will bring the script version issue up with Francesco. The cmake superbuild: James thought that a cmake superbuild could do most if not all of the basic functions of the script. Pat likes the idea and thinks it can be integrated with the script or used independently. The superbuild approach could be used without a script to do a simple build on any platform, while download_and_compile.sh wuld provide additional options not easily provided by cmake. If the superbuild had enough additional logic built into it it could also do more complex and more efficient build scenarios and could be the build engine for most flightgear components in download_and_compile.sh James goal of a simple build method for any platform would still be met. The additonal logic and variables in the CMakeLists.txt would be there, but most users would never need to examine it. Basic Instructions should look something like this: wget \ http://www.gitorious.org/fg/fgmeta/blobs/raw/next/CMakeLists.txt cmake -D.FGVERSION=2.10.0 ./ make The cmake file is incomplete at this point, and this build fails to install because its trying to use /usr/local/lib/i386-linux-gnu without admin privs -Pat -- How ServiceNow helps IT people transform IT departments: 1. A cloud service to automate IT design, transition and operations 2. Dashboards that offer high-level views of enterprise services 3. A single system of record for all IT processes http://p.sf.net/sfu/servicenow-d2d-j ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] FlightGear voice communication
Hi Clement thanks a million times for taking the initiative for that - i guess I am one of the bigger users and promoters for FGCOM since a long time - and waited very long for such a solution. Just one point: Could it be possible to start 2 instances of FGCOM in the background (just with different ports) and thus be able to switch between those two from within FGFS? We once had an additional panel in FGFS to switch between two instances of FGCOM (uncontrolled design status only i believe - but it worked fine! And helps a lot if you need to switch during start/landing between Twr/Gnd) (Wolfram Wagner wolf...@wagnerw.de) is doing that in his OpenRadar - and it works fine.) A second point: During our ATC-events the FGCOM always goes into a hang after some time of usage - so we have to restart FGCOM (after somebody tells you about the problem!). If you then use FGCOMGUI that is fine with its Stop/Start buttons -- if you just work FGCOM that is a bigger effort! So please: Could there be a restart-button (just in case)? thanks again jomoATC -- How ServiceNow helps IT people transform IT departments: 1. A cloud service to automate IT design, transition and operations 2. Dashboards that offer high-level views of enterprise services 3. A single system of record for all IT processes http://p.sf.net/sfu/servicenow-d2d-j ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
