Pete Dowson

64 bits of what? Do you just mean the P3D4 version? "gases". Does this mean "levers"? Throttle levers? What is the "CL" position? Pete

Sorry, this is not making sense. Can you explain what you are talking about, what your question is? Pete

Soorry, what P3D v4 SDK variable which is not a SimConnect variable? How are you obtaining it -- what code? The value I log for VERTICAL SPEED is the SimConnect supplied variable -- see the SDK yourself, "simulation variables" in the SimConnect API section. [LATER] See my later post which explains your confusion! Pete

As the documentation states (please do refer to it), 030C is a COPY of 02C8. They are therefore bound to be both the same units, and the copy is made as soon as 02C8 is changed by SimConnect, whilst in the air! Didn't you bother to do the logging I suggested? It will show the raw VERTICAL SPEED value received from SimConnect as well as the values in the two offsets. Log entries like this: 305013 Monitor IPC:02C8 (S32) = 669 305013 Monitor IPC:030C (S32) = 669 305013 SimRead: 02C8="VERTICAL SPEED" [also 0842] [also 030C] FLT64: 2.61257028694 That last value IS the value received directrly from SimConnect, and is therefore the Sim value at that time. 2.61257 x 256 = 668.8 = 669 to nearest integer (the offsets are 32-bit signed integers, "S32" in the monitor). Pete

Seems that it must be a Saitek problem then. You've tried everything else. Saitek support? Pete

As described in the Offsets list, all FSUIPC is doing, in order to populate offset 030C, is make a copy of offset 02C8 continously whilst in the air, at the same time as it is updated, and stopping doing this the moment "on ground" is signalled. Both pieces of information come from SimConnect at the moment they change. 030C is updated at the same time as 0328 excpt on ground, so it cannot always have a constant difference from that vertical speed value. 02C8 is the value of SimConnect variable "VERTICAL SPEED". The "on ground" indicator, which is at offset 0366, is the SimConnect variable "SIM ON GROUND". Just use the FSUIPC monitor (right-hand side of the Logging tab) to log these and check for yourself. I've no idea what SmartCars" is, but unless it is an internal DLL or Gauge then it is going to be nowhere near as precise at recording this as FSUIPC. Pete

Really, without the problem occurring there is little point examining any logs. Furthermore, you appear to have enabled more options than I requested. Enabling Weather logging fillls the log and makes it too long to be worth looking at (except for weather problems perhaps). Similarly for Axis logging -- we are not interested in every little movement of your yoke, throttles and rudder! Please ONLY enable Button/Key logging and Event (non-axis that is) logging, as requested! Pete

That didn't apparently involve FSUIPC, and the "fix" was a registry flag change. The user here says that without FSUIPC running then all is okay. He needs to check this he other way round too, whether without only SODE it is all okay. Either way, because there is no direct relationship between FSUIPC and SODE, it would point to something in P3D itself being or getting corrupted. The usual reason I know for corruption in P3D is bad weather files, but perhaps there are other possibilities. Pete

Only the main releases (with Installer) are provided through that portal. I have no control over that -- the link there actually points back here, to the same place as "Updated Modules", Interim updates, normally fixes or small changes put out for evaluation, are released here with just the replacement module supplied. All the rest of my software for flight sims is also provided here, in Download Links. This sort of behaviour has always been related to corrupt weather files. Did you delete all the .wx files in the P3D4 documents folder as well as wxstationlist.bin in the user AppData P3D4 folder? I can't imagine any way that might happen. SODE is running on many PCs including mine without problems, and since I updated GSX to version 2 I think even more airports have SODE in use. To check this, though, you could temporarily stop SODE running. Just rename the SODE folder in C:\Program Files (x86)\12bPilot. Whether or not this is the problem then I can only think that somehow SimConnect is corrupted within P3D. Try uninstalling the P3D4 Client (only) -- without deactivating -- then install it again via the Client msi file. This will change nothing but replace the program files of P3D (EXE and DLLs mainly). Pete

Not really, but it is the log I need to see, not a video. Pete

