Pete Dowson

Sorry, I can't seem to do anything with your attached file. Couldn't you simply copy and paste the details? The only relevant parts are Module Name, Module Offset and Error Code,. If the Module name quoted is FSUIPC I can look into it with that data. If it is something else then it is unlikely. I'll see if I can adapt the Lua code to run here so I can test on my system. I don't have EZCA but you say it happens in any case without EZCA running? Pete

Sorry, now home and reading this properly: The light assignments I use in Prosim do not include Cabin Lights. I don't think they work for me in the Prosim 738 model. This thread, which does imply that they should or may work, from the model's Prosim Forum is relevant: http://prosim-ar.com/forum/viewtopic.php?f=88&t=9561&p=70945&hilit=cabin#p70945 I've never really been bothered with cabin lights as (a) my cockpit has no such switch. They are controlled, I think, by the non-pilot crew, and (b) I'm rarely looking at the aircraft from outside, and especially not at night, so never really notice this deficiency. Pete

Weird! Glad you managed to nail it. Pete

Sorry, but I've never known an Elite system to work correctly, if at all, with FS except with Elite drivers. I don't even think the protocol switch works to give the later PFC protocols I know and programmed for, but some older version. The only folks I think you can get help from would be PFC or Elite, unless you are a programmer and can use the appropriate monitoring tools to see that signal formats you get and write to decode them appropriately. That's what I'd do as I enjoy it, but I always had the hardware attached in order to be able to do it. I programmed the PFC stuff I had like that (and FlightLink EPIC-based stuff before it). Pete

Program both "press" and "release" for the same controls. That's the most you can do. Each click is either a press or a release. The default poll interval should be sufficient. Any other delay is down to the processing in the gauges, or whatever is processing the controls. Pete

The first part, the [LuaFiles] section, is entirely automatic, and is not relevant. The [Auto] section loads the plug-in for the entire session. Only profile-specific Auto sections will load and kill plug-ins according to the aircraft loaded. Were you expecting your plug-in to close and reopen across each aircraft reload? Windows crashes are recorded in the Windows error logs. That is the information needed. There is no way I can help without that. Go to the START menu in Windows and enter "Event Viewer", then find your crash. The way you are starting the plug-in is universal, it is meant to continue for the entire session. There is something else causing the crash when changing aircraft. I have many plug-ins running for whole sessions. No, the whole plug-in is still running. There is nothing about changing aircraft which would influence it. It is much more likely to do with your view options. But I can't tell anything with no crash data. Pete

Wow! 17 months later? I'm away from my system at present. Please post again on Monday, or later, when I am back. Pete

The offset has all 4 digits in one encoded number, as a BCD value. The separate inc/dec controls are in any way easier to use unless you use a driver or plug-in to handle the values. Pete

How is the script being loaded? The "Kill All" facility simply loops terminating all running plug-ins, each in exactly the same way as killing them individually by any means. So, what is this crash? Where are the details? And why do you think it is anything to do with whether the Lua is terminated or not? Why do you think that it not terminating would cause any sort of crash? Without the lines between startColdAndDark and setowndisplay there are no Events pending to keep the plug-in running in any case, so it simply loads, runs once, and terminates. Pete

Yes, Thomas, but he's saying his old registration isn't working. Pete

Perfect! And it controls the aileron position, as you indicated in your original message, here: So the input works and is correctly calibrated, and it obviously has the desired effect in the simulator, so is it just the visual affect on the wings when using an external view? Maybe it's a bug in the add-on aircraft you are using? Pete

With scenery, I just install everything only in FSX-SE (which I use mostly in any case), and edit the SCENERY.CFG file so that all of the add-on entries have full paths, not sim-relative paths, and then use the exact same SCENERY.CFG file in both FSX-SE and P3D. Some sceneries (but very few) also install some stuff into places like Effects too, but not many, but I just make sure I have all the same Effects in both sims too. Pete

