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 yea
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);
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
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 waypo
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 th
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).setVal
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
On 5 Nov 2012, at 17:06, Gitorious wrote:
> commit df8a3d9c603e53810c652dbb7620e518265d1466
> Author: Thomas Geymayer
> Date: Mon Nov 5 18:05:24 2012 +0100
>
>SIMGEAR_HEADLESS define is not needed anymore
Fantastic, thank you!
James
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 t
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
ha
On 5 Nov 2012, at 14:40, Thomas Geymayer wrote:
> At first I thought about putting it into scene/util but it didn't feel
> right because it's not really falling in the category
> rendering/scenegraph utilities. The only purpose is to parse a string
> containing a color (CSS syntax) into a 4d vect
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 instea
: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://
Am 2012-11-05 14:44, schrieb James Turner:
>> 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 re
-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 :-
Than
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 -
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
Just a heads up. The error report is :-
Alan
3> shContext.c
3>C:\FlightGear\simgear\simgear\canvas\ShivaVG\src\shContext.c(37): error
C2491: 'vgCreateContextSH' : definition of dllimport function not allowed
3>C:\FlightGear\simgear\simgear\canvas\ShivaVG\src\shContext.c(65): error
C2491: 'vgR
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.
> >
> > 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 -
20 matches
Mail list logo
