Pete Dowson

Translation Ok. If you still have some problems, please then tell me what they are. I still don't understand why you posted here in the first place. Pete

Well, it won't be FSUIPC doing it, unless it is being told to operate the rudder. You should disable controllers in P3D, not "disable all axes". You can leave all the P3D assignments alone -- just disable controllers. Far safer. Try enabling Fthe Event and Axis logging in FSUIPC's Logging Tab. Switch P3D to Windowed mode first and enable the Console Log (on the Logging Tab). Then you can see which controls are being sent to P3D when you operate the yoke. Pete

Translation: Ah, sorry. Yes of course. The current INSTALLER is on that website. But I see you have the update already as you say next: But 4.957c is an UPDATE, no installer. If you have FSUIPC 4.957b already installed, as you said, you simply copy the newer DLL into your FS Modules folder. No other installation is necessary. By th way, so far you've not actually said what your problem is with 4.957b! Perhaps you need to do so if you want help? Pete

Translation: Sorry, this makes no sense to me. Choose one of the two places I mentioned, then try the other! Pete

Translation: Seems you have a problem at your end, because the file is perfectly fine and has been downloaded and installed by many folks in the last few weeks. Which place did you go to, www.schiratt.com/dowson or the Download Links subforum above? (Both work okay). Try the other, but I would suspect your ISP or your connection. Pete

The yoke's aileron axis will control the steering with the option set so in P3D. This is a facility for those without pedals. See if something has switched that on. If the option is still off, then the most likely thing is that you have the yoke double-assigned, maybe in P3D as well as FSUIPC. You should always disable controllers in P3D if you are assigning in FSUIPC. FSUIPC will only control rudder if you tell it to, i.e. assign to the rudder control. Pete

MOVED INTO SUPPORT FORUM! Google translates this as: Version 4.957b is a little out of date. Please try the later version 4.957c. SimMarket do not support nor supply FSUIPC. They merely provide the Registration Keys when purchased. I've no idea why you are complaining about them. Please post general support questions to the Support Forum, not to the specialist sub-forums unless they are specific to that subject. Please read the titles first! Pete

Then there is no file which Makerunways can use either! Check the Makerunways log ("Runways.txt". Search for the airports there. If it scans the folders containing the airports you installed, but finds no relevant data, then there isn't any. If you are seeing runways in FS then these must be the defaults. maybe be scenery only adds superstructure -- buildings and such. A bit pointless as I'd never use it -- I don't fly in the US. And if there was a problem with the airport data which Makerunways wasn't handling correctly I'd only need the AFD (Airport Facilities Data) BGL, or maybe the scenery BGL file which includes AFD information. (It can be built into the main scenery files -- it's only a series of identifiable records). The default 29palms airport includes this data, which may be suffucuent, depending what the add-on is doing: Airport 43CL :N34:12:21.9957 W115:59:52.0005 1793ft Country Name="United States" State Name="California" City Name="Twentynine Palms" Airport Name="Dick Dale Skyranch" in file: Scenery\0202\scenery\APX17190.bgl Runway 12 /30 centre: N34:12:22.0929 W115:59:50.4137 1793ft Start 12 : N34:12:31.5845 W116:00:02.2730 1793ft Hdg: 134.0T, Length 2860ft Computed start 12 : Lat 34.208862 Long -116.000749 Start 30 : N34:12:12.6014 W115:59:38.5561 1793ft Hdg: 314.0T, Length 2860ft Computed start 30 : Lat 34.203415 Long -115.993926 Hdg: 134.000 true (MagVar 14.000), Dirt, 2860 x 85 ft *** Runway *** 43CL0120 Lat 34.208862 Long -116.000748 Alt 1793 Hdg 120 Len 2860 Wid 85 *** Runway *** 43CL0300 Lat 34.203415 Long -115.993927 Alt 1793 Hdg 300 Len 2860 Wid 85 Runway 10 /28 centre: N34:12:24.8464 W115:59:48.9556 1793ft Start 10 : N34:12:30.2887 W116:00:03.7002 1793ft Hdg: 114.0T, Length 2800ft Computed start 10 : Lat 34.208462 Long -116.001175 Start 28 : N34:12:19.4366 W115:59:34.2128 1793ft Hdg: 294.0T, Length 2800ft Computed start 28 : Lat 34.205341 Long -115.992691 Offset Threshold secondary: 150 feet Hdg: 114.000 true (MagVar 14.000), Dirt, 2800 x 85 ft *** Runway *** 43CL0100 Lat 34.208462 Long -116.001175 Alt 1793 Hdg 100 Len 2800 Wid 85 *** Runway *** 43CL0280 Lat 34.205341 Long -115.992691 Alt 1793 Hdg 280 Len 2800 Wid 85 FSM A/P 43CL, lat=34.206112, long=-115.997780, alt=1793 As for Meigs, again, if there's no ADF information then maybe the airport scenery is just that -- scenery. i.e. not defined as an airport with an AFD. Does it appear in FS's "Go to airport" list, and does it have runways selectable in its drop-down? Pete Pete

