Jump to content

Highest Reputation Content

#417029 Updated modules

Posted by Pete Dowson on 18 October 2010 - 11:14 PM

Note that mostly this Announcement will contain only the changed modules. You will almost always need the main release installed first. For those please go to http://www.schiratti.com/dowson

The FS modules here, when supplied without Installer, need copying into the FS modules folder once extracted.

Please note the format here. The links for all the updates are listed first. For interim releases only, notes about changes are listed separately, below.

Install complete FSUIPC version 3.999z8 Install FSUIPC 3.999z8 for FS9 and before

-- For changes see the History document in the full install update.

FSUIPC version 3.999z9a only, for those with 3.999z1 or later already installed FSUIPC 3.999z9a

-- Fixes an ancient and obscure bug which nevertheless can crash FS on loading with certain INI file arrangements.


Install complete FSUIPC version 4.934 Install FSUIPC4934 for FSX and Prepar3D versions 1.4 and 2.0, 2.1, 2.2

-- Main change is full support for Prepar3D versions through to 2.2 build 10438.

-- NOTE: it is not compatible with the original release of P3D 2.2. You must apply the hotfix from Lockheed Martin!

--                   (Get it from the link in this P3D message:http://www.prepar3d....iewtopic&t=6453)

-- Please see the History document after installation for full details of changes.


FSUIPC version 4.934a, for those with at least 4.931 already installed FSUIPC 4.934a

-- Adds facilities for Profiles in separate files

-- Fixes display of parameter value -2147483648 or x80000000


WideFS version 6.999m WideFS 6.999m
Full release including documentation.
-- signature removed

-- See WideClient changes below.


WideClient 6.999m WideClient 6.999m
-- signature removed
-- 6.996 adds a colour facility to ipc.display.
-- Wideclient 6.997 with "event.textmenu" support in Lua (FSX only)
-- WideClient 6.998b supports text menus with more than 400 characters using FSUIPC 4.909 or later.
-- WideClient 6.999 fixes an odd bug when applications connect with bad Atom names.

-- WideClient 6.999b fixes a problem with Radar Contact options when generating APL plans from PM's CDU.
-- WideClient 6.999i supports extra Lua functions: see FSUIPC4 History

-- Wideclient 6.999j adds event.offsetmask.

-- The ButtonScreen now sends no button change for positions without a label or with a single space as a label.

-- Plan generation from the PM CDU "Route.bin" file deals with the latest format containing 'degree' signs.

PFC driver version 2.41 for FS9 and earlier PFC 2.41
PFCFSX driver version 4.41 for FSX, ESP and P3D PFCFSX 4.41
-- signatures removed

PFC HID device driver version 1.41 for FS9, FSX, ESP and P3D PFCHID 1.41
-- signature removed
-- 1.33 fix for AP APR mode not setting Glideslope option

-- 1.34 fix for macro name matching and proper macro file selection on aircraft change

-- 1.35 fix for a silly bug introduced in 1.34 which could significantly slow FS down!

-- 1.36 eliminates a 1-2 second pause when AutoSave options are in use

-- 1.37 added support for separate macros for positions on multiway switches

-- 1.38 and 1.39 only added clearer logging, especially for macro file selection

-- 1.41 fixes some further macro selection problems


Pete Dowson
16th June 2014

  • 3

#451010 New FSUIPC4 registrations for 2013 need version 4.859n or later!

Posted by Pete Dowson on 14 January 2013 - 05:26 PM

Oops. Same date limit was in FSUIPC4 too!

  • 2

#450631 FS Commander won't let me load flightplans?

Posted by JerryJet on 03 January 2013 - 12:42 PM

So it can save flightplans in those formats, but can't then reload those very same flightplans unless they exist in FSC's format? And I paid $40 for this??? Can I just say how stupid that is?

Flightsim Commander is released as shareware letting you evaluate the program to see if it suits your needs. You can also read the exhaustive manual which explains how and why FSC saves flightplans. Numerous different planes/companies can be chosen when saving, but one is always checked and can never be unchecked. I'll let you figure out what that means.

  • 2

#470088 Engine Start

Posted by Pete Dowson on 23 July 2014 - 02:44 PM

Excuse me if i'm posting in wrong section


You aren't in the wrong 'section', but yours is a new question and you are appending it to an existing thread about a different matter. I'll answer it here, but please, when you have a NEW question please start a new topic. You'll see the button to do this. Then entitle the topic with something relevant.


How I can read PMDG737NGX HDG bug value by visual basic ?

I need a basic example


I'm afraid I don't use VB so I can't tell you myself. Have you looked at example code in the FSUIPC SDK? It can't be too hard. It might be even easier if you use Paul Henty's .Net interface (see separate subforum above)..


If you really want more help then you need a topic entitled with a question which will attract the folks who can help.



  • 1

#469916 Sim Physics and anti-ice

Posted by BD-FSPS on 14 July 2014 - 08:51 PM

Indeed. If that happens then the aircraft manufacturer is not following FSX SDK to the letter, and when switching the antiice button the relative FSUIPC offset is not -as it should- updated.


So yes, only way to make it work is via the button in Sim Physics interface. We predicted that some aircraft would work that way, and we implemented the button for situations exactly like this.

  • 1

#469764 FSX Fiber Accelerator - Question about fps in air

Posted by BD-FSPS on 08 July 2014 - 01:31 PM

Hi Jan,


Fiber Accelerator is not only a "give you frames" application. Its job is to :

1) "Trying to give you the target frame rate when you are on a difficult situation"

