Hi,I was wondering, will the initial release support a FSUIPC based interface for the LDS767 Custom controls?It would be very convenient in my home cockpit, to have FSUIPC variables for most controls, as an alternative for the Keystrokes. And the other way round, it would be very nice to be able to access the state of switches/lights/leds in the sim in order to have my hardware synchronised.And what about the extra ILS in the Pedestal, can that one be accessed via FSUIPC?Hope you are able and willing to answer these questions.Thanks and Best Regards,Nicowww.nicokaan.nl

You should be able to assign a keystroke to just about any function through the program's own menu.

>You should be able to assign a keystroke to just about any>function through the program's own menu. Yes I know, but that was not my question... I asked: will there be an alternative for keystrokes via FSUIPC variables? Like there already are for more generic FS2002/FS2004 functions such as parking brake set/release... (See "FSUIPC for programmers.doc for a list of available variables.)A FSUIPC interface is much more reliable compared to keystrokes.Nicowww.nicokaan.nl

Hey ####The original version of PIC did`nt rely on FSUIPC so why would this one?Plan accordingly!!Troy

You are not a home cockpit builder, are you?Otherwise I do not understand your reaction. Please read my postings carefully. ;-)Nicowww.nicokaan.nl

No it will not.Regards,Wade

>No it will not.>>Regards,>WadeThanks for your answer Wade. Although it's a disappointing it's good to know. Now i'm gonna try to simulate the state of switches and leds via software I'll write myself (like I already did for the fuel config led). Without the real state information from the sim.it will be more prone to errors, but it's better the nothing...Regards,Nicowww.nicokaan.nl

Nico,I remember that they have mentioned the release of a full-blown SDK some time later on after the first release of LDS767.As we all know, PIC has never been dependant on FSUIPC, but that doesn't mean that with the help of an SDK the variables of the sim couldn't be utilized ;). I would imagine that the SDK could perhaps contain an interfacing module of somekind, and us sim builders could write our own programs to do whatever we like.bw,Tero

Nico's idea of using FSUIPC is not a strange one. On the contrary, it's a clear example of forward thinking, based on earlier statements of the team (see attached picture).Wade: I can understand that the first release will not support all the goodies, but can you shed some light on the future plans (support of Aerosoft MCP, internal variables)?Kind regards,Stephan Haaswww.lemont.nl/b767flightdeckhttp://www.pic767flyingclub.com/images/sas544.jpg

I'm sorry Stephan I can't say any more now. We will let you know as soon as there's more to tell.Regards,Wade

I'm sure there will be in the future a way to access the internal variables..Wade will probably make all variables read only if we are ever able to access them.. You wouldn't want a malicious programmer making a program that would randomly alter different internal variables and make the plane unflyable.. And variables that you could want to change would probably be the FS variables like fuel which can be read/write via FSUIPC.. Nico is right though, he had to write his own program to trigger an LED for FUEL CONFIG. If the internal variables were accessable without hacking it then you wouldn't need that program, you would just need a program to extract the variable and trigger the led if said variable is true or 1 (binary).. LOLI want to build a 767 replica cockpit in the future and I would love to use the LDS 767 as a model for it. The big issue I would have is the guages, if we can display the guages without the panel so we can place them against a black background for putting on a monitor behind the panel.. Similar to Project Magenta.MHO...

>Wade will probably make all variables read only if we are ever>able to access them.. You wouldn't want a malicious programmer>making a program that would randomly alter different internal>variables and make the plane unflyable.. ? Well, why would somebody want to do that? And such a person has to have access to your computer for doing that. Take a good firewall and a virus scanner and you're pretty safe.Even today in FS2002 or FS9, it's possible to randomly change important flightsystem variables that make your PIC767 or any plane unflyable. Take for instance NAV1, NAV2, COMM1, CRS, pause or slew mode. All these varaibles are writeable via the FSUIPC interface... And remember, also with the Custom Controlled key-strokes that are present in PIC767v1 and will be available in v2, you can do a lot harm. A malicious programmer could write a program that randomly generates the key's for engine fuel cut-off toggle, for instance, not to mention landing gear, flap settings and what have you...No, a R/W interface via FSUIPC would give the PICv2 an enormous sales advantage over other panels in the field, IMHO. And think positive! Regards,Nicowww.nicokaan.nl

Wade,Hope you'll surprise me one day!Kind regards,Stephan Haaswww.lemont.nl/b767flightdeckhttp://www.pic767flyingclub.com/images/sas544.jpg

>Even today in FS2002 or FS9, it's possible to randomly change>important flightsystem variables that make your PIC767 or any>plane unflyable. Take for instance NAV1, NAV2, COMM1, CRS,>pause or slew mode. All these varaibles are writeable via the>FSUIPC interface... >>And remember, also with the Custom Controlled key-strokes>that are present in PIC767v1 and will be available in v2, you>can do a lot harm. A malicious programmer could write a>program that randomly generates the key's for engine fuel>cut-off toggle, for instance, not to mention landing gear,>flap settings and what have you...You do have a point.. Never thought of that.. However, direct access to the variables will make full scale cockpits easier to model..