Pete Dowson

xxx is to be the name of the Profile in which your Asobo A320 is configured. If you are not using Profiles you can auto start the plug-in using the [Auto] section. Then which aircraft is irrelevant. For more information on this, and Profiles, please do refer to the documentation provided. Pete

Yes. It's related to the definition in the INI file stating the VRI com ports. I think it was a provision for some other VRI-related needs, but I don't remember anything specific. Looking briefly at the PFC drivers they appear to use their own comms code, not the functions in FSUIPC (which aren't exported in any case). So I mis-remembered that bit. Nevertheless the I/O functions in the PFC drivers are pretty much the same as those in FSUIPC. They were probably the source of the FSUIPC ones as the latter would have been added later. I certainly can't see that event.com can prevent other events from being triggered, which is what the user's report implies. A Lua trace log would be useful to see the sequences in the user's script. Maybe the problem is that the event.com is being continuously triggered, which would imply that the problem is in the Arduino programming. Pete

Unlike USB devices via DirectInput, you can't open COM serial ports more than once. You'd need instead to pass the handle from one to the other via ipc.set and ipc.get. The event.com will merely be waiting for data to arrive into a buffer. That's a separate always-running thread within FSUIPC. The same functions within FSUIPC are used by PFCcom64.DLL and my GA28R drivers, with potentially furious rates of input and output. Neither routines are blocking at all or the serial PFC and GA28 gear would not be operable. The most important information missing at present is the value of 'n', returned by the com.write. That gives the number of bytes placed in the send buffer, which is subject to a continuous loop in a separate thread. Pete

Without knowing anything about your settings it is difficult to advise, but some things to note: 1. Changing PCs changes the unique GUID identifications for all your devices. Even a serious Windows update will do trhat, let alone a change of PC. 2. Assignments made to joystick NUMBERS are less easy to change than those to letters. With joy letters in use it would be easy enough to compare a few lines (in the [JoyNames] section of the INI file) and assign the same letters in the new setup. We can help with that but would need to see both old and new INI files. Either way we cant help without seeing those files. Pete

Okay, I'll check it here in the next day or so. BTW, isn't this something you've used before? Do you successfully use other keystrokes assigned in the same way? If it turns out the DEL isn't a usable keypress can you change the assignment for the PTT? Pete

Is the Log extremely large? If so, why? Don't enable any logging options, just show the log with the default settings, then it'll be fine. And ZIP files before attaching. That makes them much better and smaller to attach. I don't want to see any pictures, I only need to see the standard default FSUIPC4.LOG file To me it sounds like there's a corrupt weather file. As a test add "NoWeatherAtAll=Yes" to the [General] section of FSUIPC. This may prevent your FSXWX program working (I don't know if it uses FSUIPC or not), but at least it will prove whether it is weather related. If so we can take different steps. And f FSX is crashing there should be an entry with crash details in the Windows Event Viewer (Windows Logs - Applications). Check and if so show me those details (cut and paste, no picture). Pete

The Window image you posted doesn't look blank. Don't you see the title bar and Menu, as I do, in your post? What else are you expecting it to show? The menu bar allows you to operate all of the facilities FSUIPC offers. It doesn't show images or play movies. Pete

Like John, I've no idea what you mean by "log tape". Pete

It doesn't look right, no. But I can't investigate today. The main question, though, is it sending Null or Del? i.e. is it working, as I thought you'd confirmed? The reset button is there to clear the existing key assignment so you can choose what you want to do again. Pete

Please refer again to Updated Modules. Things have moved on apace since you tried that. There's now no such link. Pete

There is a problem with the Installer at present which we are working on. If you were already registered you need not have entered details again. If you no longer have an FSUIPC4.KEY file with your registration, please create your own registration file in Notepad, to look like this: [User] Name= Address= FSUIPC= Complete all three lines with the exact details. Then save it as FSUIPC4.KEY into the FSX or P3D Modules folder. Run the Sim and check in the FSUIPC menu entry that it confirms you are properly registered. If not then you've made a mistake, so please try the above again. If still a problem, send that file to me in a PM. Do not post it here! Pete

You are being grossly unfair. John asked you for more information so he can fix things for you, but you don't even bother to do that! Please also look through the Installation document provided with the program. It does point out that sometimes you need to install other Windows components downloaded from the Internet. Full instructions are given. Your problem is probably that. Follow the instructions! Pete

For now, just edit it. Add the line for your Key, FSUIPC4=xxxxxxxxxxxx I'm trying to work out what is now wrong with the installer today. Pete

Thanks. I get the same as you. The registration check in the Installer is broken! It doesn't even like mine! I'm going to have to withdraw the release for now. I won't be able to work out what has gone wrong till tomorrow. 😞 Only if your existing FSUIPC4.KEY file is still intact. Just open it with a text editor and check that the details it contains are still correct. It's in your FSX\Modules folder. Pete

Why are you re-registering? You didn't need to! You just bypass that clicking "Not now". The registration system has not changed. Your existing registration (held in the FSUIPC4.KEY file) would still have been valid (do NOT post that here, mind). If you want me to check the registration here you really need to give me the order number, not the date and time. But be aware that 99.9% of all registration problems are because of a bad entry -- all three parts must be EXACTLY as notifiedby SimConnect. cut and paste if in doubt. try again. Pete

We need a lot more information! First, though, please get the latest FSUIPC 4 (4.976), available in the Download Links subforum. Then, if there's still a problem, we need NOT the "Install" log, but the run time log. (FSUIPC4.LOg). Also go to Windows Event Viewer and find the last crash details referring to FSX.EXE. We need those details too. Pete

It is definitely there, in the last post in the thread, the one from myself. Ah, good. Thanks for confirming -- I was awaiting confirmation from the OP in the that post. I had 4.976 ready for release (it is basically the same as the one you just tested) and released it just a few minutes before your post. So it is now the current release both on FSUIPC.com and also in the Download Links sub-forum above. Pete

Actually, a minor correction to that: the original design used the old "joy" interface in Windows. That was far simpler to code and much more compact, so it was a reasonable design choice. It was that which had the 32-button limit. I don't know what "DirectInput" was like back then, apart from being much more complex and bulky. The appearance of devices with more than 32 buttons has been quite recent in the history of FSUIPC. Back in the day you were lucky to find devices with more more than 8 or 9 buttons! Pete

Hi Vic, Seems like the problem in MSFS is related to code it needs to execute for elevated privileged mode which is bypassed in "fastlaunch" mode. Worthy of a report to Zendesk along with your description and the Event Viewer details of the CTD. Thanks for your perseverance! Pete

Yes. As well as following the clear unambiguous error report given in the Log, it's easy to check. Just make sure there#s an 'end' to go with and end every function and an 'end' to finish every "if ... else". For more information and tutorials on the Lua language please see lua.org. To correct things given error notifications you need to use the line numbers it gives you, so use an editor with line numbers enabled. Pete

But this error: is a syntax error in Lua, not an error from any function supported by FSUIPC. This is the function: function AB_OVH_Ext_LANDING_toggle () if A330 then if _tl("AB_VC_OVH_ExtLight_Landing_Sw", 0) then AB_OVH_Ext_LANDING_on () else AB_OVH_Ext_LANDING_off () end else if _tl("AB_VC_OVH_ExtLight_Landing_Sw", 0) then AB_OVH_Ext_LANDING_on () else AB_OVH_Ext_LANDING_retract () end end Note the number of "end" statements. They complement only the "if ... then ... else" statements. There's no 'end' to finish the function. Unfortunately it only takes one error in a Lua file to stop the Lua interpreter compiling the plug-in. This is why it is always a good idea to look in the Log to see if the Lua is loaded without error when you find something not working. Note also that the interpreter fails on the first error it finds, so you need to check again after correcting this one, just in case. Pete

Can you tell me what sort of PC you have? Is it by any chance a Microsoft Surface Pro? Pete

Ah, sorry. Different to FSUIPC4,5 and 6 then. I didn't remember that had been changed. Ah, I'm all of 11 years younger and already get tired in the afternoons! Pete

Yes, you should always try to use the latest. However, if you don't see the connections check screen or the added "PFC ..." menu entry in FSUIPC, then there's some thing wrong in any case -- probably the DLL hasn't been placed in the correct folder, next to FSUIPC7.EXE. If the DLL is being seen and loaded there will be an entry saying so in the FSUIPC7.LOG, like this: Loaded PFCcom64.DLL okay! Note that the PFC driver isn't loaded until FSUIPC is properly connected to MSFS. So in the Log this confirmation appears after the line: -------------------- Starting everything now ---------------------- Pete

Since these are new since the last MSFS release is has to be related to some (undocumented?) change in MSFS. FSUIPC is merely using the documented SimConnect interface, and the CTDs seem to be exacerbated by heavy SimConnect usage. FSUIPC is probably still the add-on which uses the most SimConnect functions and it does so frequently. When Asobo reply "The root cause is being researched" it means that they are trying to work out what they changed which has made SimConnect so precarious. And the problems aren't just occurring when FSUIPC is running, it just makes them more likely because of its heavy use. John wants all folks to report CTDs in MSFS reported to Asobo even if they probably have already seen similar reports. The priority with which they attend to these things will likely depend on how serious it appears to them, and the only true gauge they have of that is from feedback and reports. Pete