Pete Dowson

I've spent some time doing thorough tests here on two separate systems, one with only P3D4 installed, and the other with both P3D4 and P3D5.. ASP4 build 7459 works perfectly with P3Dv5 HF1. ASP4 build 7459 does not work properly with P34Dv4, version 4.5.13. The problem appears to be that the flag provided by the ASP4 internal interface to show whether ASP4 is connected or not remains FALSE (ie untrue). This means FSUIPC doesn not request the Call Back which provides the radar data. I have conclusively proven this by tracing through the code in FSUIPC6 in identical ways in P3D4 and in P3D5. The path is in fact identical in both cases with the small difference that the name of the Module to be used for P3D4 is as_connect_64.dll whereas for P3D5 it is as_connect_v5.dll. That is determined properly and set is proven by the fact that all of the functions it provides are then available to FSUIPC. I am therefore convinced it is a bug introduced during Active Sky's developments for P3Dv5. I have accordingly written to my contacts in HiFi with my full analysis. i will advise as soon as i receive a response. I had thought of possibly going ahead with asking for the data even if the indication is that ASP4 is not connected. Possibly the wrong indication is merely an oversight and in fact the data is all still available. I might experiment with that tomorrow. What would worry me is what might happen if, in fact, ASP4 was genuinely not connected. Pete

And was it the same build with FSUIPC5? I think I need to update my P3D4 ActiveSky installation. The ActiveSky program is common to P3D4 and P3D5 but the crucial part for this, the installed DLL in P3D, is different. Pete

There's no difference in the way this works in FSUIPC6 from FSUIPC5, except that it also accepts a link from the P3D5 version of Active Sky's installed DLL module. With P3D4 it is still the same. Which version of Active Sky are you currently using? FSUIPC merely contacts the Active Sky module asking to be sent the binary weather data which FSUIPC then just unceremoniously dumps into the nominated file. Of course there's been a lot of concentration on P3D5 recently, rather neglecting P3D4 re-testing perhaps, so I will make a point of checking it on P3D4 this weekend. Pete

Somehow your re-install hasn't worked. Perhaps you didn't thoroughly uninstall beforehand? You say, confusingly, that you "reinstalled FSX SP"" but "with RTM downloaded". What do you mean by that latter comment? The Installer looked for, but didn't find, any of the SimConnect versions which are normally installed when you install SP2: C:\WINDOWS\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dll"Found SimConnect build 10.0.60905.0 Looking for SimConnect.dll with "C:\WINDOWS\WinSxS\Fusion\*SimConnect*" Looking for SimConnect.dll with "C:\WINDOWS\WinSxS\*SimConnect*10.0.62607.0*" Looking for SimConnect.dll with "C:\WINDOWS\WinSxS\Fusion\*SimConnect*" Looking for SimConnect.dll with "C:\WINDOWS\WinSxS\*SimConnect*10.0.61242.0*" Looking for SimConnect.dll with "C:\WINDOWS\WinSxS\Fusion\*SimConnect*" Looking for SimConnect.dll with "C:\WINDOWS\WinSxS\*SimConnect*10.0.61259.0*" None of those are found except for the RTM one, 60905. But your FSX version (SP2) is 61242 and that correct copy of SimConnect is not installed. FSUIPC tries to connect with the reduced facility original version, 60905, but that is saying it cannot work with FSX: 250 Failed on SimConnect_Open, return = 0x80004005: FSUIPC4 cannot operate! Just as an experiment please try an older version of FSUIPC. I attach 4.971. Let me know, with logs again please. You'll need to delete the FSUIPC4.DLL file from the Modules folder as the Installer refuses to replace a later version. If that works then I have a puzzle to solve. But if that is also the same then the only thing I can think of which is making all this go wrong is that the Windows side-by-side (WinSxS) system is corrupted. I This would in turn imply that Windows Registry is in a mess. (It's a really horrible system which we avoided in P3D altogether). So, the choice then would appear to be really a clean start with a re-installed Windows (best bet), or, if you have one, a Restore to an earlier working time. You could consider a change to FSX-SE (the latest edition on Steam has a Beta release by Microsoft as well), or even upgrade to P3D. Pete Install_FSUIPC4971.zip

So, are you saying it is all the yoke buttons and all the attached quad buttons not working? You get no response in Bttons 7 Switched optionsi FSUIPC when they are pressed? But the Yoke axes and Quadrant levers do show in the Axis Assignments options tab? Sorry to press on with this, but your reports have been very muddled. As further clarification, are those buttons seen in FSX? Are they even seen in Windows? The point is that DirectInput, used by FSUIPC, supplies all buttons and axes at the same time. There's no way FSUIPC can read one set of values and not the other, they are all one. BTW, I've looked at your recent (still out of date FSUIPC) settings and it seems there's only one quadrant seen as connected there. However, the Log would show a lot more about connections, but your version of FSUIPC is far too old. Most of the information and analysis we do nowadays is missing. That''s probably why you can't find the JoyScan csv file now poduced. Pete

