Pete Dowson

No, sorry, all my software is intimately tied into FSX/P3D. Pete

What it actually means is that when FSUIPC tries to start it detects another copy already running. This is most often because your previous run of FS is actually still running, despite all of its windows having closed. To fix this, either re-boot the PC, or simply run Windows Task Manager, go to the Processes tab, find FS9.EXE (or is it FS2004.EXE?), right click it and Terminate it. If this turns out not to be the case, then the only other way I know it can happen is if you or some other application has put a copy of FSUIPC.DLL in the main FS folder. Check there, and remove it if so. Be sure to get the name correct. Don't delete FSUI.DLL which is part of FS. Pete

The "B737 NGX Flaps" profile? Are you selecting the same profile in Calibration? Which actual "flaps" control are you assigning to? Do you mean the range assignment setting options on the right-hand side of the assignment tab? If so then, yes, you shouldn't need to use those at all for axis calibration. They are to allow other controls, non-axis types usually, or even FSUIPC offset events, to be programmed. One common use for those is to allow an axis to be used as a Gear level, with GEAR UP and GEAR DOWN programmed for regions of the axis movement. Best to c same profile first. I do really need to see your INI file again. Obviously you've changed it since the last one you posted. Er, unless you are assigning everything in FS, which of ocurse you can do, then, yes, everything must be assigned in FSUIPC. It is optional, you can do either, but only one of those two choices. If your Flaps axis is not assigned then how can its values reach eith FS or the clabration? How would the calibration tab know what axis it was? Don't you see? In actual fact, the calibration tab knows nothing at all about axes or devices. It only understands FS controls. It intercepts the controls being received by FS, no matter where they come from, and changes the values being used. This ocurs just before FS actually uses them. It is a long way from any assignment function or device. I am 73 as well, but feeling older! :-( Pete

What "ambiguously labelled assignment function"? There's no assignments possible at all in the Calibtration Tab! The calibration part deals solely with FS control functions, not axis or button inputs. And it doesn't matter where the assignment is made, in FS or in FSUIPC, or even from a third part application! Calibration works by intercepting the axis commands being RECEIVED by FS, after any assignment anywhere, and altering the values actually being fed in, at the last stage. Historically the calibration facilities were there first, assignment in FSUIPC came a lot later and s completely separate. Assignment was from user requests, primarily (or even solely at the time) to allow different assignmetns for different aircraft types, something FS couldn't achieve, and also dual controls for such equipped cockpit builds. I think you are completely misunderstanding things, and strongly suggest you actually read a bit more of the documentation, or try reading it again. In the 18 years of FSUIPC I've never had such bewildering misaimed criticism of the interface. And, sorry, but I'm not about to start reworking any part of FSUIPC at this late stage. I'm 73 years old now and think it is about time I got on and did some other things. I try to support it as well as I can, and keep pace with all the changes to FS/P3D which are rather unexpected after a life of 9 years since Microsoft withdrew, but that's as far as I'll go. Well, except for minor additions on request from time to time. I'm closing this thread now as it is obviously going nowhere useful at all. Pete

Just some questions, first, please: 1. How many profiles do you have, and why so many? Are you really assigning different buttons, different keys, different axes or having different calibration for so many? I really cannot imagine how you could cope if every aircraft has different assignments. Profiles are supposed ot make it easy to have categories of aircraft which do have separate controls, but I cannot imagine how you are extending a list so much. 2. Whilst awaiting your settings I just created about 45 profiles, just about covering every aircraft and individual pain job from each, that is installed in a default P3Dv3. What I actually see if the drop down window becoming longer and longer until the bottom is off the screen and unreachable. Is that what you mean? If that is what you mean I don't understand why you'd say you wanted the size to be expanded. Seems to me it just keeps getting longer forever. (or at least as far as I have the patience for). I could probably do something to actually LIMIT how much it grows, so that it will get scroll bars at that stage *no it won't! see below), but this seems to be the opposite of what you appear to be asking, for the size to be expanded. [LATER] Looking at the code I see it is a Popup Menu, which cannot have scroll bars and just keeps expanding as things are added. I really think the best solution is to get your system tidied up. There should be no reason for you to have so many different profiles. I expect you've created identical ones for things like different paint jobs. Please show me your FSUIPC4.INI file and I'll sort it out for me as best I can. Pete

It should just expand until it can't any more, then provide scroll bars*. It's a normal Windows drop-down like the others. Maybe if you could give me your INI file I could see exactly what you see here? You can attach it or paste it, either. Pete [later] see later message about all this.

I can assure you it wasnn.t FSUIPC which hung. Pete

