Re: [Flightgear-devel] OpenStreetMap tool to control Flightgear
Could someone provide me with some clues here? Is there any specific thing the GPS needs to sequence to the next waypoint? Short reply since I'm at FSWeekend still - can reply in more detail tomorrow. The most likely answer is that the route-manager or GPS is not activated - activating GPS leg mode should set the route-manger mode automatically, I think. Once that's done, simply passing within 0.1 (IIRC) will sequence the next wp. James Hi James, Thanks for answering. Here is the detailed sequence I use to program the route manager via telnet: fg[/autopilot/route-manager/active]= 'false' fg[/autopilot/route-manager/input]= '@clear' fg[/autopilot/route-manager/current-wp]= '-1' fg[/autopilot/route-manager/input]= '@posinit' fg[/autopilot/route-manager/input] = lon,lat@alt .. etc fg[/autopilot/route-manager/input]= '@activate' fg[/autopilot/route-manager/input]= '@jump0' fg[/autopilot/settings/target-agl-feet]= 2 fg[/autopilot/settings/target-agl-ft]= 2 fg[/autopilot/settings/gps-driving-true-heading]= 'true' fg[/autopilot/locks/altitude]= 'agl-hold' fg[/autopilot/locks/heading]= 'true-heading-hold' fg[/autopilot/settings/target-speed-kt]= 30 fg[/autopilot/locks/speed]= 'THR' The first waypoint set is not the UFO position or a runway but an arbitrary point on the map, followed by other arbitrary points. What happens is that the UFO starts just fine towards the first waypoint, but on arrival it starts to circle it and never proceed forward. I think sometimes this happens on the second waypoint, not necessarily the first one. I've looked through the GPS and route manager classes, but I hope you could enlighten me without having to place debug messages through the source code. Thanks, Adrian -- LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Regarding the new radio propagation code
Hi all and especially Torsten and Durk, As you know, I had an older merge request containing the new and improved radio code. Since that was ~8 months old and was outdated, I retracted it so you don't have to try to merge in old code over new improvements in trafficcontrol.cxx and other files. I do these myself when I'm updating the source code. Thanks anyway to whoever maintained the old code, I've made sure to backport the changes to the new code. Since the old code is really outdated and is lacking in almost every aspect including performance, it would be highly advised to swich to the new code, if there is interest and time allows. Right now VOR and ILS are not done through the new code. I'm willing to do that myself, if the people who maintain the navradio code are willing to accept me hacking through their code. Cheers, Adrian -- LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Simgear/ShivaVG compile fails on windows
Just a heads up. The error report is :- Alan 3 shContext.c 3C:\FlightGear\simgear\simgear\canvas\ShivaVG\src\shContext.c(37): error C2491: 'vgCreateContextSH' : definition of dllimport function not allowed 3C:\FlightGear\simgear\simgear\canvas\ShivaVG\src\shContext.c(65): error C2491: 'vgResizeSurfaceSH' : definition of dllimport function not allowed 3C:\FlightGear\simgear\simgear\canvas\ShivaVG\src\shContext.c(86): error C2491: 'vgDestroyContextSH' : definition of dllimport function not allowed 3C:\FlightGear\simgear\simgear\canvas\ShivaVG\src\shContext.c(258): error C2491: 'vgGetError' : definition of dllimport function not allowed 3C:\FlightGear\simgear\simgear\canvas\ShivaVG\src\shContext.c(267): error C2491: 'vgFlush' : definition of dllimport function not allowed 3C:\FlightGear\simgear\simgear\canvas\ShivaVG\src\shContext.c(274): error C2491: 'vgFinish' : definition of dllimport function not allowed 3C:\FlightGear\simgear\simgear\canvas\ShivaVG\src\shContext.c(282): error C2491: 'vgMask' : definition of dllimport function not allowed 3C:\FlightGear\simgear\simgear\canvas\ShivaVG\src\shContext.c(286): error C2491: 'vgClear' : definition of dllimport function not allowed 3C:\FlightGear\simgear\simgear\canvas\ShivaVG\src\shContext.c(346): error C2491: 'vgLoadIdentity' : definition of dllimport function not allowed 3C:\FlightGear\simgear\simgear\canvas\ShivaVG\src\shContext.c(362): error C2491: 'vgLoadMatrix' : definition of dllimport function not allowed 3C:\FlightGear\simgear\simgear\canvas\ShivaVG\src\shContext.c(393): error C2491: 'vgGetMatrix' : definition of dllimport function not allowed 3C:\FlightGear\simgear\simgear\canvas\ShivaVG\src\shContext.c(416): error C2491: 'vgMultMatrix' : definition of dllimport function not allowed 3C:\FlightGear\simgear\simgear\canvas\ShivaVG\src\shContext.c(446): error C2491: 'vgTranslate' : definition of dllimport function not allowed 3C:\FlightGear\simgear\simgear\canvas\ShivaVG\src\shContext.c(457): error C2491: 'vgScale' : definition of dllimport function not allowed 3C:\FlightGear\simgear\simgear\canvas\ShivaVG\src\shContext.c(468): error C2491: 'vgShear' : definition of dllimport function not allowed 3C:\FlightGear\simgear\simgear\canvas\ShivaVG\src\shContext.c(479): error C2491: 'vgRotate' : definition of dllimport function not allowed 3C:\FlightGear\simgear\simgear\canvas\ShivaVG\src\shContext.c(493): error C2491: 'vgHardwareQuery' : definition of dllimport function not allowed 3 shGeometry.c 3C:\FlightGear\simgear\simgear\canvas\ShivaVG\src\shGeometry.c(852): error C2491: 'vgPathBounds' : definition of dllimport function not allowed 3C:\FlightGear\simgear\simgear\canvas\ShivaVG\src\shGeometry.c(891): error C2491: 'vgPathTransformedBounds' : definition of dllimport function not allowed 3C:\FlightGear\simgear\simgear\canvas\ShivaVG\src\shGeometry.c(926): error C2491: 'vgPathLength' : definition of dllimport function not allowed 3C:\FlightGear\simgear\simgear\canvas\ShivaVG\src\shGeometry.c(935): error C2491: 'vgPointAlongPath' : definition of dllimport function not allowed 3 shImage.c 3C:\FlightGear\simgear\simgear\canvas\ShivaVG\src\shImage.c(564): error C2491: 'vgCreateImage' : definition of dllimport function not allowed 3C:\FlightGear\simgear\simgear\canvas\ShivaVG\src\shImage.c(622): error C2491: 'vgDestroyImage' : definition of dllimport function not allowed 3C:\FlightGear\simgear\simgear\canvas\ShivaVG\src\shImage.c(644): error C2491: 'vgClearImage' : definition of dllimport function not allowed 3C:\FlightGear\simgear\simgear\canvas\ShivaVG\src\shImage.c(808): error C2491: 'vgImageSubData' : definition of dllimport function not allowed 3C:\FlightGear\simgear\simgear\canvas\ShivaVG\src\shImage.c(853): error C2491: 'vgGetImageSubData' : definition of dllimport function not allowed 3C:\FlightGear\simgear\simgear\canvas\ShivaVG\src\shImage.c(896): error C2491: 'vgCopyImage' : definition of dllimport function not allowed 3C:\FlightGear\simgear\simgear\canvas\ShivaVG\src\shImage.c(948): error C2491: 'vgSetPixels' : definition of dllimport function not allowed 3C:\FlightGear\simgear\simgear\canvas\ShivaVG\src\shImage.c(1001): error C2491: 'vgWritePixels' : definition of dllimport function not allowed 3C:\FlightGear\simgear\simgear\canvas\ShivaVG\src\shImage.c(1058): error C2491: 'vgGetPixels' : definition of dllimport function not allowed 3C:\FlightGear\simgear\simgear\canvas\ShivaVG\src\shImage.c(1109): error C2491: 'vgReadPixels' : definition of dllimport function not allowed 3C:\FlightGear\simgear\simgear\canvas\ShivaVG\src\shImage.c(1162): error C2491: 'vgCopyPixels' : definition of dllimport function not allowed 3C:\FlightGear\simgear\simgear\canvas\ShivaVG\src\shImage.c(1179): error C2491: 'vgChildImage' : definition of dllimport function not allowed 3C:\FlightGear\simgear\simgear\canvas\ShivaVG\src\shImage.c(1184): error C2491: 'vgGetParent' : definition of dllimport function not allowed
Re: [Flightgear-devel] Simgear/ShivaVG compile fails on windows
Am 2012-11-05 12:14, schrieb Alan Teeder: Just a heads up. The error report is :- Thanks for the report. Should now be fixed. Tom -- Thomas Geymayer www.tomprogs.at / C-Forum und Tutorial: www.proggen.org Student of Computer Science @ Graz University of Technology --- Austria -- LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [Flightgear-commitlogs] SimGear branch, next, updated. 186bae2bd445f16540a66e23e81c307c194cf721
On 5 Nov 2012, at 13:04, Flightgear-commitlogs wrote: - Log - commit 186bae2bd445f16540a66e23e81c307c194cf721 Author: Thomas Geymayer Date: Mon Nov 5 13:35:06 2012 +0100 Proper headless build fix - Summary - simgear/misc/parse_color.cxx |4 simgear/misc/parse_color.hxx |6 +- 2 files changed, 5 insertions(+), 5 deletions(-) This is still not ideal: the goal is to have no #ifdefs, because we simply partition the files based on requiring OSG. So if this header file needs OSG, it should be in some other location than misc; probably some sensible subdirectory of 'scene'. Ifdefs are bad because they change the contents of the SimGearCore library - ideally building headless or not, should make no difference at all to the SimGearCore library that is produced. Regards, James -- LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Simgear/ShivaVG compile fails on windows
-Original Message- From: Thomas Geymayer Sent: Monday, November 05, 2012 12:19 PM To: flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] Simgear/ShivaVG compile fails on windows Am 2012-11-05 12:14, schrieb Alan Teeder: Just a heads up. The error report is :- Thanks for the report. Should now be fixed. Tom Yes - it all compiles and runs again. And my canvas HUD (in development) still works! Thanks Alan -- LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Simgear/ShivaVG compile fails on windows
:Alan Teeder wrote Am 2012-11-05 12:14, schrieb Alan Teeder: Just a heads up. The error report is :- Thanks for the report. Should now be fixed. Tom Yes - it all compiles and runs again. And my canvas HUD (in development) still works! But mine doesn't :-( https://dl.dropbox.com/u/57645542/fgfs-screen-068.png Any clues/hints? Vivian -- LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Simgear/ShivaVG compile fails on windows
Am 2012-11-05 16:02, schrieb Vivian Meazza: But mine doesn't :-( https://dl.dropbox.com/u/57645542/fgfs-screen-068.png Any clues/hints? Have you also updated fgdata? The way how the background color is set has been changed (Now it uses only on single property for the whole color instead of one for each color component) and defaults to opaque black. Using the latest Nasal API for setting the background color should still work the same as before. Tom -- Thomas Geymayer www.tomprogs.at / C-Forum und Tutorial: www.proggen.org Student of Computer Science @ Graz University of Technology --- Austria -- LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Simgear/ShivaVG compile fails on windows
On 5 Nov 2012, at 13:50, Alan Teeder wrote: Yes - it all compiles and runs again. And my canvas HUD (in development) still works! Can you talk a little about the Canvas HUD? Moving the HUD to use the Canvas would be a great step from my point of view, since it and 2D panels (which I am happy to write the convert for!) are the last places besides the UI which make raw OpenGL calls, and hence would benefit from moving to the Canvas (and thus, to use OSG internally) James -- LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Simgear/ShivaVG compile fails on windows
There is a template on the canvas wiki - http://wiki.flightgear.org/Canvas_HUD, which I have used. The Nasal code is quite simple and hardly needs explaining. The symbology that I needed is not hard-coded into the existing (flightgear/src/Instrumentation/HUD/) and I had been putting off doing that job, until the canvas HUD suddenly appeared. My HUD is that used on the TSR2 and was a development of the even more basic HUD fitted to early Buccaneers. I spent many, many hours behind this HUD in the simulator at Weybridge. The TSR2 is still very much in development, and I am currently replacing a very unstable Datcom based FDM with CFD derived data. You can preview it at g...@gitorious.org:fg-ajt/tsr2.git. The main differences between the TSR2 and later HUDs are the flight director and the pitch gearing. The flight director was named highway in the sky and looks like a runway pattern. You fly the vanishing point of the runway to the central circle of the HUD. The HUD is not geared 1 to 1 in pitch. This sounds quite wrong, but the gearing is similar to that of the head-down artificial horizon, which pilots are quite accustomed to. Once I get an attack computer built up, there is simple symbology for that also. To fly the TSR2, use the idiot start button (as with the Lightning). Select one notch of flap. With the autopilot menu-bar (F11) select the take-off flight director. When the engines are running open up full and follow the director signal. It should demand rotation at 160 kts. Keep manoeuvres small, otherwise the present FDM will soon get unstable. Also keep a close eye on airspeed as the minimum drag speed is quite high and therefore it is speed unstable. In short the canvas HUD is very simple to program. Alan -Original Message- From: James Turner Sent: Monday, November 05, 2012 3:11 PM To: FlightGear developers discussions Subject: Re: [Flightgear-devel] Simgear/ShivaVG compile fails on windows On 5 Nov 2012, at 13:50, Alan Teeder wrote: Yes - it all compiles and runs again. And my canvas HUD (in development) still works! Can you talk a little about the Canvas HUD? Moving the HUD to use the Canvas would be a great step from my point of view, since it and 2D panels (which I am happy to write the convert for!) are the last places besides the UI which make raw OpenGL calls, and hence would benefit from moving to the Canvas (and thus, to use OSG internally) James -- LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Simgear/ShivaVG compile fails on windows
Thomas wrote fails on windows Am 2012-11-05 16:02, schrieb Vivian Meazza: But mine doesn't :-( https://dl.dropbox.com/u/57645542/fgfs-screen-068.png Any clues/hints? Have you also updated fgdata? Yes, using MSVC10, and after the same problems as Alan. The way how the background color is set has been changed (Now it uses only on single property for the whole color instead of one for each color component) and defaults to opaque black. Looks like it might be using the default ... but Using the latest Nasal API for setting the background color should still work the same as before. I'm using the Nasal API - it used to all work before today's update. Can't really see what to change Vivian -- LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Simgear/ShivaVG compile fails on windows
Am 2012-11-05 18:30, schrieb Vivian Meazza:
I'm using the Nasal API - it used to all work before today's update. Can't
really see what to change
Are you using canvas.setColorBackground(r, g, b, a) and is there a function
setColorBackground: func () { me.texture.getNode('background',
1).setValue(_getColor(arg)); me; }
in your Nasal/canvas/api.nas?
Are there /canvas/by-index[i]/color-background/[red,green,blue,alpha]
nodes in your property tree or just a single
/canvas/by-index[i]/background string property per canvas?
Tom
--
Thomas Geymayer www.tomprogs.at / C-Forum und Tutorial: www.proggen.org
Student of Computer Science @ Graz University of Technology
--- Austria
--
LogMeIn Central: Instant, anywhere, Remote PC access and management.
Stay in control, update software, and manage PCs from one command center
Diagnose problems and improve visibility into emerging IT issues
Automate, monitor and manage. Do more in less time with Central
http://p.sf.net/sfu/logmein12331_d2d
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenStreetMap tool to control Flightgear
On Sunday, November 04, 2012 09:49:25 James Turner wrote: Short reply since I'm at FSWeekend still - can reply in more detail tomorrow. The most likely answer is that the route-manager or GPS is not activated - activating GPS leg mode should set the route-manger mode automatically, I think. Once that's done, simply passing within 0.1 (IIRC) will sequence the next wp. James To be more precise, the gps sequencing problem only appears at the second waypoint in the list. With loglevel info, I get the following messages at waypoint #1: GPS doing overflight sequencing 'saw current WP changed, now 1' GPS waypoint index is now 1 current waypt has altitude set, setting on AP route manager, current-wp is now 1 At waypoint #2, the ufo starts circling, and the console is swamped with this message: already done @ WayptController::setDone Any ideas? Thanks, Adrian -- LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenStreetMap tool to control Flightgear
On 5 Nov 2012, at 18:08, Adrian Musceac wrote: To be more precise, the gps sequencing problem only appears at the second waypoint in the list. With loglevel info, I get the following messages at waypoint #1: GPS doing overflight sequencing 'saw current WP changed, now 1' GPS waypoint index is now 1 current waypt has altitude set, setting on AP route manager, current-wp is now 1 At waypoint #2, the ufo starts circling, and the console is swamped with this message: already done @ WayptController::setDone Any ideas? Hmmm, no is the quick answer - if you can wait a little, I'll try to replicate this tomorrow. Regards, James -- LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Simgear/ShivaVG compile fails on windows
Vivian´s Buccaneer, (from fgdata git, with canvas hud) is fine on my
laptop, but has an occluded screen on my desktop. Both have Windows 7 and
Nvidia cards.
On the other hand my development TSR2 hud is fine on both machines.
This is with git sources (fgdata, flightgear and simgear) up to date at the
time of posting.
Strange.
Alan
-Original Message-
From: Thomas Geymayer
Sent: Monday, November 05, 2012 5:52 PM
To: flightgear-devel@lists.sourceforge.net
Subject: Re: [Flightgear-devel] Simgear/ShivaVG compile fails on windows
Am 2012-11-05 18:30, schrieb Vivian Meazza:
I'm using the Nasal API - it used to all work before today's update. Can't
really see what to change
Are you using canvas.setColorBackground(r, g, b, a) and is there a function
setColorBackground: func () { me.texture.getNode('background',
1).setValue(_getColor(arg)); me; }
in your Nasal/canvas/api.nas?
Are there /canvas/by-index[i]/color-background/[red,green,blue,alpha]
nodes in your property tree or just a single
/canvas/by-index[i]/background string property per canvas?
Tom
--
Thomas Geymayer www.tomprogs.at / C-Forum und Tutorial: www.proggen.org
Student of Computer Science @ Graz University of Technology
--- Austria
--
LogMeIn Central: Instant, anywhere, Remote PC access and management.
Stay in control, update software, and manage PCs from one command center
Diagnose problems and improve visibility into emerging IT issues
Automate, monitor and manage. Do more in less time with Central
http://p.sf.net/sfu/logmein12331_d2d
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
--
LogMeIn Central: Instant, anywhere, Remote PC access and management.
Stay in control, update software, and manage PCs from one command center
Diagnose problems and improve visibility into emerging IT issues
Automate, monitor and manage. Do more in less time with Central
http://p.sf.net/sfu/logmein12331_d2d
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Simgear/ShivaVG compile fails on windows
Thomas wrote:
Am 2012-11-05 18:30, schrieb Vivian Meazza:
I'm using the Nasal API - it used to all work before today's update.
Can't really see what to change
Are you using canvas.setColorBackground(r, g, b, a)
I have this:
m.canvas.addPlacement(placement);
m.canvas.setColorBackground(0.36, 1, 0.3, 0.02);
which is a direct copy from
http://wiki.flightgear.org/Canvas_HUD
and is there a function
setColorBackground: func () { me.texture.getNode('background',
1).setValue(_getColor(arg)); me; }
No - there isn't one in
http://wiki.flightgear.org/Canvas_HUD
in your Nasal/canvas/api.nas?
Are there /canvas/by-index[i]/color-background/[red,green,blue,alpha]
nodes in your property tree or just a single
/canvas/by-index[i]/background
string property per canvas?
And no other references to color-background
Vivian
--
LogMeIn Central: Instant, anywhere, Remote PC access and management.
Stay in control, update software, and manage PCs from one command center
Diagnose problems and improve visibility into emerging IT issues
Automate, monitor and manage. Do more in less time with Central
http://p.sf.net/sfu/logmein12331_d2d
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FSWeekend 2012...
Hey Thorsten et al, Yeah, I guess it's time for some further impressions of FSWeekend from my perspective. This year was our 7th consecutive presentation, and the first time we had a presentation that was considerably scaled down compared to our previous tradition of growing in size every year. Though I think it's okay to throttle back a little, every once in a while, it did mean that our prominence was a little less present this year. This is something we probably need to consider for next year. Let me come back to that at the end of this post; first some impressions. My pictures are are here: http://www.flickr.com/photos/durktalsma/sets/72157631936384731/ As the Pictures show, Martin, Mathias, James, and myself started out on Friday with a 4-hour session at the full-motion simulator at simcenter (http://simcenter.nl/) lelystad Airport. Gijs also made some with my camera, but I haven't had the chance to process those yet. Yes, there are some rumors. Firstly, yes we did hijack the main projection screen in the uiverzaal, and yes a broomstick was involved. Secondly, there are some rumors that people may have seen a person walking around with a Curt Olson name-tag. Rumors also have it that the person carrying it spoke with a rapid Scottish accent. So, what's up with the projector/broomstick rumor? Well, despite my good intentions, I wasn't as well prepared as I had thought. I did bring my computer, a projector, and a screen. But, as we were setting up, I had realized that I had forgotten to bring the pole that is holding the screen up, making the entire exercise rather useless. In order to find a replacement, I tried borrowing a broomstick from the museum. Although that would have worked, we couldn't borrow it for the entire weekend. While we were contemplating our next move, Frans offered us to use the big screen. I hope that none of the other clubs took offense, because the screen was rather big. Secondly, by the time I had to register for the booth, Curt and I were discussing ways that would enable it for him to visit. With the deadline in sight, I did decide to go ahead and register Curt. But in the end, the travel plans didn't work out and in the mean time I had gotten an email from James Turner showing his interest in participating, but that was already after the registration deadline. So with one spare badge and one person without a badge, we decided that James should pretend he'd be Curt during the course of the show. I think that it worked out pretty well :-) So, compared to the previous years, a number of things were a little different. A few of our regular members couldn't make it this year, including Torsten, Jorg and Lindsey, Hans (but thanks for briefly stopping by Hans!), and even Gijs had to bail out on sunday. Their absence was offset by the presence of James Turner, Christian Schmitt, and Alexis Bory. It was a joy having you guys around! I hope you can make it to FSWeekend again sometime. Although in general I'm looking back at a fun weekend, I also have to admit that I've had some reservations about the event -and our presentation- that I feel I need to share as well. As mentioned above, this was the 7th time we were there and in those 7 years the format of FSWeekend hasn't really changed much. Most of the presenters are regulars and they seem to be doing exactly the same thing as in previous years. With FlightGear, I usually felt that we managed to escape that, by presenting something drastically new every year. But this year the new essence seemed to be missing somewhat. I didn't really feel that we had any major innovations to show (with the notable exception of project rembrandt, which ran well on Alexis' machine). With our multiscreen setups, we were somewhat limited in terms of graphics capabilities, and I also didn't feel that there were a lot of exciting new aircraft to demonstrate. Now, I want to emphasize that this was largely due to our personal situations, and nobody is to blame (if anybody, perhaps myself, because I was really late an a little lazy in organizing this year). So, despite our good intentions, not everything came about as intended, and I would like to consider possible ways of smoothing that out in a better way. But, to end on a positive note: We also met a lot of fabulous new people again. In addition to James's, Christian's, and Alexis's presence, I met Rob de Vries, who run the newssite www.simflight.nl, Gijs was interviewed for PCPilot, and we established contact with the folks at Saitek, which may hopefully result in full FlightGear support for their Pro line of products. We're still working out the details, but they gave me a copy of their radio stack for play with, and if we get that to work, more stuff may follow. So, to conclude, it was a fun weekend, but for next year I would like to come up with a slightly more organized plan of approach. Cheers, Durk On 04 Nov 2012, at
