Pete Dowson

Actually, there are no offsets for either ADF standby frequencies. I don't think they could have been supported in earlier versions of FS. Either that or no one was ever interested in the enough to ask. I'll add them soon, in another Interim update. I'll let you know in this thread. Maybe before the weekend. I find no way to WRITE them documented in the SimConnect SDKs though. For the main frequencies I use KEY_ADF_COMPLETE_SET and KEY_ADF2_COMPLETE_SET. How would you set the standby values? It looks like I'll just have to make them read only! Pete

Assuming you mean "FSUIPC4.LOG" (that's it's full name -- make sure you don't have names hidden from you by Windows Explorer), then it isn't loading. Also, it isn't an "addons list2, it is the menu item in P3D when ready to fly, the right-most one called "Add-Ons". What is listed there? Where exactly is the DLL.XML file you've been messing with? Is it in: C:\Users\Ajambeg\AppData\Roaming\Lockheed Martin\Prepar3D v3 That's the place it should be according to the Installer log. Also, I've just noticed something else drastically wrong in your system. Look at these extracts from the Install log: Looking in registry for FSX install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Parameter"SetupPath" ... >>> OK! FOUND FSX! <<< ... SetupPath=E:\Flight Simulator Looking in registry for FSX-SE install path: HKEY_LOCAL_MACHINE\SOFTWARE\DovetailGames\FSX Parameter"Install_Path" ... >>> OK! FOUND FSX-SE! <<< ... SetupPath=E:\Games from Steam\steamapps\common\FSX Looking in registry for Prepar3D v3 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v3 Parameter"SetupPath" ... >>> OK! FOUND Prepar3D v3! <<< ... SetupPath=E:\Flight Simulator\ According to the Registry you have both FSX and P3Dv3 installed in the same place! And FSUIPC4 is installed for both of them! Further: INSTALLATION FOR FSX: SetupPath="E:\Flight Simulator\" Checking version of the FSX EXE: ... Version 10.0.61637.0 (Need at least 10.0.60905.0) and INSTALLATION FOR Prepar3D v3: SetupPath="E:\Flight Simulator\" Checking version of the Prepar3D v3 EXE: ... Version 3.2.3.16769 (Need at least 1.0.677.0) You have both P3D and FSX EXE's there too! What a mess! How did you end up with this? Did you just install P3D over FSX? Didn't you bother to uninstall one first, or at least choose somewhere else? I would guess that things are so screwed up that not much will work! :sad: Pete

Just fired up P3Dv3.2 as well -- it's perfect there too. Either A2A have somehow managed to really screw things up, or you are making a mistakes somewhere in your checks. Try the monitoring as I suggested. Pete

Okay. I can confirm that P3Dv2.5 has those variables working exactly as in FSX. Please use the FSUIPC Monitor facilities -- logging tab, right-hand side. Enter 07D4 as type U32 and 07F2 as type S16, then check "normal log" at the bottom. FSUIPC will log changes to those along with the value of the actual SimVar read. Compare those to the values displayed in the MCP. The SimVar altitude is in metres and the V/S in feet. Pete

Well, let's see: 1.Reinstall fsuipc. All that does is replace like for like. 2.removed the fsuipc.dll and removed the line in the dll.xml file and reinstalled. That's the same except risks messing up the DLL.XML file 3.i renamed the dll.xml file and then installed fsuipc. That will create a DLL.XML file loading only FSUIPC. 4.i reinstalled simconnected. FSUIPC for P3D doesn't use an installed Simconnect, only the DLL in the Modules folder. 5. i created a new dll.xml with only fsuipc. Step 3 already did that. When you say "FSUIPC stopped working", what do you actually mean? What is the symprom of it "not working"? Is it loading? Is there an FSUIPC Menu entry in Add-Ons? Is a log produced? You need to be more descriptive or the problem, more so that what you did or didn't do to try to "fix" it. If an new FSUIPC4.LOG file is produced when you run P3D, that's what I need to see. If it isn't then FSUIPC isn't being loaded. Pete

Yes, but those are described in exactly the same way in the FSX SimConnect SDK. But when the data is requested you can specify the units, thus: HRESULT SimConnect_AddToDataDefinition( HANDLE hSimConnect, SIMCONNECT_DATA_DEFINITION_ID DefineID, const char* DatumName, const char* UnitsName, SIMCONNECT_DATATYPE DatumType = SIMCONNECT_DATATYPE_FLOAT64, float fEpsilon = 0, DWORD DatumID = SIMCONNECT_UNUSED ); It also says (my highlighting): "UnitsName [in] Specifies the units of the variable. See the Simulation Variables document for a table of acceptable unit names. It is possible to specify different units to receive the data in, from those specified in the Simulation Variables document. See DEFINITION_2 below for an example. The alternative units must come under the same heading (such as Angular Velocity, or Volume, as specified in the Units of Measurement section of the Simulation Variables document). For strings and structures enter "NULL" for this parameter. " FSUIPC uses that flexibility to request them in the units which are immediately more compatible with the offsets and the same as FS9 and before. I really don't think P3D is different to FSX in this regard -- there are many folks using instrumentation from the likes of ProSim, Project Magenta and so on which use these offsets for reading and writing these A/P values. Are you not sure it isn't just A2A who've got things wrong? Your first message says A2A in both FSX and P3D. Your last paragraph in that message was contradictory which is why I asked for clarification there. I have P3Dv2 installed on this PC, I'll go check now. I do have P3D v3 too, but on my cockpit system only which isn't powered up at present. Pete

Both things can be done with Lua plug-ins, which you can then assign to your buttons. They are dealt with in the ext library (ext for "external"). For sending a keypress to a program external to FS use the ext.sendkeys function. For starting a batch file use the ext.shell function. Pete

Use WideFS to get FSUIPC offsets readable over a Network. Pete

I don't know what A2A have done, but the units for these things are stated to SimConnect in the request made by FSUIPC. FSUIPC wants those units for compatibility with earlier non-SimConnect versions of FS. It seems A2A use the units FSX things of as metres or ft/min as feet or metres/min. Very strange! Have you asked them about that? This statement confuses me and seems to contradict when you said just before. Can you clarify it please? Pete

Yes.

It isn't related to the conditions at all. If a button is programmed for use in the overriding Profile assignments then any programming for the same button is ignored in the generic assignments. To not do so would tend to cause more confusion that less in my opinion. What is stopping your generic RED assignments working in the Profile is the assignment of Y34 and Y38 in that Profile. The conditions aren't relevant to this. Pete

FSUIPC does NOT change assignments once set. If the two quadrants are identical in all respects it may be that Windows sees them in a different order each time you boot up, and assigns its IDs in that order. But that would certainly not happen if you mean just restarting P3D. AutoAssignLetters=Yes will not re-assign previously known and assigned joysticks, it only allows FSUIPC to cope with newly connected ones. Without seeing your INI file and LOG files I can't really assist much further. Feel free to paste them here. Pete

There's virtually no information provided here so I can't help directly. You need to explain what you mean by "not working". If you mean they aren't being loaded, then it will certainly be that your DLL.XML file is messed up. XML is a very intolerant format. Paste the file here if you want it checked. Pete

In FS the engines only shut down when the fuel it cut. So you'd need to assign a Fuel Cut control to the point on your throttle axis where you cant this to happen. You can do that on the right-hand side of FSUIPC's assignments tab. There are many ways of dealing with trim. If the hat is only being seen as two buttons, "up" and "down" then using Elev Trim Up and Down controls you should be able to get single increments of about 256 (which is 1/64th of the range). Surely 64 increments between level and full should be enough? Beware of repeats though. If FS sees two such controls close together it does often add accelerated changes -- like double tapping the relevant keys on the keyboard. It don't know how your military aircraft are stated, but usually you need some way of spinning them and then introducing fuel. If you know what controls you use to do that then, again, you can assign them to the throttle on the right-hand side of the assignments tab. Note that you can make different assignments there for increasing values to the decreasing ones you'd use to stop the engines. Pete

FSUIPc merely sends that control number to FS. It cannot change what it does. And the list of control names is generated from the list in FS's "CONTROLS.DLL". So it would seem you have found an original FSX bug -- possibly FS9 and before too? Too late to get Microsoft to fix it, but maybe you should report it to DoveTail Games for FSX-SE and to Lockheed-Martin for P3D? Pete

I don't know how their could be any connection to sound (unless you have sound driver problems), but it may be that all these things are symptoms of the same problem. It sounds like one of overloading, or as alaxus said, memory getting tight. It's odd that there's nothing logged by FSUIPC when the menu entry disappears -- that's always a sign that things are overloaded to such an extent that SimConnect data isn't reaching FSUIPC in an acceptable time. FSUIPC disconnects and reconnects to try to fix this and that action should be getting logged. You can extend that time limit using an INI file option (see the Advanced User's Guide), but in general that's a bad solution which doesn't help in the long run. If you are using a complex add-on aircraft and using AutoSaves then try switching AutoSave off -- aircraft like the PMDG 737 and 777 do freeze the sim for a while whilst collecting their data for saving. Pete

