>for me its a feature and not a bug!
> D-NXKT
I'm fine with having that [2D panel shown regardless of selected view] as an
optional feature, but it shouldn't be the default because it doesn't reflect
reality. The current menu switch to turn 2D panel on and off is NOT adequate,
because I have t
On 23 Jun 2012, at 19:50, syd adams wrote:
> Back when i started the ATC 'aircraft' , Csaba added an autohide
> feature to 2d panels . This keeps them on the display regardless of
> view direction. 0 needs to be added to the base
> panel xml file. Aircraft/ATC/MP-ATC-panel.xml uses it.
Except, i
. Indeed I would prefer to
> make it visible for all views (at the moment the panel is only visible in
> forward-view direction). I think such a behavior could be an advantage over
> the 3D panels.
>
>
> I think there's already a property (and if not I can trivially add one) to
> control this behav
On 23 Jun 2012, at 10:56, D-NXKT wrote:
> for me it's a feature and not a bug!
> I often find it useful to watch the instruments while NOT sitting in the
> cockpit. And since the panel can be switched off interactively it's up to the
> user or aircraft author to enable it or not. Indeed I would
Hello,
for me it's a feature and not a bug!
I often find it useful to watch the instruments while NOT sitting in the
cockpit. And since the panel can be switched off interactively it's up to the
user or aircraft author to enable it or not. Indeed I would prefer to make it
visible for all views
On 23 Jun 2012, at 08:16, Catherine James wrote:
> I recently found a bug in some of the latest git build (next branch, June 13
> and later). When flying planes such as the T-38 with a 2D panel, the 2D
> panel is always displayed even when you are using an outside view. This bug
> did not ex
I recently found a bug in some of the latest git build (next branch, June 13
and later). When flying planes such as the T-38 with a 2D panel, the 2D panel
is always displayed even when you are using an outside view. This bug did not
exist in 2.6.
I've created a patch 3 lines long that fixes t
As part of some work on cleaning up picking and mouse-interaction in the OSG
scene, I recently converted 2D and 2.5D panels to be picked via the 'normal'
hit-testing mechanism. Unfortunately this has broken some panels, due to some
latent bad behaviour:
http://files.goneabitbursar.com/f
On Tue, 31 May 2011 15:46:32 -0500, Curtis wrote in message
:
> Thanks everyone for the responses.
>
> So far the Anders' suggestion of using screen.nas seems to have the
> most promise. Torsten: I have another project I want to use the
> fgpanel system for, but with this project we are trying
Thanks everyone for the responses.
So far the Anders' suggestion of using screen.nas seems to have the most
promise. Torsten: I have another project I want to use the fgpanel system
for, but with this project we are trying to keep the logistics of starting
things up as simple as possible, also I'
On Tuesday, May 31, 2011 11:00:58 AM Curtis Olson wrote:
> I could be imagining this, but I seem to recall a while back, someone
> asking if it was possible to keep a 2d panel visible all the time, even in
> external views. I just took a quick peek at .../Cockpit/panel.cxx and it
> doesn't appear
Am 31.05.11 20:00, schrieb Curtis Olson:
Are there any other options or ideas that I'm missing?
Can you spawn an external application and render it's output window on
top of FlightGear? If so, fgpanel might be worth looking at. You find it
in utils/fgpanel and an example how to use it is in
Ai
On Tue, 31 May 2011, Curtis Olson wrote:
> I am working on a project where we are modeling a skydiver in free fall, and
> we want to display some basic information on the edge of the screen (like
> decent rate). But because this is not an aircraft, it makes more sense to
> use external views. Al
I could be imagining this, but I seem to recall a while back, someone asking
if it was possible to keep a 2d panel visible all the time, even in external
views. I just took a quick peek at .../Cockpit/panel.cxx and it doesn't
appear that we have the ability to do this, but I just thought I'd ask i
Hi all,
I'm working on a new cockpit and found a problem. I use 2D panel
because of some reasons and placed every element of the panel as
instrument (even the static, background elements).
It looks fine, but has got a big problem: if an instrument is
overlapping an other one, it's active area stop
On Wed, 2008-07-23 at 23:27 +0200, Erik Hofman wrote:
> The README.xmlpanel file shows what I already seemed to remember:
>
> Regarding Window Geometry:
> -
> For the sake of simplicity the FGFS window is always considered to be
> 1024x768 so all x/y values for instrum
The README.xmlpanel file shows what I already seemed to remember:
Regarding Window Geometry:
-
For the sake of simplicity the FGFS window is always considered to be
1024x768 so all x/y values for instrument placement should relative to
these dimensions. Since FG uses
My brain cells are running out of steam this afternoon so I thought I'd post
this to the list to see if anyone has a quick answer or suggestion.
Here's the situation. I am working on setting up a flight simulator with a
cockpit enclosure and physical cockpit controls. The display consists of
one
On Thursday 17 July 2008, Bebesi Janos wrote:
> Thanks for your help leeE,
>
>
> now i have a new problem. Could you tell me, how can i change the
> view sequences in fgfs? Now the 2D panel hide the HUD but i want
> to change them. so i want to see the hud before the 2D panel, not
> behind that.
>
Lee wrote
> > Sorry to go off thread. I've emailed you a couple of times but
> > they bounced. I want to resurrect the RNHF Seahawk livery, but I
> > seem to have lost it here - do you have a copy?
> >
> > Vivian
>
> Hi Vivian,
>
> were you sending it to my old e-mail address? Had a new one fo
Thanks for your help leeE,
now i have a new problem. Could you tell me, how can i change the view
sequences in fgfs? Now the 2D panel hide the HUD but i want to change them. so
i want to see the hud before the 2D panel, not behind that.
Thanks for your help.
Janos
___
On Wednesday 16 July 2008, Vivian Meazza wrote:
> Lee,
>
> Sorry to go off thread. I've emailed you a couple of times but
> they bounced. I want to resurrect the RNHF Seahawk livery, but I
> seem to have lost it here - do you have a copy?
>
> Vivian
Hi Vivian,
were you sending it to my old e-mail
Lee,
Sorry to go off thread. I've emailed you a couple of times but they bounced.
I want to resurrect the RNHF Seahawk livery, but I seem to have lost it here
- do you have a copy?
Vivian
-
This SF.Net email is sponsored
On Wednesday 16 July 2008, Bebesi Janos wrote:
> Hello,
>
> Could somebody tell me, how can i creat 2D panel which will be
> visible in different views? It shold be visible from outside
> view, like from inside view.
>
> Thanks for your help
>
> Janos
I have not updated my local cvs copy for a whi
Hello,
Could somebody tell me, how can i creat 2D panel which will be visible in
different views? It shold be visible from outside view, like from inside view.
Thanks for your help
Janos
___
Genertel casco szenzációs áron!
A Genertelnél elfelejtheti, amit eddig a casc
On 10/23/06, syd <[EMAIL PROTECTED]> wrote:
Hi Mike,Ive run across the same problem occasionally , with 2d panels in a 3dcockpit. I think the best solution is to add something like this...--- snip ---Thanks for the help, Syd! I'll try that out. Makes sense. Well, it wasn't a loss since I learne
Hi Mike,
Ive run across the same problem occasionally , with 2d panels in a 3d
cockpit. I think the best solution is to add something like this...
panel1
< " dimensions , etc...">
and then a sorting layer like so ...
Sort
panel1
panel2
cockpit
whatever
this will set the o
Ok, I've been trying to figure out how to fix this for HOURS and I really hope someone has a clue how to fix this. I'm starting out a C172R model with the Nav III avionics (i.e. glass cockpit). So I'm trying to get the basics up and working properly from the C172R plane.
If you try it out and mov
My mistake, the right link is
http://sfp1.site.voila.fr/images/2dpit.png
(case sensitive :( )
> Message du 27/09/06 à 01h59
> De : "Syd" <[EMAIL PROTECTED]>
> A : flightgear-devel@lists.sourceforge.net
> Copie à :
> Objet : [Flightgear-devel] 2d panel clippin
>
> I have read with some interest the post regarding the new 2D panel
> code (clipping within a layer) because I am running into the
> following problem with the 2D "aerobatic" panel of the Su-26 :
>
> http://sfp1.site.voila.fr/images/2Dpit.png
>
> This screenshot has been taken with the lates
Hi all,
after updating from cvs a couple of days ago I found that all the
2d instruments I use for displaying info appear to be cropped
into the top left hand corner and are now unreadable.
Anyone else seeing this?
I suspect it's something to do with 're-sizing' them in the
panel.xml file - i
> Just wondering if it is possible to clip 2d instruments to keep
> textures / text from sliding around on the panel /windshield:
AFAIK this has always been a limitation of the 2D panels.
> Also could a groundspeed property be added to /velocities property
> tree without too much difficulty?
I'
Hi all ,
Just wondering if it is possible to clip 2d instruments to keep
textures / text from sliding around on the panel /windshield: I never
noticed this before I'm more into 3d panels... but if a 2d instrument
could be clipped / cropped it would make PFD's /MFD's ,etc much easier
to implement..
* dene maxwell -- Wednesday 21 June 2006 22:55:
> I answered a previous post before before reading yours could this
> problem have existed for a while (previous versions)?
No. It was a kind of copy&paste error that I committed recently, with this
log message:
revision 1.47
date: 2006-06-
>From: Melchior FRANZ <[EMAIL PROTECTED]>
>Reply-To: FlightGear developers discussions
>
>To: flightgear-devel@lists.sourceforge.net
>Subject: Re: [Flightgear-devel] 2D Panel memory leak
>Date: Wed, 21 Jun 2006 21:54:54 +0200
>
>* Lee Elliott -- Wednesday 21
* Lee Elliott -- Wednesday 21 June 2006 21:39:
> I haven't tried using other fonts yet either, to establish if
> it's just with the LED font or with any font.
Fixed. Sorry too all. :-)
m.
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The hig
Lee Elliott wrote:
> Hi all,
>
> I think I may have a lead on this now, and it turns out that
> there was a connection with the 2D radio stacks but probably not
> one that many would suspect.
>
> First of all I commented out all the instruments on both the vfr
> and mini panels to see if just re
Hi all,
I think I may have a lead on this now, and it turns out that
there was a connection with the 2D radio stacks but probably not
one that many would suspect.
First of all I commented out all the instruments on both the vfr
and mini panels to see if just revealing/loading the panels
start
Jean-Yves Lefort wrote:
http://javky.rozhled.cz/jprojdwn.php?id=fgfsl410/l410-0.9.9-src-v4.0.tar.gz
Search for "JVK" in src/Cockpit/panel*
I've added this part of the patch (and I've renamed 'emisive' to
'emissive'). I still have to scan the rest of the patch.
Erik
--
http://www.ehtw.inf
Jean-Yves Lefort wrote:
On Wed, 15 Feb 2006 17:16:03 -0600
"Curtis L. Olson" <[EMAIL PROTECTED]> wrote:
I have a 2d panel question.
I want to make an annunciator light for a 2d panel. But, I don't want
it to have any of the default panel illumination at night. I want it to
be dark when
On Wed, 15 Feb 2006 17:16:03 -0600
"Curtis L. Olson" <[EMAIL PROTECTED]> wrote:
> I have a 2d panel question.
>
> I want to make an annunciator light for a 2d panel. But, I don't want
> it to have any of the default panel illumination at night. I want it to
> be dark when the light is off, an
I have a 2d panel question.
I want to make an annunciator light for a 2d panel. But, I don't want
it to have any of the default panel illumination at night. I want it to
be dark when the light is off, and lit when the light is on. But at
night, the default panel illumination makes it diffic
42 matches
Mail list logo
