Adamski

Pete - thanks for taking this on! Here's the error window. Hard to screengrab, as Windows takes focus on the 2nd error window: The registry entry: The FSUIPC log itself appears to be fine - and updates itself everyu time I run P3D. The install log (also in "Modules") is the old 5.102 one - and doesn't seem to have been updated by the [failed] 5.103 install. Here it is anyway, just in case it's useful. Installer for FSUIPC5.DLL version 5.102 Looking in registry for Prepar3D v4 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v4 Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v4 Parameter"AppPath" ... >>> OK! FOUND Prepar3D v4! <<< ... AppPath=H:\Program Files\Lockheed Martin\Prepar3D v4\ =========================================================== INSTALLATION FOR Prepar3D v4: SetupPath="H:\Program Files\Lockheed Martin\Prepar3D v4\" Checking version of the Prepar3D v4 EXE: ... Version 4.0.23.21468 (Need at least 4.0.20.21316) Checking if there's already a version of FSUIPC5 installed in: H:\Program Files\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.DLL ... No previous valid version found. Prepar3D v4 Modules folder created okay! Okay -- installed FSUIPC5 into "H:\Program Files\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\Adam\AppData\Roaming" Now finding \Lockheed Martin\Prepar3D v4\Prepar3D.CFG for all users, including this one Looking in "C:\Users\Adam\AppData\Roaming" Found Prepar3D.CFG in "C:\Users\Adam\AppData\Roaming\Lockheed Martin\Prepar3D v4\Prepar3D.CFG" Now checking DLL.XML ... ... No previous DLL.XML found, creating new one. Now checking for a SimConnect.XML file ... ... No SimConnect.XML file found. This is okay. Looking in "C:\Users\Administrator\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\All Users\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\Default\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\Default User\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\DefaultAppPool\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\Public\AppData\Roaming" ... No Prepar3D.CFG there "Modules\FSUIPC Documents" folder created okay! Now installing additional files into the "Modules\FSUIPC Documents" folder: Installed "FSUIPC5 User Guide.pdf" okay Installed "FSUIPC5 for Advanced Users.pdf" okay Installed "The 2016 List of FSX and P3D Controls.pdf" okay Installed "FSUIPC Lua Library.pdf" okay Installed "FSUIPC Lua Plug-Ins.pdf" okay Installed "Lua License.pdf" okay Installed "LuaFileSystem.pdf" okay Installed "Example LUA plugins.zip" okay Installed "FSUIPC4 Offsets Status.pdf" okay Installed "Profiles in Separate Files.pdf" okay Installed "FSUIPC5 History.pdf" okay Installed "Lua Plugins for VRInsight Devices.pdf" okay Installed "ASN WX Radar facilities in FSUIPC4.pdf" okay Installed "Offset Mapping for PMDG 737NGX.pdf" okay Installed "Offset Mapping for PMDG 777X.pdf" okay Installed "Offset Mapping for PMDG 747QOTSII.pdf" okay =========================================================== All installer tasks completed. Registration dialog exit: selected FSUIPC REGISTER Providing FSUIPC registration dialogue ... Registration for FSUIPC5 was successful! (result code 00) *************** End of Install Log *************** Anything else I can do to get more info? Many thanks, Adam. EDIT: Sorry - I forgot to add - I'm using the same Avast as you (free version). Here's the Windows error entry: Faulting application name: Install FSUIPC5.exe, version: 5.1.0.3, time stamp: 0x59515139 Faulting module name: Install FSUIPC5.exe, version: 5.1.0.3, time stamp: 0x59515139 Exception code: 0xc0000005 Fault offset: 0x0000b5c4 Faulting process id: 0x199c Faulting application start time: 0x01d2fd60fdd82c31 Faulting application path: F:\_Archive\P3D_Archive\_PAID\P3Dv4_Utils_PAID\FSUIPC\FSUIPC5103\Install_FSUIPC5103\Install FSUIPC5.exe Faulting module path: F:\_Archive\P3D_Archive\_PAID\P3Dv4_Utils_PAID\FSUIPC\FSUIPC5103\Install_FSUIPC5103\Install FSUIPC5.exe Report Id: 3ba806ae-6954-11e7-a5ad-6c626d3b5dfd

