Search the Community
Showing results for tags 'interface'.
Found 3 results
-
Hi Pete You will know that LINDA is built around FSUIPC4 and I have been doing some compile tests in 64-bit. The only issues/compile errors are in the code and data structures used to interface with FSUIPC. The main issue I have is with the DWORD usage - it does not appear to copy across to 64-bit in Delphi Pascal. 64-bit key types of concern are: Type FS6IPC_READSTATEDATA_HDR = packed record dwId : dword; dwOffset : dword; nBytes : dword; pDest : pointer; end; FS6IPC_WRITESTATEDATA_HDR = packed record dwId : dword; dwOffset : dword; nBytes : dword; end; Are there are changes to the FSUIPC5 external program interface data structure? LINDA will also need the full licenced version of FSUIPC5 once the ordering system is up and running.
-
Forum Languages: english, german, italian The special Mouse-Click-Interface: - more functions, single files, for each airplane, mouse-wheel ..... - the new Pilot Interface version: 1.5.5 With the new Pilot Interface you simulate in automatic the movements/hand of a Pilot or Co-Pilot. The Mouse-Click-Interface is included with CockpitStatus + Simcon. The new dedicated Manual: http://www.intrasystem.it/FSX/Mouse_Interface.pdf - All single actions can be saved within a dedicated Aircraft-Folder. - [Apl] listing all airplanes including Mouse-click files. - [Files] listing all single Mouse-click files not belonging to a single aircraft. - [Panels] opening single CockpitStatus Views. - Including 2 Buttons [VC] and [2D] switching directly from any actual FSX View to: ---- the standard 2D Cockpit Forward-View ---- or standard VC-Cockpit Forward-View. With the [Register Mouse] function you save any single click and execute for testing. Open a Switch-Cover, click on a switch, close Cover ...... Save as single File or within a dedicated Aircraft-Name.
-
Now I am developing the aircraft instrument interface of A320. I read and/or write access to internal variables of the Wilco Airbus aircrafts through FSUIPC offsets.Complex aircrafts like these can not be modeled using only the standard variables provided by Flight Simulator (FS2004 or FSX), so many variables had to be created to make all the systems work. The FSUIPC Exporter extends the list of available offsets to provide additional access to Airbus internal variables.I have installed FSUIPC EXPORTER,but I still can't read variables.Who can help me?
