John Dowson

Hi Emile, in addition to what Thomas has said, you can also reload your assignments by using the 'Reload all assignments' button in the Axis Assignment tab, or the 'Reload all buttons' button in the Buttons & Switches tab. Cheers, John

Hi, Which input fields - all of them? If so, that is very strange. The key fields will go white if the registration is incorrect, and an error message shown below. Is that your issue? Please try again and make sure you use the details ( name, email and key) exactly as shown in your email from SimMarket - best to cut-and-paste to make sure. If you are still having issues, please attach your Install FSUIPC4.log file, which will be in the installation directory (the Modules folder in your FS main folder). John

For FSX-SE, you need FSUIPC4. There is no difference between the free and paid/registered versions, they are the same. However, once registering your license, this unlocks the additional facilities. To download and try FSUIPC, please go to www.fsuipc.com or Licenses for FSUIPC are only available from SimMarket. Cheers, John

Hi Joe, if the PMDG aircraft use the standard SimConnnect text messages, then they should be available via offset B000. Cheers, John

Note that Saitek "Mode" switches can be tricky. I don't know the AV8R stick, but if your mode switch registers in FSUIPC then you should be ok. If FSUIPC can't see your Mode switch, it could be tricky as you need to determine what the switch is doing (i.e. button number)...if thats the case, the following support request relating to the Saitek Yoke Mode switch may help: Or it may be possible to determine what button the "Mode" switch is using via the 'windows test page', according to this post: https://www.avsim.com/forums/topic/477157-saitek-yoke-mode-1-2-3-switch-fsuipc-newbie/ Cheers, John

Saitek panels don't work with FSUIPC as they are not registered in windows as standard joystick devices. You need to use either SPAD (freeware, available from http://fstools.weebly.com/download.html) or SPAD.next (payware, trial license available, from https://www.spadnext.com/home.html). Cheers, John

Its John, not Pete! Pete has retired, I am now supporting FSUIPC5. John

Yes, but the length would be 127 characters for read and 126 characters for write (both including the terminating zero), as you need to precede the lvar name with ':' or '::' Yes, that is correct. Nothing has changed here, the zero termination is still required. John

Hi Paul, please try the attached dll below which contains FSUIPC v5.153b. This will be officially released as v5.154 at some point. I have re-mapped offset 0D70 internally to a 128 byte array, which should hopefully be sufficient for all future needs. Note that this is currently only implemented for reads/writes from the SDK, and also the lua ipc.writeSTR and ipc.macro commands. Theoretically you can write to this offset (range) with other lua statements (e.g. ipc.writeUB). I'm not sure whether I should handle these or not at the moment - maybe a clarification in the documentation would suffice. I'll discuss with Pete when he's back from holiday next week. I've tested via the SDK and via lua, but not with lvar lengths > 40 as I don't think I have any aircraft with such long lvar names (although I guess I could create one....). Let me know if you have any issues. Regards, John FSUIPC5.dll

Pete is on holiday at the moment, back at the weekend, so it may take him a while to reply. The email address is correct. Regards, John

Please check your assignments in the FS (P3D or FSX) first - if you are only assigning in FSUIPC then its best to disable controllers completely as without being disabled they can occasionally be re-assigned automatically. If you are still having issues after checking this, please post your ini file and I'll take a look. John

The elapsed time for each entry is also logged in each entry (first column), so you should be able to calculate the interval. Alternatively, you can also adjust the script to directly log the interval (since last entry) if required. Note that the record to csv.lua script as provided is sleeping for 48 milliseconds on each loop iteration, to allow logging roughly 20 times per second. You can adjust this to your requirements. This delay/interval is approximate, so you should use the elapsed time to calculate the actual interval. John

Your question is very similar to the ones posted by you already and answered by Pete in this topic: If you need further clarification, its better to continue the conversation in the same topic. Also, as your question is not directly related to FSUIPC, you may be better off asking over on https://www.cockpitbuilders.com/ Cheers, John NB Note Pete is also now on holiday and not back until the 17th or so

Hi Paul, lets keep offset 0D70 for this (for external use). Internally I'll map to a different area so that I can increase the size. I'll look into this over the weekend (hopefully!) and post an updated dll in this topic when ready for testing. Cheers, John

Hi Paul, no, the size of that offset is still 40 chars and can't be extended to 64. I think I'll have to add another offset for this. Let me take a look and I'll get back to you. John

Can you PM me your FSUIPC5 license details please and I'll check them here. Cheers, John

Following up on your PM, your license is for FSUIPC4, which is not valid for FSUIPC5. John

Please make sure that you are using the same name, email address and key as in your SimMarket purchase email (best to copy/paste). If you still have issues, please PM me your details and I'll verify them here (please do not post them!), or let me know your order number and date. Thanks, John

It should be available as an entry in the 'Control sent when button pressed' menu and assignable there, in the usual way. John

Hi Andy, You can assign mouse macros to physical button presses on your devices, or keyboard presses - as many as you like. You can't reassign the macro to a different simulator button press (by which I guess you mean in the simulator, i.e. the ui). For this, you need to create a new mouse macro. Or do you perhaps mean something else? Try activating event (non-axis) logging as well as button and key press logging, from the FSUIPC logging tab. Take a look at the log file (in your Modules folder) when you activate your controls to see whats happening. If you need further help with this, please post your log file (with logging activated) as well as your ini file. Cheers, John

Yes, as I said, offset 0580 would be the a/c heading (native fsx heading). You could try offset 6038, which is the GPS: aircraft true heading (from simvar GPS GROUND TRUE HEADING). However, being PMDG, they probably implement their own and this may not be available. If it is available, there is also a simvar called GPS GROUND TRUE TRACK. This is not currently stored in an offset, but could be added - if you can check offset 6038 and that is working for you, I could add this. Let me know. Alternatively, this would need calculating. You may want to ask on the PMDG forums on how to do this (or if its available via their SDK). I don't have any PMDG aircraft. John

Your logs show that FSUIPC is installed correctly, so your problem is with ADE. As previously mentioned, make sure that if you are running FSX-SE as an administrator, then you must also run ADE as an administrator. Also, please check your ADE set-up, as Thomas says. John

Its not in the PMDG list, its a general FS offset which should still be applicable to PMDG aircraft. FSUIPC doesn't 'send' any data, it just populates the offsets with the data. You just need to get your client application (FSXpand in this case) to read the correct offset for the data that it needs. John

As the offset documentation states, this is the MCP heading (equivalent to 07CC for non-pmdg aircraft). For the actual aircraft heading, see 0580 (and surrounding offsets for lat/long/pitch/bank and timestamp flags). John

Where did you get 622C from? For PMDG offsets, please see the Offset mapping documents for the PMDG aircraft, which should be in your FSUIPC Documents folder. Looking at these, I can see that the MCP_Heading is in offset 652C - could it be this (confusing 5 with 2?)? Also, please check that you have the PMDG offsets activated (see previously mentioned documentation). Regards, John N.B. Once assigned, we do not change offsets as this would cause compatibility issues!