2) "If you are on an easy situation tries to gives you the best possible graphics at max distance, keeping the frame rate" and

3) "If it can keep the target frame rate AND the best possible graphics THEN give further frames".



on 1) As you say you are OK. Difficult airport... Gives you frames sacrificing visuals you cannot see.

2) On air situation should be easier but in your case is not. I am sure while flying your CPU terrain power is not staying at 100%. If it was you would go to situation 3)


In other words... you are on "Phase 2) " but not yet on phase 3) ... 

  • 1

#469603 Frustrating UX - why I'll stop using FSC

Posted by jhaley101 on 04 July 2014 - 08:32 PM

Well, glad to see that you did end up reading the manual, but perhaps not as closely as you may think.    Seriously, for FSC, if you can't spend the time to read about the product, you're better off using something simpler.   Most of the items you have listed are personal adjustments.  The frustration you experience, is coming from a lack of using the program, IMO.  


It's a super program but it does take some time to master its finer points.  


BTW, there IS zoom a attached to the mousewheel.     Under Window, Options, Flight - check the box that says "Zoom with Mouse Wheel".   Easy to find and easy to adjust.    


The "simple truth" of this program is that you need to spend more time using and reading about it.   You may be able to click, click, click with some programs, FSC is not one of them.  


I admit it took time to adjust some settings, but after a regular bit of use, FSC is a breeze to program and manipulate.  



  • 1

#469593 Frustrating UX - why I'll stop using FSC

Posted by Matthew Merrill on 04 July 2014 - 04:44 PM

Greetings folks,


I purchased FSC 9.3 a while back so I could have a decent flight planner. I don't use FSC for anything else. It appeared to be able to get all the necessary information I needed with the ability to plan.


However, after using FSC for awhile I've found that the User Experience (UX) is too frustrating for me. I don't want anyone to think that I'm bashing or flaming this product. I'm not. I just want to express my frustrations and hopefully they may be addressed in the future.


One of the issues that I would like to bring up is documentation. Even though everything we need is in the help file, the simple truth about end users is; they don't read documentation. They install, fire up the program and click click click away. This mean the developers have the burden of intuitiveness. For the application to be successful there must be some intuitive programming involved.


Here are some of the frustrating issues that I've come across:




1. The single left click-move-to-clicked-spot is a very difficult way for me to move around. I find that left-click-hold-and-drag is much more intuitive. There have been many times where I've tried to move like this and all I've done is zoom in on a map area.

2. There is no zoom attached to the mouse wheel. This is also an intuitive response from end users.




1. After reading the manual I found how to use Navaid and Low Alt together for a flight plan. However, the method is very difficult to find. A user has to read the manual. By default when users add Navaids and intersections they should be addressed as such. So the mixed plan should be a default mode.


2. When adding intersections and navaids by typing in the string value the plan defaults back to Low Alt. All Navaid types are converted.


3. After typing in a long string of waypoints, if the destination airport is a typo (such as KDRR instead of KRDD) a message pops up stating the destination does not exist then the plan gets wiped out. Very frustrating.


4. After making a mixed flight plan I manually add a new waypoint, after which the entire plan is converted to Low Alt.


