John Dowson

I do not understand why people keep posting this same problem, when there are now hundreds of support requests with the exact same problem. As I tell everyone else, can you PLEASE consult the documentation and then also the support forums for the same/similar issues before posting. Please first se see the provided Installation and Registration guide, section Invalid Key Problems. You will need to update your VC++ redistributables, as it says there and in the hundreds of support requests on the same subject.... John

I have cleaned-up your ini (a bit!) in the attached, if you could try this. I have removed the use of the hidBravoButtons.lua script - you should delete this, as well as the alpha script, from your installation folder. I have also moved some assignments, but not as many as I would have liked, to your general [Buttons] section. I have also re-ordered your button assignments on device (letter) and number, and removed duplicates. It should be far easier to see your assignments, and compare the assignments in different profiles. I suggest you also move more common assignments (e.g. standard light controls) to the general [Buttons] section, and just overwrite them if not needed/used in your profile section. I did not do this as you seem to have the lights set-up differently in different profiles. Anyway, please try the attached. As before, if you are still getting the issue you originally reported, please show me your updated .ini and .log files, with the same logging as before. John FSUIPC7.ini

Note also that for the Milviz Cessna 310 profile, you have assignments to both the standard controls AND the presets, e.g. for Beacon lights you have the following assigned: In fact, you have multiple assignments to nearly all buttons. I suggest that you go through your ini and remove these conflicting assignments. You would normally have all the assignments to the standard controls in your general [Buttons] assignments. These would then be overridden/replaced un a profile section, where something more specific, such as a preset, is needed. You should therefore move all of your standard assignments to the general [Buttons] section, and remove these from all your profile button sections. You also have the same multiple assignments to some buttons: e.g. magneto in your 310 profile This may be due to the fact that the GUID of the device changed, and then you re-assigned using the new letter, and so when I corrected this missing device (to restore other lost assignments), you ended up with multiple assignments. So, I suggest you open your ini in an editor and correct these issues for your button assignments. First, move all general button assignments to your [Buttons] section and out of the profile specific section (they will be inherited in profiles). Then take a look at each profile-specific button section and remove duplicate assignments for buttons. You should also take this opportunity to remove the use if the hidBravoButtons.lua script. The assignments to P65 should go and be replaced by assignments to the actual button numbers on your Bravo (device C). But better to correct all the other issues before doing this. John

Looks like I missed a few changes in the last ini (although I would need to review that to confirm). I have corrected the missing device in the attached, so can you please use this for the next test. Please do the same (just one aircraft please), with the same logging and show me your updated ini and log files. Thanks, John FSUIPC7.ini

Ah, ok. I can release over the weekend, probably Sunday, if that helps.

Ok, thanks for the update. Have you made any software available that depends on this change? I have been getting some support requests through stating that 7.3.25 is needed to support the ACARS program they are using, which is strange as this has not yet been officially released...

You can develop am FSUIPC client app without having anything running. WideClient or FSUIPC7. These only come into play if you want to run (or debug) your app. For this, you can use either WideClient or FSUIPC runnning in client mode.. If you are using the features of the dll client for .Net that use the WAPI/WASM, then you will need to configure simconnect for remote access. In the WAPI itself, this is simply a mater of calling the setSimConfigConnection function to specify the (configure) connection to be used, and the value used would usually be taken from a config file (so that it can easily be changed between remote/local). Presumably the .net client has access to this function, but Paul should confirm. John

Just took another look at this to see if there was any change, and it seems that the TBM930 improvement mod is no longer working with the latest version of MSFS. And the throttle animation is still broken - you can assign the throttle in FSUIPC7 and it does work, but the animation of the throttle in the VC is broken so you will not see the throttle move. If toy want to see the throttle move, you must assign in MSFS. So, basically no change here, except for the fact that the improvement mod no longer works. I don't expect Asobo will get around to fixing this, so I am closing this thread now. John

I have removed the re-writing if the Delay ini parameter in the [Programs] section in the attached (beta) version, 7.3.25c. Regards, John FSUIPC7.exe

I would hope that most people understand what is meant by add ....the comma is used there as this is the list of options that can be used. The meaning is perfectly clear and I see no reason to change this. John

