I got this idea ..Why not ask MS to add a whole list of unused variables to their code. Like .. say "var001", "var002", ... , "var200".This way MSFS default planes won't use those but freeware/payware panel builders could store their panel data into those variables and provide us builders with a list ( var001 holds this data, var002 holds this data, etc) Then Pete could add those variables to the list of fsuipc and we would all be happy.Or would the creation of these variables in FS use up memory, while for most users (not-sim-builders) remain empty but still take up valuable memory ?Or perhaps it would be unhandy for the panel builders to use something like "var001" instead of a variable with a name they make themselves ... ?Either way I am quite sure that if payware panel builders would do the effort of adding the option to read/write data trough fsuipc and make a deal to reserve a memory slot with Pete, then promote cockpit building for their panel .. they might both:-encourage people to start building sims-encourage simbuilders to buy their product and build a sim around their panelMight be worht the try for one of them to see if this marketing strategy would pay off or not .. no ?

>This way MSFS default planes won't use those but>freeware/payware panel builders could store their panel data>into those variables and provide us builders with a list (>var001 holds this data, var002 holds this data, etc) Then>Pete could add those variables to the list of fsuipc and we>would all be happy...zap..>Either way I am quite sure that if payware panel builders>would do the effort of adding the option to read/write data>trough fsuipc and make a deal to reserve a memory slot with>Pete, then promote cockpit building for their panel .. they>might both:>-encourage people to start building sims>-encourage simbuilders to buy their product and build a sim>around their panelThis can be done through FSUIPC already, Pete has such offsets available. It's just that most people are not aware of the home cockpit stuff and what it requires, and more importantly, if they'd sell even 100 more copies of their product, it is not giving them anything significant in return. How much more would you pay for this? Then again, when you look how Joel reacted with Squawkbox3 when he was visiting a cockpit project, it opened his eyes and SB3 now will feature a fully interfaceable transponder with nifty offsets for COM1 tansmit and receive that can be used for a led for example, "controller in range" for the transponder blinker light etc.. People need to be told about what home cockpits are and what it takes to help us so their product can be more useful for this niche hobby. Somene might get excited.The new LDS "767 PIC v2" will have a SDK to access the variables I think. There was this offset list for PMDG 737, what happened to it, did it work at all, or was it critically incomplete? Those of you who have finished, working sims, what do you use if you built an airliner cockpit?Project magenta exists that does everything cockpit'able of course.//Tuomas

> There was this offset list for PMDG 737,>what happened to it, did it work at all, or was it critically>incomplete? It was critically incomplete -- not because of a lack of effort, but best I can tell, many of the things you want to be able to control (e.g. overhead switches) simply are not accessable via FSUIPC offsets. I spent a couple of days studying things right after Christmas (because I got an x-keys pro and wanted to use it to fly the PMDG 737), and it looks like the data just isn't there for the taking. The only things really available were the various MCP settings.What annoys me, though, is that many of the built-in things on flightsim aren't available via keyboard shortcuts... e.g. you can't press the 'heading' button on the cessna autopilot via keyboard, without -also- re-centering the heading bug on your current heading. Or, at least, not that I could identify.That one is probably accessable via FSUIPC, but I'm not currently aware of any programs that will just do keyboard->FSUIPC mappings (see this key, change this offset), so I don't really have a way to do it, even if it's possible. [Anyone have any hints on that one?]

>What annoys me, though, is that many of the built-in things on>flightsim aren't available via keyboard shortcuts... e.g. you>can't press the 'heading' button on the cessna autopilot via>keyboard, without -also- re-centering the heading bug on your>current heading. Or, at least, not that I could identify.>>That one is probably accessable via FSUIPC, but I'm not>currently aware of any programs that will just do>keyboard->FSUIPC mappings (see this key, change this offset),>so I don't really have a way to do it, even if it's possible.>[Anyone have any hints on that one?]You can do that via FSUIPC, see the Keys tab in that program.Just define a key(-combination) and assign the wanted FSControl function to it. There are generic FSControl function that can set, reset and/or toggle any bit, byte word or dword in the FSUIPC address space...Nicowww.nicokaan.nl

>Then again, when you look how Joel>reacted with Squawkbox3 when he was visiting a cockpit>project, it opened his eyes and SB3 now will feature a fully>interfaceable transponder with nifty offsets for COM1 tansmit>and receive that can be used for a led for example,>"controller in range" for the transponder blinker light etc..Great indeed, a good example for panel developers! I'm fully prepared for the release of SB3 with a COMM1 module with Rx, Tx and Voice Room connected leds http://forums.avsim.net/user_files/103449.jpgand a XPDR module with Ident button, ident led, Squawkmode Charly/Stby switch, text message for you led, and so on...For more details visit my website, Pedestal page.http://forums.avsim.net/user_files/103450.jpgNicowww.nicokaan.nl