I don't know what sort of coordination there is between AS16 and PMDG aircraft. I only thought the latter might read the weather radar information from AS. Active Sky does have the option of automatically loading a plan into itself when it sees it loaded into the Sim, but what is relaoding it every 5 minutes? BTW i assume you mean ASP4 rather that AS16, as you are using FSUIPC5 and therefore P3D4. Pete

I don't fully understand, but it seems you are saing that your aircraft cannot use a lever with the normal full range of values from -16384 to + 16384. Can that be correct? What happens, do the values actually jumpt from -16385 to 1020 when the lever is in the last third of the movement? What values are "start", "idle" and "feather"? Is this peculiarity specific to that aircraft? Can you check on a default aircraft so that we can tell whether it is something to do with the throttle unit and FSUIPC, or actually a problem of the Majectic? Perhaps that's how that aircraft is designed, with specific indents on the condition leversl really selected specifically rather than by a continuous axis? Let's see. Your link points to this: [Buttons.Dash8]0=P1,30,Cx3200088E,x3E800FA0 -{offset sword increment, offset 088E (Incr=4000, Limit=16000)}-1=P1,17,Cx4200088E,x00000FA0 -{offset sword decrement, offset 088E (Decr=4000, Limit=0)}-2=P1,31,Cx32000926,x3E800FA0 -{offset sword increment, offset 0926 (Incr=4000, Limit=16000)}-3=P1,18,Cx42000926,x00000FA0 -{offset sword decrement, offset 0926 (Decr=4000, Limit=0)}- Now 088E and 0926 are Engine 1 and 2 Prop Lever inputs, with values -4096 to +16384 allowed. I think -4096 to -1 represent reverse pitch settings. Proper FSUIPC calibration of the levers with Reverse Range allowed will calibrate your -16384 to +16384 to that range. So that's step one. THe above assignments actually make the values starting from, assumably 0, jump to 4000, 8000, 12000, and 16000. Those 4 values don't seem to agree with yours x, y, z, 850, 900, 1020. (x y z being the three unknowns for feather, start and idle). Uoir values don't even get to 4000 let alone the others which are apparently needed. Did you actually do the other change suggested in that link, i.e. and the entry in themjc84.ini file: CL1_FUELOFF =0CL1_START =12000CL1_850 =24000CL1_900 =48000CL1_1020 =64000 CL2_FUELOFF =0CL2_START =12000CL2_850 =24000CL2_900 =48000CL2_1020 =64000 Seems to me that it is crucial, as it realtes your values to some others which at least have even spacing, though of 12000 instead of 4000. maybe the sim's values are multiplied by three in the aircraft code before use? You CAN program a lever to be like a series of buttons at intervals along its movement. You do this in the Axis assignments tab, on the right-hand side. There yo can calibrate up to 10 different parts of the lever movement, assigning whatever you wish to each -- and something different going to to going down. That facility would easily let you replicate those button assignments above. See the section about this in the Axis assignments chapter of the User Guide. Yes, of course. it's actually another application of the facility just mentioned, the right-hand side of the axis assignments tab. Find the exaple for "gear up" and "gear down" in the Chapter of the User Guide about Axis assignment. It's on about the 5th page (actually page 36 in the FSUIPC5 User Guide). Pete

Wow! A typo all the way from 2003, surviving 15 years! Thanks, It will be corrected along with other minor changes on the next full release of FSUIPC5. Pete

You need to enable Button logging AND Event logging, and check the log after it happens to see which button or switch made the changes. The log you attached is no use. In fact it is very odd indeed. It contains nothing useful, but this repeated every 300 seconds (5 minutes): 1532328 Planned flight from WSSS to VHHH 1532328 E:\Windows Libraries\Documents\Prepar3D v4 Files\WX.pln What is reloading the plan every 5 minutes? Also, the log finishes in the middle of that sequence. Looks like the session was not terminated. These "buttons" are actually locking toggle switches, then? Not normal "on when pressed" buttons? A log with the correct logging options selected will show if those are operating at times you don't expect. Pete