Try assigning to the control named "Simconnect menu 0". I think there are controls for all 10 of the menu entry possibilities. Pete

That was ONLY for one very specific error, not "errors", though it was the most common -- in FSX (MS edition) only. It is fixed in FSX-SE and doesn't even apply to P3D where things are quite different in this area. Pete

Well that would mean your calibration wasn't very good. with correct calibration you should be able to steer with good sensitivity whilst braking, keeping straight should be easy. But it was the Spoilers you said you set in P3D, not the Thottle. you do have the throyyle assigned in FSUIPC! As explained at length in the User Guide, because FS/P3D does not support Reverse Thrust on its throttle assignments, FSUIPC does it using older controls which are only availble for separate throttles for each engine. You'd need to map the single throttle to multiple throttles, a simple checkbox on the calibration page. Mind you, PMDG's 737 and 777 add-ons don't work with FSUIPC calibrated throttles, and you cannot assign directly but only to the FS Axis controls. I see you have that wrong too. That is all done by proper calibration! You shouldn't be using P3Ds sensitivity or dead zones, they really just limit the precision of your devices. The main reason folks use FSUIPC for their devices is for the far better calibration and results. You can even apply different sensitivity curves. P3D's sliders simply make it ignore more of the inputs from the device so gives less precision. It would really be worth your while reading at least some of the User Guide, especially the chapter on calibration. I think you are rather wasting your money on FSUIPC the way you are using it. Pete

This not related to anything in FSUIPC so I'm not sure why you are posting here. FSUIPC cannot fix such crashes for you! G3D crashes are nearly always due to bad textures or scenery files. If you can isolate the scenery responsible you may be able to fix it by reinstalling that scenery. Pete

The latest version is always the one available here, in this, the Download Links subforum. The version of FS or p3D isn't relevant, it's the same for all (and back to FSW95). Please, in future, only post support questions to the main Support Forum. You are lucky I noticed this post. Pete

The default of 256 is perfectly adequate. A Delta of 1 means most of the time FSUIPC will be sending controls to FS with no effect whatsoever, except maybe to overload SimConnect to the detriment of other applications. A Delta of 1 is used for controls for setting specific discrete values where every increment is meaningf ul. Yes. The format is documented in the FSUIPC Advanced User's manual. Yes. Well that's more usually to do with calibration. The difference between 1 and 256 on most FS controls is neglgiible. That's why it is best to ignore every difference less than 256. After all, the standard calibration gives a range of -16384 to +16383, a full 32,768 values. Very few of those are actually seen from devices as their resolution is rarely better than 1024 positions, and most are 128 or 256. The higher resolutions are only really seen with optical devices, depending on the graduations on the disc they use, but with electrical deices like potentiometers it depends on the grade of the carbon or the number of windings of wire, and the length of the track the wiper moves on. Oh, and the width of the wiper of course. Pete

The rudder control isn't assigned in FSUIPC, but the toe brakes are (normally part of the rudder device) AND another Spoiler control to the SAME device. All the rudder devices I know have a rudder input and two toe brake inputs, but not a fourth axis, so it does appear in your assignments as if you have the rudder acting as a spoiler control as well! Exactly what I said, but there it is, in black and white: 0=0X,256,D,7,8,0,0 -{ DIRECT: LeftBrake, RightBrake }-1=0Y,256,D,8,7,0,0 -{ DIRECT: RightBrake, LeftBrake }-2=0V,256,D,22,0,0,0 -{ DIRECT: Spoilers }- The 0 directly after the = means device 0, which as you saw in the [Joynames] section, is the rudder. Also I don't understand why you've assigned both left and right toe brakes to each of the brake pedals! Really it is all rather a mess. Can you please elaborate on this. FSUIPC includes ALL of the controls offered by P3D plus many more. P3D only offers a subset. So which controls are difficult for you? And why the rudder, when it is one of the main controls alongside the aileron and yoke? Probably a good idea. Better, it won't matter which port you plug them into, as FSUIPC will track them by their names. No, you would need to do nothing. What's to go wrong? The only problem you'd be left with is having controllers not disabled in P3D. I won't really be able to help if you continue with that. Pete

Ah, so you haven't disabled controllers in P3D? It's not a good idea to mix assignments in both FS/P3D and FSUIPC. Both FS and P3D have a habit of making automatic assignments sometimes. Then you'll get two inputs from the same controls and buttons, often conflicting. You should always assign only in one or the other, and if in FSUIPC disable controllers completely in P3D. If this hasn't affected you before you've been lucky. The really odd thing, though, is that you have the spoillers assigned to the same device as the toe brakes (as well as on two other devices). Does your pedal set have a spare lever you've assigned for this? Seems rather odd. You shouldn't need to reassign everything, although seeing that you have so many duplicate assignments, probably unwanted, it might not be a bad idea. However, if you tell FSUIPC to assign letters then it will do, automatically replacing the IDs in at least the assignments to devices 0 and 2, the two you have listed at present. Then, if these are wrong, you only need to change the letters over manually in the [JoyNames] section. As it is at present, since there's no known device 1, those assignments won't get lettered. If you only ever have those two devices then you might as well delete those assignment lines. But implement the lettering first. It's easy to do -- just one line to change: Set that to Yes. Pete

