Pete Dowson

Thank you! To you and yours too, Pete

I don't know what "steps 1 and 2" are, but if there are ANY files at all with filetype Lua stored in your FS Modules folder, then any recent version of FSUIPC will most certainly be listing them in all the possible assignment dropdowns there are! In fact it will list them with a Lua prefix, a LuaKill prefix, a LuaSet prefix, a LuaClear prefix a LuaToggle prefix and a LuaDebug prefix! So, for every Lua file you will have 6 extra entries in the drop-downs! The entries are sorted alphabetically, and once the drop-down has dropped you can get to the #lua entries quickly by typing LU quickly enough. Regards Pete

You have others? Without staying in thread I'm sorry but I cannot keep track of different folks' complaints! Where are you looking? So it does recognise axes, even though you just said is doesn't? You seem confused. The calibration section only sees assigned axes. If oyu don't assign them in FS or FSUIPC you cannot calibrate them. There's no difference between 4.60 and 4.645 or any in-between increments in any of that. Pete

Sounds like they are faulty. Are they reasonably new -- you should get them fixed. The spikes were very definite one-off maximum deflections, one way or the other, and caused by something specific as far as I recall. If they are just jumping then the most FS can do is filter them (the little F button). But mostly jumping about is caused by doupble assignment. make sure they are not being assigned both in FS and FSUIPC. Regards Pete

But you've installed the PFC driver, PFCFSX.DLL, into the FS Modules folder. Nothing I provide will do that, It's a purely manual process by the user (i.e. you). Sorry, I don't follow. If things accept COM ports with such large numbers, I suppose you can do that. You need to be careful though. But the PFC check is done by the PFC driver which is looking for PFC devices. Perhaps you should simply delete PFCFSX.DLL and its INI and LOG files from your FSX Modules folder. How on Earth did you come to install it in any case? Pete

Hmm. Does the thread description show up in the brief list? I'll try it. I still haven't got the hang of this new forum software yet! ;-) Pete

Which manual tells you that? It sounds like the known SimConnect bug. There's another thread on this subject which I explained in great detail the options you might have. See . If that doesn't sound like your problem i need to see the Install log file, and if there is one, the FSUIPC4.LOG file. Both from the FSX Modules folder. Regards Pete

