Pete Dowson

MOVED FROM FAQ SUBFORUM: please always post support questions here. Evidently there is something wrong with that "FSUIPC OFFSET CHOOSER". I'm afraid other people's programs cannot be supported here. You need to go to FDS support! Pete

Sorry, still none the wiser about the first two. Pete

I'm not saying that, only that it doesn't work with many later add-ons. I don't have to test on. Pete

That's to do with the piles of requests accumulating. Mouse and keyboard use activates acceleration which increases changes to the values instead, though I think with PMDG stuff you are just bypassing the control system. The GoFlight dials should give you 4 button to program -- fast as well as slow in each direction. Program the fast ones to do larger increments, if that's possible with PMDG controls. Pete

Have you programmed both press and release to the same control? I think each click is either a press or release. At least, that's the case with standard rotary encoders. Else you will have to wait for PMDG to reply. After all, they are their supplied controls. FSUIPC is only sending them. Pete

I don't know if those aircraft can support mouse macros. In FSX very few aircraft do -- exepialy not those which use XML gauges. They need to be gauges written in C++ abiding by the FS2002 SDK rules. Many of Microsoft's own models don't support them either. It's a bit of post luck. Is that the default King Air? 2D cockpit? You enter a name you the macro file I assume? Pete

Using ServerName+Protocol or ServerIPAddr+Protocol parameters in each WideClient instance, the Broadcasts for Server identification, though still being sent, are not being used. Use TCP protocol and you are guaranteed correct addressing and retained order of frames, as well as error checking. Whilst UDP can be faster it really isn't significant unless there are truly large anounts of data on a less capable network. The clients do not "broadcast", so WideServer doesn't receive any. And using only TCP and the identication parmeters in WideClient, nothing is using broadcasts. Pete

Please always put support questions in the SUPPORT FORUM, i.e. here, not in the reference subforums. Your question is about WideClient. So why is it headed "fsuipc auto start"? The WideClient parameters you can use are documented in the WideFS Technical PDF, part of the documentation included in both the WideClient and WideFS ZIP files. Check the [User] section part of the WideClient.INI file part. Around page 12 and following. Pete

What is "seat arming"? Never heard of that! As well as what John suggests: These are in the list of Contorls supplied in your FSUIPC documents folder: AP master is called "AP Master" which is a toggle action. Autothrottle has "Auto throttle arm" which is also a toggle. Sorry, I've no idea what they are in any case. The logging suggested by John will help, if they are built-in controls. Also, with the logging, if you set the Sim into Windowed mode (ALT+ENTER) then enable FSUIPC's console log (on the Logging tab) to will be able to see the Events lgged in real time as you invoke them. Pete

No, sorry. They don't contain any of the (optional) logging for buttons or axes which yould indicate anything from your INI file. There's only the basic stuff there. Backing up files is really an important part of running a computer system. You should also consider backing up P3D-realted files, possibly all of the Prepar3D v4 Documents, Prepar3D v4 AddOns, AppData\lockheed Martin, and ProgramData\Lockheed Martin folders. I actually take full System and Disk backups of my setup whenever I've made sets of changes, I use an excellent program called AOMEI which also lets you open backup files and attach thrm as disks to your system, so you can access indicidual files and folders in Explorer just as if they were on that PC (even though in my case they are on a Network drive). Pete

So the device isn't responding. Ouch. No, all the initialisation for VRI devices is performed only when loading. It would be quite an upheaval to try to do it again, at least automatically. It might be possible to make it occur by FSUIPC option or control. I don't know without looking. And it would be only for FSUIPC5, not FSUIPC4. Pete

That's really just a basic default INI file, as if you didn't have one before running P3D. So, either you (accidentally?) deleted your previous INI file, or some other add-on you are using did so. The only other possibility i can think of is that you have two instances of P3D and started the wrong one. Either way, you need to restore it from your most recent backup. Pete