Ah, so there was definitely a crash -- they both refer to the same incident. If this happens often I think you will need to try and find which add-on s responsible. The module MSVCR80.DLL is used by FS itself and many other programs, so it could be almost anything -- or it could simply be a memory problem. It is known that some crashes can occur because of memory shortage problems as VAS gets used up. However, looking back at the FSUIPC log, the date matches to that of the recorded crash, but not the time: So I think the FSUIPC log does relate to a hang rather than a crash -- which won't be recorded in the Event logs. Pete

Nice, but not really that realistic. Perhaps when aircraft are fresh out of the factory all the mechanisms are exact and the engines identically performing, but not as they get used. Anyway, your "idle" positions should be EXACTLY equal, because the idle positions are one of the three normal positions you calibbrate! If you haven't got them in the same place it is your error for not calibrating them to the same place. There's even a range for idel, two positions with idle in between, so it's easy, with no excuse. If yo want it to match in most other places, then use the Sync Pos option -- you can calibrate many points to match, all the way. The facilities are there, it is up to you to use them if you wish! See page 52 in the User Guide. Er, why? First, why change the Deltas? The default is fine. There's no point in changing them. All you should be doing on the Axis assignments tab is assigning the axes. Leave the rest well alone. Second, calibrating is simply clicking a button for minimum, two buttons for the idle area, and one button for max. That's it. How is it "fiddly" and how does it take more than about 30 seconds? I get the feeling that you are not following the simple step by step instructions for calibration given in the User guide, or are completely misunderstanding something which is really easy! Unnecessary? Of course calibration is "unnecessary", bu if you don't want calibrated axes why on Earth bother using FSUIPC? FS should be sufficient surely? After all it is intended to work with external controls. And if your controls are so perfect, so clearly matched, there wouldn't be a problem, would there? But if you know the values without even moving the lever, why bother? The point of calibration is that no two axes are the same and without recording the positions you need, by simply moving the lever and clicking a button, values you might conjure up would be relatively meaningless. How are they going to match? And entering 4 numbers requires up to 20 digits on the keyboard. Why is that easier or quicker than 4 clicks on the mouse? Sorry, very little you say is making any real sense! :-( If you know all the numbers for the correct positions on all your axes, just enter them directly in the calibration section of the INI file. The format of most of the INI file entries is documented in the Advanced User guide, and where it isn't it is pretty obvious in any case. Pete

It isn't complete! What happened, did FS hang? I always need to see the complete log -- there's important and relevant information in the summaries at the end, after close down. And here's evidence of very poor performance here: 3708296 **** Restarting traffic scanning due to non-reception **** and here: 6672625 Sim stopped: average frame rate for last 29 secs = 8.3 fps Your second log, which was complete shows no symptom of poor performance. Pete

Yes, you need the license for WideFS6. Pete

I don't remember off-hand, but it is somewhere in aircraft realism options in FS and presumably P3D. Pete [LATER] Okay, loaded P3D to take a look. it's the "Autorudder" option in Settings-Realism (as, in fact, it was in FS). Pete

Sorry, I cannot reproduce any similar problem. Also, FSUIPC is never checking the altitude, so the altitude part isn't really relevant. Possibly when you are nearing the airport something is getting overloaded and preventing some of the SimConnect actions being requested. Check the Log to see if any problems are reported. Quite honestly, I cannot change any code related to weather at this stage. It's been the way it is now for 10 years and I'm likely to do more harm than good making any changes at all in this area. Pete

You have no assignment to Flaps! In fact you have no axis assignments at all except, oddly, just for Gear: 0=0Z,256 1=0Z,U,6400,16383,66079,0 -{ Entering=GEAR_UP }- 2=0Z,D,-16384,-3901,66080,0 -{ Entering=GEAR_DOWN }- You also have a strange line in the [JoystickCalibration.B737 NGX Flaps] section: 0=0X,256 which looks like it really belongs in an Axis section. Also, you seem to have made some Flaps detente calibrations, as they are there: FlapStarts=–16384, –16219, –15450, –12975, –6980, –573,4606,15600,16217 FlapEnds=–16256, –16200, –15417, –12950, –6950, –550,4644,15650,16384 Flaps=0,16380 Pete

Well, I don't quite understand that, but I assume it means that the AFD data in one of the BGLs is scrambled in some way and that DTG have added software to FSX-SE which de-scrambles it. That obviously will stop anything else needing to use the airfield information. I don't know of any other add-on scenery maker who finds it necessary to go to such steps, and many airports are very extensive and not at all cheap. Yet you don't get folks peddling "tampered" versions! Seems some paranoia is creeping into some quarters of the FS world! Shame. Pete

The normal download site, www.schiratti.com/dowson, as pointed to by SimMarket and in the documentation (and I think, on the screen?) always gets you the current supported installer. There's also the Download Links subforum, here (just look above) not only contains the latest versions, plus interim updates, but many other "goodies". Pete

