Pete Dowson

Okay. Thanks. Not heard of that one. I'd only useful to know if case others come up with the same symptoms. One more thing to check. I assume it's part of another product? "F1" = "Flight 1" maybe? Pete

If FSUIPC is not registered, it does nothing whatsoever with joysticks or FS controls. Absolutely nothing. All that part of the code is simply by-passed. Despite your findings apparently to the contrary you most certainly must have something else going on there. "Yoke calibrate menu"? Where is that? There is no calibrate menu in FSX. Or are you talking about some different Flight Sim program? You fail to identify either the flight simulator or the version of FSUIPC, but I assume you meant FSX as it is only in FSX that FSUIPC applies a fix for one specific G3D crash. Pete

No, ASN is purely a SimConnect application. You need to install SimConnect on the client and configure it with a SimConnect.cfg file. I'm sure there are instructions in the ASN documentation. You need to install ASN on both PCs, but then only run it on the Networked one. It uses additional program modules on the P3D PC for its weather control and radar image extraction. You might need to install the FSX SP2/Acc version of SimConnect -- look in the P3D folders, find redist\Interface\FSX-SP2-XPACK\retail\lib and run the Simconnect.msi you find there on the networked PC. It's worth running that installer on the P3D PC too, maybe also the FSX SP1 version, as many SimConnect applications need the FSX ones. Pete

Can this DLL be named, so if others get the same issue it can be solved more speedily? Pete

Hmm. Strange -- some other parameters elsewhere in the system, then. I think P3D3 must be storing stuff in files other than those I'm aware of in FSX. Aren't you now going to update to 3.1? Pete

You mean to just run your Lua plug-in, as you showed me, on it's own? I take it that you were running Linda before? Did you call your bit tmp.lua? As in Steam\steamapps\common\FSX\Modules\linda\lua\tmp.lua If you want to run it on its own, yes, you can start it via an Auto parameter line. But just to test it would be easier to put it directly into the Modules folder (not Modules\Linda\Lua) and assign a spare keypress or button to it, one to can remove later. If it's in the Modules folder when FS is loaded it wil be assignable in the drop-downs as "Lua tmp" (or whatever you call it instead of "tmp", because I don't think that tmp.lua can be exactly your code as it has at least 22 lines and yours only 17, as I said). Pete

The Lua, exactly as you have it there, all 17 lines of it (no line 22 possible with only 17 altogether) loads fine here. Enable Lua debug/trace in the Logging tab and load the plug-in again. Show me the log. i want to see how it can be different to the exact same plug-in here! BTW your subject title mentions Linda. What has that to do with this? Are you sure you are checking the correct Lua file? Doesn't Linda use a lot of different ones? Pete

Is that event.Lvar line number 22? It doesn't count to 22 but maybe you've taken an extract? I've just saved your plug-in above as "TestLvar" and with Trace/Debug Lua option enabled in FSUIPC I get this okay results logged: 191054 LUA.0: beginning "E:\Steam\steamapps\common\FSX\Modules\testlvar.lua" 191054 LUA.0: E:\Steam\steamapps\common\FSX\Modules\testlvar.lua:12 191054 LUA.0: Global: ipcPARAM = 0 191054 LUA.0: E:\Steam\steamapps\common\FSX\Modules\testlvar.lua:3 191054 LUA.0: E:\Steam\steamapps\common\FSX\Modules\testlvar.lua:17 191054 LUA.0: Waiting for an event in "E:\Steam\steamapps\common\FSX\Modules\testlvar.lua" Line 17 seems correct for the last line in your plug-in. BTW please always state the version of FSUIPC in use. If not at least 4.949 please update. Pete

You really need to be able to see it to Zap it, unless you just Zap everything around you -- see the ZapCylinderAltDiff parameter as described on page 9 in the FSUIPC4 Advanced Users manual. The proper thing to do on a TCAS warning is to take the avoiding action it shows on the PFD. Your FSUIPC is out of date and no longer supported. In more up to date versions of FSUIPC that you are using (the current one is 4.949c), the Zap control takes a parameter too which widens the angle (see the Changes document for it). But this really applies only to the traffic in front of you. Many TCAS warnings are for traffic above and below and not visible in front, so those angles don't apply. the Cylinder option operates on the nearest aircraft above, below and behind as well. But try the more realistic method first if you can. Pete

There's the problem. Why on Earth have you renamed FSX.EXE? Fix that and you'll be okay I'm sure. Pete

Well, rolling back to 3.0 would have replaced all the modules in any case, so that rules out any corruption in that area. I don't think so, but even if it did those would be bypassed by FSUIPC sending the Axis controls directly with the proper parameters. Sorry, I think you need to report the whole stoty to L-M on their Forum, including the fact that everythnig works on FSX-SE. Pete

Opened FSUIPC4? There would be no folder called "FSUIPC4" unless you made one. The files are in the Modules subfolder or FS. Please look there. Also you may be confusing yourself by having Windows hide the full filenames. Go to the Explorer folder options and de-select the "hide extensions for known file types". Otherwise you'll just see the settings file as "FSUIPC4" type "configuration settings" rather than FSUIPC4.INI, and the LOG file as just "FSUIPC4" with the type "text file" -- althoguh other programs and selections can change these descriptions. I re-state with emphasis", if there is no FSUIPC4.LOG file then FSUIPC4 has never run. I checked the order number, and that registration most definitely works if you enter it all correctly. You must be making a mistake. Use cut and paste to copy each part, Name, Email and Key. I see the key has lots of otherwise ambiguous characters in it -- 0/O, 1/I, 2/Z are often confused. Pete

Trouble is your problem doesn't looks quite the same as the others -- have you looked through the reports on the LM Forums? The fact that you have the same problems with two different devices is also suspicious. I think you at least need to try to repair P3D rather than just hope it'll come good in an update. You know you can just uninstall the P3Dv3 Client and re-run just that installer? You'd have to do that on an update to 3.2 or whatever in any case, and it doesn't affect settings, scenery, add-ons etc. It just replaces all of the P3D program modules. Maybe make backup copies of tour Prepar3D.CFG, DLL.XML and EXE.XML files just in case, but I've never needed to on any of the main or Beta client updates. Pete

Didn't really want or need any pictures. Just the numbers would have done. Only the one throttle for all engines? Does the log I suggested you check show the Axis_Throttle_Set controls being sent to P3D with this range of values? If so then it's a P3D problem, but what it could be I don't know. I have P3D3.1 installed here on my test PC, and it works fine with a Saitek throttle assigned and calibrated in exactly the same way. Maybe your P3D installation is wrong in some way? Does it look all correct in the FSUIPC Lo (FSUIPC does a lot of checks when it starts and logs things). Maybe you need to reinstall. Pete

I'd rather just see the numbers which you can read yourself, and maybe the Log if you enable logging. Screenshots are usually unnecessary, over the top, and difficult to read in any case. In that case it seems like you are one of the many P3Dv3 users suffering some of the assorted mixed and odd problems with controls being reported regularly over in the L-M Forums. FSUIPC is no different in any of these areas whether used with P3D or FSX/FSX-SE. the only thing which might make a difference is your settings, so try using your FSX-SE copy of FSUIPC4.INI -- just make a copy in the P3D Modules folder. Pete

That's part of the Mousewheel Move option. Please see the FSUIPC4 User Guide, page 18, for a description of the three mouse options == trim, move and look. If you onl;y want 'look' only enable look! Pete

Ha ha! That'll be soon then -- end of next week for two weeks. ;-) Pete

FSUIPC4 is only for FSX and P3D. FSUIPC3 is for FS98, CFS1, CFS2, FS2000, FS2002 and FS2004. They are totally different internally. Pete

It has been reported to and acknowledged by L-M. Pete

There were problems with one version of PMDGoptions, some years ago. Is your DLL recent? Might be worth checking for an update. The process and module should be recorded for it in the Windows Event Viewer. It won't be FSUIPC as it doesn't use it. Pete

Or, better, add a terminating character if youcan, like for instance ASCII 0 or maybe a control like NL or CR (10 or 13, decimal). Then just specify the maximum length and the termination used. First, try without the com.test part. It isn't needed as com.read will return the number of bytes read in any case. If that works then maybe I have a problem in com.test, so let me know please. (I do have an Arduino, but at present it's only being used to control indicators, so outputs from the PC only, no inputs. All my input devices are HID, so using the HID functions.) Lastly, you could try using com.readlast -- just as a test. It assumes fixed length blocks though. If you get data with that but not with com.read let me know directly because something is wrong with my code if so. Pete

