Pete Dowson

Sorry my error. The customer number is no use, I need the ORDER number. I did ask for this in my first reply if you check back. If there is no log file in the FS modules folder, then FSUIPC4 has never run. It ALWAYS produices a log file. There will be several FSUIPC files: FSUIPC4.DLL the module itself FSUIPC4.INI the configuration file which will contain all the settings FSUIPC4.KEY the registration file containing your registration details, and FSUIPC4.LOG a text file which is produced anew every single time you run FS with FSUIPC4 installed. There's also an FSUIPC Documents subfolder too, containing all the documentation and other goodies. If you can't see these things you are certainly looking in the wrong place. Pete

By deleting the order number you prevent me checking it. The order number doesn't need to be kept secret, and others don't have access to your account in any case unless you publish your password. And please paste the complete log (FSUIPC4.LOG) from the Modules folder into your message in case I can see something else wrong. Pete

I'll take a look, but I'm not likely to be able to implement anything between now and Feb7th -- daughter's wedding and another break intervening. I've made a note and will get back to you as and when. Pete

Something you are using is either corrupted or is becoming corrupted. The routine in FSUIPC which tries to apply hooks to those two modules only runs once, during initialisation, and that code is never re-entered. The initialisation part succeeded okay, as shown by the easrlier line: 140 --- Wind smoothing fix is installed The errors are being logged by FSUIPC because of some spurious calls being made by code elsewhere, outside of FSUIPC. But FSUIPC isn't crashing. What happens AFTER this, and why are these entries your prime concern? Does P3D crash, and if so what module is identified? I think this maybe a part of the reason so many folks are getting crashes in P3Dv3 with the PMDG 777X during long flights (I see yours was over 5 hours). Check the P3D forum thread P3Dv3 CTD Event 1000 MSVCR120.dll. It also seems to happen with the PMDG 737NGX. I think they have some workarounds now. Pete

Whilst awaiting some fix to my access rights to the Download section of the Forum, you can get FSUIPC 4.949c from Dropbox via this link: Petes Downloadable Files Pete

Unfortunately I cannot at present get access to the Forum repositories in order to upload the corrected version. Seems that when all the SimFlight forums went down yesterday for an "upgrade" not everything was reinstalled correctly. I'm waiting for this to be fixed and will upload 4.949c as soon as I can. Pete

Okay. Found it. It's the same with all the togglebits, setbits and clearbits variations! I don't know why it seemed okay when I tested it earlier. And it seems amazing that it's actually been wrong for years and no one has mentioned it till now! The problem was that originally the same Lua code was used for FSUIPC3 and FSUIPC4. Now FSUIPC3 only has one memory space for offsets, and they are all read and written there. But because SimConnect is asychronous in operation I had to have two such memory spaces -- one for writing into and the other for the results returned (often a little later) from SimConnect. I adapted all of the Lua code to handle this -- EXCEPT for these functions! They were reading and writing the write area, where they should read from the read area, do the changes, and write to the write area. The FSUIPC Offset controls for the same functions work fine because that part wasn't based on original FSUIPC3 code! I've fixed it in version 4.949c, available (DLL only for now) in the Download Links subforum shortly (about 30 minutes or so ...). Thanks & Regards Pete

You posted this AGAIN in the FAQ subforum! Please do NOT post support questions there, and please stick to the thread you already started on the same subject. Pete

How is it possible to hold the space bar with a mouse? I don't understand. And why are you using the space bar to look right in any case? Pete

Hmm. Very very strange. I'll try your test, exactly. Incidentally, you apparently did not turn on the Lua debug/trace option. And you don't want a separate Lua log as the idea is to make the Lua steps inter-relate to the monitoring action. Don't use "Luadebug" to start the plug-in, just start it normally, with a keypress or button. [LATER] Okay. I've reproduced the problem you describe. I don't know why I got a different result on my first test. I'm checking now to see what could have got messed up. Pete

A question first. Why read once character at a time and accumulate them? Why not just read what's there, or at least the 3 characters, all at once (assuming you were receiving anything, that is)? Additionally, i'm not sure whether Arduino terminates strings with a zero as in C. I know it uses a sort of C, but if it does, that zero would be part of the return. I don't think Lua uses zero terminators. And does "println" actually add a new line or line feed code too? That might mess up comparisons for equal strings. However, the answer to the question "why is nothing being received?" can only be that the port is incorrect. The fact that it opened without error doesn't mean it's the correct port. Also COM ports, unlike USB ones, can only be used by one program at a time. You aren't running the Arduino PC programming program at the same time are you? The handle is actually a 32 bit address. You should really only check it it is zero or non-zero, not greater or less than zero. And do consider using event.com to trigger entry to a processing function, rather than a loop with a sleep. Pete