5. Once I felt I was done with the flight plan I clicked the "OK" button assuming that meant "OK we're finished with the plan". Instead the flight plan is converted to a Low Alt plan. Once again frustrating.


6. When editing the flight plan if I click a waypoint the maps gets zoomed to that area. This can be a problem since the area I want to work in is not at that waypoint.


Again, this is not bashing and saying this is a bad application. It is a good application, just too frustrating for me to use.


I hope that the developers will consider some of this feedback as positive.





  • 1

#468858 My Traffic in P3D 2.2 - Green taxiways?

Posted by Burkhard on 10 June 2014 - 03:31 PM

Still 2000 to go, 600 done now....

  • 1

#468295 Microsoft Visual c++ 2010 message error

Posted by FeelThere on 22 May 2014 - 10:43 AM

First please try to ignore this message. If it still fails make sure to uninstall any previous version of MS C++ then run our installer.


Thank you



  • 1

#468241 Read / write hardwares values for FSUIPC (module for FS)

Posted by Pete Dowson on 20 May 2014 - 01:41 PM

Hello Pete, thanks for your response. I decided programming in C to start learn my own connection with sim. But i have the first problem: I can't compile the UIPCHello example.

In 'UIPC_SDK_C' folder i have intructions to put the header file and the LIB in my source folder. So, i have IPCuser.c and IPCuser.h in folder of complier includes. But when i compile, it gives me a several 'Linker Error':


There's an art in trying to get projects set correctly in Microsoft C. You need to make declarations for the libraries you are using. there's all sorts of arcane magic to getting things correct. If you are a beginning programmer, then C is really not a good choice.


You might want to consider Visual Basic and Paul Henty's easy-to-use .Net DLL -- see the subforum about this.


In your example of connection (UIPCHello), in function FSUIPC_open i dont have any reference to FSX, only until FS2004. I have to create a connection for FSX?


Just use the ANY option. The Header file defines the options, though it might be out of date for FSX and P3D. The current Programming and Offsets guides are the best references.


I'm afraid than in the last few years much more attention has been afforded to the Lua plug-in facilities, and these are generally so much easier for new programmers and experimenters. Even though i do write fluently in C I still use Lua for many things, or for prototyping something i later code in C.


I have an unregistered version of FSUIPC, is this a problem?


No. Access through the interface is free (except for commercial purposes).



  • 1

#468234 strange problem with EFB

Posted by wildeboer on 20 May 2014 - 11:20 AM

hallo pete, the reason that searching outside Aivlassoft is that the also not know how to solve the problem .


And the very strange thing is there was never a flightplan to KGBD .And it is not a EFB problem because display unit sends the FP to the data unit and i can see that the dataunit loads the fp.

and than in the gps comes prvpos-kgdb.

Is there a possibility that in FSX is some checkmark that prevents a FP entry from an other source other than FSX



  • 1

#468207 Lua programs to access your Saitek Radio, Switch and Multi panel

Posted by kamarad on 19 May 2014 - 08:22 PM



This post explains how you can use a LUA routine to access the status of the buttons/switches/selectors/gear and flaps lever and trim wheel (herewith named collectively as Buttons) on 3 Saitek panels using FSUIPC and Linda. The first section presents a quick instruction to start gathering information  based on lua program attached to this post. The second section gives a simple example of a Lua program that access the Saitek panel buttons status and select specific FSX/P3D actions accordingly. The third section goes more into the details about how this LUA programs was made.


You need a registered version of FSUIPC for this to work.


Section 1 – Quick Start


Download and install the relevant LUA routines;


Attached to this post are 3 Lua programs corresponding to the 3 Saitek panels. You just need to install the ones corresponding to the panel you own.  The 3 Lua programs are:


-          HIDRadio.lua

-          HIDMulti.lua

-          HIDSwitch.lua


Note; I have renamed the 3 programs with a .txt exension for upload as the system doesnt allow to upload .lua files. You will need to change the extension back to .lua before using them.


To install them, just drop the ones corresponding to the panel you own into the “module” directory of FSX/P3D.


Automatic start of the LUA programs


The LUA programs selected above must run in permanence to scan the status of the buttons and map (copy) this information into specific address of the FSUIPC offsets. To inform FSUIPC that those programs must start and run continuously, it is necessary to add the following lines to the FSUIPC.ini files (located in the module directory of FSX/P3D).



1=lua HIDRadio