It really can only point to the hardware, or connecting cables, then. USB socket(s) on the PC? Try different ones. More power needed by the X56 (when I had an X55 set I found they needed not only a powered USB hub, but one with nearer 2Amp capability than 1! Finally, maybe it's the X56? Pete

FSUIPC doesn't have anything to do with scenery really. It doesn't care where you are and certainly not about jetways. I really do need the Windows crash data, from the Event Viewer. But first please install the current interim version 5.141e, so that any data in the crash data is clearly related to the current code. You can get it from the Download Links subforum above. Pete

Sorry, is this part related to FSUIPC at all? I cannot really resolve anything for you without more information.What are the "unusual assignment readings"? The term doesn't really make sense. And what exactly does "1-2 1x, 3-4 1z, 5-6 1u" mean? you have 6 throttles in pairs as axes x, z and u? The 1-2, 3-4, 5-6 needs explaining please. Pete

Well, there is most certainly a problem, either with your device or more likely with the Registry. You would probably need to edit the registry, but that's not a job for the beginner. Saitek drivers would not be a solution, they'd probably make it worse if anything. The alternative is a disk wipe and fresh install of Windows, then just reconnect the device without installing anything from Saitek. Pete

Well, it is definitely down to P3D then. The only change that makes is using the Simconnect text display call instead of the Simconnect message disaplay call. The same line in fact -- it's the same function call, just with the parameter to the call changed according to that INI file setting (the Menu request is also the same function but FSUIPC doesn't provide such an option). I'll report it to L-M. But as I can't reproduce it on either of two different systems, and yours is the only report, I suspect they won't be able to nail it. Pete

These all show everything good for both Stick and Throttle. I can't see anything wrong! The results look as good as any X-56 user's I've seen, and my own X-55 (when I had one here). Have you tried assigning in the Sim instead? Why are you assigning in FSUIPC in any case? Pete

Try FSUIPC5141f_TEST.zip, but first add NoMessageWindows=Yes to the [General] section of the INI. All this does is force the use of the simpler SimConnect text display instead of the Message Window. I don't know if that will make any difference, though. Let me know. If it makes no difference I'll take the option out. Pete

No, not unless QW are using FSUIPC and providing such. Many sophisticated add-on aircraft do their own thing and ignore the standard built-in controls of the Simulator. FSUIPC's offsets are concerned with the built-in systems. If QW don't provide keyboard shortcuts which you can assign, and no "custom controls", then you would need to investigate the use of either Mouse Macros or local panel variables (L:Vars). You can't "read controls". They are merely numbers which are sent as part of a message, like an order. The record of what they achieve may be readable but that's a different matter. 65859 is AP AIRSPEED HOLD (as you could have found out by referring to the supplied list of controls -- see your FSUIPC documents folder). Now FSUIPC does get the status of this from SimConnect and place the result in offset 07DC. So that should be seen as changing from 0 to 1, the that may not happen if the Sim doesn't see that the AutoThrottle is Armed. If it isn't then it's really a question for QW -- they presumably process this in their own systems code. PMDG provide an SDK detailing how to read all of their settings, and also a list of the "custom controls" they've added. They've fully catered for those wishing to program hardware. Have QW done similarly? Pete

Okay. The problem is that all FSUIPC does is call the SimConnect Text function to display the text. It has no control over the focus, nor can it flash the title bar. I really have no way of proceeding to help in this. Just logging the fact that I'm calling a SimConnect function won't help, and nothing else is actually involved. There are other programs which use the Simconnect Text function, of course, but I don't know of any others using the Simconnect Message Window. they either use the more basic SimConnect text (the one which defaults to the bar across the top of the Window), or the Menu. I could provide you with an option to only use the basic Text display, to see if that helps. I can't really think of anything else I can do. Pete

Good. So it looks like FSUIPC is not scanning for sound devices if it has a list already. I'll fix that in for the next release. Pete

Sorry, I'm lost. This is from over 4 months ago? Am I supposed to read the thread from the start? What is CTRL_F10? Where is it assigned? Where are you using it/ (I'm not going to start viewing YouTube videos without knowing why!). Isn't this a symptom which can only be a P3D4 action? Is the problem that P3D steals focus? Did you try updating to P3D4.3? Pete