Pete Dowson

If FSUIPC is not registered -- i.e. you've not paid for it -- then you cannot assign buttons or axes in FSUIPC nor can you calibrate in FSUIPC, so FSUIPC has nothing to forget because it has nothing to remember. I think you must therefore be talking about FS itself forgetting your settings, and that is usually either to do with the drivers for your hardware, or faulty hardware, or maybe the power management on the USB ports -- Windows by default lets them go to sleep to save power. Either way it seems you were transferred here incorrectly. This Support site is for FSUIPC and WideFS users. Regards Pete

But evidently you missed the part about how to use the RunKey option with KeySend! Because you did not equate the KeySend with the RunKey program, that is why, as I showed. Why would you think a KeyPress assignment entry for FSUIPC would do anything in WideClient which has no keypress assignments facility in any case? And why do you want the KeySend to press a key in any case -- you said you wanted to start a program, not press a key!!! English may be difficult for you, but you will frustrate yourself even more if you simply do not read what is presented to you. You ignored my answers in my last message, and you seem to have ignored the very part of the documentation I mentioned and even reproduced for you above! It is STILL because you persist in not entering the correect assignment for the KeySend. I actually told you EXACTLY what line to put in in my last message. Why did you ignore that and persist in doing things your own invented way which bears no relation to what is needed? Change that to KeySend1=RunKey1 i.e Exactly as I told you last time!!! How otherwise do you expect WideClient to even know which program to start? Assigning the KeySend to a keypress just makes WideClient press that Key. Nothing else! That syntax is for pressing keys! Not starting programs! This was made clear in the odcumentation and in the bit I quoted last time by: The KeySend facility can also accept any of these keywords after the KeySend<n>=: RunKeyN, CloseKeyN, RunReadyN, CloseReadyN, RunN, CloseN As you must surely see, KeySend can be set to run (or Close) ANY program,, whether RunReady, Run or RunKey. The only difference with RunKey programs is that they can ONLY be started by the KeySend. With Runthey start immediately too, with RunReady they start when FS is ready too. But all can also start with a KeySend assignment. EXACTLY AS DOCUMENTED IN THE SECTION I QUOTED FOR YOU, and which you ignored. Why did I bother to write all those details and include the answer in my reply if you just ignore it? :sad: Pete

Where do you get that syntax from? It is nothing like anything documented.. KeySend1=191,8 would be valid, and would cause the /? keypress to be send on the Client PC when the KeySend 1 was received. I assume you don't really want that? And of course the "1006,1" part you have afterwards is completely meaningless -- in FSUIPC 9not WideClient), control 1006,1 is KeySend1. What do you think that would mean assigned to KeySend1 in the Client? The client knows nothing of FSUIPC-added controls! You really should read the WideFS documentation. This part, in the technical guide, tells you the format: So the line in your case is surely "KeySend1=RunKey1", assuming you only want the program to be Run when that KeySend is sent. Actually, I think you've just not read the relevant part of the documentation, otherwise you would have surely seen this? Regards Pete

Good! Thanks for testing. The current release is 4.827 (other urelated corrections, to do with Lua). I'll build a new Install package tomorrow. Meanwhile you can notify the others in the P3D Forum thread. Best Regards Pete

Yes, there's a summary at the end of the log after the Sm has closed. There may also be one or more lines showing: *** G3D bad pointer trapped and crash prevented *** but this is only logged at most once per second, to aboid filling the log if there's a whole bunch. The summary contains the true count. Regards Pete