Hmm. Let's examine your assignments: Generic assignments, for all aircraft (unless overridden): [Axes] 0=0X,256,D,4,0,0,0 = generic throttle only. No yoke or pedals. [buttons] 1=P0,1,C65758,0 = Flaps incr -- but no complementary Flaps decr! So what use? 2=R0,2,C65615,0 = Elev trip up -- but no complementaery Elev trim down? So again, what use? You have several profiles, but let's just look at the Cherokee: [Axes.Cherokee 180] 0=0X,256,D,4,0,0,0 =throttle 1=0Y,256,D,6,0,0,0 =mixture 2=0Z,256,D,4,0,0,0 =throttle (why two?) 3=1X,256,D,1,0,0,0 =aileron 4=1Y,256,D,2,0,0,0 =elevator 5=2X,256,D,7,0,0,0 =left brake 6=2Y,256,D,8,0,0,0 =right brake 7=2R,256,D,3,0,0,0 =rudder [buttons.Cherokee 180] 0=P0,0,C65759,0 =Flaps incr, but still no Flaps decr 1=R0,2,C65615,0 =Elev trim up 2=R0,3,C65607,0 =Elev trim dn [Keys.Cherokee 180] 2=68,8,65752,0 =parking brake on D key All of those axes are assigned "direct to calibration", but you haven't calibrated any of them except the toe brakes! The uncalibrated ones won't be working correctly at all. You should either calibrate them, or assign them to the FS controls instead. Your toe brakes look to be the only things which should be working okay: [JoystickCalibration.Cherokee 180] LeftBrake=-16380,16383/8 SlopeLeftBrake=2 RightBrake=-16380,16383/8 SlopeRightBrake=2 So, I'm suspecting that your problems are mostly due to the fact that you have controllers still enabled in FS. You must not assign axes and buttons in FSUIPC without disabling controllers in FS. That could easily expain why the toe brakes are misbehaving. However, nothing explains why your parking brake is coming on, unless somethnig is sending a "D" keypress, or the assignedt FS keypress for the same function. The parking brake cannot come on through anything FSUIPC is doing. Pete

If the Aerosoft lights are handled by an LVar, don't you need to write to that LVar to change it, not 0D0C? The latter collects together all of the default FS-implemented light switches. Correct. If you are programming your own application using the regular FSUIPC interface you'd need to read 0D0C, change a bit using AND, OR or XOR, and write it back, hoping no one else had changed it in the meantime. But from Lua the setbits, clearbits and togglebits do it for you with no intervening changes guaranteed. Strange. If this were happening many things would be going wrong -- the technique is used extensively. No, that looks fine. Please try two things: 1. Monitor 0D0C using the Monitor option, right-hand side of the Logging tab. 2. Enable Lua debug/trace option, in the Logging tab (do this before starting your plug-in). Let me see the log please. [LATER] Just tested here with FSUIPC 4.929, and those functions definitely still work fine. Pete

You got a fatal error with no add-ons loading at all! Wow!. Then your FS installation must be corrupt in some way. Ah, so by the above you meant you disabled EXE and DLL XMLs but then installed FSUIPC, which would add it back to DLL.XML In that case I need to know what the "fatal error" was with only FSUIPC running, please. That shouldn't happen. I certainly don't understand how running any EXE would make that better. Pete

Sorry, what is the difference between "displaying text" and a "window". Is your text not appearing in a window? I don't understand what you are now asking. Please check offsets 3380 and 32FA in the Offsets list, as I pointed out earlier. AES and ATC use SimConnect, not FSUIPC. The Radar Contact menu is an example of one using FSUIPC. Pete

As pointed out in the Installation document which you would have found in the ZIP alongside the Installer, the User Guide, which explains all, is in the FSUIPC Documents subfolder along with a lot of other things you might find of interest. Basically, the unregistered FSUIPC is the free interface into FS for applications to use, not users. It performs all the functions which have been free for all the years FSUIPC has existed (since 1999). Registration enables all of the user facilities as well. Pete