Nothing updated for VRI devices for years. I no longer have any VRI devices. No further VRI development was anticipated. The "Good" log is from 5.15. Your "bad" log is from 5.14! I suspect the 5.14 user hasn't got the VRI driver installed or set correctly. What's the "Device ID"? No, not for years. And it evidently works in 5.15 as shown in your "good log". (Why isn't the other user on a supported version?) You can use FSUIPC VRI comms logging. You need these lines in the [General] section of the INIfile: Debug=Please LogExtras=x4 For more logging, with all data on COM ports use LogExtras=x44 Pete

Is that with default aircraft? Here it is too fast if anything. Make sure the "Delta" value is the PAN VIEW assignment in FSUIPC is set to 1. You could try increasing FSUIPC's scanning frequency. It defaults to 100 times per second, but you can increase it. But it shouldn't be necessary and could affect the performance of the sim as it would be spending more time looking at joysticks. To do this:set or change the "PollInterval" parameter in the INI file's main [Axes] section. It defaults to PollInterval=10 which is 10 mSecs (so a rate of 100 per sec). You could try try 5 for 200 per sec. That would mean it should send 200 "PAN VIEW" commands every second, IF your system is capable of it (these commands pile up in Windows queues, and duplicates will be discarded then. Pete

Try Saitek support. What do you assign it to? If FSUIPC axis assignments, use "Pan View". that works pretty fast here, every time. Well, I don't recall exactly what the keystrokes are assigned to in the Sim, but there are several likely control candidiates you could try: VIEW MODE VIEW MODE REV VIEW TYPE VIEW TYPE REV NEXT VIEW PREV VIEW I'm sure thgose keystrokes with be two of those (and the REVerse ones, the same keystrokes with Shift pressed). Pete

MOVED FROM FAQ SUBFORUM -- please alaways post support questions to the Support Forum, i.e. here, not to reference subsections! Encoder's send button presses, effectively. If your pot is seen as an axis input in the Axis Assignments tab of FSUIPC, then you can do what you want in either of two ways: 1. Use the right-hand side of that assignments facility to assign up to 10 different actions depending on the value being seen. For keystrokes you need to assign to one or other of the FSUIPC-added controls "Key press and release" or the similar separate Press and Release controls. 2. Assign the axis on the left-hand side of the same Tab to a Lua plug-in program you'd need to write. This would receive the Axis value as "ipcPARAM" and could test the value and send a keypress using the Lua ipc library facilities to do so. Bear in mind that with pots achieving the exact values every time is virtually impossible. You'd need to allow a range of values for each, just as with the first option. Pete

That wouldn't work. Apart from the switches/buttons (which must surely be a problem of assignments), the symptoms you are seeing appear to be typical of Saitek devices (in particular) when they install bad registry entries which define the assorted axis actions incorrectly: usually as "digital" (i.e. on of off) rather than analog. First off, if using FSUIPC for assignments, you need to DISABLE controllers in P3D, not just deete assignments. That is a checkbox in P3D, in the last Controller settings item. Then delete or re-name your FSUIPC INI file so none of the assignments you previously made apply. Unplug the Saitek gear, go to Windows' Device Manager. Find your Saitek yoke and throttle units, and uninstall them -- making sure to also uninstall drivers when/if the option arises. Re-boot your PC, reconnect the devices so that Windows recognises them. Run P3D. Edit the [JoyNames] section in the default INI file produced so that it says AutoAssignLetters=Yes. NOW start assigning and calibrating. Bear in mind that flaps and spoiler will need reversing (REV option in calibration) before calibrating. If you still get the "digital" symptoms on axes, then it needs more intervention. See this thread in the FAQ subforum above: Pete

You are just re-naming it so you can restore it after, or use it to restore other DLLs you have installed. So just choose any old name -- perhaps "DLL.PREVXML" or "PREVDLL.XML" Running the FSUIPC Installer as administrator will then create a new DLL.XML just to get FSUIPC loaded. Pete

If you mean that FSUIPC isn't listed for selection in the Sim's Add-Ons menu, then this indicates that FSUIPC isn't being loaded. You have a corrupt DLL.XML file. Try renaming it (it is in your AppData\Roaming folder for the simulator), and re-running the FSUIPC4 Installer. Pete .

The '8 digit number' is the time since FSUIPC started, in miiliseconds. For example, 12345678 would be 12345 seconds plus 678 thousandths of a second -- over 205 minutes, or 3 hours 25 minutes. Finding the source of those events is not easy. FSUIPC can't tell you, because all it sees is the event arriving into the simulator. Probably the only way to find it would be to stop or remove each of your add-ons one at a time until it stops. The most likely culprit would be an add-on aircraft, one which is reading that switch somewhere and thinks it is off. So the first test is to see if it happens even witha default aircraft. If the event is coming through SimConnect, then a SimConnect log might show it, along with the source. For this you need a file like this in your simulator's Documents folder: [SimConnect] level=verbose console=No OutputDebugString=0 file=C:\simconnect%u.log file_max_index=9 That writes up to 9 log files, cyclically overwritten, named "simconnectN.log" (N = 1 to 9). With that setting they go to 😄, but you can direct them to wherever you want. But such logs with be VERY large, and may not trap the events in any case. Try it without FSUIPC as that is a huge contributor to SimConnect logging! Pete Pete

Yes, it is. Not sure about your throttle/joystick problem without more detail -- those Saitek problems are usually due to the bad registry entries the Saitek install makes. They can be fixed or worked round though, every time. but not without more information. you can find lots of examples of solved Saitek problem here in this Forum, if you look. But your other complaint, this: really cannot be down to FSUIPC as ASP4 doesn't use FSUIPC at all, and all FSUIPC does for ASP4 users is provide weather radar information, well used by many applications (expecially in cockpits using Prosim). If naything was wrong with that it would mess up FSUIPC, not ASP4. So, I'm sorry, you do need to look elsewhere for that. I suggest the HifI Simulations forum -- they are good at dealing with such things, though they'll need rather more details -- the actual meaning of "send a lot of error" for a start. My only other comment on your rather insensitive and, in my opinion, ill-considered posting (apart from "why post it if that's the way you feel?"), is that the title could at least have described one or both of your problems, as then it might have attracted help from others who may have solutions for you, assumung you actually want any. If you wish to re-consider, please post again and we'll explain what information you can supply to enable us to help you. Pete

The files you RARed are so short it would have been quicker simply to paste them. MakeRwys isn't doing anything because there's nothing to do. Here's the total Scenery list as generated by LorbySceneryExport: [General] Title=Prepar3D Scenery Description=Prepar3D Scenery Areas Data Clean_on_Exit=TRUE [Area.001] Title= So it's the processing of your main Addons.XML file which fails. It isn't MakeRwys. Did you look at the display from AddOnOrganizer? Does that show all the scenery correctly? (You can export the displayed details -- right click on it. You get an .html file). Try running MakeRwys with the Export program removed from the P3d folder. it will process your main scenery.cfg file, which should contain all of the default scenery, and probably the ORBX stuff (as I think they don't use the Addons.xml method). If that works then I think your main Addons xml (or cfg file) is corrupt. That'd probably be the one in the ProgramData or your AppData folder (or both?). If MakeRwys works okay, then you need to ask the Lorby author about the Export program, because I've no idea how it works, what files it is processing. If it doesn't work, I need to see your main Scenery.cfg file (in the ProgramData\Lockheed Martin\Prepar3D v4 folder). Pete

Well, those programs do nothing at all except when actually used, so what you are saying makes no sense whatsoever! If merely having another program file in the root folder of P3D causes ORBX software to fail, then they have some seriously bad programming and i suggest you report it! Pete

I need to see the Log ("Runways.txt") file that it generates, and also the MakeRwys_Scenery.cfg file. If in addition you have AddonOrganizer, its dirplay export file (an html file obtained by right-clicking on its main window and opting to export it). In the thread you referenced you said "Also the ORBX FTX VECTOR Configuration Tool does not seem to see any Airports anymore.". So doesn't that also indicate that you have some serious corruption in your installation somewhere? You also said "Yesterday everything was fine. Nothing changed on my Config in that time. ", but changes do not happen without changes being made (unless you have a bad disk or faulty memory in the PC, of course). Pete

MOVED FROM "USER CONTRIBUTIONS" SUBFORUM FSUIPC 5 is a new program needing a new key. Please see SimMarket, Pete