2=lua HIDMulti

3=lua HIDSwitch


On the next start-up of FSUIPC, the Lua program will start to scan the status of the buttons and selector on Saitek panels.


Checking with FSUIPC logging facility that the Lua programs are in place and operating


FSUIPC has a built in logging facility that can be useful to check the proper operation of the Lua programs and the correct mapping of switches to the offset address.


Go to the FSUIPC Logging tab and on the right part of the screen, enter the following information:


Offset   Type of data       Remark

3358       U32                        Saitek Radio panel offset address

335C      U32                        Saitek Multi Panel offset address

3360       U32                        Saitek Switches Panel offset address


Then click on “FS window” and you should have a green message on the top left of your screen. Move some selectors or push buttons on each of your panels and see if the values on screen change according to the position of the buttons. An annex at the end of this post gives the value of each button.


Note1  : The knob just send a short pulse so the number on screen will just change very rapidly and come back to the value prior to moving the knob when you stop moving it.

Note 2: The buttons just change status while they are pressed, they doesn’t indicate the status of the corresponding function. Ex: the Autopilot button will just send a ON status when you press the button. So this is not intended to test if functions like the AP are engaged or not. It’s just to test the instantaneous position of the hardware buttons.


Make sure you have version 4.934 as the previous one has a problem that killed lua programs on start-up and caused me a couple of evening of head scratching... 4.934 solved this as soon as I installed it.


Accessing the information from within a LUA program in Linda


Now everything is in place and you have the possibility to access the information on your panel switch.


For simple assignation of a single button, you usually doesn’t need complex programming as FSX, Spad or Linda menu all allow you to directly select FSX/P3D commands. On the other hand, if you want to combine the status from different buttons to trigger a specific FSX/P3D action, then you need to use a Lua program (you can also use FSUIPC conditional button programming but Lua is more flexible).


Using Linda, it is possible to assign user created Lua program to a button so the program is called when the button is push (or a switch is move to the “on” position or a selector is put in a specific position). The Lua program allows you to test the status of others buttons and makes your program act accordingly to send the proper FSX/P3D command.


In Linda, you can create individual LUA program module (a module can contain several Lua program) for each aircraft. Linda includes also a text editor that makes creation of Lua program easy. Some functions in the Lua library allow reading specific address in FSUIPC offsets. Each address that will be assigned to the 3 Saitek panels covered here will contain between 18 to 20 bits of useful information (not considering the LED display) that correspond to all the buttons, switches, selectors and gear and flaps lever of the panel. The switches panel for instance contains 20 bits of information that you can test. The address to use in order to read each panel information are:  


0x3358 = Radio panel

0x335C = Multi panel

0x3360 = Switch panel


Note : You can assign other address if those one are already used for other purposed on your setup. You will need to modify the HIDxxx.lua program that correspond to the device you want to change.


Note: The "0x" in the adress above just means that its written in hexadecimal notation. You will need to include the 0x within Lua program otherwise it will consider that the address provided is decimal. Please note that in the FSUIPC logging page, you don’t need to include the 0x as this page always consider that the value entered is hexadecimal.


There are two main functions within Lua programs that can help you to read buttons status.


First, the following Lua program line read all the bytes of information from the Saitek Radio panel and put it in a variable named “pos”.


pos = ipc.readUB(0x3358)


But the value returned is not quite useful by itself as it represents the cumulative sum of all the individual bits for switches that are in the “on” position resulting in a large number of possible values. You then need to isolate the value that you are specifically interested by using the following function (here represented in a separate line).


pos = logic.And(pos,mask).


Here mask correspond to the specific value (or sum of values) you are interested in. For instance, if you are interested to test if the position of the magneto switch is at the “right” position on the Saitek switch panel, then the value for the mask is 32768 (see annex for all possible values) and the Lua program line becomes


Pos = logic.And(pos,32768)


Section 2 : Example for the Duke piston or Douglas C-47 Magneto selector


In the Duke Piston from Real air (and Douglas C-47 from Manfred Jahn), the magneto animation in the VC are reversed compared to the Saitek switch magneto button for the “left” and “right” position which create a weird jump in the VC while you move the magneto selector on your Saitek panel.

-          Duke Piston/Douglas C-47 VC magneto selector order: Off – Left – Right – Both – Start

-          Saitek Switch panel magneto selector order: Off – Right – Left – Both - Start