Unless you assign the parking brake control to something, FSUIPC doesn't touch it. It sounds like you've been assigning all the wrong things. Please show me your FSUIPC4.INI file, from the FS Modules folder. You can paste it into a message here. Pete

FSUIPC isn't in charge of bringing up the menu at all. That is purely a Windows action, very standard. FSUIPC does do things when you select one of the Tabs involving joystick assignments or calibrations -- it will re-scan your devices. However, that is a repeat action of what it does during loading in any case, and if there was any rogue driver causing a hang it would hang then. It sounds like there's a nasty interaction occurring between FSUIPC and one of your other many add-ons. I use UT2 and GSX so I doubt those are involved. They only way I know of for narrowing this sort of problem down is a process of elimination. Start by re-naming both your EXE.XML and DLL.XML, so no other add-ins are loading. You'll find those files in C:\Users\Conrad\AppData\Roaming\Microsoft\FSX Then rerun the FSUIPC4 Installer so you get just FSUIPC4 loading. Test that. If OK, then re-name back the DLL.XML but edit it setting all but one of the entries other than FSUIPC to "Disabled". Test. Then enable them one by one. Then do the same with the EXE.XML, if you have one. I'm afraid this is a bit laborious, but I don't know of any other way to narrow it down and identify the problem. Pete

SimMarket don't supply FSUIPC, only the registrations. You can get the current Installation package (currently 4.949) here in the Download Links subforum, or over in the Enrico Schiratti "Dowson" page. No one else supplies legitimate copies except where they are packaged as part of a supported application. The Registration system has not changed since it was first incorporated. You are making a mistake. All three entries -- name, email, key -- MUST be identical, character for character, to those originally used. If you want me to check your details, just state your order number. Pete

Which "Clear" button? There are 5! What does it say in the text box to the left of the top right Clear button? Maybe you need to show me your FSUIPC4.INI file. Pete

It would really be better to post support questions to the Support Forum. They'd be seen earlier, usually. FSUIPC3 sees any axis which can be read using the original Windows joystick API. There are only 6 of these -- X Y Z R U V. It sounds like what you think of as "V" is actually one of those only supported by DirectInput, which is used in FSUIPC4. FSUIPC4, using DirectInput instead, supports 12 axes: X Y Z R U V, plus sliders S T, and POVs P Q M and N. Maybe the Bodnar board puts yuor missing 3 onto one of these latter ones. See if any of the three are recognised in the Buttons & Switches tab -- FSUIPC3 did support two POVs as sets o 8 switches. Pete

Very few application programs need FSUIPC to be Registered. They only need it if they use Lua plug-ins or macros. I don't think PlanG needs it at all, so I think you might have a different problem. That would be for FSUIPC3, then, for FS9, not FSUIPC4, for FSX and later. They are not the same. FSX came out in 2006. if you've lost your FSUIPC4 registration details go to your SimMarket account and retrieve them. But I don't think this can be related to your PlanG problem, unless perhaps you are trying to use a pirated key? Pete

Do you need to see them move? Surely one is spring loaded (and in any case the result is obvious on the EICAS) and the other just a momentary button in any case. Pete

The installation attempts for SimConnect which you did must have failed then. With no DLL to connect to, nothing using SimConnect will work. You could try deleting those folders you listed and trying again, but I recall that when I had a similar problem with SimConnect many years ago the only solution I found was to reinstall Windows and FS. You could try going to the Windows control panel "programs and features" and uninstalling all those Simconnects, then install them again. If that doesn't work, I suppose you could try reverting Windows to the last backup you made before installing FSX-SE, then installing again. Try those things before resorting to ire-installing Windows. Windows XP was easier. You could just patch things in the Registry. But the WinSxS system since vista has become so complex it is impossible to follow. Pete

What's the "FSUIPC folder"? Something you've made? The FSUIPC Installer doesn't create one. As stated n the documentation (see the Installation document you got with the original downlaod), FSUIPC4.DLL itself resides in the FS/P3D Modules folder (along with your settings, the Log, and your Registration), and all of the documentation, examples and other "goodies", in the FSUIPC Documents subfolder. Please do read it again. Sounds like you are missing a lot. BTW, it does actually say, at the top of the Thread from which you downloaded the interim update: The FS modules here, when supplied without Installer, need copying into the FS modules folder once extracted. You missed that too? Pete