Re: [Flightgear-devel] 1.9.0 feedback

2008-12-28 Thread Stuart Buchanan
Durk wrote: In the mean time, here is the changelog. A couple of comments on reading this again. rendering bugs). The switch to OpenSceneGraph marks an important milestone for FlightGear, as it allows us to make full use of the advanced rendering options already available in

[Flightgear-devel] A patched patch, a repatch, and a mystery

2008-12-28 Thread Brian Schack
The recent 1.9.0 release of FlightGear has seen the Atlas protocol take a tiny step backwards, rather than forwards. I guess that's the nature of software development. Basically, there are 3 problems: (1) The most recent patch (1.13) had an omission (my fault) (2) The previous patch

[Flightgear-devel] Panel designers: feedback needed

2008-12-28 Thread James Turner
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

Re: [Flightgear-devel] Panel designers: feedback needed

2008-12-28 Thread Curtis Olson
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 units

Re: [Flightgear-devel] Panel designers: feedback needed

2008-12-28 Thread Heiko Schulz
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

Re: [Flightgear-devel] Panel designers: feedback needed

2008-12-28 Thread James Turner
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

Re: [Flightgear-devel] Panel designers: feedback needed

2008-12-28 Thread James Turner
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 some

Re: [Flightgear-devel] Panel designers: feedback needed

2008-12-28 Thread Tim Moore
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 does

Re: [Flightgear-devel] Panel designers: feedback needed

2008-12-28 Thread James Turner
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: [Flightgear-devel] Panel designers: feedback needed

2008-12-28 Thread Alexis Bory - xiii
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 was

Re: [Flightgear-devel] Panel designers: feedback needed

2008-12-28 Thread Vivian Meazza
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 units

Re: [Flightgear-devel] Panel designers: feedback needed

2008-12-28 Thread John Denker
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 some

Re: [Flightgear-devel] Panel designers: feedback needed

2008-12-28 Thread sydadams
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

Re: [Flightgear-devel] Panel designers: feedback needed

2008-12-28 Thread sydadams
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

[Flightgear-devel] Grr... I am so angry

2008-12-28 Thread LeeE
Hello dev list, If you're in no mood to critically appraise a rant then read no further. For quite a while now, since I stopped actively contributing to FG, I've been sitting here watching the direction in which FG development is heading and if ever there was a good project, which has

Re: [Flightgear-devel] Grr... I am so angry

2008-12-28 Thread Jon S. Berndt
What finally broke this camel's back was the thread about release schedules, but it goes further than that. The idea of release schedules for an open source project struck me as odd, as well. Jon --

Re: [Flightgear-devel] Panel designers: feedback needed

2008-12-28 Thread John Denker
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 interval-sec0.2/interval-sec Roger, thanks, that helps. Here's the patch to make the new pick animation behave more like the good old

[Flightgear-devel] lack of foresight, and lack of foresight

2008-12-28 Thread John Denker
On 12/28/2008 02:19 PM, LeeE wrote: What finally broke this camel's back was the thread about release schedules, but it goes further than that. On 12/28/2008 03:45 PM, Jon S. Berndt wrote: The idea of release schedules for an open source project struck me as odd, as well. Me, too. Grr... I

Re: [Flightgear-devel] a few more bugs

2008-12-28 Thread John Denker
57:: Core feature: As of CVS 26 Dec 2008 I observe that at (say) KJFK the Tower view and the Tower Look From view are conspicuously broken. Other airports are broken, just less conspicuously so. This appears to be the same problem previously discussed on the devel list under the heading

Re: [Flightgear-devel] A patched patch, a repatch, and a mystery

2008-12-28 Thread Brian Schack
[This is a repeat posting - Sourceforge decided the entire original message was an attachment and scrubbed the whole thing. Sorry for the noise.] The recent 1.9.0 release of FlightGear has seen the Atlas protocol take a tiny step backwards, rather than forwards. I guess that's the nature of

[Flightgear-devel] From forums... progress on solving black-box issue?

2008-12-28 Thread Rob Shearman, Jr.
Hi guys -- This was just posted on the forums about a half-hour ago, and I wanted to pass it along to the devel list in case it helped to shed light on one of the commonly reported bugs in 1.9. Re: Big Black Box by cj chitwood on Sun Dec 28, 2008 11:20 pm Alright...

[Flightgear-devel] problems with z-buffer

2008-12-28 Thread Alex Romosan
the latest commit to src/Main/CameraGroup.cxx changed the value of zNear from .1 to .4 and this causes strange artifacts to show up when panning around (like holes in the cockpit, etc.). the following patch changes it back: --- src/Main/CameraGroup.cxx27 Dec 2008 14:35:33 - 1.9 +++