Hi Pete! I'm sorry to say that I've also been struck by some installation weirdness ... after so many years of using FSUIPC with no problems. I tried to install 5.103 and the installer pops up the familiar install window, gets as far as querying the P3Dv4 registry entry, then crashes every time. This is P3Dv4 with Hotfix1. 1) The zip is properly extracted (no errors). 2) Win7x64. I'm logged in as "Admin" - and have also tried "Run as Administrator". 3) Comodo Firewall and Avast A/V temporarily disabled. 4) The install log never gets created. 5) I checked my registry entry for P3Dv4 - the setup path is in there OK. Is the installer faioling because it looks for (and can't find) entries for P3Dv3 and/or FSX? I still have FSX active on my system. 6) FSUIPC 5.102 is working fine in P3Dv4. 7) Installing immediately after a restart/hard reboot doesn't help. OK ... so I tried re-installing my current 5.102 (over the top) ... but now I get the same problem as for 5.103. I suspect that the very latest Microsoft [security] update may have something to do with it - or updates to Avast or Comodo. Maybe a complete uninstall of both (Avast+Comodo) would help, then reinstalling them after the FSUIPC update, but I'd hate to have to do this every time FSUIPC gets an update. Anything else I could try? I have the Windows crash report zipped up - should I PM you that? As ever, thanks for your amazing contribution to the FS world! Adam.

I'm tempted to ask about pricing, but I almost don't care. I know it'll be worth every penny/cent/yen. Needless to say, I'm delighted we're getting an update so quickly. I'm holding off buying/installing P3Dv4 until the new FSUIPC has been released (and given a nice road test by anyone/everyone but me, LOL!). Like many people here, I find it hard to imagine running FSX or P3D without FSUIPC. Keep up the good work, Pete - it's very much appreciated. Adam.

Pete - I hope you had a nice break ... and you're suitably refreshed to tackle the 64-bit DLL!!! I think you'll be amazed - not so much by how many people use FSUIPC, but how much those of us that do actually depend on it. Adam.

Fantastic - many thanks, Pete! Adam.

Great news, Pete! That appears to have nailed it! I did nothing part from doing the log change. I copied over the new 4957b DLL and set FixControlAcceleration to "Yes". My FSUIPC weather options are still set to off (or disabled) but that's OK - I never fiddle with weather related stuff in FSUIPC anyway. I've made a few flights - using default or complex add-on aircraft with no problems. OPUS weather and Live Camera are behaving normally. Do you still want/need any logs from me? Many thanks, Adam

My P3D always starts up with the aircraft selection menu (whatever it's called). I have the Baron as my default starting aircraft. In many of the tests, I hit the "OK" button without making any further selection. At other times (wondering whether it was perhaps aircraft related) I'd select a different aircraft and then launch. Sorry if I'm a bit unclear: by "immediately" I meant "immediately after clicking the launch aircraft button". I need to be a bit more precise! I'll set the default start to the generic P3D F-22 Raptor at its default start position next time - or just rename the file as you suggest - which will force P3D to load its basic default, will it not? I'll do the log setting and also move the wx files out of the way somewhere (it's what I meant by "delete" anyway)! Too late tonight - I'll have another play tomorrow - and check out the Windows error log in case there's anything new there. FSUIPC has been working like a dream until this latest P3D 3.4.9 update. I'm dead keen to help find out what the problem is. At least I can always switch the FixControlAcceleration setting back to "No" when I fancy some light relief! Adam.

Pete - here's the debrief (!): 1) Copied over the new 4957a DLL (thanks). No "Control Timer" log entries in any of the logs (unless I'm blind!). 2) Reinstated the FixControlAcceleration option (set to yes). Instant crash (twice). 3) Deleted the wxstationlist.bin file (though didn't delete all my .WX files as they related to themes. But will try deleting all those later (if all else fails). 4) Wondered whether my OPUS auto-start was maybe kicking things off too early, so commented out the entry from [Programs] - and started OPUS FSI manually a short while after entering the aircraft. Result: P3D crash instantly on OPUS load. 5) Tried the same again - but waited longer before starting OPUS - and reinstated the wxstationlist.bin file. Worked fine. 6) As 5) - but deleted the wxstationlist.bin file. Instant crash on aircraft load. Didn't even get a chance to load up OPUS. 7) Added WeatherReadFactor=0 and NoWeatherAtAll=Yes in FSUIPC.ini. Deleted wxstationlist.bin - crash - same as before. 8) Same test as 7) but managed to get into the aircraft and could enter the FSUIP GUI. Crash on OPUS FSI start up. 9) As 8) but with wxstationlist.bin reinstated. Crash after a minute or so (still no OPUS loaded). 10) As 9) but with the.wx file for my default start deleted. Crash when going to outside view (still no OPUS loaded). 11) In desperation - set FixControlAccel=No. Sod's law - everything works fine. I also use OPUS for all my camera views/controls. Could that have anything to do with it? See [10]. https://www.dropbox.com/s/eqzdbx9974b4aja/fsuipc_crashlog2_adam.zip?dl=0 Do you want any Windows error reports? Anything else I can do, Sir? ;-) Adam.

Wow, Peter - I'd no idea things can get as complicated as that! I'll go through your recommendations step by step and report back. :-) Thanks! Adam.

