>
> > I generally make 3d panels, but I find textranslate etc useful,
> > indeed vital
> > within these 3d instruments for example in HIS.
> >
> > I'm also using them for rain effects on canopies, so as far as I'm
> > concerned
> > the 2d panel stuff is still very much in use.
>
> (still trying to
On 12/29/2008 05:28 AM, James Turner wrote:
> Possibly I'm being a little slow, but what does 'bobble' mean in this
> context? The last time I heard that word, it was referring to a round,
> fluffy ball that might be attached to the top of a child's hat.
According to http://www.yourdictionary
On 28 Dec 2008, at 20:27, sydad...@telus.net wrote:
> I'm aslo in favor of keeping and upgrading the 2d panel system. It
> would be nice to have a 2d line drawing layer also.
>
Yes, that seems to be second most common request after text. I'm still
debating that one, because while I can see it
On 28 Dec 2008, at 19:50, Vivian Meazza wrote:
> I generally make 3d panels, but I find textranslate etc useful,
> indeed vital
> within these 3d instruments for example in HIS.
>
> I'm also using them for rain effects on canopies, so as far as I'm
> concerned
> the 2d panel stuff is still ve
On 28 Dec 2008, at 23:05, John Denker wrote:
> Here's the patch to make the "new" pick animation behave more
> like the good old "2D" panel. This makes it possible to turn
> on the feature in 3D without quite so many bobbles.
>
> --- a/simgear/scene/model/animation.cxx
> +++ b/simgear/scene/mod
On 12/28/2008 01:31 PM, sydad...@telus.net wrote:
> The "repeat" function is a rather important user-interface feature.
>
>
>
> the pick repeat rate is set with a 0.2
Roger, thanks, that helps.
Here's the patch to make the "new" pick animation behave more
like the good old "2D" panel. This
Parameterizing the repeat rate via the property tree might be nice.I don't see such parameter in the existing tree.Feedback i.e. clues (or patches!) from folks who are familiar with this code would be most welcome.The "repeat" function is a rather important user-interface feature. the pick repeat r
I'm aslo in favor of keeping and upgrading the 2d panel system. It would be nice to have a 2d line drawing layer also.I made my own attempt to convert the text layer to an osgText layer , but tracing backwards it seems the txf fonts are cached , and used by the PLIB dialog / menu system , so not a
On 28 Dec 2008, at 15:54, Heiko Schulz wrote:
>> Currently there are two approaches:
>> -making it all 3d. Means that signs, symbols lines are mostly done
>> with 3d-objects. Good example the 787-display
>>
>> -using 2d-layers. Syd is using this approach on his 777 but it does
>> have problems
James Turner asked
> From: [mailto:zakal...@mac.com]
>
> I'm planning to create some slightly advanced cockpit instruments in
> the near future, and to do this I need to support some more complex
> text displays. (This is for the character-based displays on the
> KLN89/94/etc GPSs, and FMS/MCDU u
James Turner wrote:
> I'm planning to create some slightly advanced cockpit instruments in
> the near future, and to do this I need to support some more complex
> text displays. (This is for the character-based displays on the
> KLN89/94/etc GPSs, and FMS/MCDU units in the longer term).
>
> I
On 28 Dec 2008, at 16:12, Tim Moore wrote:
> You should also take a look at the weather radar code in
> Instrumentation/od_gauge.cxx and wxradar.cxx for yet another
> appproach.
I'm familiar with that code (it's how I built my current Nav Display
prototype) but I'm not 100% happy with the re
James Turner wrote:
> On 28 Dec 2008, at 15:54, Heiko Schulz wrote:
>
>> Currently there are two approaches:
>> -making it all 3d. Means that signs, symbols lines are mostly done
>> with 3d-objects. Good example the 787-display
>>
>> -using 2d-layers. Syd is using this approach on his 777 but it
On 28 Dec 2008, at 15:54, Heiko Schulz wrote:
> Currently there are two approaches:
> -making it all 3d. Means that signs, symbols lines are mostly done
> with 3d-objects. Good example the 787-display
>
> -using 2d-layers. Syd is using this approach on his 777 but it does
> have problems on s
On 28 Dec 2008, at 15:48, Curtis Olson wrote:
> In my opinion, the 2d instruments are still very useful for people
> that are setting up full screen panels as part of a larger simulator
> where the out-the-window view is drawn on separate monitors and the
> there may be one or more displays
> I'm planning to create some slightly advanced cockpit
> instruments in
> the near future, and to do this I need to support some more
> complex
> text displays. (This is for the character-based displays on
> the
> KLN89/94/etc GPSs, and FMS/MCDU units in the longer term).
>
> I was intendi
On Sun, Dec 28, 2008 at 9:38 AM, James Turner wrote:
> I'm planning to create some slightly advanced cockpit instruments in
> the near future, and to do this I need to support some more complex
> text displays. (This is for the character-based displays on the
> KLN89/94/etc GPSs, and FMS/MCDU unit
I'm planning to create some slightly advanced cockpit instruments in
the near future, and to do this I need to support some more complex
text displays. (This is for the character-based displays on the
KLN89/94/etc GPSs, and FMS/MCDU units in the longer term).
I was intending to create some s
18 matches
Mail list logo