All that is very mysterious and I can't even hazard a guess as to what the problem could be. Item 5 above suggests that the range of values the axes are supplying is not in the acceptable range for throttles, yet default throttles (standard FS "Axis..." controls use -16384 to +16383 for the entries forward range. Using *-1 to negate the raw entries must be putting them outside this. Which is inexplicable. What range of "IN" values do you see in FSUIPC's Axis assignments page? Rather than inverting axes using *-1 you should instead use the REV checkbox in the calibration screen. Try assigning direct ot FSUIPC calibration, and in the Calibration tab, check REV before calibratin (when sing "direct to calibration" you MUST calibrate for proper results). Actual numbers being seen might help clarify what is going on. FSUIPC works with numbers and these are always displayed, so it isn't hard to do. You might also enable axis logging in FSUIPc, which works no matter where or how you assign them. You can even see the resluts in real time by temporarily running FS/P3D in Windowed mode and enabling the FSUIPC Console Log in the Logging tab. Pete

Okay. This indicates that there is something wrong with your Registration key. Tell me your SimMarket order number and I will check it for you. Pete

There's no facility in FSUIPC for doing exactly that, transparency and so on. That is a SimConnect Menu, not just a display window. You need to use SimConnect for that. It isn't FSUIPC's job to replace SimConnect, but primarily to provide ongoing compatibility for applications through from previous versions of FS. You can produce a sizeable, undockable, Window using the offsets I mentioned by providing multilined test -- i.e. any text with NewLine (ASCII 10 or 13) codes embedded. Even a single line with one at the end or start will do that. This is what Radar Contact does, for example. You can also get a text Windows similarly using Lua plug-in display facilities. FSUIPC doesn't support the SimConnect menu system directly because you'd need to be able to process the SimConnect answers, the selections made. Pete

After running FS and closing it down, find the FSUIPC.LOG file in the FS Modules folder and show me it. You can paste it complete into a message here. Pete