Except for showing that you are using an older unsupported version of FSUIPC (4.947c), the INI looks fine, the calibration looks fine. But what is the RANGE of values for IN and OUT? That's the important part of my question. You only give both as 0. If they stay as 0 whilst you move the yoke then that's a big problem. The input from the aileron axis is stuck at 0. Please update to a supported version. Current is 4.955c (released 14th June). Pete

No. But then with the aircraft models I've used since we were able to modify the frictions have never seemed to need such adjustment. That is the Project Magenta 738 with PM, and first the Jetstream then the Prosim versions with Prosim. I would probably try using it on my Piper GA simulator when I get back to commissioning that again. Probably with P3D for better VFR visuals. (I use FSX-SE with Prosim on my 738 cockpit for better performance). Pete

Hmm. Thanks for letting me know. I have to assume that the cause really was the order of loading of FSUIPC4 relative to the AS Connect module, as_btstrp.dll, although I think that was one of the things we thought we'd checked. Pete

You appear to have no Event logging enabled for the Logging, so it really isn't useful. Also, please do not start a new log --- by doing that you fail to provide essential start up information, like version numbers and log setting. Pete

The Event logging should show the events occurring no matter where they come from. Which version of P3D are you using? Early version 3's had a problem with SELECT controls, I seem to remember. I can't check at present, away from my main system, but what happens when you use the keyboard Shift+E then 3? With and without FSUIPC? And with Event logging when with FSUIPC? Pete

Keys for FSUIPC never become inactive, so how do you work that out? The registration data is only EVER stored in the FSUIPC.KEY file, which is a text file within the FS Modules folder. There are no copies elsewhere, and that file is rewritten if you re-register. Since registrations never become inactive, you evidently have something else going on there. Please show me the complete log file, with FS closed. Pete

Toggle Aircraft Exit with no parameters, and no immediately following "SELECT" control, opens passenger doors only, exit 1 -- same as pressing Shift+E 1. The SELECT controls, 1, 2, 3, 4 are by default assigned to the 1, 2, 3, 4 main keyboard keys. You don't say how you are operating the doors, but if you are using keypresses Shift+E and 1, 2, 3 or 4, then FSUIPC will need the "time to select" parameter left default in order to ensure they are properly associated. And you'll need to check that you don't have the 1, 2, 3, 4 keys assigned to other things. Best to assign directly to Toggle Aircraft Exit with a parameter, 1, 2, 3, or 4, to control specific doors. Aha! Yes! The SELECT_1 to SELECT_4 controls are used to select the correct door(s). I've no idea how it becomes "UNRECOGNIZED" as it's a standard part of FS. See if you can assign to it in FS's assignments and whether it works that way. Or try pressing "3" in the keyboard whilst you have Event logging enabled. Pete

What does the calibration tab show for the ailerons? i.e IN and OUT (range of values seen), minimum, centre (2 values) and maximum? Pete

Also don't forget that all three parts of both registrations must be exactly correct, matching those associated with your original order(s). i.e. Name, Email and Key. Pete

What, none of it., like finding and deleting specific weather related files? "That was the solution. I deleted the WX file and the WXStationList.BIN file and everything is working again." Please explain your problem. Is it the English? Else just delete the default flight's .WX file and the Wxstationlist.bin file and try again. Corrupted weather files are a big problem and seem to occur quite easily. FSUIPC is only involved here because it uses SIMCONNECT to read the weather data regularly. Pete

Sorry, if "nothing happened" how do you know you key was invalid? Please explain exactly what you mean, not your interpretation. The keys never change, and you never need to re-register when simply doing an update! All the update does is replace the DLL and the documentation. Pete

Yes. Both symptoms and the log ( which I assume is all you got? I did ask you to close FS first) point to a corrupted weather file. So please proceed to the references I gave you earlier. Pete

No, LINDA is not mine, and I cannot really help with it -- I don't use it and don't know it at all. The Bodnar cards look like normal joysticks to FS and FSUIPC, so can be assigned directly there. If those assignments aren't working with default aircraft let me know, with details. Pete