So the objective is to program a function in a Linda module that will reverse the operation of the left and right magneto position between the Saitek panel and the VC. In addition, we want to test the position of the upper mode button for the Saitek radio panel to determine if we want to operate the motor 1 or 2. Spad has a built-in functionality that allows using several switches (ex: Aternator, fuel pump, cowl, de ice)  to act on motor 1 or on motor 2 according to the position of the top selector on the Radio panel and we want to replicate this functionality here.


First you need to create a module for your targeted aircraft if it’s not already existing. See Linda documentation to do this.


Then you need to copy the following program (or use the Magneto.txt file provided) into the aircraft module using Linda editor screen. Again, refer to Linda documentation to see how to open the editor.


The title between double hash characters is recognized by Linda as a heading separator for functions. It makes easier to identify function you have created.

Comments (text preceded by --) in the program below provide detailed comments for each steps.


-- ## Magneto ##


Function MagLeftVC ()


-- This function handle the reversal of the magneto in the VC panel compared to the Saitek selector.

-- It is activated when the selector on the Saitek switch panel will be put at the left position. 

-- It will result in positionning the VC magneto selector to the "right" position.

-- The Saitek Radio top left selector at position COM1 means that the left engine is considered. If the selector is at the COM2 position, then the right engine will be treated.


-- The information about the radio panel status is at offset 0x3358

-- reading the offset to get all Radio panel switches current status


pos = ipc.readUB(0x3358)


-- The next line of lua code will isolate the bits of information we are interested in

-- mask = 1 would be usefull ot test if the top left selector at the COM1 position

-- mask = 2 would be appropriate to test if the top left selector at the COM2 position

-- Mask = 3 accept both COM1 and COM2 and will return either 1 or 2 as the selector

--   can be only in one of the two positions at a given time.

--   If the selector is not at COM1 or COM2, then the logic.And function will return zero and no action will be done.


pos = logic.And(pos,3)


-- the next group of lines will send the command to put the magneto for left or right motor in the right position in the VC.

-- 66400 is the Magneto1_set command for FSX/P3D

-- 66401 is the Magneto2_set command for FSX/P3D

-- The parameter 2 is for the “right” position of the magneto


if pos ==1 then ipc.control(66400,2)

else if pos ==2 then ipc.control(66401,2)




Function MagRightVC ()

-- same approach as for the left mag function, without comments here

pos = ipc.readUB(0x3358)

pos = logic.And(pos,3)

if pos ==1 then ipc.control(66400,1)

elseif pos ==2 then ipc.control(66401,1)




Section 3 – Nut and Bolts.


This section provides some additional explanation on how the HIDRadio.lua program was created from the HIDDemo.lua program provided by Peter.


Step 1: Obtain HIDDemo.lua


We need to have a Lua program running continuously to scan the Saitek panel switch status then map this information in FSUIPC offset. The offset can then be read from a Lua program in a Linda module for an aircraft. Peter Dowson provided an example of a Lua program that scan HID device like the Saitek panels and write the information on offset. We just want to use his demo and modify it a bit.


The HidDemo.lua program is available in the complete install of FSUIPC4.


Or you can download the latest HidDemo.lua  example from : http://forum.simflig...and-wideclient/


Step 2: Create HIDRadio.lua


Make a copy of HIDDemo.lua and name it HIDRadio.lua (we will give only one example herewith but the same approach works for the switch and the multi panel also).


Step 3 – Adjust HID device identification


At the beginning of the HIDDemo.lua program, there is two lines that identify the Saitek panel (HID device) you want to communicate with. You have to insert the hexadecimal code for the vendor and for the product.  For instance the lines for the Saitek radio panel are:

-- Saitek Radio panel

Vendor = 0x06A3

Product = 0x0D05


If you dont know the HID device codes, there is a utility provided by Peter Dowson called HIDscanner.exe that gives a report about all devices connected to your PC and their vendor rand product codes.


I already run this utility to find the relevant information of the 3 following Saitek Products.


Radio Panel :

Vendor = 0x06A3

Product = 0x0D05

Multi Panel :

Vendor =0x06A3

Product = 0x0D06

Switch Panel :

Vendor =0x06A3

Product = 0x0D67


The HIDScanner.exe utility is available at the same link provided above on Peter support page.


Step 4 : Change the size and destination of information blocks