>and a XPDR module with Ident button, ident led, Squawkmode>Charly/Stby switch, text message for you led, and so on...>For more details visit my website, Pedestal page.Seen it all :) Good inspiration..Can you access the privmsg data? You could get a small roll printer (our local electronics store had a bunch for EUR30 or so, old shop receipt printers) - put it behind a slot on the pedestal and have it print out the text message when one arrives .. ;-) Kind of like ACARS :)There's nothing more annoying when you have successfully eliminated the keyboard and mouse from sim flying, than to get a private message on VATSIM while enjoying the flight.. GAR! :)//Tuomas

>Can you access the privmsg data? You could get a small roll>printer (our local electronics store had a bunch for EUR30 or>so, old shop receipt printers) - put it behind a slot on the>pedestal and have it print out the text message when one>arrives .. ;-) Kind of like ACARS :)Tuomas,Unfortunately, the privmsg data is not included in the SB3 interface to FSUIPC.... :-( (see SB3, Plug-ins, FSUIPC)Nicowww.nicokaan.nl

Since SB3 maker is willing to help simbuilders out .. perhaps in the future if we ask ?Then I would think of yet another LCD instead of a printer :(

>You can do that via FSUIPC, see the Keys tab in that program.>Just define a key(-combination) and assign the wanted>FSControl function to it. There are generic FSControl function>that can set, reset and/or toggle any bit, byte word or dword>in the FSUIPC address space...Heh. I should have known that, really. I wonder why it slipped my mind at that particular moment...I plead 'temporary insanity.'

>I got this idea ..>>Why not ask MS to add a whole list of unused variables to>their code. Like .. say "var001", "var002", ... , "var200".Every single gauge defines its own variables.I have never ever did anything like that buy my guess is this:being much of the programming in c++, you can intance FS own variables or get the address of them and you can define your own variables both public and private.I think that since many many variables get defined "private" they are not accessible by fsuipc.In fact fsuipc just maps the memory used by FS (in a smart way) and that it can access.In theory, should Peter ever want to, he could hack his way into the protected areas and get whatever data he wants.So you can already define whatever you want, as long as you make it public (again this is a guess) fsuipc can read it.

>It was critically incomplete -- not because of a lack of>effort, but best I can tell, many of the things you want to be>able to control (e.g. overhead switches) simply are not>accessable via FSUIPC offsets. I spent a couple of days>studying things right after Christmas (because I got an x-keys>pro and wanted to use it to fly the PMDG 737), and it looks>like the data just isn't there for the takingThat's because, sadly, all the PMDG overhead (just like many many others, just about all) is fake.At least in terms of fs system operation.Nothing on the overhead (exept a couple switches, like the battery and master bus) acts on any Fs simulated system.Not even the fuel pump switches (i still wonder how the heck did they program that thing... if you have a look at it, when your engine is running and the switches are on, the Fuel Pump state in fs is 0, meaning off! but it never dies out...and it's on when the switches are off....).So it's not there because it's pretty useless.I was just redoing all the overhead in the fsbus CCC, but stopped waiting for a more stable version.

>>I got this idea ..>>>>Why not ask MS to add a whole list of unused variables to>>their code. Like .. say "var001", "var002", ... , "var200".>>Every single gauge defines its own variables.>I have never ever did anything like that buy my guess is>this:>being much of the programming in c++, you can intance FS own>variables or get the address of them and you can define your>own variables both public and private.>I think that since many many variables get defined "private">they are not accessible by fsuipc.>In fact fsuipc just maps the memory used by FS (in a smart>way) and that it can access.>In theory, should Peter ever want to, he could hack his way>into the protected areas and get whatever data he wants.>So you can already define whatever you want, as long as you>make it public (again this is a guess) fsuipc can read it.Yea, I dont know anything about gauge programming either, but AFAIK gauges can access the stuff directly. Now, I wonder if it would be possible to make *a gauge* that interfaces with the stuff of those panels and then pipes stuff into the "unused" offsets of FSUIPC?This would of course require reverse-engineering or knowing more about the internals of such panels..?//Tuomas

>Yea, I dont know anything about gauge programming either, but>AFAIK gauges can access the stuff directly. Now, I wonder if>it would be possible to make *a gauge* that interfaces with>the stuff of those panels and then pipes stuff into the>"unused" offsets of FSUIPC?>>This would of course require reverse-engineering or knowing>more about the internals of such panels..?As i said, should the variables be defined "private" there is no "legal" way to access them.You have to use external programs to find the protected memory areas and try to read the values.And BTW many many things in a gauge are totally useless.It's practically a waste of time and effort.