That is supposed to happen (100 changing to 1000's on keypress repeat or mouse hold), but 30 times in one second is wrong. Sounds like the Rotary (or SPAD?) repeat rate is too high. Too many keypresses getting queued? I never like keypress methods. If it's the rotary sending on/offs very fast, doesn't turning it slower do the job? You could do almost anything you like with Lua, but I'm not sure how the mechanism would work. What can you make SPAD do to help? Pete

Can you tell me how you have it assigned. What controls? Buttons with the repeat whilst held option normally work fine. I didn't realise SPAD provided button emulation too -- others seem to be using it to send keystrokes. Regards Pete

Or, as I suggested, simply assign the key release in FSUIPC to do something you don't care about, something completely innocuous. Regards Pete

The only difference is that the Ident writes to a different byte of SB4's ClientData. It uses SimConnect in exactly the same way for all of the SB4 inputs. I don't have SB4 installed and don't use it at all. The facility has been tested and proved working by others. All I could do is verify that my end was doing what it was intended to do. If you want me to verify that on your system, with SB4 running, you'll need to get a SimConnect log, as it all happens there. If you look in the FAQ SubForum it tells you how to how to get one of those (FSX Help: Logging SimConnect"). Otherwise, sorry, but you probably need to go to the SB4 support forum and ask around. Regards Pete

The controls for that were named by Microsoft as "Kohlsman inc" and "Kohlsman dec", after the German maker of the first altimeters to feature that "Kollsman Window" (note my spelling which is correct, unlike Microsoft's). To determine the name of any regular FS control simply enable event logging in FSUIPC and use the switch or knob in the usual way. Then look in the FSUIPC log to see what it is called. Pete

Is this a newly connected VRInsight MCP COmbi you are wanting to use FSUIPC with? Which PFC devices do you have? What COM device did you use to have the PFC device connected ot? Any COM port which is available will open. That doesn't mean the right device is there. Er .. you have a PFC MCP as well as a VRInsight version? Why bother with the VRi one when you hsave the far superior PFC one costing 10 times as much? I don't understand. All that shows is no PFC COM device on that port. I'm not that surprised. Why are you using COM50? What happened to COM11 through to COM49? Is it correctly created in your VSPE? Pardon? If you don't want to use SerialFP2 you must program everything in the VRI device(s) yourself. But please answer the other questions first. Why do you even want ot use a VRI MCP when you have the splendid PFC one? Pete

Sounds like it timing out. Saitek devices seem to take a while to respond sometimes, and FSUIPC is fussy. Are you using a old version of FSUIPC? Because that was changed to be more tolerant in 4.60 and 3.98. Just delete the [Axes] section in the INI file. But make sure your FSUIPCs are up to date. Also see the Download Links subforum. Pete

Yes. Their software is not cooperative, unlike mine. Their LED states can only be set by writing all of them at once. GoFlight provide a facility to READ the LED states as well as WRITE them. FSUIPC's Lua reads the existing states of all of them before changing the ones you want to change and writing them all back. That preserves the states of those written by others, so -- cooperative. Unfortunately GoFlight's own software doesn't use the facilities GoFlight provides. The software assumes it is the only thing accessing the hardware and doesn't read them to preserve other settings. I have asked for this oversight to be remedied, but nothing happened. Regards Pete

I'd rather do support for my products here. I'm not sure where your delay is coming from, but I have both RC and ASE on a separate WidClient PC and there's no noticeable difference now from before. When RC asks for the weather for a particular location, FSUIPC asks ASE for it, and updates it in FSUIPC offsets withing a second or two. Altogether that's 4 transfers over the network for each request. But they never amount to more than a couple of seconds. Since RC is supposed to allow at least 10 seconds to answer any request I'd be amazed if that timeout was ever exceeded. It would mean that your ASE program was simply not getting adequate processor time. What RC sees is EXACTLY the same as it always has been. The DWC/ASE linkup in entirely a matter between FSUIPC and ASE. FSUIPC would otherwise read the weather from SimConnect -- and depending on how busy FSX is, that can take a second or so too. You are way off beam in your speculation about some sort of "weather parsing". If you have delays on your system it is because something isn't being able to run adequately and/or, if networked, your network is running badly. I seem to recall that BEFORE the new facilities, allowing use of DWC with correct weather, folks were saying use of DWC slowed RC down intolerably, and the advice I saw on the RC forum was to turn DWC off. Maybe this is what you are seeing, not the result of any new facilities! You could easily check by setting the UseASEweather parameter to 'No'. Didn't you think of that? From other reports I've seen, ASE SP2 along with these new facilities have made things for most RC users more responsive, not less. So something would seem to be wrong on your set-up. Regards Pete

FSUIPC3 uses the Windows "joy" interface, which supports 32 buttons (0-31 or 1-32 depending who's counting), plus 6 axes and one POV (Point-of-view, or 'Hat'). FS9 and FSX and FSUIPC4 use the DirectInput interface, which supports two extra axes and another 3 POVs. Later versions of DirectInput support up to 64 buttons I think. So, if those Saitek controls aren't seen by FS9 nor FSX, I'm afraid FSUIPC has no hope whatsoever. Unless the freeware SPAD program can handle that device I think you are stuck with Saitek software. SPAD is at http://fstools.weebly.com. Regards Pete

Sorry, what 'page' is this? What Lua file? The one you are saving? Surely if you have downloaded it or copied it, as a file for saving, it is a file, a single file. If it was multiple files, it will be multiple files. I don't know because I don't think you are referring to noe of mine? Pete

Have you just installed it? If not, before this morning did it load without any prompting asking if you wanted to trust it? And what have you changed since it last loaded okay, if it did? Have you installed something else? Without seeing the Install log I don't have enough information to be sure, but are you running an old version of FSX? If it is not fully updated (SP1 and SP2 or Acceleration) then please get it so. The problem is almost always due to a known SimConnect bug which causes some sort of clash when it is involved which checking module credentials. It was really bad in the original release of FSX, and never actually properly fixed but the updates did make it occur less often. Once FSX has the module listed as "trusted" it is never again a problem. The trouble you are having is a crash just when it is trying to ask you if you trust it or not. The crash is much more likely when SimConnect has several things to load, so one way around it which nearly always works is to temporarily rename your DLL.XML and, if it exists, your EXE.XML files, THEN re-run the FSUIPC installer, then run FSX to get FSUIPC trusted. After that you can close FSX, delete the new DLL.XML file the FSUIPC installer would have made, and rename the original and EXE.XML files back. Those files are found in the same folder as your FSX.CFG file. I could tell you exactly where if I had sight of the Install log -- but take a look yourself. Also, please do check whether FSUIPC is creating a run-time log (FSUIPC4.LOG) in the FSX Modules folder. If it is it may be an entirely different matter -- I'd need to see that log. Finally, you could try replacing the DLL in the FSX Modules folder with the latest one from the Download Links subforum. We are up to version 4.645 now. There's just a small chance that the difference in size will change the timing in SimConnect sufficiently to avoid the clash. Regards Pete

Did you not even find the Installation and Registration guide inluded right next to the Installer, inside the ZIP? Please find it and read the first few lines which tell you what you get and where it is! :-( Pete

Yes, but only by using a Lua plug-in. Take a look at the example supplied and installed in your Lua plugins Zip. It's called "TripleUse.lua". It's one I made for my own use and gives different results for a single quick press and release, a double quick press and release, and a longer press and hold before release. I'm sure you can adapt that to whatever you need. Regards Pete

I assume you are doing this in the version 4.60 installer or later? If not update! Otherwise the problem will be that you are making a mistake entering some of the details. You have to spell your name the same way as well as the email address - exactly the same as your Registration. All three parts are linked together and cross-checked. The only other possibility is that you purchased keys for FSUIPC3 and WideFS6 by mistake. But if you are Bruce, I think not. Pete

The GoFlight software should be able to handle the V/S setting quite easily for all default aircraft, as that is just a simple FS function. I'm sure it must work okay, but you need to go to GoFlight support because I can only support my own software. Regards Pete

Sounds like you have different assignments for different aircraft. FSUIPC will not change any assignments you make, but you can make different assignments if you wish for every different aircraft you have. Explain what you want to do. FS doesn't suppply a separate "reverser" functions -- the F2 key simply gives "throttle decr". Reverse thrust is simply negative forward thrust. if you want separate reverser axes FSUIPC assignments provide that. Pete

I'm not surprised! According to your details at the end of your message you are using FSUIPC version 4.57! I should have noticed that in your small print before! 4.57 is well out of date and many of the new Lua facilities were not implemented then, and some were still breing tested and buggy. There have been about 50 releases since then, the earliest suported one being 4.60. Please do not come to the Forum seeking help without also checking you have an up to date FSUIPC because it wastes a lot of time for all of us. After installing 4.60 (from the Schiratti site) you will do well also to update further to the very latest version, 4.645, which you'll find in the Download Links subforum. Pete