In HIDDemo.exe, you will find a loop of instruction toward the end of the program that read the status of the buttons on your HID device and copy it to a specific offset.  The loop is initially programmed for reading 8 blocks composed of 4 Bytes of information. For the Saitek panel switches, you only need to do it once as all information fit into a double world (32 bits of information).  So I cleaned the iteration loop (from 1 to 8 and adjusted the HIDDemo.lua program to do a single read of a 32 bits of information that is sufficient for the Saitek panels.


Next, you need to select the destination for the button information in the FSUIPC offset table. There is an ipc.writeUD instruction in the HIDDemo.lua program that was modified to correspond to an offset that was used for mapping.


The possible offset for the 9 contiguous blocks of 4 bytes (32 bits of information) are: 0x3340, 0x3344, 0x3348, 0x334C, 0x3350, 0x3354, 0x3358, 0x335C, 0x3360. See the “FSUIPC4 Offset Status.pdf” document provided with FSUIPC documentation. The Saitek version of HIDDemo.lua use the 3 last virtual joystick addresses so Joystick 71,72 and 73 located at 0x3358, 0x335C and 0x3360 respectively.


Step 5 : Install your newly created Lua program


Just copy them it in the “module” directory of FSX or P3D. If you have started with the quick start portion of this document, you have already done this.


Step 6 : Automatic startup of HIDRadio.lua


To start automatically your Lua program add the following lines in FSUIPC.ini. If you have applied the quick start instruction, its already done.



1=lua HidRadio


Step 7 : Create custom lua program


See the example provided for the Duke above.


Annex: Saitek panels reference of  “buttons” value


Saitek Radio Panel (20 bit of information + 2 bit unused)


Top left mode selector

1= Com1

2= Com2             

4= Nav1

8= Nav2

16= Adf

32= Dme

64= Xpdr

Bottom Left mode selector

128= Com1

256= Com2

512= Nav1

1024= Nav2

2048= Adf

4096= Dme

8192= Xpdr

16384 = Top right ACT/STB button

32768 = Bottom right ACT/STB button

65536 = Clockwise turn of the top knob

131072 (2E17)=Counter-clockwise turn of the top knob

1048576 (2E20) = Clockwise turn of the bottom knob

2097152 (2E21) = Counter-clockwise turn of the bottom knob


Saitek Multi Panel (20 bit of information)


Selector button

1= Alt

2= VS

4= IAS



32= Clockwise rotation of knob

64= Counter clockwise rotation of knob

128= AP button

256= HDG button

512= NAV button

1024= IAS button

2048= ALT button

4096= VS button

8192= APR button

16384= REV button

32768= Auto Throttle switch ON

65536= Flaps up (2^16)

131072= Flaps down (2^17)

262144= Elevator Trim Pitch up (2^18)

524288= Elevator Trim Pitch Down (2^19)


Saitek Switch panel (20 bit of information)


Note: The minimum value returned corresponds to the position of the landing gear handle plus the position of the magneto knob. 262144 is returned if the gear lever is UP and 524288 if the gear lever is DOWN.


1= Battery

2= Alternator

4= Avionic

8= Pump

16= De Ice

32= Pitot heat

64= Cowl

128= Panel

256= Beacon

512= Nav

1024= Strobe

2048= Taxi

4096= Landing


Magneto selector

8192= Off magneto

16384= Left Magneto

32768= Right Magneto

65536= Both Magneto

131072= Start Magneto

Landing gear lever

262144= Landing gear Up

524288 (2E19)= Landing Gear Down

Attached Files

  • 1

#468136 Accu-Feel v2 & impact on performance

Posted by Ian P on 17 May 2014 - 02:32 PM

Yeah. I might have messed about with the 172 a bit...






Ian P.

  • 1

#468118 Profile for multiple aircraft of same type - CX750

Posted by aua668 on 16 May 2014 - 03:58 PM



You need just one entry in your C750 Profile:


1=Eaglesoft Citation X 2


As you have setup the ShortAircraftNameOk=Substring this should detect all your C750 aircrafts and apply the button profile to it. To avoid later conflicts with other planes you should consider also to create a seperate [JoystickCalibration.C750] profile.




  • 1

#468105 Possible ? In : offset with multiple variables / Out : offset without variable

Posted by EW321 on 16 May 2014 - 08:14 AM



just check Lua for that. You will find lots of examples for use and of course a manual in FSUIPC download section.

  • 1

#468090 Accu-Feel v2 & impact on performance

Posted by Ian P on 15 May 2014 - 04:31 PM

You missed the people running around screaming "THIS IS FS11!!!" on every forum under the sun... ;) :mrgreen:


What you get with Accu-Feel is probably about 25%-30% of the additional functionality that comes from a dedicated Accu-Sim add-on aircraft. As you say, though, it applies to every single aircraft you have (except, technically, helicopters!)


My favourite part of the add-on is the improved floatplane dynamics, because I don't tend to operate around the edges of the flight envelope enough to get the most from much of the rest. I agree entirely, though, that it's an excellent add-on and well worth having. I'd recommend it without question. On the other hand, if you've not tried a full Accu-Sim aircraft, I would really, really, really, recommend getting one of those. The C172 is a little sedate and behaves a little too well, if you want to see what they do, unless you set out to break it. On the other hand, the Spitfire, P-40, P-47 or B377 force you to do things by the book and bite quite hard if you don't. Possibly not the best from a beginner's point of view, the C172 would probably be best there, but they really are in a league of their own. Things like the PMDG jets, Majestic Q400, LDS767 are fantastic systems simulations, but even they could do with a touch of Scott's magic in places. ;)




Ian P.

  • 1

#467934 FSX freezes in 8 minutes

Posted by Ian P on 08 May 2014 - 09:14 PM

Setting frame rate to unlimited can actually lead to sim crashes, rather than solving them - depending on what settings you are running.


Each process within FSX (e.g. drawing mesh, drawing landclass, drawning autogen/scenery objects, flight modelling, AI, gauges, lighting...) requires CPU time. They're not covered by one catch-all process, they all run individually. If you set your frame rate to unlimited, you are maximising the amount of processor time used by drawing mesh/landclass/objects and, basically, stuff any other process. That means that you have less processor time available for flight modelling, weather, monitoring control inputs, etc.


FSX is, apart from some fiddling round the edges, a single CPU application. Therefore, if you push it too hard and ask it to do more than that single CPU can handle, at best you'll get massive stutters, missed control inputs and display problems such as AI taxying across the grass. At worst, you'll crash your sim (theoretically crash Windows, but most modern versions of Windows handle FSX crashing without losing Windows as well).


As with everything, it's up to you what you do with your sim, but it's always worth realising that every action has an effect and that Frame Rate: Unlimited causes more problems than it usually resolves.


Ian P.

  • 1

#467826 Tracon! 2012 demo

Posted by FeelThere on 06 May 2014 - 09:48 AM

We provide shortcuts that you can customize.


Thank you



  • 1

#467816 Hat Switch

Posted by Pete Dowson on 05 May 2014 - 11:39 PM

I am considering installing a DigiKey 4-way hat switch to my Ace yoke via a Bodnar board.  My question is, does FSUIPC "interpolate" between Up, Down, Left, Right to provide 8-way POV functionality?  Reason I ask is that my Saitek joystick when using JOY.CPL in Win7 shows all 8-ways, but the Hat Switch/Bodnar board only show the 4 ways.


A proper hat, recognised by Windows as a POV ("Point of View") device, and not just a collection of buttons, returns to FS and FSUIPC a value in either degrees (0-359) or 1/10ths of degrees (0-3599). Whether it can only supply discrete values like 0, 90, 180, 270, or many different values depends entirely on how it is made. I think the normal cheap ones consist of 4 buttons, but usually with the firmware in the device it is connected to able to detect two adjacent ones pressed together and so give you the intermediate, 45 degree, positions -- i.e. 8-way. 


FSUIPC4 can see POVs as axes, in the axis assignments tab, in which case it takes the number provided, 0-360, as an axis value. It can also see them as a set of up to 8 buttons, 32-29, (this method derives from how FS98 and earlier saw them). In that case it merely treats values 337.5 - 22.5 as 0 == button 32, 22.6 - 67.5 as 45 = button 33 ... and so on.


There is of course no way FSUIPC can detect values which aren't supplied by the hardware. It can't "interpolate" given only one value, obviously. If the Bodnar implementation doesn't do the 2-button detection in order to send the intermediate values, then I'm afraid your hat will remain 4-way, not 8.



  • 1

About simFlight - simflight.com - simflight.de - simflight.fr - simflight.nl - simflight.pt - simflight.es - simflight.it - simflight.jp - simrussia.com - simMarket