I moved your question to the Support Forum so it'll get answered. You posted to the "download Links" subforum, which is for ... download links! ;-) I've really no idea what settings you mean nor why you might be losing them. If the problem is due to bad hardware sending inconsistent cvalues -- such as when the pot measuring the lever position is loose and moving as well -- then, no, there's no software fix. You'd need a hardware fix. In other words, you need to determine what is happening before finding the solution. What is "run as admin" to do with anything? If you are using an old version of FSUIPC3 or FSUIPC4, with FS9 or FSX or some other version of FS (you don't even say what!), you will need to update in any case as I cannot support old versions. Regards Pete

If you are talking about FSUIPC and FSX (you mention neither), then the current full version of FSUIPC4 is 4.823 and there is an interim update 4.826. Version 4.57 is years old and completely unsupportable. Regards Pete

It might be worth your while asking this over in the MyCockpits forums. I think there are a few Sismo users there. http://www.mycockpit.org/forums/ Pete

Always download the latest. Currently that is 4.826. All old unsupported versions are always removed. Please look in the Download Links subforum. Pete

Looks like your registrations have been revoked. If you want me to check, ZIP up your KEY file (do NOT send unzipped, it won't get through. In fact for safety rename a copy as "FSUIPC4.key.txt" and ZIP that). Send it as mentioned earlier. Pete

There's absolutely no difference in how and 4.xxx versions check the keys, so your findings are rather inexplicable -- unless your keys have for some reason been revoked. Last time someone reported anything like this it turned out that they had two installations of FSX and were running a different one from that which the KEY file had been created. Why did you re-register in any case if all you were doing was updating from one version to another? Please show me the FSUIPC4.LOG files from both the 4.82x install and your "old" 4.30 or whatever so I can compare. In both cases please close FSX down first. Don't post any confidential data such as keys here, but ZIP both logs and your KEY file and send as attachment to petedowson@btconnect.com. Regards Pete

In FS9 and before you could simply test offset 0760, the recording on/off flag. I'm afraid I never found it in FSX and though it was one of the promised items in SimConnect it never made it before the development ended. Sorry, Pete

Okay. Found it, thanks. The change was the suspension and resuming of Lua threads when the DirectInput devices are being re-scanned. There was a path through this which exited without doing the "resume" so all running Lua threads remained suspended. Ironically the change was to prevent FSX crashes which appeared to be due to LINDA activity simultaneously with FSUIPC's rescans. Sorry about that. Wish it would have been found earlier as there have been at least six releases since I made that change. :-( FSUIPC 4.826 is being built right now. This also corrects the separate Lua logging, where the time value got stuck at the end and the Lua.n number was unnessessarily included (only needed when all Lua logs merge into the FSUIPC log). I'm awaiting confirmation that 4.825/6 also handles the G3D.DLL crashes in Prepar3D. Then I'll build a complete new Install package. Regards Pete

Please ALWAYS give version NUMBERS. I've no idea what you mean by "previous " and "latest"! The latest one uploaded for tests by one or more users was 4.825, the previous one 4.824. The last "report" of any problem I received here quoted 4.703 as "previous" and 4.80 as "latest". I really can't work things out without proper reports. All releases are numbered, and this is the reason why, so I can keep track of things. It's a bit late here at present for me to start looking at this. I'll check it with 4.825 in the morning. Regards Pete

First, there is an evident misunderstanding here. The button flags for a real button are automatically toggles each time that button is pressed. This is a deliberate action to allow an easy adaptation of a momentary button as a locking toggle switch. If you want to use a flag to change the action of a button press you need to choose one which cannot be used by a real button -- i.e. one associated with a joystick you don't actually have. So, change your lines 1 and 2 to toggle flag 15,0, and 15,1 for example. Second, yes, in order to make something change faster, send the same control several times. Just repeat the line with different line numbers. and, of course, the same condition. That's an option for all FS controls. However, there's an easier option in this specific case because FSUIPC provides a special additional pair of controls (not FS ones) actually called Heading bug inc fast and Heading bug dec fast. They operate in 10s. In fact I think (not sure now, they are so old) that both change it to the next or previous 10 degree mark. I'm surprised you missed these as they are listed in the drop down assignments, and also in the Advanced User's list of controls a little after the 1005 you are using. Regards Pete

More information is needed.

I got a reply and permission directly. Please download FSUIPC4825 and test it for me -- I haven't got any G3D crashes here. When you confirm, I'll upload it to Download Links and you can notify folks in that P3D Forum thread. Okay? Regards Pete

Do you mean the facilities to run programs, like the ones in the ext Lua library added back in September, soon after your request? Here's the entry in the current FSUIPC4 History file: The current versions of FSUIPC are 4.823 (with a minor 4.824 update available too), and 3.999g, with WideClient at 6.961. They all include these facilities among many others. See the Download Links subforum. I think you perhaps need to scan the forum occasionally for updates? ;-) Pete

There is no interaction between the 737NGX and FSUIPC, other than the provision of data from the 737NGX if you've enabled same as documented in the NGX SDK. And FSUIPC has absolutely nothing whatsoever to do with graphics like 2D or VC renditions. You really need to look elsewhere for a solution to your problem. Pete

I've just written directly to my contact in LM. I'll get back to you when I have a reply. Regards Pete

Good. Thanks for confirming. Pete

Yes, of course. Same as Ultimate Traffic 2 using SimConnect to create AI Traffic and GSX to create ground traffic. That's not a specific Multiplayer facility, it's an AI object interface. FSUIPC uses the same interface to get information on objects for TCAS tracking and to remove certain airport vehicles when AES is active. If you want information on AI aircraft you can get that from SimConnect, or via FSUIPC if you like. If that's the only information you need t could use something ready-made like Super TrafficBoard, or evben my own freeware TrafficLook. Pete

No, not without writing a driver for it. Sorry, but it would be far cheaper to buy a USB serial port adapter than to commission a special driver! ;-) Regards Pete

Of course you can. You don't declare varaibles, though, just set them, like "LandingGearLights = 0x29C" or "local LandingGearLights = 0x29C" if you want to restrict that to within a function or code block. I don't publish a Lua language guide, only the documentation for the libraries added by FSUIPC and WideClient. The full documentation and assorted tutorials are available on the Lua website or in books you can purchase, as with other languages. Pete

Doesn't really matter. Either way it's being converted to a binary number. Te most efficient way is possibly the one you've not mentioned, decimal: Hex 029C is decimal 668. so "event.offset(668, ..." would do the same. But I'd defy you to measure any actual difference in practice. Regards Pete