Pete Dowson

Really nice! What screen are you using now -- curved with multiple projectors? WidevieW or all on one PC? Are you still using Project Magenta, or switched to SimAvionics or ProSim (though ProSim haven't released their MAX yet, or maybe they have to Beta testers). Stay well. Pete

Ah, P3Dv4!? In that case something is most definitely amiss with your installation. As well as an FSUIPC6 re-install please try to uninstall your P3Dv4 Client (only -- don't deactivate) and re-install that, in case it's corrupt. That should only take a few minutes. It does here. The other thing to consider is a possible memory corruption occurring through corrupt weather files. You can try adding this to the [General] section of the FSUIPC6.INI file: NoWeatherAtAll=Yes. If that fixes it then you have some weather files corrupted, possibly caused by some P3d4 crash. Pete

Is this with P3Dv5 or P3Dv4? It certainly works fine in 4. maybe they've messed something up in 5. I can try that, but not till tomorrow I think. Same with the Zapper. Maybe the interface into P3Dv5 for traffic control has been messed up by L-M. Hopefully, by tomorrow, I'll be able to run P3Dv5 with traffic. It's been taking me ages to get it downloaded, installed, and just about running! I don't understand how part of the Traffic tab dialogue can vanish. That's just got to either be some sort of corruption or a video driver problem. Pete

Which version is that? 5.155 or 6.000? You need to be specific. Were you using the Traffic facilities before? Do you think things have changed? That probably depends on which version you updated from. You probably need the parameter set to 100 then. It always toggles between 0 and whatever you set there. I *think* it should assume 100 if you default to 0, but I've always been explicit. I'll try 0 here. The top left selection is a LOWER limit only if you use the second part to set a non-zero frame rate target. In the default case you would have no frame rate target and the first option becomes an UPPER limit, and the text changes to show you, being helpful! Really? I'm using it all the time. It was my favourite addition. Traffic set at 25% in P3D? How much traffic did that give you, and what was your lower limit? You don't need to change the assorted preferences at all until you see how it performs for you. Leave that till last. Best leave them all equal at 50% initially. The reduction to your lower limit will occur over time -- it doesn't delete big batches all at once to avoid stutters and annoying noticeable disappearances. So it will try to gradually approach your chosen frame rate but won't go further than the LOWER limit set. Pete

The problem is that none of the currently "approved" throttle axis controls have any sort of reverse range. The normal assignments, and the ones PMDG aircraft expect, have a range of -16384 for normal idle to +16383 for full thrust. So there's no way of having any axis based reverse with an add-on aircraft which does not support the old ways (dating from FS98) using Throttle Set controls. The sim itself doesn't really support or simulate a "reverse idle". The idle is just idle and that's it. Really if the more sophisticated aircraft like those from PMDG implement this then there should be a method of engaging it which they provide. I can see for the various posts in this thread that you've got close to "fiddling" it, and I agree with Thomas that sending -1 using the old ThrottleN Set controls should theoretically work -- provided there's no interference from the normal throttle axes (so you need a reliable idle calibration zone). However, in the end I think that if you cannot get consistent results with your add-on aircraft, you probably need to ask the makers (still PMDG?) how this sadded ophistication is supposed to be used. Pete

I don't know how the PMDG aircraft implement it -- they may do their own thing. But generally: If you want to use a switch or button instead of a position on the axis movement you could just assign that to send the Spoilers Arm On. Or maybe Spoilers Arm Toggle -- but I think the Arm will come off anyway when you operate the lever. If you want just to use the axis, the sim's spoiler axis has a zero effect from full down (i.e. off) to a point on the axis scale where the spoiler becomes ARMED. If your axis has such a position marked you can calibrate in FSUIPC to match the Arm position to that marking. See step 6 in the numbered steps to calibrate in the FSUIPC User Guide. If not, you just have to tell by whether the ARMED indicator lights. Pete

The log just shows you starting and closing P3D, and not even waiting till FSUIPC's closing logging has finished. More importantly it shows that you have not Registered FSUIPC, so it isn't even looking at your controllers. The settings in the INI file are just the default for an unregistered install. You need to sort out your reverser problems in P3D or with PMDG as you are not using FSUIPC and really have posted in the wrong Forum. Pete

No problem, glad you fixed it! Pete

Why not just Monitor the offset in FSUIPC's Monitor facility (on the Logging page)? The controls 65607 and 65615 (ELEV TRIM DN and ELEV TRIP UP) are standard sim controls. FSUIPC's Lua function does nothing with them except send them on to the sim via SimConnect. You could just check that the controls were sent by logging Events in FSUIPC's logging. You can also test via the FS controls directly -- eg. NUM kerys 7 and 1 (by default). I'm afraid I can't really deal with crashes in FSInterrogate2 -- that's the first ever one reported! The author might still want to know so it might be worth getting in touch with him. I'm pretty sure Trims must still be working in P3d5. 0BC0 is populated directly by Sim Vars supplied by SimConnect. If you monitored 0BC0 it would log also the incoming value (before conversion to the old FS98 compatible scale used in 0BC0). You might also want to check 2EA0 which would give the actual deflection. Also check that whatever changes you are trying to introduce are not being overridden by a Trim Axis input from somewhere. Pete

But not your first post in this thread, which was merely asking about recommendations for PMDG in view of other posts about the way PMDG unusually handles control axes. On your changed subject since that first post: This is patently NOT the same as "losing all calibrations and having to recalibrate"! If unplugging a USB device and plugging it in again "fixes" things it must only because that device has lost proper contact with the drivers in Windows. This can happen if you let Windows operate its annoying "power management", so make sure you disable that on all USB devices (hubs etc) in Device Manager. It tends to be enabled by default. Basically a re-initialisation of the link would do the same job, so if visiting FSUIPC axes tab and exiting again by "OK", without re-calibration, does the same thing for you then that's most likely the problem. If it isn't then I think you have a USB problem of a different kind. the fact that you get 'erratic' behaviour first seems to point to this. And are they, so far? Pete

Interesting! I wonder who said that and where? Care to provide the reference? Maybe it was related to the installation being via Add-On.xml now. Seems a lot of users are very fond of that. Pete

FSUIPC5 is for P3Dv4 only. You need FSUIPC6. You need to buy a new key from SimMarket to register FSUIPC6. Pete

Ah, yes. Hi James. Hope you are well! I remember that visit well. In fact I have a picture pinned up here somewhere of Enrico and I in the pilot seats of your cockpit! Was that 2003? I think we popped over after a visit to PFC's place in Sacramento. Do you still have the same 'pit? Pete

No. It is just that I never got consistent results with those Simconnect Menu events in P3D4. If you want to keep it at Ctrl+F you can assign to the added FSUIPC controls to send a keypress. Pete

Maybe. I've alays assigned directly to the normal 0-9 keypresses. You just need to make sure the menu (i.e. P3d) has focus. Pete

As it states in the offsets list PDF they ARE strings. They are plain ordinary ASCII strings, as supplied by SimConnect. Maybe you are trying to access them as Unicode or Wide character. ASCII uses one byte per character, e.g. A-Z are 0x41-0x5A, space is 0x20, and 0-9 are 0x30 - 0x39. All strings in the Offset interface are ASCII. Pete

Nevertheless there will be a log, even if it isn't finished. That's what John needs to see. You could also describe what happens before is closes without finishing. Such information is all essential else it is difficult for anyone to help. Don't you see? Repeating the attempt to install with no changes isn't going to help either. Software tends usuallyto do the same thing if nothing changes. If it didn't it would be rather useless for most things, except generating random numbers perhaps! 😉 Pete

Yes. You can use all of your FSUIPC5 settings, Just copy in the FSUIPC5.INI file and rename it as FSUIPC6.INI (delete the default FSUIPC6.INI, if there is one, first). You will also want to copy over any macro (.mcro) and plug-in (.lua) files you are using and, if you use separate files for Profiles, the Profiles subfolder. I'm pretty it tells you these things in the installation document. Pete

Change logs are provided for increments. FSUIPC6 is a new version with built-in compatibility for both P3D4 and P3d5 and is ready for onward developments as P3D5 develops. Apart from the new Installer, now also supporting the Add-on.xml method which seems so popular with some, there are no notable new user facilities. What were you expecting? Pete

Sorry, that is a matter for ProSim support. Maybe they are still to update their software to handle the different reported version number of FSUIPC and possibly P3D -- version 4.5 would give "45" in the version number offset, 5.0 naturally gives "50". This information is provided so that applications can make such compatibility checks. It is likely that whilst ProSim have updated to check properly in the Simconnect link they forgot about their FSUIPC check. BTW there was absolutely no need to post a picture, which i didn't even look at, just to ask such a simple question. Pete

This doesn't seem in any way related you your first post at all. I don't know any way that could happen. FSUIPC stores the calibrations quite clearly in the settings file, the INI file. How are you detecting that these are "lost"? Perhaps you need to post your FSUIPC INI file so we can see what you've got. Pete

There's no use for WideServer.DLL with FSX, FSX-SE or P3D. It was incorporated into FSUIPC4 then FSUIPC5 and now FSUIPC6 -- in other words, since 2006. This is mentioned in the documentation, and in fact on the download sites for WideFS. You only need WideClient and the documentation. WideFS is registered in the FSUIPC installer, which then enables the built-in wideServer. Pete

There's no part in the WideFS download you need in the P3D5 PC. You need WideClient.exe on your CLIENT PC, not the P3D PC! The only other part you need are the documents (the.PDF files). Just unzip to any chosen folder, even one you perhaps create called "WideClient", on your client PC(s). Pete

You can certainly try calibrating in FSUIPC. Many folks actually do with throttles and have no problems. The axes which give folks most problems are the flight controls -- aileron, elevator and rudder. What tends to happen is that the PMDG aircraft read thet values before FSUIPC gets them to calibrate them, so giving the sim two potentially different inputs. Pete

Sometimes corrupted code or data might cause strange errors, usually crashes (CTD's) immediately the Sim becomes ready for flying. The only such data which FSUIPC would instigate FSX reading and processing are the weather-related files, the wxstationlist.bin file in this folder: C:\Users\<yourusername>\AppData\Roaming\Microsoft|FSX (or the LockHeed Martin\Prepar3D equivalent) and the .wx files in your FSX (or Prepar3D) documents folder (the folder where your saved flights are). If any of those are corrupted, possibly from a previous crash of FSX, then they can cause unpredictable errors when loaded. Unfortunately FSX's SimConnect doesn't check these files before use. So, the first step is to try deleting all of those files. The .bin file will be rebuilt, and .wx files will be created for new flights, and are largely irrelevant if you use an add-on weather program. Another test would be to insert "NoWeatherAtAll=Yes" into the [General] section of the FSUIPC4.INI file. That will stop FSUIPC asking for the weather data. Of course this will stop any FSUIPC applications you may have getting weather data, but perhaps you have none.