Jump to content
The simFlight Network Forums

Pete Dowson

Moderators
 View Profile  See their activity

  • Posts

    38,265

  • Joined

  • Days Won

    170

 Content Type 

Everything posted by Pete Dowson

  1. Pete Dowson
    I've just released FSUIPC 4.949n. This contains support for reading (only) the ADF standby frequencies. Details are in the accompanying "Changes" PDF, but here they are too: 72. Additional offsets are now provided for the ADF standby frequencies, as follows: 0284 2 bytes ADF1 Standby Frequency: main 3 digits, in Binary Coded Decimal. A frequency of 1234.5 will have 0x0234 here and 0x0105 in offset 0286. 0286 2 bytes Extended ADF1 standby frequency. The high byte contains the 1000’s digit and the low byte the fraction, so, for a frequency of 1234.5 this offset will contain 0x0105. 0288 2 bytes ADF2 Standby Frequency: main 3 digits, in Binary Coded Decimal. A frequency of 1234.5 will have 0x0234 here and 0x0105 in offset 028A. 028A 2 bytes Extended ADF2 standby frequency. The high byte contains the 1000’s digit and the low byte the fraction, so, for a frequency of 1234.5 this offset will contain 0x0105. Note that there appears to be no way to actually write to the standby frequencies, so writing these offsets will do nothing except mess up the last value read. If this can be fixed at some time, it will be. Additionally the ADF2 radio swap control appears to be broken – it swaps the ADF1 frequencies instead of ADF2. This applies to FSX, FSX-SE and P3D at least up to version 3.2. Pete
  2. Pete Dowson
    But if both are renamed, ond only FSUIPC4 is listed, with no EXE's, how are all those other external DLLs and EXE's being listed in the SimConnect log file? There's still something fishy here. 0.03115 DLL Loaded: Path="radar.dll" Version="3.0.0.0" 3.04454 DLL Loaded: Path="Oculus.dll" Version="3.0.0.0" 3.04582 DLL Loaded: Path="ControllableCamera.dll" Version="<Unknown>" 3.04651 File not found: Path="C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\SODE\SimObjectDisplayEngine.exe" 3.04697 File not found: Path="C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Aerosoft\AirportController\APController.exe" 3.04768 File not found: Path="Captain_Sim\727\cs.sound.dll" 3.04815 File not found: Path="Captain_Sim\727\Captain_Sim.p727.menu.dll" 3.04859 File not found: Path="C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Sode\SimObjectAnimationModule.dll" 3.21380 DLL Loaded: Path="Modules\FSUIPC4.dll" Version="4.9.4.9" The FSUIPC entry is now good, and the FSUIPC4.LOG shows it is running fine. And the ONLY things now not loading which were loading before are: 4.04911 Exe Launched: Path="fsdreamteam\couatl\couatl.exe" CommandLine="" Version="3.0.0.3187" 4.06729 Exe Launched: Path="C:\Program Files (x86)\EZCA\EZCA.exe" CommandLine="" Version="1.1.8.7" 4.06900 Exe Launched: Path="C:\Program Files (x86)\SPAD\Spad.exe" CommandLine="" Version="0.5.0.0" So all you want is an EXE.XML with those three in it. Or, maybe better, run them using FSUIPC's "[Programs]" facility instead. Note that you don't have BGLMANX.DLL loading so COUATL.EXE is pretty useless in any case I think. Are you trying to use GSX? That needs BGLMANX for sure. At least you have FSUIPC now. I'm afraid I can't really help with the other things. You'll need to work out how those other DLLs are being referenced as well as the two EXE's it can't find -- somewhere you have another set of DLL.XML and EXE.XML files. Look in the ProgramData folder, where the Scenery.CFG file is. Pete
  3. Pete Dowson
    Okay. I've added offsets to read both ADF2 active and standby frequencies, but there's no way to change the standby ADF2 value. The aircraft you are using has a workaround to do the swap. That doesn't apply in general. The ADF2 complete set control only sets the active and you can't swap because the swap control doesn't work. I've tried all sorts of fiddles to make it work, but unless you have an add-on which has been coded to do it some other way, as you have, then the ADF2 standby is a wasted resource. I've reported it to L-M and can only hope they fix the Rado Swap control, at least. There are vacant slots in the controls table, so maybe some of those might do the ADF1 and 2 standby complete sets,, but I doubt it. I haven't the time or patience to try them all, just in case! If you think it might be useful I can let you have the version of FSUIPC4 with the new offsets, but otherwise it will simply be part of the next release, whenever. Pete
  4. Pete Dowson
    But what about all the DLLs which are loading but which are not listed in your DLL.XML? I really needed to see a log consistent with your earlier information, not one relating to completely different files. Try renaming both EXE.XML and DLL.XML, so nothing else will load, THEN re-run the FSUIPC4 Installer, test again, and show me just the early parts of the SimConnect log. I am only suggesting that since things seem to be in such a complete mess! How else to simplify matters so we can both understand what is going on? (But it need not be a separate DRIVE, just a new folder, like "E:\P3D"). Pete
  5. Pete Dowson
    See the stuff in the FSUIPC Documents subfolder. in your FS Modules folder. Did you not even read the Installation document packaged with the FSUIPC installer which tells you what is installed and where? Pete
  6. Pete Dowson
    And why were you not seeing text documents? It is NOT "FSUIPC.LOG" but "FSUIPC4.LOG". I only needed the first section, where it is loading stuff in any case. Look: 0.03235 DLL Loaded: Path="radar.dll" Version="3.0.0.0" 4.04425 DLL Loaded: Path="Oculus.dll" Version="3.0.0.0" 4.04546 Panels data export found and set to 559FF2F8 4.04547 DLL Loaded: Path="ControllableCamera.dll" Version="<Unknown>" 4.04618 File not found: Path="C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\SODE\SimObjectDisplayEngine.exe" 4.04663 File not found: Path="C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Aerosoft\AirportController\APController.exe" 4.04911 Exe Launched: Path="fsdreamteam\couatl\couatl.exe" CommandLine="" Version="3.0.0.3187" 4.06729 Exe Launched: Path="C:\Program Files (x86)\EZCA\EZCA.exe" CommandLine="" Version="1.1.8.7" 4.06900 Exe Launched: Path="C:\Program Files (x86)\SPAD\Spad.exe" CommandLine="" Version="0.5.0.0" 4.06980 File not found: Path="Captain_Sim\727\cs.sound.dll" 4.07044 File not found: Path="Captain_Sim\727\Captain_Sim.p727.menu.dll" 4.07093 File not found: Path="C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Sode\SimObjectAnimationModule.dll" 4.07200 DLL Load Failed: Error=-1 Path="Modules\FSUIPC4.dll" I see it is successfully loading "radar.dll" and "Oculus.dll", and it fails to load "cs.sound.dll" "Captain_Sim.p727.menu.dll" and "SimObjectAnimationModule.dll" because it can't find them. Now NONE of those are listed in the DLL.XML file you posted earlier! Also How can that be? And none of the ones you do list are loaded at all. I am thinking you are looking in the wrong place for these things. Also, I only just noticed, but the DLL.XML you did show has this entry: <Launch.Addon> <Name>SPAD</Name> <Disabled>False</Disabled> <Path>C:\Program Files (x86)\SPAD\Spad.exe</Path> </Launch.Addon> which is for an EXE file! That should not be there! It belongs in the EXE.XML file! And you have many entries in the EXE.XML, two of which are bad -- SimObjectDisplayEngine, and APController! You have Couatl.exe loading but the BGLManx.DLL it depends on is not being loaded. So all in all, nothing corresponds with what you posted before and it looks to be in a mess. The attempt of SimConnect to load FSUIPC4 is logged, but with Error -1. I've no idea what error -1 means. I've never seen one before. All the documented SimConnect errors are positive numbers. I think you have somehow got your P3D installation into a real mess. I can only suggest you start again, uninstall it and try reinstalling it some place differently, to avoid the mess with FSX. And edit the Registry to remove the FSX installation pointers. Pete
  7. Pete Dowson
    Interesting, but I'm not sure how useful it is. L:Vars are specific to the gauges which are part of the add-on aircraft. It looks like they've implemented parts of the ADF2 logic using L:Vars, probably because of the lack of proper support in FS. In other words, it's a work-around. No. That is bound to be the actual frequency in Hz in BCD format. Values not in the correct range for ADFs will just be ignored. I would experiment here, but there is no default aircraft with two ADFs both with standby's as far as I know. I'll see what else I can do. Maybe reading the standby frequency, then using ADF2 Complete Set with the value can solve the lack of a swap control, and reading the active, using Complete Set with the new standby value, THEN using it again with the saved active will do the job of ADF2 standby complete set. First I shall get the standby frequencies into offsets, then perhaps you could try that logic there, since you have such an aircraft? Pete
  8. Pete Dowson
    FSUIPC makes no distinction about the source of the button press. So could this be a question for Spad? Have you tried Button logging in FSUIPC to see what the difference is, apart from the button numbers? Pete
  9. Pete Dowson
    Sorry, I've no idea. How would it get it on the FS PC? I thought you implied it would work there? If it did and it uses FSUIPC, then WideFs would solve it on a client PC -- there's nothing to it other than paying for it and installing it, so what's "not simple"? What would Teamspeak do with this frequency when it has it? I didn't think it had anything to do with FS, but then I've never used it. If it doesn't use FSUIPC then you are in the wrong Forum. Maybe this explains your confusion? Pete
  10. Pete Dowson
    Sorry, i cannot really support add-on aircraft. Many do their own thing. You need their support. Pete
  11. Pete Dowson
    I know how to use the ADF2_COMPLETE_SET control. They are simple decimal Hz. decimal That's no problem. But what does the swapping? Are you clicking a button on screen? Is the value in the control the one which was in the STBY frequency display or the current one? Pete
  12. Pete Dowson
    No no! I mean the FSUIPC4.LOG file -- the LOG which FSUIPC always makes anew when FS is started! You said you hadn't deleted it, so it is still there from when things were okay! Please check again! That is fine. So there MUST be a log in the Modules folder called "SimConnect01.log" (or similar). I'm beginning to think the files I need to see are there but you are simply not seeing them. You are either looking in the wrong place or you are not recognising them. Check that you are allowing Windows Explorer to show the proper names -- select the "Organize" menu in Explorer, then Folder Options. -- View, and ensure the option named "Hide extensions for known file types" is NOT checked. Then look again. I'm to bed now. Tomorrow is another day ... Pete
  13. Pete Dowson
    There have only ever been TWO purchasable FSUIPCs -- FSUIPC3 and FSUIPC4. Once you purchase either one then all versions are freely updated as you wish and as expected of you. Same with WideFS -- only WideFS 6 and Wide FS7. All previous versions of both were free. First off, WHY do you want to use range assignments? Also what is so obscure about them? You simply move the lever, make the assignments and so on, for up to 10 separate areas and if needed differently for up and down. It is all included in the FSUIPC User guide. did you read that? Anyway, for flaps there are already calibration facilities for all steps of your flap lever, provided you first choose the aircraft withn the number of detents you need. And spoiler calibration sets both the Armed and Flight detents, which is all any aircraft has. I think you are expecting something in the Assignments which is really all to do with Calibration! You are, maybe, just looking in the wrong place? Calibration can apply to FS assignments, which is why it is separate from assignment. Pete
  14. Pete Dowson
    So it is still there, with the old date? Simconnect MUST create a log if instructed correctly! Please show me the SimConnect.INI file you made and tell me where you placed it! Pete
  15. Pete Dowson
    Please enable Event logging in FSUIPC and try that so we can see if any standard events are used. Pete
  16. Pete Dowson
    Hmmm. I need to see a SimConnect log please. See the FAQ subforum here for details of how to make one. BTW did you delete the last log from when things were "okay"? Pete
  17. Pete Dowson
    How were you using the standby ADF frequencies in any case? Pete
  18. Pete Dowson
    Well there's an entry in the Registry saying that FSX is there too, and the FSUIPC installer is installing itself there too. It's just lucky that the Installer installs for P3D after FSX! So what did that do which could possibly stop FSUIPC4 even being loaded? Makes no sense at all. Are you sure that FSUIPC4 is not being loaded when you rename the DLL.XML and rerun the FSUIPC installer to get a DLL.XML which only loads FSUIPC? Try that again and check the add-ons menu and look for an FSUIPC4.LOG again. (You must have a log there already from when "everything was okay", by the way). Pete
  19. 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
  20. Pete Dowson
    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
  21. Pete Dowson
    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
  22. Pete Dowson
    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
  23. Pete Dowson
    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
  24. Pete Dowson
    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
  25. Pete Dowson
    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
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.