So your problem is actually with specific conditional programming issues? Not this as you said before: All your buttons are seen and respond but you have somethnig you don't understand in some conditionals? Is that right? I really don't see any point in me looking at any of your data until you make it clear what your problem really is. I see that even this log is over 2000 lines. What am I supposed to look at? What is is you think is wrong? Yes, do the update. No, don't 'start again'. just do a short session where you demonstrate exactly what you want help with. Just cut the relevant part out of the log if that makes it clearer -- you can paste it into a message (best to use the <> brackets above for that). Pete

You only attached a log file, not INI file so i can't check your settings. Looking at that: 1. I see you are using a very old long-unsupported version of FSUIPC (4.939k). Please update so you can get proper support! 2. The log is very long (over 5,000 lines), and from sampling it I see lots of Button responses, all resulting in controls being sent, so it shows nothing wrong that I can see. If you have only some things not working, not all of them, then you need to narrow it down, At least say which joystick buttons. All of those I sampled in the Log which were shown to be working were on Repeated button C 7 which was continually sending "THROTTLE4 DECR SMALL". So I really have no idea what you were doing other that that. Maybe that button is stuck? If so it could make it difficult to do much else. Best to change it to not repeating. Pete

I've never made one, but I'm sure it must be possible with ScruffyDucks' ADE (Airport Design Editor). If all you want to do is remove or close runways and you know which BGL file they are defined in, then I believe it is pretty easy. But I am not the one to teach scenery design work. Have a look at ADE. i think much of it is self explanatory and there's good help I think. Pete

Considering that the value at 0B4C is only 16 bits long (2 bytes), its value cannot possibly be more than 65535, when treated as a positive short integer. This multiplied by 3.28084 therefore cannot be greater than 215,010. In fact, however, of course it is a signed value so it ranges from -32768 to +32768, giving a maximum altitude possible to read of 107,503 feet. I suspect you are reading it as a 32-bit (4-byte) value and are therefore also including some unspecified 16 bits beyond. If you want a 32-bit value and more accuracy use offset 0020 as it suggests in the offsets list. Pete

The log shows that you have a corrupted or missing install of SimConnect. This could mean you need to reinstall FSX, but to try to avoid that could you find the SimConnect installers ("SimConnect.msi") and run those. There will be two or three -- for the RTM version of FSX, the SP1 update, and the SP2 update. Best to run all three. You should have them in the FSX installation somewhere as they are provided in case you need to run a SimConnect program via a Network. I don't remember the exact location I'm afraid as my last FSX installation was cleaned out long ago. With FSX-SE (a far superior version and well worth your time installing to repalce FSX) you wpuld find them in: <FSX folder>\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces\FSX-RTM and similar but FSX-SP1 and FSX-XPACK, for all three versions applicable to FSX. Pete

You need to retrieve them from your SimMarket account (As far as I know this applies to all simMarket purchases -- it does for me, anyway). BTW you should rreally entitle your posts here by something to do with the subject, not your name! Pete

FSInterrogate has always worked fine. Maybe more details would help the author who donated it long ago, but he's probably long forgotten it. I use it a lot. it is very useful indeed. Pete

That's the same successful Install file you sent before. It's the FSUIPC5.LOG file you need to show. It is called FSUIPC5.LOG Pete

The log file shows a normal termination. FSX didn't crash but terminated gracefully. You need to explain exactly what happened, what you saw. I suspect your PC crash has caused some corruption somewhere which is preventing FSX working properly -- at least in the SimConnect interface if not also other places. I would strongly recommend a reinstall of FSX. Pete

The version of P3D isn't relevant. You just want to stop FSUIPC running for some reason? But what version of FSUIPC do you have? FSUIPC5 or FSUIPC6? For FSUIPC5 every file concerning it, is in your P3D Modules folder. the User Guide will be there in the FSUIPC documents folder. For FSUIPC6 you can uninstall via the normal Windows Programs & Features or App settings uninstall method, in Windows Settings. The FSUIPC6 user guide is in your Documents folder, in the folder called "FSUIPC6". Can you say why you want to uninstall it? Pete

