Pete Dowson

No, it stays at whatever you set it to. The default setting is only what it sets if it creates the parameter in the first place. In that case I haven't a clue. It is now doing what it did before, which you say worked, except that with "auto" set it only does it if you actually load the aircraft. With "Yes" set it is identical now to before. With "No" you are turning it off in any case. There is a slighly modified later version, 5.103j, which might be worth a try. Let me know, but really I think I'll have to wait and see if PMDG will send me anything. FSUIPC5103j.zip Pete

I think I've found and hopefully fixed the problem. haven't yet tested all the options, but if you'd like to try this version and let me know, please: FSUIPC5103j.zip Pete

Just disable controllers altogether in the sim. You should be doing this in any case if you are doing any assignments in FSUIPC (except for just keyboard assignments, which FSUIPC can override). In P3D4 the option is in the Settings - Controls options, in the last tab (I don't remember its name at present, maybe "Others"?) Pete

FSUIPC does not use the GoFlight drivers for P3D, only the GFDev64.DLL module, which was included in the download ZIP since the first version of FSUIPC with Goflight support incorporated! Just place to GFDev64.dll into the Modules folder. Download the currtent interim update for FSUIPC5 from the Download Links subforum. ALWAYS look there for the latest versions. Pete

It should work with the default, "Auto". Only try "Yes" if that doesn't work please. Pete

Try this please. Let me know. I've reverted back to separate clients for each of the three aircraft. Not tested with a PMDG aircraft here -- waiting for an answer to my request from PMDG. Install_FSUIPC5103g.zip It's a revised (64-bit) installer build, because I'm testing the Installer too to fixcrashes some folks have been reporting (see separate thread). Pete

No. If you look back this thread was started by a Kevin which had the Installer crash too. I've now built a 64-bit version of the Installer, and that works either way -- HKLM then HKCU or vice versa, as does the FSUIPC4 installer. I just hope that's the answer. 64-bit installers for 64-bit programs. Never thought it was needed. Pete

The value actually in 0580 cannot ever represent anything over 359.999999 ... degrees. 360 would be zero in any case. The units in the 32-bit offset 0580 are the actual heading (0-359.9999...) divided by 360 (so it is completely fractional) then multiplied by 4294967296 (the maximum possible unsigned value in 32-bits), so making full use of those 32 bits. Thus the largest value, converted back to degrees, cannot be 360 or anything higher. Pete

I know about the WOW6432Node business, but that's supposed to be hadled automatically by Windows. Pete

I'm afraid I will have to remove the built-in LuaSocket facilities in FSUIPC5. I have been trying to compile 64-bit versions of socket.core, mimi.core and ltn12.core (I did find I was including them -- wrongly as they were the 32-bit versions), but there are vital bits missing in the LuaSocket sources I downloaded and the things just won't compile. There is a work-around. Install WideClient on the same PC asFSUIPC5. Change the ClassInstance parameter in the INI to 1 so it can run at the same time as P3D4, and connect to FSUIPC in the normal way, and use socket plug-ins in WideClient. It's still a 32-bit program and has the requisite modules built in. I'll publish this as a note in the next "changes" notice for an FSUIPC5 update. Pete

Strange that in the Installer I can get the HKCU one but not the HKLM one -- says it isn't there (it is) on my system and crashes on yours. All I did in the later instakker is reverse the order of HKCU/HKLM (and of course the parameter names. Even odder is that it works fine for the FSUIPC4 Installer with exactly the same code. No, I don't think the captitalisation matters. Well the results are not logical. So they are "out of everyone's depth" I think. I'm just glad there's a work-around. I might try to build a 64-bit version of the Installer, just to see if that makes any difference, though it shouldn't -- the registry entries are the same, the P3D3 ones are right next door! Thanks for your investigations, nevertheless. Pete

Okay. If you've not changed the 777 install in any way, then this problem must be down to P3D. All I'm doing in the newer versions is making the request for the data in the main FSUIPC SimConnect Client, instead of in separate Clients for each aircraft. I'm going to ask PMDG for a trial version of the 777 (or 737 -- similar reports for that). I have the 747 on such an arrangement but that simply hands my P3D4 immediately, with a black screen. I might post a link here to a test version anyway, later today or more likely tomorrow. Pete

Providing you either don't iinstall the CH control manager, or you do but it doesn't stop the devices being seen by FS or FSUIPC as normal joystick-type devices, then you can assign them as you like in FSUIPC or FS (but not in both). I've used it since the Apple II version, moving to the Amiga later, before PCs. Please use the Support Forum for questions and support. "FAQ" does mean "Frequently Asked Questions", but as on most support sites it is actually a repository for the the answers to FAQ's. Pete

Did you delete your KEY file? There's never a need to delete anything when installing an update. That's crazy! I don't know how that is possible. Unfortunately you seem to have cut the top off the Install log -- the title and registry paths are missing. What version are you trying to install (saying "latest version" doesn't really help). There is a special trest install, with a small cvhange in the order of the Registry checks. Try: Install_FSUIPC5103g.zip The Download Links subforum often has interim updates which are just a ZIP containing the DLL and a changes note. It is always worth perusing that sub-forum. there are lots of useful things there as well as updates for FSUIPC. Pete