No. Such a keystroke in impossible. 10 is not a character on any keyboard so has no keystroke code. I think you are referring to the bug in P3Dv3 which produces a 10 on screen where there should be a 0. Try 0. I think this is fixed in the latest update for P3D. If not it soon will be. Pete

On the contrary, that is probably precisely the reason. Each time to reconnect them it is quite possible that they will be assigned a different ID. FSUIPC relies on the IDs to tie the devices to your assignments. Windows assigns IDs on some basis depending on which sockets they connect to and what order it sees them. Looking at your settings: You have a Yoke as ID 2 and pedals as ID 0. In your assignments you have many to device 0, which isn't (now) attached. Just for now looking at the profile you used last, PMDG: You have here assignments to devices 0, 1, and 2. Judging by the axis assignments, here: You have two assignments to the main aircraft yoke controls -- devices 1 and 2, and 3 assignments to spoilers seemingly on the same device (pedals) as the toe brakes! But no rudder assignment? If you want to be able to unplug and plug devices in to your heart's conent, you need to tell FSUIPC to use letters instead of numerical IDs. It will then match them up by name -- the only time it would then have trouble is if you had several identically named devices. There's a chapter in the User Guide about this. Look up Joy Letters. Oh, and version 4.957b is out of date and unsupported now. Please install the current version, 4.957c. Pete

You don't need to delete them -- when you change the assignment, the new assignment replaces the old one. I suspect you still have controllers enabled in FS. That's a recipe for trouble. You should either assign everything in FS, or everything in FSUIPC. In the latter case it is best to disable controllers altogether in FS, otherwise it may at some stage perform automatic reassignment, to confusing and unwanted results. You can do, though the normal way would be do do it in the Buttons tab in FSUIPC options. That's what the "Clear" buttons there are for. No. They are sequence numbers only, and need not be consecutive. They determine the order when a sequence of assignments, or conditions, are programmed. The numbers will get re-used if you make further assignments. Pete

The default aircraft have no control for the wipers. Pete

You only showed part of the INI file, just for the KingAir, which seems unlikely to be a 737! You'll need to show the complete INI file, and the FSUIPC4.LOG, please. The LOG would show me whether FSUIPC loaded okay and was the correct version, and also what the Aircraft name was, and the rest of the INI would show the Profile allocations. Be sure you updated to the latest version (4.957c at least) of FSUIPC, as earlier ones will not work with P3D 3.4. The usual reasons folks find assignments not working are: * The profile where the assignments are made does not include the aircraft you loaded, * The control devices have been removed and reconnected, causing the Joystick ID numbers to change. Pete

Good! Glad you got it sorted! Pete

Okay. Evidently, when deleting in preparation for adding afresh, I'm not deleting the previous Tab. I'll fix it in the next release. I'll remove all tabs beforehand before inserting the new tab+text, so it will revert to the way it should be! Thanks, Pete

The installer only updates the program itself, and the documentation. It changes nothing else. I don't think IVAO uses FSUIPC. To see if FSUIPC isrunning check the Add-Ons menu, see if FSUIPC options are there. Old? Perhaps you started FS 3 minutes before you looked? If you mean older than the LOG, then either you are looking in the wrong place (not the Modules folder within the FS installation you are using), or you are not running FSUIPC at all. It ALWAYS starts a new LOG and updates the INI as soon as it loads. More likely you are looking in the wrong place. Run the latest installer. That will at least ensure it starts running when you load FS. Then if you still have a problem, show me the Install log -- you can always find that as it is placed next to the Installer, wherever you put it. Pete

Okay. Thanks. I do get depressed sometimes. I actually left employment when I was 36, starting my own software business with a more outgoing friend who was good at marketing and devising projects. I've always been a programmer only, really, leaving ICL when microcomputers became available -- the Commodore Pet was my first, on which I developed a word processor called WordCraft. Later, when my eyesight problems stopped me getting a pilot's license I got into flight simulation., writing software for FS4, FS5 FSW95, FS98 before FSUIPC, which was freeware, as it was a hobby. The company we formed stopped making enough money to pay me anymore a bit before FS9 appeared, so I was on the point of looking for a job instead of continuing FSUIPC when others suggested asking for donations. I did, but that paid almost nothing, certainly not enough to survive, so that's when FSUIPC went payware. It's been full time (apart from holidays) since. So I have my ups and my downs. Pete