Pete Dowson

See if JoyIDs sees your joysticks (see the thread "Fixing joystick connections not seen by FSUIPC" in the FAQ subforum. FSUIPC only uses standard DirectInput actions to locate these things. It sounds like the registry is corrupted. Try uninstalling them completely in Device Manager (drivers included), then re-booting. The VRI is evidently not responding. What is connected, exactly? Doesn't it need the VRI driver between FSUIPC and the device -- i.e two COM ports and a program to link them? I'm afraid I know nothing about LINDA, but Windows certainly tells fS that the file is not found in the Modules folder. Is there a LINDA support? Pete

It stores it where you tell it to in the parameter you add to the FSUIPC4.INI file. It is Prosim which wants it named a particular way and put in its folder. FSUIPC will name it whatever you want and put it in the folder of your choice. Without the parameter there it will not even make the file in the first place. Pete

No need to save anything, the installer doesn't touch INI or Lua files. The full FSUIPC Installer for 4.949 would simply be a DLL and documentation update, nothing else needed to have changed at all. Both INI and Log files agree, there are no recogisable joystick connections registered via USB HID. The only connection you have is the MESM: 405 ---------------------- Joystick Device Scan ----------------------- 405 ------------------------------------------------------------------- and 21824 Using "C:\Program Files\GoFlight\GFDEV.DLL", version 2.2.6.0 21824 GoFlight GFMESM detected: 1 device As for LINDA, the LINDA program isn't being loaded because it isn't there: 608 FSUIPC couldn't run: "H:\FSX\Modules\linda.exe" [Error=2] Error 2 is the Windows system error code for "file not found". Furthermore, your identified COM port for the VRI connection appears to be wrong, or the device wasn't connected: 608 VRI port 1 "COM3" failed to open Something to do with LINDA appears to be started by an entry in ipcReady.lua, but can that work if the EXE is missing? 21824 LUA.0: beginning "H:\FSX\Modules\ipcReady.lua" 21824 LUA.0: ended "H:\FSX\Modules\ipcReady.lua" 21840 LUA.1: 21840 LUA.1: ************************** START ************************* 21840 LUA.1: [sTART]LINDA:: Loading... 21855 LUA.1: LINDA:: ---> ERROR:: [sTART] Main system config not found! Run GUI and check configs! Basically it looks like you've not actually properly installed LINDA, doesn't it? Pete

Better for you to write to me at petedowson@btconnect.com, if it isn't support but private. Pete

From 4.948, or earlier? Did you do a straight update, or did you delete eveything first (generally a bad idea)? Nothing attached, but generally it is easier to simply paste the text into your message. Pete

Note that most rotary encoders send a message on each click, so you should be able to adjust in one increment just by a small turn. Twirling it will generate many messages, of course. That test mode only reports what it receives. If you can't get single results I think you need to contact PFC support. Eric is very helpful -- try email to eric@flypfc.com. Pete

I have now managed to test this on my P3Dv3.1 installation, and the loading terrain progress is as normal, a few seconds only. I think you might need to go through a process of elimination. Certainly try without GFDev first, but also look at other add-ons or add-ins you might have installed. Pete

I've had a chance to try this here, and I don't get any problems like that at all. Mind you, I don't have any aircraft with complex cockpits. In fact I don't use an on-screen cockpit at all since I have a hardware one. But I did try with a few of the default aircraft cockpits and again no problems. Are you perhaps using a complex add-on aircraft? Try with a default if so, just to make sure. It may well be something to do with the way the gauge system is interrogating mouse positions for their switch operations and so on. I seem to recall reading something similar somewhere on the L-M support forums. Pete

NEVER EVER publish your registration openly like that. This is the way it gets pirated, and then it has to be withdrawn. I've obliterated it now, hoping I was in time. I'm sorry, but it is most certainly you who did something different. The software hasn't changed and I assume your system isn't haunted? I've managed to locate your order details on SimMarket (would have been easier with your order number), and you have the email address incorrect!!!!! Just use the correct one! dnrwhite@rogers.com As I said, all three parts must be correct and exactly as first registered! You do seem to have your name right, though (I'm always amazed at how many different ways folks find to spell their name) ;-) ). Pete

If you already had a registered install I don't really understand why you are trying to re-register?*** And there's been no change in the process in all the years from and including 2011. Good. Progress then! ;-) Registration dialog exit: selected FSUIPC REGISTER Providing FSUIPC registration dialogue ... Registration for FSUIPC4 was cancelled or failed! (result code 40) Okay, so this time you did actually select the correct option "Just enter new registration(s)". So, that's better. Well done! And you got the registration dialogue. So now you have to enter all three parts, EXACTLY as your original registration and as files on SimMarket. If there is any error on any of the three entries, the registration will fail. (BTW if you still have the original registration file (FSUIPC4.KEY), in a backup perhaps, you can simply copy that into the FS Modules folder instead. I know most folks don't bother with backups, but it is always recommended, especially for things like Registrations.). Pete *** Sorry, reading back to your first post I see you were starting over with new disks etc.

The arithmetic operations / and * have the same priority, so are obeyed left to right -- so you are getting ((HDG * 360) / 65356) * 65536 You need to use parentheses exactly as shown in the dox. Pete

Version 4.694 of MakeRunways, now released, includes a command line option: /+Q to run in Quiet mode, with no dialogs. Pete

