John Dowson

Hi, you posted in the FAQ section - please post support requests in the main forum. Usually such issues are caused by incorrect permissions - can you check that if you are running your sim with administrator privileges then you are also running your other apps with the same privileges. Please check that first. If thats not the issue, more information is required - your FSUIPC log file for a start, and the errors you are getting from the apps trying to connect. John

Hi Andrew, no, you don't need WideFS - as I said, this is used to allow client applications running on a different (network connected) PC to communicate to FSUIPC (and thus the FS) over the network. FSUIPC5 is a different product to FSUIPC4 (as the former is 64bit and the latter 32bit) and will require a new license. I believe there was initially a special upgrade price from FSUIPC4 to FSUIPC5 (before my time I'm afraid) but this is no longer available. Cheers, John

I'm still using VS2017 for FSUIPC5, and the build shouldn't have changed. Worth trying with 5.152 though, but I would be surprised (and worried!) if it was the 5.153 build. John

First, you posted in the FAQ section - I have moved your post, but please post all support requests here in the main support forum. For P3D v4.5, you need FSUIPC5 (available from SimMarket). WideFS is a separate product for extending the FSUIPC interface to other PCs on a network to allow appropriate application programs to run on separate PCs. Cheers, John

Hi Luke, sorry, you are correct - the numbers were strange as they were written as 32bit floats instead of 64 (and some conversion was applied). Please try the attached dll where this has been corrected. The lat/long/alt are in the format as received from P3D with no conversion, which is lat/lon in degrees and alt in feet. Not sure what the format of 05B0 and 05B8 was at the moment- I'll check this. Cheers, John FSUIPC5.dll

Btw, you need to look into the PMDG SDK PMDG_777X_SDK.h file to know how to interpret the PMDG offset data. John

Hi Luke, first, apologies for the long (!) delay with this... Took another look and found that there is a simvar called ACTIVE EYEPOINT LLA which I've now added to populate offset 83BC. Please try the attached dll below and let me know. Thanks, John FSUIPC5.dll

Hi Joe, so I think you need to look at the PMDG 777 offsets - see the document Offset Mapping for PMDG 777X.pdf. You should be able to determine the messages from these offsets. This post shows that they can be used to get the messages, although its for the 737 and is using Paul Henty's clien dll for c#/.net: Cheers, John

Yes, that does sound strange! And nothing to do with FSUIPC! Thanks for the update, John

FSUIPC should not affect your FPS. If you rename the FSUIPC5.dll (to something like FSUIPC5.dll.unused) so that it is not loaded, does your fps go back to its previous level? John

The name, email address and key must be entered exactly as shown in your SimMarket registration email - best to copy and paste. If you still get issues, PM me your details and I'll check them for you (don't post them publicly). Thanks, John

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