Thomas Richter

Hi, easiest way to check what value is readable is by using FSInterrogate, you will find it in the FSUIPC SDK. Just to make sure it is not related to the pascal version you use. Thomas

Hi, it doesn't matter if those axes are already in use because it is in use by a different controller. But you should decide where you want to define and calibrate your controller, in FS or FSUIPC. Best definitely not in both, just in one or the other. If you want to define all your controller in FSUIPC you have to disable Controller in FS, in controls page of FS, and then define all your axes and buttons of each controller you want to use in FSUIPC. Thomas

Hi, I removed the Key information from your post. Only send key information when asked to do so BUT then please only by email. just copy and paste the information direct from the source into the fields rather than trying to type, works always best. Thomas

Hi, do you use maybe unsinged byte instead of signed byte? Thomas

Hi, at SimMarket http://secure.simmarket.com/pete-dowson-fsuipc4.phtml Thomas

Hi, MakeRwys has nothing to do with the Autopilot system, neither original FS or Add-on aircrafts or systems. If you have tweaked airports with ADE you might have disabled or removed their ILS. Again MakeRwys only reads all active (in FS) airports and crate different files third party programs can use for Airport, Taxiways, Parking positions and Rwys to work with those data. MakeRwys doesn't do itself anything with those data and it also doesn't even connect to FS, where you would use it anyway when FS/P3D is NOT running. Thomas

Hi, other Add-on aircrafts might have as well their own modelled gauges but maybe not an SDK available and standard Offsets might not be used in those cases. Best place to ask would be their forum where maybe others tried as well to get data out of their aircraft model systems. It depends all on if they make use of standard FS/P3D gauges and if not if they provide a way to get data out of their gauges. Thomas

Hi, there is no other FSUIPC4 version than the current supported one (the only supported one) needed. The SimMarket FSUIPC4 version you talk about is declared as a Demo FSUIPC BUT is actually the link to the current and supported Installer (FSUIPC version 4.958). ..., I still need to ask this question.Am I good to go with the .938 version I installed from simMarket or do I need to install the .938a download I read somewhere, but the link did not work? It might work but there is no reason or need to do so. There will not be any support for old versions. Thomas

Hi, so that is a perfect match, PMDG! They use their own logic for spoilers, armed position will not be seen in standard FS Offset (maybe in their own offset list there is something). For GPS the same, they have their own planning and route system build into their FMC (CDU) that is not linked to FS GPS, so again no information available via standard FS Offsets. And again you will need to check their SDK if you can read route / procedure information. Thomas

Hi, as you can read in Pete's answer above there is no signature anymore, it was removed couple years ago. Which windows you use doesn't matter. Make sure you use latest FSUIPC version. Thomas

Hi, first I guess you use latest FSUIPC version 4.958 Install FSUIPC4.958 ? To your questions: 1. the spoiler armed state can only be given in air if the flight model you use supports that. On ground the spoiler don't arm but deploy. 2. and 3. those offsets will give you only information if the FSX/ P3D original GPS system is used by the GPS gauge. If your flight model uses a different or external (add-on) GPS system that doesn't support those offsets then you will not get any information by reading them. Thomas

Hi, that is mostly related to graphics card, if I remember correct it was mostly and Radeon problem (only if I remember correct). Just leave the full screen modus (Alt + Enter), it should be ok in windowed mode. Thomas

Hi, by looking at your profiles you will have a working Rudder in-flight but not on ground! Actually you didn't create a new profile but you copied the existing one that didn't work for the rudder and did changes on that one. So you just copied the error in it with it every time. You have a tiller calibration in it but no tiller axis defined/ available for it, so on ground it uses the calibration but with no axis. Just remove this line: SteeringTiller=-16384,0,512,5760 Thomas

Hi, it will be no where stored because it is only temporarily as long the menu is active. The manual describes that as well: ... To get over that you can choose, temporarily, to ignore the axis that is interfering with your efforts. To do this, click on the “Ignore axis” button, over there on the right. This doesn’t ignore it forever, only during the scanning. You can ignore as many as you like, and clear the whole list of ignored axes by clicking on the “Clr ignores” button at any time. Thomas

Hi, yes if you original bought the FSUIPC and WideFS for FS9 (FS 2004) you will need to buy a new licence for FSUIPC4 (for FSX/ FSX-SE/ P3D) and WideFS7 (if needed). Just for info, there is also a reduced price if you buy FSUIPC4 + WideFS7 at the same time (Bundle Offer) at SimMarket BUNDLE OFFER Buy 2 for 22.14€ incl. VAT (18.00€ excl. VAT) each Thomas

Hi, 1. make sure you use latest FSUIPC/ FSUIPC4 installer 2. make sure you use the key you bought at the time is for the correct version, FSUIPC for FS9 (FS 2004) is different from FSUIPC4 for FSX/ P3D. The key for FSUIPC does not work for FSUIPC4, same is true for WideFS versions. Thomas

Hi, you might find something in the forum. I think someone did something like that with Lua already. But you might have to search for it. Thomas

Hi, do you mean as soon you move the Aileron or Elevator axis that the Autopilot will disconnect? If so, that might be ok because most Autopilots in aircraft work that way. Normally there are four ways to disengage the Autopilot, 1. Stick Disengage button 2. AP Disengage bar/ button on the AP panel 3. Stick movement with certain pressure against the artificial feel (if available on A/C) 4. Pulling the CB Thomas

Hi, you can also use the Offset direct in FSUIPC4 for your buttons 029B 1 Alternate static air source (0=off, 1=on) 2EC8 4 Prop sync active (1=Active, 0=Inactive) Thomas

Hi, did you check the included Offset Status PDF file? You would have found 0BC8 , 2 , Parking brake: 0=off, 32767=on Thomas

Hi, what happens by using FSUIPC but non controller programming? Also you have this, where your mixture1 lever controls the gear. 0=BX,256,D,13,0,0,0 -{ DIRECT: Mixture1 }- 1=BX,U,4224,16383,66079,0 -{ DIRECT: Mixture1Entering=GEAR_UP }- 2=BX,D,-16384,-4681,66080,0 -{ Entering=GEAR_DOWN }- 3=BY,256,D,14,0,0,0 -{ DIRECT: Mixture2 }- Thomas

Hi, it's not FSUIPC that has a problem but your P3d. As you say P3d crashes and it seems that FSUIPC is still open and cannot close because it didn't receive the closing (P3D crash). Did you follow what the message box says? - Open Task Manager and check what is still running before restarting P3d ! Thomas

Hi, you might maybe not be able to do that in PM's MCP. Maybe best to Project Magenta support instead direct, they should know best and give the correct advise. Thomas

Hi, back to the manual, page 45 to 47 (included) describes step by step the calibration process and also takes note of the Rev function. (Modules folder (FS) there is the folder FSUIPC Documents and you will find there the FSUIPC4 User Guide.pdf file) Thomas

Brakes work in relation to applied pressure. It sounds like you have the axis in reverse working, means you need to reverse the axes function in FSUIPC, by ticking the 'Rev' box for each axis. Thomas