John Dowson

I'm not sure what you have done but you have no axes assignments at all, either general or profile specific. Please try setting up your axes again in your profile. Before doing this, you should change this ini section: To this: [Profile.747] 1=PMDG 747 This will then match any aircraft with 'PMDG 747' in the title to your profile (as you have the default ini paramater ShortAircraftNameOk=Substring set) There was a correction from v6.0.10 to v6.0.11 that should have prevented assignments being lost when not importing general assignments into a profile. Maybe you did this with v6.0.10 before installing v6.0.11?

Strange. The same python SDK has been included with FSUIPC5/6 for many years without issue. Lets see what they say. Malwarebytes also seems to have some false positives with FSUIPC7, but I think with the .bat file.

When installed, its integrated into FSUIPC7. Run FSUIPC7, and look in the Add-ons->WebSocket Server menu, There's an Online Help menu entry that takes you to http://fsuipcwebsockets.paulhenty.com/

If you have installed the web-socket server, there should be a menu entry that takes you to the on-line manual.

Then I'm sorry, I don't know what the issue is or could be.

Then maybe its just the character set? For the FSUIPC SDK, you need to compile with a multi-byte character set, not unicode. John

I'm not sure what 'GPS button' you are referring to, or in which aircraft. Best to just try and see.

Ok, I can now confirm that 64-bit compiled programs work ok with the 32-bit WideClient.

Problems compiling this, sorry. So, does your software work with WideClient when recompiled with the 64-bit lib?

Sorry, that doesn't make sense. ipc.control is for sending controls. A read from an IPC (Inter-Process Control) is the same as reading from an offset...all the IPC means is that its in a different process. Sorry, I'm confused as to what you mean by IPC here. You just read and write values to an offset, it doesn't really matter where the read/write is coming from. Well, I am still not clear on what you are saying or trying to do! A control/event is a command - it is sent to the sim. The offset area contains information (sim variables) received from the sim, and also a writeable area that updates these either directly or via using commands/events. Did you download and try the latest version with you numpad key assignments? John

Pete's found a 64-bit TrafficLook client and is testing now....I or he wil let you know shortly... Yes, you can use that. Its built on top of the .net dll client, which (I believe) is built on top of the 32-bit SDK, so it will be using the same under the covers.

Its a problem with the model then. I suspect that the event is for a general model for all aircraft, and there is no specific check on this on what the actual aircraft model has. Yes, it will depend on the offset. Some offsets are updated by updating the sim variable directly (identified as 'Ok-SimC' in the offset documentation), and some use events/controls (documented as 'Ok-SimE').

This is expected. Why is this frustrating? If you have FSUIPC open, you do not need to access P3D. FSUIPC blocks visibility of your devices (all controllers including keyboard and mouse) while it is active so that you can assign to these without them having an effect on the sim. John

WideClient is 32-bit (all versions). Its seems unclear if this would work with a 64-bit client. You can re-compile against the 64bit SDK and try it. But 32-bit clients work fine with all versions of FSUIPC and WideFS, so you can just stick to 32-bits unless you have other reasons to move to 64-bit. Sorry I can't give more information. I'll do some testing on this at some point as I'd also like to be clear on this (i.e. 32-bit/64-bit client with 32/64 bit WideFS or FSUIPC) but I have a lot to do at the moment (and for the forseable future!) so haven't really got time to check this any further at the moment. If you do rebuild you client as a 64-bit one, please let me know if it works ok with WideFS/WideClient. John

What version of FSUIPC7 are you using? The use of the numpad keys was corrected with the release of the MSFS SDK 0.8.00 and updated in FSUIPC7 v7/0/2 release on the 28th November. If not using that version, please download and try with that. I'm not sure I understand this question. Yes, there is no access to lvars at the moment, but SPEED_SLOT_INDEX_SET is an event/control, which you can send using lua via ips.control and provide the parameter needed. John

Yes, probably on a 6 hz sampling rate but depends on the data item. Yes, each lua runs in its own thread. That's strange... Does the control actually work on the aircraft you are using? If so, what happens when you send an invalid value - is it just ignored? The offset just holds the value of the associated simulator variable. But it doesn't make much sense that its being updated to an invalid value for that aircraft.

No, sorry. All the drivers and additional freeware we provide are available in the download links section here or on www.fsuipc.com. John

If its not seen in the assignments panel, then its probably not recognised as a joystick type device. You can post your FSUIPC7.log file and FSUIPC7.Joyscan.csv file and I'll take a look. If its recognised as a Hid device, then you could access it using lua. there is a demo lua script provided that you can use and adapt (HidDemo.lua) as well as documentation (both installed in your windows Documents folder under a folder called FSUIPC7).

Its in the SDK folder, UIPC64_SDK_c_version2.zip.

But that is probably an old version now. You should download and install v7.0.2, released yesterday. Not really. This is why we provide profiles, so you can configure your assignments for the controls or features that work for the aircraft in that profile. Sorry, I don't know Xplane 11, and FSUIPC doesn't support it. I think thats XUIPC by a different developer. John

Yes, as the control is sent to the FS and the offset is updated when we get this information back to tell us that the offset has been updated. Most probably due to the event not being connected yet - from the MSFS SDK: Internally, not all events are mapped to the relevant SimObjects If that should be possible with the aircraft, you can raise a zendesk ticket with Asobo.

Where is this, on the DA40, for example? The ignition switch (ELECTRIC MASTER: Off - On - Start) in the DA40 is using the Toggle Master Battery Alternator event (with param 1) for Off <--> ON, but there doesn't seem to be anything for On ->Start (apart from the generic Engine Auto Start or Ctrl + e). Is it this what you are looking for?

FSUIPC7 should in no way affect any assignments you have in MSFS. Check that you are still using the default Keyboard profile in MSFS, and search by input to see if your arrow keys are still bound. If you run MSFS without FSUIPC7, does this problem go away?

There is currently no access to lvars. In such circumstances (i.e. no event seems to be triggered), you can look at the MSFS assignments to see if there is anything that works there. Then assign this to a key press (or key press combination) in MSFS, and then assign the key press to your button in FSUIPC. Just looked at the DA40, and there is a Toggle Master Battery control which seems to work for this aircraft (if thats what you are after). John

They do - they all use the Fuel Selector Set control. The offset for the other indices (2, 3, 4) use the Fuel Selector n Set contols (n=2,3,4). I'm not sure why there is no generic fuel tank selector 2..4, but you can use the other indexed offsets instead as they use the same control. John