Pete Dowson

Version 5.131 is now available. Pete

Yes, it is identical. It'll be fixed in 5.131, probably later today -- tomorrow latest. Pete

I've located a problem here with the use of Number keys (0-9 on the main keyboard) when used in combinations. Does this describe what you see? If so it will be fixed soon -- probably 5.131 and hopefully tomorrow. Pete

Lua plug-ins started by another plug-in, like ipcReady do run in separate threads, just like starting them by assignment. All plug-ins always have their own thread. Pete

Can you provide more details please? I have nothing to go on from this brief report. The exact button press combinations, and maybe a log from both 5.13 and 5.124a for comparison. Please enable "button and key logging" in the Logging tab first. Pete

Well, possible, yes. eeded? Debatable. How do you build up such a number? What do these actually do for you? I cannot imagine why you would ever get so many! Actually, as for Macro Files, the limit is 127. Maybe this part confuses you?FSUIPC allows up to 256 simultaneously running Lua programs, each independently running ... You can get to 256 running plug-ins by having plug-ins started by other plug-ins, much like the way LINDA works. In that case your plug-ins can be anywhere as you can give a path. The 127 limit is only on the ability to assign to them in the assignment drop-downs. But why Lua plug-ins? And do you really have 112 different types of aircraft (I don't mean different liveries or minor variations)? And wouldn't most needs for controls come down to macros for L:Vars or Mouse Macros or (for the PMDG Boeings, for example) custom controls? What are the Lua plug-ins, which really prove a way of programming rather than assignment, doing for you? Incidentally, if you are using P3D4 and FSUIPC5, then such an enhancement is more reasonable as it is still being developed. But there, with the release of FSUIPC 5.13 you have a Mouse Macro facility which will work for all switches and knobs on all aircraft (courtesy of nice new facilities provided by L-M). Pete

Strange. I also use IDM on my main PC, and I don't need to do that! And the "https" part is correct -- it just means that it is "secure" (needs a password or registration?). I use Chrome for my browser and IDM is an App added to it, so it operates as part of Chrome and therefore within its registrations. Anyway, I am glad you found a way to do it, albeit rather mystifying. Do you have a link to the Google place you found which explains this, as I'd like to know more? Thanks. Pete

Well, I don't know what to advise. Sorry. It dowsnloads fine here. Are you sure it isn't a virus checker at your end objecting to it for some reason? After all, that's two different download sites -- and furthermore the two files are not by the same name. The one here is called "Install_FSUIPC513.zip" and the Schiratti one is just the usual "FSUIPC5.ZIP" (as it has to be to maintain links in many places)*. The fact that it occurs with two differently named files certainly implies it is something at your end disliking the content. Try temporarily disabling your virus checker. Pete * And Enrico hasn't yet updated the text there to say it is 5.13, but it certainly is as I've proven by downloading it and opening the ZIP.

It downloads fine here from there. Can you try the normal one, in www.Schiratti.com/Dowson.html?

I need to know which place you are having problems with — here in Download Links subforum, or over in the Schiratti site? Pete

Well done! So IVAP is the culprit! I assume they have a Support Forum? Pete

You merely edit the [Profile ...] section in the FSUIPC INI file (in your Modules folder) so that the entry after the heading reads something like 1=A320 or some suitable part of the name to narrow it down to the FSL ones only. This facilty is described in the documentation. eg. the first paragraph in the Profiles section of the Advanced User's guide (see contents for page number), and Appendix 2 in the same document is a User Contribution which goes into more detail, with examples. Pete

The failure of FSUIPC to start is probably because Windows has marked it not to be loaded. This must be due to a previous FSX crash either blamed on FSUIPC or when FSUIPC was the last DLL running. The latter can happen simply because something else caused FSX to crash and FSUIPC has many threads, for Lua plug-ins, WideFS and the like. You say it was okay for 4 weeks and then suddenly did this. That can't happen without something changing -- so what changed? That's what you need to identify. Seeing the DLL.XML file is not much use to me, except for showing several other add-ons which could also be causing the original crash. What I need to see is the crash data. Open Event Viewer, find the Application Logs, and scroll down the Event List til you find a Red icon labelled Error, and identifying FSX as the culprit. Then copy the text data in the lower panel and paste that into a message here. There's absolutely no point in deleting it, but using the FSUIPC4 Installer to re-install usually fixes the Registry entry which tells Windows not to allow FSUIPC to load. One other thing to do is to remove / rename your DLL.XML file, then re-run the FSUIPC4 Installer. that will create a new DLL.XML file which only loads FSUUIPC. If that works okay then there's a problem with one of the other programs being loaded. Pete

Is that showing FS time then? Pete

I've moved your post to the Support Forum, where all FSUIPC questions should be posted. you posted in the "User Contributions" subforum, which, as its name suggests, if a repository for useful contributions from users. you won't get answers to new questions there. The 737 can pretty much turn in its own radius, so there's something wrong with the way you are doing it or the PMDG model. Have you tried using the built-in FS/P3D pushback, or perhaps considered GSX? Without knowing how you are doing it I couldn't say exactly what you are doing wrong, but certainly there's not going to be a pushback facility in FSUIPC. it really isn't needed. Pete

Do you need Saitek drivers? Mostly Saitek software interferes with norm Windows joystick treatment. If you are assigning in FSUIPC there's no need for any Saitek software at all -- except for their display modules. I'm very pleased you found a combination of installs which worked well! Pete

FSUIPC uses the built-in P3D4 SimConnect. The SimConnect DLL used by many programs isn't installed by the P3D installer. Those programs needing it, generally those originlly written for earlier sims (FSX -- P3D3) need the "Legacy" installers folks download for FSX or FSX-SE. I think the early versions of P3D also had them. I'm not sure how remote (networked) PC installations of programs handle this, though, as they also need a local SimConnect installation. I know some come with their own builds -- Prosim are doing this now, for instance, but for all the ones I use I install one or all of the three available FSX Legacy SimConnect versions. Were all those add-ons you have originally written for FSX or older versions of P3D? If so there must either be a SimConnect DLL installation, or they are all either FSUIPC-based applications, or they don't interface at all to P3D in the first place. Maybe this should be determined first. It might help with tracking down the problem. Certainly FSUIPC is a big SimConnect user -- 99% of everything it does, which used to be via hacks into code in FS9 and before, and about 20% still so in FSX and P3D1-3, is, in P3D4, via SimConnect. Obviously a heavy usage of FSUIPC by add-on applications (for actively writing to P3D, not reading which doesn't increase SimConnect actions) could be a factor here. Pete