This is confusing. Where are you seeing the "set figures do not change"? Is that in the axis assignment tab or the calibration tab? If in the axis assignment tab I need then to ask how it is possible that the "same lever axis for mixture for MAAM Dc3 works fine under present conditions, both via FSUIPC4 ..."? Sorry, what is the "De"? Maybe you need to show me the FSUIPC4.INI file, the one with your settings, so I can see what you've done? You can paste the text here in a message. Pete

Well FSUIPC simply asks Windows to load it, and Windows evidently has difficulties getting access to it. Permissions might be the problem, but sorry, I don't really know a lot about thet. I have difficulties of my own in that area! Pete

Maybe. Certainly I'm really surprised it installed there. Can you try uninstalling it and re-installing the a normal folder sleection? And "FlightSim" is your user name, the one you are logged in with? Pete

Windows error 2 is simply "file not found". You have the wrong path, I expect. It is rather unusual to have actual program files stored in the AppData folders. Those are pretty much exclusively used for program data specific to the user. You need to find the correct path for vPilot.exe. Pete

It would help if you showed the annotated entries -- or are you using an old version of FSUIPC before the annotation was added? (If so, please update now, as I cannot support old versions -- current is 4.957b, with 4.958 imminent). Here I've used a current version of FSUIPC to annotate them: 9=R2,20,C65966,0 -{THROTTLE1_DECR}- 10=U2,20,C65967,0 -{THROTTLE1_CUT}- 11=R2,20,C65971,0 -{THROTTLE2_DECR}- 12=U2,20,C65972,0 -{THROTTLE2_CUT}- 13=R2,21,C65976,0 -{THROTTLE3_DECR}- 14=U2,21,C65977,0 -{THROTTLE3_CUT}- 15=R2,21,C65981,0 -{THROTTLE4_DECR}- 16=U2,21,C65982,0 -{THROTTLE4_CUT}- No you can see clearly what the problem is: when you press the buttons you are getting repeated DECR, so eventually going into reverse. But immediately you release them you are doing a "CUT" which sets the throttle to idle! You need to set the throttle to idle first, THEN send repeating DECR, i.e. 9=P2,20,C65967,0 -{THROTTLE1_CUT}- 10=R2,20,C65966,0 -{THROTTLE1_DECR}- 11=P2,20,C65972,0 -{THROTTLE2_CUT}- 12=R2,20,C65971,0 -{THROTTLE2_DECR}- 13=P2,21,C65977,0 -{THROTTLE3_CUT}- 14=R2,21,C65976,0 -{THROTTLE3_DECR}- 15=P2,21,C65982,0 -{THROTTLE4_CUT}- 16=R2,21,C65981,0 -{THROTTLE4_DECR}- No need to send anything when you release the buttons, unless you want to have to keep the button pressed whilst in reverse. Pete

Sorry, I'm confused. Do you have 1, or 2 throttle axes? It sounds here like you have 2:: If you have 2 exes, you certainly shouldn't be mapping 1->2,3,4! You should assign lever 1 to Throttle 1, lever 2 to Throttle 2, then calibrate both separately on the separate throttles calibration tab. Each has its own REV option. If you need to reverse axes you need to do that BEFORE calibrating. Then, once set and working correctly for engines 1 and 2, you can map 1->12, 2->34 if you wish. You don't get separate "REV" options for mapped axes because they are set as an exact copy of the one you map from. That sounds more like "doing it correctly", rather than "working around it"? Pete

Well spotted Thomas! Thanks! Pete

When you say it "doesn't work" do you mean there's no response at all? Or what? The INI file shows a calibrate rudder axis, on the "R" axis input. So I assume it shows up values within the ranges you've set in both the axis assignment and calibration tabs in FSUIPC? Okay. This does suggest that it isn't to do with FSUIPC, but something else interfering with the rudder control. You said: By "disabled" do you mean you disabled controllers (one checkbox)? If so there's no need to delete assignmnts as well. Try using FSUIPC axis and event logging on the FSUIPC logging tab. If you run FSX in Windowed mode and enable the FSUIPC console log (logging tab again) you'll see what is being sent/received by FSX in real time. Pete

No idea. There are no other reports. This: means that my code, that DLL, wasn't in memory when the error occurred. Normally such errors would only occur when P3D was being shut down, as nothing else would really unload it -- or perhaps it could do that if it ran out of memory space in the 4k. Did you check VAS? The error probably occurs on a callback from SimConnect, or maybe one from FSUIPC itself, which tries to enter the relevant function in the DLL and crashes because the code is no longer there. I really have no control over that, and suspect it's actually a symptom of memory depletion. Pete