John Dowson

Hi Andreas, Ok, thanks. I'll add these to FSUIPC7 in the next release. John

Did you click the Register button after entering your registration details at the end of the installation process? If so, what did the pop-up say? If not, please re-install and try again. John

What else do you expect? That is just showing the contents of your FSUIPC6 installation folder. Note that your FSUIPC6 documents are installed om a different location: FSUIPC6 User Manuals installed in C:\Users\afvur\Documents\FSUIPC6. You also installed in the default location, i.e. your P3Dv5 Add-ons folder: FSUIPC6 dll file installed in C:\Users\afvr\Documents\Prepar3D v5 Add-ons\FSUIPC6. It is better to choose a different folder for your FSUIPC6 installation folder, and just use that location for your add-on.xml file. Please see the provided Installing and Registering FSUIPC.pdf manual. John

Ah, yes - that would explain your issue. Thanks for reporting back - and a Happy New Year to you as well, John

But they should be - at least in one direction! The other not. You really need to just determine the button/phase numbers and follow the instructions in the Advanced User guide. Its difficult to advise on such matters when we don't know how your rotary operates, but the facilities provided should be sufficient. John

But the function returns on end - you only need to explicitly return if you want to pass back a value, which isn't needed by these functions.... ... I see Pete has also replied in the same vein...! John

I can understand your grievance but a decision was made before release and has been discussed in many previous topics. Discussion on licensing policy and deductions is now closed. It is what it is. John

@LucaT & @Stone_B We have identified the issue with the latest windows update on the Surface Pro that causes this issue. @Pete Dowson will post an updated dll for you to try in the next few days. John

Erm...no...why would I do that? If I was still contracting, you could pay me to call you - would cost you £100 for an hour, but I ain't doing that no more... Please read that link I posted, and if you have an issue then post with a relevant topic title, that is of course you cannot find an existing topic for your issue. John

@pilotjohn Yes, after testing we have found that there is definitely an issue here - initial delay times are ignored (!) and subsequent delay times are different for virtual button repeats .... I'll post an update for you to try when I get time to investigate and resolve. Cheers, John

Are you using a steam or ms store (or boxed) version)? Check the start command in the MSFSwithFSUIPC7.bat file in your FSUIPC7 installation folder (paste it here if you do not understand it). There has been another support request where the installation was not detected as a MS Store install (as MSFS hadn't been ran before installing FSUIPC7), and so the start command added is for a steam install, even though the user had an MS Store installed version. John

These errors indicate problems receiving data via simconnect. Each time that error is reported, the connection is closed and re-initiated. This can cause problems with the number of clients configured to use SimConnect, especially if you have any other SimConnect clients (i.e. add-ons that also use SimConnect). If its due to a slow pc with too many things running, you could try increasing these ini parameters in your [General] section to see if it improves: Maybe try with: Or you could also try without re-connecting by giving -ve values, i.e. This would then just log messages (the '-' indicates to not automatically re-connect in this situation). It maybe worth playing around with these parameters to se what works for your system. but if its being overloaded then you will always get issues.... Such issues are usually due to pushing your system to its limits, either CPU or GPU bound. John

Yes, that should be the case, although I haven't tried this.... It depends on what you mean by 'end'!! If they had an event call, the function should exit, but the lua thread will keep running as it is waiting for events.... Remember that each lua will run in its own thread, and that thread will terminate when that lua has finished. If it has event.* calls, it will only terminate when those event calls have been cancelled. John

@blazer05 Yes, worth pointing out that this setting CAN change on P3D updates, so you should check after each update, especially if you have issues! John

You are posting in a topic that is over 15 years old... I will close this. If you have an issue, can you please start a new topic. And, if you do this, please give enough information for us to investigate. Please, at least read this before posting again: Your location is from 'WestMidlands'. I am from Stoke-on-Trent, but cannot understand your posts.... John

Yes. Its a problem with the MSFS SDK that you should report to Asobo via zendesk. John

@daveflyer Sorry, but I do not understand your post. Who is 'David Haynes'? Is this question for him, or is that you? If the former, please use the '@" notation (with the forum username), and then he will get a notification for the message. If the latter, then please take more time to explain what your problem is so that we can assist. John

This means that you are using an unregistered version of FSUIPC. The assignments menu is only available for registered versions. If you don't have a license, there is a time limited one available on another topic post, but that expires tomorrow. If you have a license, you need to register it during the installation process (and make sure to press the Register button). John

@spokes2112 Please see the original HidDemo.lua that is included in the lua examples zip (in your documents folder). The ones you are looking at are the modified ones for which I made this mod, to exclude duplicate notifications, as you say. John

Ah, sorry. You mean in the attached/modified version. I changed this in the modified version as a user didn't want both the original and virtual buttons triggering in the UI, so I changed this to disable update of the 1st 32 buttons. John

I see it as 1: ?

They are bits - &3 would test on bits 1 and 2. Taxi lights is bit 3, so that should be '&8' (2^3 = 8). John

You are probably triggering the same virtual buttons in each script - each DWORD (32 bits) from offset 0x3340 represents one "joystick". So, for a second joystick, start at offset 0x3344. John

@Juxpax Glad you figured it out. Yes, the information is spread about a bit and difficult to find. It would be good to create a FAQ entry for the Honeycomb Alpha I think, as well as the Bravo. I'll look into this in the new year, when time permits. John

Once the window has been created, it saves its size and position in the FSUIPC7.ini file - look for the following line in the [ExtWindow] section and remove it: Asking for inout: test=[444,146,346,102] Note that you can manually move and resize the display window by selecting it and then using the arrow keys, with Ctrl switching between move and resize. They can be be anywhere. Yes, this is a bug that was picked-up recently. I will correct this in the next release so that a single evemt.cancel() call will cancel all events registered on that function. Yes, thats a typo (as well as 'inout' in the name of the window created). I will correct and replace the uploaded file. John