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 hardware- some layers disappear and are not >> visible and shines trough other objects. >> >> The second approach seems to be easier for me as modeler, I only >> have to make the textures, but the current issues prevented my from >> using this method yet.
1) It is going too far to suggest that 3D is "good" and 2D is "buggy". 1a) It's true that the two don't always play together nicely, but this cannot be blamed entirely on the 2D system. 1b) Some of the bugs are clearly on the 3D side. See example below. On 12/28/2008 09:05 AM, James Turner wrote: > Okay, that's very interesting. I'd love to know what the specific > problems are with the 2D layers code, because some of them may be > fixable. See item (1) above. 2) To answer a slightly different question, here is an example of a bug in the 3D system. This is bug #56 on my list of bugs: 56:: Example: kr87Panel.xml uses the old mouse interface written by Dave Megginson et al. circa 2000. <PropertyList><instruments><instrument><actions><action><binding><command> In this case, I observe that holding down the mouse causes the command to repeat at a reasonable rate. Counterexample: kx165-1.xml uses the new-fangled "pick" animation. <PropertyList><animation><action><binding> In this case, holding down the mouse would cause the command to repeat at a rate that is much too fast to be usable. Having mouse events repeat at frame rate is not acceptable. Apparently the only workaround for this problem is to turn off the "repeatable" feature entirely, which is what kx165-1.xml does. I briefly looked into this, and found it's not easy to trace the code flow because of the callbacks. It wasn't immediately obvious where the "2D" code implements the repeat rate, or where the "3D" code should implement it. 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. ------------------------------------------------------------------------------ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