I never worked out how to do that. but FSPS does it, automatically for you. I think it's called Fiber Accelerator. I know SimMarket sell it. Pete

Can you try that with HKLM instead, because it's when I try that first you are getting the crash. And, yes, I don't see your ... in regedit here

Which comparison are you referring to? I'm afraid I still don't understand your code. Have you tried enabling the Lua debug/trace option on the Logging tab, before running your plugin? It will show the lines (by number) executed, and the values when they change.

Please try the current update, 5103g, and set PMDG737offsets=Yes in the [General] part of the INI file. Show me the log if still no luck. Pete

Hmmm. That's strange, because the log does show that the 777 offsets are enabled. Are you sure the facility is enabled in the 777? Pete

Well, I have good news and bad news. I get the same results here as you. The bad news is that I cannot at present figure out why. All the code is c/c++ source re-compiled for 64-bits. There are no actual "precompiled chunks", at least not unless they are well buried in some of this lua source code. I've traced through to where it gets the error and I'm none the wiser at present -- the code is very dense, very obscure. If I don't get anywhere I'll have to seek assistance over in the Lua website. Pete

Perhaps the program being invoked to play the mp4 file is not 64-bit compatible? I'm not sure if a 64-bit program can shell a 32-bit program or not, though it would indeed seem illogical for it not to, as it isn't part of the same process. Your other test proves that the shell call is working. Perhaps you can google it, or if not I'll try when I catch up with things. The bat file itself can contain command-line parameters. Pete

Ah! Thanks ... I'll check. Maybe I'm inadvertently building in some 32-bit code myself Pete

Please don't create identical multiple threads! Pete

But GearStateVal is the addition of three values, 16383 + 16383 + 16383 is NOT = 16383. Sorry, but I don't understand your code or what you are trying to do. It makes no sense to me adding three gear state values together. Pete

You might need to find another way. Doesn't the documentation for the aircraft suggest anything? Some aircraft have assignable keypress combinations already. I assume you've tried the obvious one, "AP PANEL VS HOLD"? "AP APR HOLD ON" perhaps? All FS and FSUIPC controls are just names for event IDs. There's a list of control names and the equivalent IDs provided in your FSUIPC documents subfolder. Unfortunately not many add-on (or default) aircraft support muse macros these days. most did back in FS2002 and even FS2004 days. The Advanced User's guide gives details, but first try using the FSUIPC control to list L:Vars, after loading the aircraft. Then, if you see one which may be a candidate, operate the switch with the mouse and see if its value has changed when you list them again. There is even a Lua plug-in provided to load them as they change in real time (see the example plug-ins ZIP). After that it's a matter of hand building a macro to set it. Pete