Re: [Flightgear-devel] OpenStreetMap tool to control Flightgear

2012-11-05 Thread Adrian Musceac
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 -

[Flightgear-devel] Regarding the new radio propagation code

2012-11-05 Thread Adrian Musceac
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.

[Flightgear-devel] Simgear/ShivaVG compile fails on windows

2012-11-05 Thread Alan Teeder
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:

Re: [Flightgear-devel] Simgear/ShivaVG compile fails on windows

2012-11-05 Thread Thomas Geymayer
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

Re: [Flightgear-devel] [Flightgear-commitlogs] SimGear branch, next, updated. 186bae2bd445f16540a66e23e81c307c194cf721

2012-11-05 Thread James Turner
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

Re: [Flightgear-devel] Simgear/ShivaVG compile fails on windows

2012-11-05 Thread Alan Teeder
-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 :-

Re: [Flightgear-devel] Simgear/ShivaVG compile fails on windows

2012-11-05 Thread Vivian Meazza
: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 :-(

Re: [Flightgear-devel] Simgear/ShivaVG compile fails on windows

2012-11-05 Thread Thomas Geymayer
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

Re: [Flightgear-devel] Simgear/ShivaVG compile fails on windows

2012-11-05 Thread James Turner
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

Re: [Flightgear-devel] Simgear/ShivaVG compile fails on windows

2012-11-05 Thread Alan Teeder
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

Re: [Flightgear-devel] Simgear/ShivaVG compile fails on windows

2012-11-05 Thread Vivian Meazza
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

Re: [Flightgear-devel] Simgear/ShivaVG compile fails on windows

2012-11-05 Thread Thomas Geymayer
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',

Re: [Flightgear-devel] OpenStreetMap tool to control Flightgear

2012-11-05 Thread Adrian Musceac
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.

Re: [Flightgear-devel] OpenStreetMap tool to control Flightgear

2012-11-05 Thread James Turner
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

Re: [Flightgear-devel] Simgear/ShivaVG compile fails on windows

2012-11-05 Thread Alan Teeder
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

Re: [Flightgear-devel] Simgear/ShivaVG compile fails on windows

2012-11-05 Thread Vivian Meazza
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);

Re: [Flightgear-devel] FSWeekend 2012...

2012-11-05 Thread Durk Talsma
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