Pete Dowson

Sorry, there's no longer any way I can develop FSUIPC3. FS9 is now 12 years old and I've changed development systems several times in that period. I just don't have the tools to work with it, nor, I'm afraid, the interest at all. The improvements still occurring in FS developments -- FSX-SE, P3Dv2 and P3Dv3 -- are filling my time and PCs as it is. Pete

Ah, the wxmapping.bin file. Yes, that can get corrupted if FSX crashes, and like corrupt WX files, will cause Simconnect to crash FSX when FSUIPC asks for weather data. I thought you meant a program called wxmapping. FSUIPC doesn't read any weather files directly -- it just uses standard SimConnect weather requests. The trouble is both wxmapping.bin and WX files (those with flight files) are binary files with no checks whatsoever, and SimConnect doesn't check them. Corruption causes crashes. It often only crashes if a Registered FSUIPC is running, because it is reading weather data as soon as FS is "ready to fly". Pete

Okay, please try this version and let me know if it works (i won't have time to test properly till the weekend): FSUIPC4948d_TEST.zip In this the Traffic Zapper control can have a parameter as follows: Ground 0 (default) == 15 degree deviation either way, as before 1 == 30 degree deviation either way 2 == 45 degree deviation either way 3 == 60 degree deviation either way 4 == 75 degree deviation either way Air 0 (default) == 2.5 degree width either way, as before 1 == 5.0 degree deviation either way 2 == 7.5 degree deviation either way 3 == 10.0 degree deviation either way 4 == 12.5 degree deviation either way Hope this meets your needs. Please test and let me know. Pete

Well, it is magic then, because FSUIPC can only ever get those assignments from an existing settings file, and only in the Modules folder. Pete

No idea what wxmapping is, but it sounds like it is corrupt. Pete

That was before the new Prosim -specific 738 model. The old one wasn't quite so good, but still a lot better than the PM-specific one. With PM I used to use an FS9 version PMDG 738. i haven't got motorised throttles. i always retard my throttles to idle during cruise and not really notice what the system does. Whatever it does it works okay. Maybe next time I'll watch the throttle settings it uses more closely. I disconnect AP and AT at 1000 foot AGL or soon after in any case if I have sight of the runway as landing manually is the fun part. I'll try a complete autoland next time maybe. Don't know when I'll get time to get back into my cockpit though .... Pete

You'd need a program interfacing to FSUIPC, or a Lua plug in. You might just be able to fiddle it with an offset conditional prefix on an assignment to a button but you'd still need something to press the button. Examples of Lua plug-ins doing all sorts of things are supplied in your FSUIPC Documents folder, and there are lots more in the User Contributions sub-forum. Have you ever considered using Prosim737? I changed from PM to Prosim at the end of 2014 and haven't looked back since. Pete

Unknown length names are not easily supported by the offset method. I would have to limit the length to a specific size. What would be reasonable but not too extravagant? And since all the other parameters are the same I would need to reuse those offsets -- so the nameless ones would first need zero in the first offset byte for the name. Pete

Of those, is FSXWX the only user of FSUIPC? What is HDE V2? When is FSXWX started? Are you going to do the log and show it to me as I suggested? Pete

Reinstalling FSUIPC never deletes or changes any of your settings. I'd be in lots of trouble if that happened -- folks spend hours getting their stuff just right! To install from scratch you would need to delete all files in the Modules folder, or the whole folder itself. Looks okay. You may want to go into the Logging tab next time and turn off the logging options you no longer need. Pete

I doubt it. That stuff may tend to confuse the Installer (though I think I've now caught most of the likely problems these migration tricks can cause), but once FSUIPC is installed none of that stuff matters -- it either works (because it recognises the underlying FS version) or it will cause all sorts of problems and crashes (because it thinks your P3D is FSX). Pete

You still have ABORT assigned, look here: 117515 Button changed: bRef=0, Joy=0, Btn=1, Pressed 117515 [buttons.Maule M7 260C] 2=P0,1,C65733,0 117515 FS Control Sent: Ctrl=65733, Param=0 117515 *** EVENT: Cntrl= 65733 (0x000100c5), Param= 0 (0x00000000) ABORT The line in the INI where it is assigned is 2=P0,1,C65733,0 in the [buttons.Maule M7 260C] section. Maybe you assigned it generically and specifically for the Maule? And, anyway, why would you assign ABORT if you didn't want FS to terminate when you press that button? There's another assignment there which is not doing anything useful:: 0=P0,0,C0,0 Control 0? There isn't one. So that button will do nothing on the Maule. Is that what you intended? Pete

It isn't crashing. it is terminating normally. I already told you that! Something is telling FS to terminate as soon as FS is ready to service applications. So the first thing to do is list all the add-ons you have installed. Then enable some logging. Add these lines to the [General] section of the FSUIPC4.INI file: LogEvents=Yes DebugLua=Yes LogExtras=Yes LogWrites=Yes and run it again. Er .... What do you think I'm trying to do? And you can't expect a reply within minutes every time!!! I had to go to the Doctors, soon I have to go out again. It may sometimes be minutes, sometimes hours, rarely a day or two. Pete

Okay. So you have no joysticks being recognised and nothing being tun by Lua or Auto sections. But, you have WideFS enabled. Are you aware of that? Maybe it's a Network problem. Try changing the WideFSenabled line to say 'No'. If that does nothing we'll need to add some logging lines to get more data. FSUIPC certainly cannot cause FSX to terminate normally without being told somehow. Something might have got corrupted in FSX. Maybe you need to try repairing it or reinstalling. Pete

The log shows a normal completion to the FS session. Look: 29953 System time = 08/12/2015 13:45:44, Simulator time = 13:45:18 (21:45Z) 30922 Starting everything now ... 35281 System time = 08/12/2015 13:45:50, Simulator time = 13:45:20 (21:45Z) 35281 *** FSUIPC log file being closed Minimum frame rate was 21.6 fps, Maximum was 21.6 fps Minimum available memory recorded was 32768Mb Average frame rate for running time of 3 secs = 18.9 fps G3D fix: Passes 7846, Null pointers 0, Bad pointers 0, Separate instances 0 Memory managed: 4 Allocs, 4 Freed ********* FSUIPC Log file closed *********** Something you have is closing FS as soon as it runs. It isn't a crash but a normal termination. Your INI file is incomplete. CAn you post the whole thing not a fragment, please? Pete

You need to ask LINDA support what is going on at this point: Was there a cTD there too? Is it the same as the button 19 crash? That's very strange. It looks like there's some sort of corruption occuring there. But what is LINDA doing? I suspect it is still a P3D crash in their joystick support. Don't you have any crash data, like the module name and offset? On a CTD there will be data in the Windows Event Viewer. On the earlier report you said it crashed on pressing "button 19". What is that assigned to? Pete

The log is not so good. To start with it is a "continued" log -- you pressed the New Log button for some reason. Please do not, You've lost all the initialisation data. Second, the sim did not crash in this log, it terminated normally as you can see at the end. Thirdly, why are you logging weather and so on? That just fills up the log with irrelevant things. I don't know any way pressing a button on a joystick can crash FS or P3D. What is it assigned to do? Is it this button, pressed near the end? 150484 Button changed: bRef=0, Joy=0, Btn=1, Pressed 150484 [buttons.Maule M7 260C] 2=P0,1,C65733,0 150484 FS Control Sent: Ctrl=65733, Param=0 150484 *** EVENT: Cntrl= 65733 (0x000100c5), Param= 0 (0x00000000) ABORT Why are you assigning to ABORT? That presumably tells P3D to close (I've never used ABORT). Is the fact that you are telling P3D to close and it is doing so, quite normally, confusing you? Pete

Obviously if you enable the mousewheel trim option in FSUIPC then it uses the mousewheel. But apart from that, elevator trim axis assignment is implemented by assigning to the elevator trim axis in FS, it is just a control and same as you could do it in FS itself no difference. Or elevator trim by elev trim up / down controls similarly is by FS controls, again identical to assigning in FS. Pete

You are misunderstanding things big time. There's no difference between "registered" and "unregistered" except the presence of the registration details in the KEY file. There's only one current version at any time. Registration will let it use any User Settings you made, or defaulted, which are saved in the INI file. That's all. All files associated with FSUIPC are kept in the Modules folder, nowhere else. The difference in behaviour is only the user facilities, which are all under your control. Pete

FSUIPC only uses the mouse wheel if you've elected to use any of the mouse options on the Miscellaneous tab in the Options. It most certainly does not interfere with normal use otherwise. Active Sky and FSUIPC have always cooperated perfectly together. Pete

No, sorry. Error code 20D (525) isn't even listed in the Windows Error Code index, so I expect it is specific to COM technology, which is a complete mystery to me having never used COM. Sorry, I cannot help with this. You need someone who knows more about the technology. Pete

First download this update: FSUIPC4948c_TEST.zip Then try again. I then need to see the FSUIPC4 LOG file,please. It looks like you have a bad P3D install. Pete

You aren't using Joy Letters, so FSUIPc is treating joystick #0 as #0 and #1 as #1. it has no choice. The joystick IDs are assigned by Windows at boot time and are liable to change if you reinstall Windows or unplug devices and plug them in again. To get around this first edit this section: [JoyNames] AutoAssignLetters=No 0=Saitek Pro Flight X-55 Rhino Throttle 0.GUID={30691CB0-9A59-11E5-8001-444553540000} 1=Saitek Pro Flight X-55 Rhino Stick 1.GUID={30691CB0-9A59-11E5-8003-444553540000} adding these extra 4 lines: S=Saitek Pro Flight X-55 Rhino Throttle S.GUID={30691CB0-9A59-11E5-8001-444553540000} T=Saitek Pro Flight X-55 Rhino Stick T.GUID={30691CB0-9A59-11E5-8003-444553540000} I've chosen "S" for stick and "T" for throttle but assigned the other way around. I know they are wrong at the moment, but bear with me. Now run FS. FSUIPC should now replace all assignments for 0 and 1 to assignments for S and T. Close FS. Then edit those 4 lines to swap the S and T. i.e. T=Saitek Pro Flight X-55 Rhino Throttle T.GUID={30691CB0-9A59-11E5-8001-444553540000} S=Saitek Pro Flight X-55 Rhino Stick S.GUID={30691CB0-9A59-11E5-8003-444553540000} Next time you run FS it should all be as you intended, and will stay okay over further reinstalls or unpluggings. Pete

No, the cylinder option is different and wouldn't do what you want. I'll take a look at a width option. Pete

No. FS doesn't simulate the Off position. Pete