Yes, maybe, but this has just got to be something wrong in P3D. Maybe you should report it to L-M. FSUIPC is simply not in control, nothing like it, when P3D is loading files. You said earlier that you changed the date/time earlier, before thew 18 second point ("Starting everything now"). That "Sim Stopped" is where you closed down P3D, as it evident in context: 17847 Starting everything now ... 18034 Using "C:\Games\GoFlight\GFDEV.DLL", version 2.2.6.0 18034 GoFlight GF45 detected: 2 devices 18034 GoFlight GFP8 detected: 5 devices 18034 GoFlight GFT8 detected: 2 devices 18034 GoFlight GFRP48 detected: 2 devices 19157 Advanced Weather Interface Enabled 640166 Sim stopped: average frame rate for last 20 secs = 19.9 fps 647155 === NOTE: not calling SimConnect_Close ... 648153 System time = 03/01/2016 18:03:59, Simulator time = 17:54:02 (23:54Z) 648153 *** FSUIPC log file being closed One thought has occurred to me. Could it be that the GoFlight driver is clobbering things? GFDev is only used when FSUIPC is enabled. Try renaming it -- pathname highlighted above. (The version of GFDev I use is 2.1.0.1 at present). BTW why not set date/time/airport/aircraft in the initial selection menu? That's really the best place, and what it is for! Pete

Ah, you are not setting date/time/aircraft/airport within the initial selection screen? You are interrupting the loading process (before FSUIPC even gets to "Starting everything now")? Even so, that seems to me to be a very short time -- less than 18 seconds from start of the session till ready to fly. Here FSX and P3D aren't ready to fly for a much longer time! (Maybe you don't realise, the numbers on the left are in MILLISECONDS, so 17847 is less than 18 seconds). All that's happening when changing date or time or aircraft or airport is that all of the SimConnect interaction, getting the data requests initiated, are being interrupted and repeated. That can take a few seconds indeed, depending upon the complexity of your setup and the loading on SimConnect from FSUIPC and other add-ons. Either set the date/time/aircraft/airport in the initial selection screen, which is designed specifically for that, or wait till you are ready to fly (this would be AFTER FSUIPC gets to "Starting everything now"). FSUIPC is not "proactive", but "reactive". It receives lots of data, but no more often than once per frame and only when it changes. But all of that data must be requested at the start, and you appear to be interrupting that process. Nevertheless, I am jealous of your short loading times -- your scenery and AI setup, for instance, must be fairly simple or default, as 16-17 seconds is very short especially if this includes seconds in the Menus setting the date and time. Is the entire elapsed time of 17 seconds what you are calling a "long loading time"? I need to refer back (see later). If you are not actually using FSUIPC (and from the INI file it appears you are not), and not actually using WideFA, why are they installed? In your first message you said: but this is obviously not borne out in the log. Honestly, FSUIPC cannot have anything to do with your terrain data taking 10 minutes to load -- FSUIPC itself is completely frozen out whilst FS/P3D loads anything, scenery, weather, aircraft, AI, whatever. So it is why your system is taking to long to read files which needs investigating. Pete

Which version of P3D? Which version of FSUIPC? Use the text option in the PFC menu entry in "Add-Ons" and see what it shows when you turn those knobs. Pete

MOVED FROM FAQ SUBFORUM! PLEASE ALWAYS POST SUPPORT QUESTIONS TO THE SUPPORT FORUM. This occurs if you started with a flight which was stored in the first place with a flight plan but then saved a flight with a different name and wanted to reload that. I think the flight plan needs to have the same name if it is to be automatically loaded with the flight. You'd be okay to load the plan manually, using the menu. Pete

Yes, for which I altered the Installer to diagnose exactly what is wrong and informed you of the results. Please follow my recommendations: 1. Check "FSUIPC4" (left-most of top three selectors). Make sure the black blob is in the white circle. 2. Check "Just enter new registration(s)" (bottom onr of three selectors below. Again make sure the black blob is in that circle. 3. Double check the above. 4. Click "Go ahead". That's it. That's what everyone does and it has never failed yet in the 12 years or more of FSUIPC registrations. Regards Pete

What did you expect? As I carefully explained, it simply adds more logging. And this is it: Which does definitively show that you had FSUIPC4 checked and the Check existing registration(s) selection checked. There's really no way possibly for the above log to show what it is showing without that selection. Pete

Neither of those are at all useful. Does the FSUIPC4.LOG show anything? Pete

Please download this updated installer and try that. It simply adds log entries about exactly what it thinks is going on at the registration dialogue stage. Install_FSUIPC4949_.zip Then let me see the Installation log please. Pete

It sounds like both options are selecting the "just check" entry. When you looked at the contents of the folder, was there an FSUIPC4.KEY file there? This has not occurred before, and I can see no possible reason for it. The ONLY way error code 16 can occur is when the Installer is simply checking the existing KEY file, and finding no FSUIPC entry. (code 32 = no WideFS, and 48 = neither, assuming you ask also for WideFS checking). I'll make an installer with additional logging to see what is going on. Pete

Yes, of course you can get the G-force from the offset in which the value is placed. That is why FSUIPC provides all the data listed -- for applications to read. You can read it n a program interfacing to FSUIPC or via a Lua plug-in Module. You can also monitor it in the Log and/or display it on screen using the Monitor facilities in the FSUIPC Logging tab. Pete

Hmm. Nothing wrong there. The error you report occurs if you have not previously Regstered and, instead of checking "Just enter new registration" you wrongly checked the "Check existing registration" option. Can you please confirm you are actually following the dialogue correctly? Pete

Is this the FSUIPC mouse look option, or the one in P3D itself? Have you been to the P3D support forum? I have noticed a number of reports of problems with mouse click recognition in 3.1. Possibly this is one of those? FSUIPC itself won't be doing anything differently. Might be worth reporting over there? Pete