-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Paul Surgeon schrieb: > Running Nasal code in the rendering loop to do tons of work would not be a > very good idea in my opinion. > I've looked through an A320 FCOM manual and it would take many thousands of > lines of C++ to accomplish a half functional aircraft. > I don't think Nasal is the tool for the job. > > What I would need to create a aircraft with glass cockpits is : > > 1. > A way to code self rendering OpenGL intruments. i.e. The renderer loops > through the intruments and lets them do their own rendering.
As I wrote in the other mail I think we need to explore how to render to an texture and use that texture in an instrument. Then it's no problem to write C/C++ code that renders (a part of) an instument to that texture. This could then be added to NASAL (plus some basic OpenGL commands) to create a full MFD out of these bulding blocks. > 3. > A generic communications bus that can be used to hook instruments/switches > and > the blackbox together. Using a handful of sockets is not a good way to do it > and properties maybe be a bit messy and I would require hundreds of them. Why not use the property system for that? So far I found the property system very good for unidirectional communications (I'm responsible for system "foo" and tell everybody that it is in the state "bar"). But I couldn't solve a bidirectional point-to-point communication with it (I need from system "foo" the state of "bar" at position lat/lon somewhere on the world) - but it doesn't sound that you need such a capability. CU, Christian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFB7UHQlhWtxOxWNFcRAgHDAJ0cazzJtFS+2SS04x2SyEUrpMEuOwCgsWQi AalCWiCgYBHCwUl6t94ZtcU= =7qmi -----END PGP SIGNATURE----- _______________________________________________ Flightgear-devel mailing list [email protected] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
