Free 777 Instruments

[Guest rprather]

I have created a smaller version of the 777 Collection, which is available for free (no timers). It may be useful for those who just want basic functionality, or who just need a space filler, etc.http://www.t-b-x.com/prather/777project/77...lectionDemo.zip The documentation is the same, and the displays are selectable using the function keys (F1-F5 or 6 I believe)http://www.t-b-x.com/prather/777project/77...er%20Manual.zipI will likely re-post the Airbus instruments in May, for free, for anyone who wants them (if anybody is interested)...Enjoy!Roberthttp://777Simulator.comhttp://HSBRegistry.com

[Guest PoRrEkE]

What's all this ?

[Guest spiliot_]

Robert I'm glad that you decided to do that. I never had the chance of seeing the a320 software, but from what I see in your panel pictures, if it is half as good, it'll be just great!

[Guest PoRrEkE]

Ah .. now I found the info is on your page under the "software" link.How hard is it to make something like this ? What software programming knowlege is required ?

[Guest yoss]

Great stuff and for free..Tnx a lot , Robert

[Guest rprather]

>How hard is it to make something like this ? What software>programming knowlege is required ?The core programming is not very difficult, but synoptic displays are EXTREMELY EXTREMELY extensive in detail. The primary flight displays are more "what you see is what you get" (although they can get complex). But the synoptic displays are VERY interlaced, and trigger many different hardware/software events based on infinite combinations of events. Hence the problem with EICAS messaging.Keep in mind that synoptic displays have to read/control the majority of the switches in the aircraft. So even with the frontend portion done, the backend components can become extensive. If you only want a "display" that shows data directly from MSFS, it's not terribly difficult to write though. Just time consuming.The conditional statements become pretty wild with things like engine starts, where it depends on many conditions being met (i.e. is APU running, is fuel available, are bleed air ducts set, which DC/AC electric busses are available, N2 monitoring, fuel switch positions, etc).The final verdict is that the code is not terribly difficult, they can just become quite time intensive to develop.Robert

[tigert]

>The conditional statements become pretty wild with things like>engine starts, where it depends on many conditions being met>(i.e. is APU running, is fuel available, are bleed air ducts>set, which DC/AC electric busses are available, N2 monitoring,>fuel switch positions, etc).Heh, then there's always someone to complain when engines wont start up with just Ctrl-E! :^)//Tuomas

[Guest PoRrEkE]

So can you teach us ? Or is there a way to change the things you got already for F50. F50 Don't have no EICAS. Just the virtual horizon, engine (analogue) gauges and the NAV instrument.

[Guest rprather]

>So can you teach us ? Or is there a way to change the things>you got already for F50. F50 Don't have no EICAS. Just the>virtual horizon, engine (analogue) gauges and the NAV>instrument.It's all about programming strategy and REALLY studying the systems of whichever aircraft you want to develop. Visual Basic is typically the easiest language to use for developing displays, but the refresh rates aren't very good if there is a lot of motion (unless you use OpenGL VB). This is usually not an issue for synoptics though since they only need to update maybe once per second (versus 20+ times per second with primary displays)It's best to start with a low-graphic display, which contains basically only lines and text labels. Practice synchronizing the text with MSFS, then try using conditional statements to change the color of a line (or the text) when a specific condition is met. This is the simplest form of a synoptic display. Although condition statements may become more complex, or more lines may be controlled by a particular event, everything on a synoptic is fundamentally an indicator or a readout. Newer airplanes, like the 777, incorporate static graphics on the screen to make things look good. However these components are easily reproduced.Robert

[Guest PoRrEkE]

I have tried using Visual Basic for making analogue gauges to show on a display (digital shown analogue gauges) but I didn't manage to get it right. I can read FS data from my software in VB.Net so there's not the problem. The problem I got is making things move. If it were slider bars it would be easy. Making a triangle move up/down on a line is easy. Rotating a needle however .. I got no idea where to start.That's where I get stuck .. the graphics that move. Let alone that I would know how to make a virtual horizon.EICAS with text or lines that change color etc would be easy but I don't need that in F50.If only there was an option in VB.Net to rotate something by some given degrees ... that would solve a lot.

[Guest twabi2]

maybe consider openGL, as VB never was never really ment for motion programming (unless with openGL ;) )

[Guest migzz]

yep... thanks for giving us a free version... something to fill up my screen...

[Guest PoRrEkE]

yes but where can i find openGL for dummys online starters guide ?

[Guest twabi2]

http://nehe.gamedev.net/These are great tutorialsonly for Visual C++ tough

[Guest PoRrEkE]

I am checking it. Seems most interesting !Meanwhile I also managed to make a line rotate in VB.Net code with a picture as background. As you say VB.Net is not super for graphics but in case the OpenGL gets over my head I can still go back to that.Tnx