The Install log is irrelevant. If FSUIPC is in the AddOns menu. There MUST be an FSUIPC5.LOG file. You probably have Windows Explorer set to hide well known file extensions from you, like ".LOG" which will be seen as a text document or whatever it has been associated with on your PC. Please take a look at the Installation guide, or the User Guide. In the former the section at the end (all the way to page 5) entitled IDENTIFYING FILES IN WINDOWS EXPLORER will tell you how to change the Explorer option so you can really see what files are. In the user guide the section Finding and Editing files relating to FSUIPC and WideFS on page 6 tells you more. Pete

You should have said that first. Assuming you mean "FSUIPC5.LOG" rather than "FSUIPC4.LOG", it will certainly be the reason! FSUIPC cannot provide any information if it isn't running. The quicker way to see if it is installed and running is to look in P3D's menu -- there must be an FSUIPC entry in the AddOns menu. So, either you haven't actually installed FSUIPC5 yet, or something went wrong. You'd need to try again. If still no luck then you need to show us the Install Log (which will be found in the same folder as the Installer). Pete

Sorry, if they are both at the same privilege level then the problem must lie in AICompanion. I cannot debug their code -- the error message is from their program not from FSUIPC itself. If the author needs help debugging his interface to FSUIPC then he should contact us himself so we can discuss what he's doing and find out what is wrong. Maybe it is something as simple as a version check. Pete

You probably have P3D and AICompanion running at different privilege levels. If one is running "as administrator" so must the other. FSUIPC data exchange works via shared memory ("memory mapped files") and that can't be done between to privilege levels. Pete

MOVED FROM USER CONTRIBUTIONS SUBFORUM! You posted in a SubForum clearly labelled, in red, "not for support requests". Please always use the Support Forum. I moved it for you so it can receive attention. If your scenery marks then as not in use (closed for takeoff and landing), then the reference in MakeRunways' generated data will show this -- see the format definitions in the documentation. If they no longer exist, but are present in the default airport data, then they need excluding in an add-on scenery file. Then MakeRunways will no longer list them. MakeRunways doesn't actually "make runways", it "makes runway data files". It can't change anything. For that you need something like ScruffyDuck's Airport Design Editor" (ADE). Pete

Are you by any chance trying to run it from the opened ZIP package? That won't work. You need to unpack the files to a folder on your system, even if you wish, to the desktop, then read the Installation guide provided before running the Installer "as administrator" (a right-clcik menu option). Pete

Sorry. but you misunderstood! I meant to assign your CTRL-B directly to the control "G1000 PFD Softkey 1", so that we know that that is being semt once and once only. Of course the other way to check that would be to simply enable logging of non-axis Events. BTW "ipc.control(66761,1)" is a call to a Lua library called "ipc", and it can't possibly have any effect outside of a Lua program. The Lua interpreter in FSUIPC only operates for loaded Lua plug-ins, so I really don't know what you thought you tested there! Anyway, I see you might have other reasons for what you see occurring and may now realise it is nothing really to do with Lua or FSUIPC. Pete

On my list, control 66762 is G1000 PFD Softkey 2. The Softkey 1 control is 66761. But assuming that was an error in your question, all that FSUIPC will do is send that control on to FSX. Have you tested in a more simple way -- assign to a keypress or button in FSUIPC, or perhaps, more directly, assign in FSX. Just as a test? One more question. I don't know Linda very well, but does it use the same method, via Lua? Pete

In that case it's a bug in the add-on aircraft code. I would ask in their support forum. As I said, FSUIPC doesn't manipulate these offset values apart from the cnversion, and you can see if that is correct quite easily using the logging. Pete

As with most of the offsets populated by FSUIPC, 07CC is merely a result of SimConnect supplying a value, in this case the SimVar called "AUTOPILOT HEADING LOCK DIR". If you add 07CC to the Monitor facility on the right-hand side of the Logging tab in FSUIPC Options, and check 'normal log' below, then the FSUIPC log will show that incoming SimVar in its original form. (Use the Console log option to see it in real time). It sounds like that aircraft is very slow updating the actual Sim's AP Heading value, or is updating it incorrectly or maybe not at all. Such sophisticated add-ons tend to implement their own Autopilot so are not dependent on the operation of the Sim one -- you may even find that the AP Master switch in the Sim (offset 07BC) is always off (zero). If not it may only be in use for part of its facilities. Yes, L:Vars are internal to the add-ons own gauges and are implemented as their form of "SimVars" when the operations are independent of the Sim's subsystems. If you are concerned, check offset 07CC with a default aircraft, or at least one which doesn't take over or replace the built in autopilot. I use a full cockpit software implementation external to the sim itself (ProSim737). All of the display values are then under its control, the subsystems in the sim itself not being involved. Pete