FSUIPC does not control weather. If you want weather controlled by FS or AS just leave all FSUIPC weather settings defaulted. They only act as filters, not controls. Pete

You need ADE support. Pete

The problem is one of timing. It sometimes works for me, but it is inconsistent. The time between SimConnect notifying FSUIPC of a shutdown and the shutdown actually occurring varies and is sometimes insufficient. The only reliable way to do what you want is to tell FSUIPC to initiate the shutdown (as you have described from a Client). You can do it from the Server too, using the shutdown hotkey in WideServer. I use "Ctrl+Shift+E" so my parameter in the [WideServer] section of FSUIPC4.INI is: ShutdownHotkey=69,11 Pete

The list of FS controls supplied with FSUIPC is related to standard built-in FS controls. If some add-on maker decides to ignore those and use some other method, you need to find out what that method is. Maybe they allow keypresses to be assigned for them, or maybe they are accessible through some other way? For example, it they are real "custom controls", with new non-FS control numbers assigned, you can assign these in FSUIPC using "<custom control>" and entering the control number. If they are gauge internal "Local Variables" ("L:Vars") then you can write to them using FSUIPC macros, as explained in the Advanced User's guide. There is an assignable FSUIPC control you can use to list L:Vars with correct values, and there is a Lua plug-in supplied which will display them in real time as they change. Pete

You need VRI support, it is their software. Pete

Test OFF the ground. When you increment the "Arm" setting is engaged, and FS mistakenly then engages full spoilers if you are already "landed". Pete

Just caught me -- last message before I'm off till April 12th. First try the latest interim version, 4.949k, available in the Download Links subforum. That fixes one potentially serious bug with FSUIPC on P3D3.2. If that doesn't help then I think you need to make sure ASN is up to date -- get the latest P3D beta, and in any case re-run the ASN installer. Otherwise it will be an P3D mis-install and you could try re-installing the Client or running a repair. Pete

Yes, that's new in FSX. It's the SimConnect "FLAPS HANDLE INDEX" variable which unusually is both read and write enabled. (Most are read only, writes being rejected). FSUIPC just sends it directly when you change it. Pete

Yes, I've explained what is going on in my reply to you in the main forum. Your solution is the same one I proposed, but I can probably also improve FSUIPC in this area as I also said. Not sure yet though. Pete