If you are developing using the FSUIPC SDK, then using WideClient will provide the same (server) functionality as FSUIPC. To read/write lvars and hvars, and to use calculator code or presets. you would have to use the offset facilities provided. If you are using the WAPI (or anything that uses the WAPI, such as Paul's ,Net dll), then this uses SimConnect to talk to the FSUIPC WASM module, not FSUIPC itself, so you would have to configure network access for SimConnect to use these facilities. Note that you can also run FSUIPC7 in client-mode on a client PC, which will save you having to purchase a WideFS license. To run FSUIPC7 on a client PC, see the appendix in the Advanced User guide. John

Licenses sent.

Yes, and I quoted it in my previous comment....again: The options can be any mix of these (add them together):WND_BOLD, WND_ITALIC, WND_UNDER, WND_STRIKE. Of course that doesn't work. As stated in the document, the signature for this function (when using options) is: bool = wnd.font(w, face, size, options) and not bool = wnd.font(w, face, size, option, option) which is what you were trying. That doesn't exist.

As the documentation states: The options can be any mix of these (add them together):WND_BOLD, WND_ITALIC, WND_UNDER, WND_STRIKE. So it would be: wnd.font(w, WND_ARIAL,64, WND_UNDER, + WND_BOLD) As I have said, can you please consult the documentation before asking such questions. If it doesn't work according to the documentation, then post. That obviously won't work, i don't understand why you would even try that as there is no such function for that second call. Again, please read the documentation. John

Done.

Took a quick look and the problem was a lot easier than I thought - it was just that the global definitions for WND_ITALIC, etc hadn't been defined. Also the globals for the font specification weren't defined, so even font selection wasn't working. I have corrected this in the attached version, 7.3.25d. if you would like to try. John FSUIPC7.exe

But you do have an ACARS program that IS connecting. Why that one and not the others? Have you tried asking the program developers/providers? And if the CEO has told you that his program cannot connect, has he not asked his team/developers to look into this? I can provide other versions of FSUIPC6 but I do not think this will help, as you have already said that it was working with 6.1.9 but is no longer. And there has been no change to the FSUIPC SDK functionality, which all 3-party clients use, for many years. But if you let me know what version you want to try, I can build that for you. There is really nothing else I can do about this. If this was a freeware program, I could download and see if it connects, but even then I cannot do much else. Please hassle your CEO friend about this, not me!

Then ask him to look into this - its his program, not mine... FSUIPC does not distinguish between client apps. If there is an issue with client apps not being able to connect, then I would look into this. But as this issue seems to be with specific ACARS programs only, there is no way I can look into this. You need the ACARS program developers to look into this. You did report that other ACARS programs are working, so this must be a problem with the program, and not FSUIPC. And, as this was previously working, I suspect the issues lies in a change somewhere in your system, but I have no idea what this could be, if it is not privilege related. This seems to be a common issue with ACARS programs, reported many times (check the forum), my answer is always the same. I cannot help with client programs I know nothing about and don't have - you need to contact the developer. What ACARS program are you using? Is this free-ware or payware?

Ah, sorry... From FSUIPC's logging tab - where else?

Ok, I have just checked and none of the font options (bold, italic, under, strike) seem to be working. No idea why this is at the moment. I will look into this when time permits, but it will be a few days before I can get a chance to look into this in detail. John

Also please see this post - there seems to be one ACARS program that requires FSUIPC 7.3.25, which hasn't been released yet: John

This really isn't my problem - you should contact the developers. I don't understand why they are even checking the version. There is currently no planned release date for 7.3.25, but it will probably be next month sometime. For now, the latest beta, 7.3.25c, can be found here: John

Your registration details are in your purchase email, and they are also available from your SimMarket account. If you didn't receive a purchase email, you can ask about this on SimMarket support. But you can still get your details from your account. John

Yes, of course, but if you look at the offset status guide, you will see: 0xA000 512 0xA200 3584 Reserved i.e. there are 512 bytes available starting at offset 0xA000, so 0xA000 - 0xA1FF. The ones you are using are in the reserved area, and I cannot predict the behavior when using such offsets. Please always check the Offset Status document when using offsets. Yes, this is the issue: John

If an FSUIPC client cannot connect, it is usually due to the client being ran at a different privilege level. But if that is not the cause, I cannot really help - you need to contact the support for the ACARS program. You could try logging IPC Reads and Writes. Don't run any other FSUIPC client apps, and see if any activity is logged from the ACARS program.