Do they wear hats with corks hanging down in Virginia, too? Thought that was an Aussie thing. I’m not surprised! Seems like some sort of multiple interaction. Maybe it’s also dependent on the order of loading, and also possibly it’s a timing thing which changes according to the order. I think you might need to eliminate just one add on, and give it a longer test. Then add it back and eliminate the next. I’m just trying to think what I would do in such circumstances. Pete

Wow! Where are you, Australia? (Ah! I should have guessed so from your pic!) Pete

BTW just to show there can be other causes of serious freezes, take a look at https://www.avsim.com/forums/topic/535967-having-problems-with-5-10-second-freezes/ I know this is not applicable in your case (since Autosave on/off makes the difference) but it does illustrate that the matter is not as simple as taking the straight line choice. One idea is that it may just be that the small delay any file saving does make is causing an FSUIPC application to play up -- when FSUIPC makes the request itself (and thus without the Sim signalling a "stop" as it would for both the ; and menu way of saving a flight). Or possibly one or other of the add-ons you are using is a serious SimConnect user and that somehow reacts in a similar way. Are you a WideFS user by any chance, because if you are there's another check you can do? Pete

By the way, this: is a message from one of the add-ons you are using. FSUIPC has no such message. Something you are using is an FSUIPC Application, evidently. If FSUIPC loses connection to SimConnect it will log this event and proceed to re-initialise the connection. That certainly can result is noticeable pauses, so please check the FSUIPC5.LOG file (in the P3D4 Modules folder). Pete

That's definitely some sort of SimConnect problem then. Try a process of elimination on the other add-ons. Start with none then add one at a time. I assure you that it is most certainly NOT anything FSUIPC is doing, nor can do. There's simply no code to check. It's a simple call to SimConnect. Testing here with no other add-ons there's absolutely no hesitations caused by AutoSave, and I've set it to every 10 seconds to make it more noticeable! Pete

There's nothing I can change or do differently in FSUIPC. As I said, it is a simple call to SimConnect, as it always has been since the start of FSX back in 2006. If it doesn't turn out to be extra files being saved by your add-ons then there's something wrong with P3D or more specifically SimConnect and you will need to report the issue to L-M. BTW I already have little to no hair (see my pic!) ;-) Pete

No. The Autosave facility does nothing more than sending the exact same request to P3D as you would manually by using the ; key or the P3D menu and entering a name. What then happens is that P3D saves the flight details normally and sends notifications of this to any add-on which asked to be notified. Few applications are interested EXCEPT sophisticated add-on aircraft, especially those from PMDG, which then freeze the sim whilst they collect and save files for all of their sub-systems. If you don't believe this, try autosave with a default aircraft. Or use the ; key for the default mechanism and enter a filename. Time how long it takes after pressing Enter. This information, especially for PMDG aircraft, would have been easy for you to find if you'd looked, or at least asked, before pulling your hair out. Now you'll want a toupe, needlessly! Pete

Old? You don't look any older than me! (I'm 75 this year). Pete