Hi Pete - I have a similar problem - but the culprit in my case appears to be the "FixControlAccel=Yes" setting. I had repeated crashes with 4.57 (I skipped 4.56) but put that down to maybe a corrupt (or out of date) fsuipc.ini. I thought I had it all fixed after rebuilding the ini from scratch (using 4.57). Even the "FixControlAccel=Yes" setting appeared to be OK. However - returning to P3D at some stage later I had the same crash. Setting "FixControlAccel=No" fixed it. I'm not at my sim PC at the moment, but will post the log here later, if it helps. Adam. EDIT: Here are the two logs (successful and crash): https://www.dropbox.com/s/vme4wb2vhflrxv8/fsuipc_crashlog.zip?dl=0

Pete - this may not be the right place - but a quick vote of thanks for your continuing work on FSUIPC. I've been using it for so long I just take it for granted. Keep taking the tablets! :lol: To stay on topic - I've always upgraded as soon as I've heard of a new version. Touch wood, I haven't been caught out yet. Adam.

Thanks, Pete. I value your opinion ... looks like it'll go on Santa's list ;-)

Wow, Pete ... that was *fast* ... thank you ... at least you've put me out of my misery! I've re-enabled them in the past when I'm in "photo-shoot mode" but often forget to disable it again and wonder why my controls have gone erratic! I looked at EZCA but was a bit leery of all the key assignments that needed to be set up. Is that much of an issue (for someone not quite as savvy as you, LOL)?

Thanks to some great help here, I've managed to pretty well stabilise my (fairly spikey) X-52 Saitek throttle/stick and CH rudder combination. This required passing all axis & control management via FSUIPC and disabling the FSX controllers option. All good so far. However - I often compose fancy screen shots and used to use the mouse-yoke-pan function to fine tune my [outside] views with the mouse, as panning around with my POV hats was too coarse. I've found that the "mouse-yoke-pan" function only works when FSX controllers are enabled. Is there a way round this?

This should be printed in red and bold in the manual! :wink: I followed those instructions (which are pretty good, I have to say) but I think my pots may be past it. I don't just get small spikes - I get really huge values at the very beginning, then a smooth bit and a final huge value when the pedal is all the way down. I did calibrate just short of this last spike - or I couldn't have got them to work at all! It's that huge spike at the beginning that causes the brakes to jam on - just when you're taxiing past the control tower :lol: On the subject of spiky pots - it's great to see Bob Church around in this forum. I'm a long time Falcon/Thrustmaster customer of his! I have every hope that FSUIPC can do in software what his digital chips did in hardware for my venerable TM gear 8) I'll have another go at calibrating - but it's already 100x better than it was - much appreciated! EDIT/UPDATE: Last calibration seems to have totally tamed the beast :D

Well - I'm embarrassed :oops: to say I think I've solved it! The advice here got me thinkingthat nothing was being sent by the TBso I re-did my calibration and set my DELTA to a much smaller value. I'd set it unnaturally high as I was getting a fair few spurious spikes that were jamming the brakes on when taxiing. I found a sweet spot that didn't trigger the brakes, yet was enough for FSUIPC to "see" the axes. I've tested it about four times now - each time from a fresh FSX startup - and all is OKyay!!! Thanks to both Petes here for pointing me in the right directionI'm a happy camper :D

Thanks Pete D and Pete H (!!). I must say I'm still a bit perplexed by this. I agree that the toe brakes shouldn't be behaving differently. I updated to 4.616. 1) I disabled power management for all USB devices (then rebooted). 2) Started up FSX without touching any controllers. Same problem. All axes work except the toe brakes. 3) Restarted FSX, but kept moving the toe brakes as the flight loaded. This time, the axes were recognised, but didn't appear to be calibrated properly. Opening up the FSUIPC window gets things back to normal again. How can I check if they're operating "digitally"? As far as I can make out, they apply gradually - more pressure gives greater braking effect. I suspect that my TB calibration is somehow not quite as it should be. I've scoured various posts as to how to do it but can't see where I may be going wrong. Adam.

FSUIPC 4.60a. I have a Saitek X52 throttle/stick plus CH rudders with toe brakes. All axes are UNassigned in FSX. Everything calibrates and works fine via FSUIPC- all my additional axes (rudder, toe brakes, reverser, prop, mixture) are mapped to various rotaries or sliders ... However - I seem to need to open up FSUIPC and just use one additional axis and closing the window (without making any changes whatsoever) before FSX "sees" my toe brakes. When I'm in this pre-open FSUIPC window "limbo", all my axes operate fine - except the toe brakes. It's not a huge problem - I make a point of opening and closing FSUIPC for each new FSX session, but I'm wondering whether this can be avoided. It feels like FSUIPC isn't quite initiliasing properly on startup. My first post here, so be gentle with me! *Great* program, BTW Pete! EDIT: Just installed 4.616. Same issue. Correction to the above: simply opening and closing the FSUIPC window kicks things off.