Jump to content
The simFlight Network Forums

Pete Dowson

Moderators
  • Posts

    37,991
  • Joined

  • Last visited

  • Days Won

    158

Everything posted by Pete Dowson

  1. So where FSUIPC's install log says: Looking for SimConnect.dll with "C:\Windows\WinSxS\*SimConnect*10.0.62615.0*" Found the path, now trying "C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_1ed9da73c880e429_10.0.62615.0_none_69960aa860d87067\SimConnect.dll" No SimConnect.dll found there are you saying you looked in that folder and found SimConnect.dll there, even though the installer cannot see it? The 62615 version is the correct DLL to work with your FSX-SE which is also 62615. I can only think that you forgot to run the FSUIPC installer "as administrator", and in consequence it is being denied access. One other thing you can try is to copy that specific DLL into the FSX.EXE folder: C:\Program Files (x86)\Steam\steamapps\common\FSX Pete
  2. I don't know whether GoFlight have (yet) updated their software for MSFS -- possibly the FSX version they made will work with some MSFS aircraft, assuming the latter obey the original FSX controls (which many don't, unfortunately). But GFEFIS is one of the devices supported by FSUIPC and it's Lua plug-in facilities. You need GFDev64.dll in the same folder as FSUIPC7.EXE. Then you can program the buttons and switches as needed for your specific aircraft. It isn't pre-programmed for you. Pete
  3. Yes, it will be to do with needed quotes. For Windows error numbers, like 267, refer to: https://docs.microsoft.com/en-us/windows/win32/debug/system-error-codes--0-499- where you'll see, as Reinhard said: ERROR_DIRECTORY 267 (0x10B) The directory name is invalid.
  4. The "course" display/dial is the "Omnidirectional Bearing Selector". Look for OBS controls in the list. Pete
  5. I'd just like to make two points after looking at the files: 1. You only have the two throttles assigned in FSUIPC, but you've assigned to THROTTLEn_SET. Those are the controls which have the lower part of the lever movement operating reverse thrust. If you are using an aircraft which doesn't accept this then you would either see nothing in the aircraft, or only on the part of the lever movement set for forward thrust. Best to assign to AXIS_THROTTLE controls, and check "no reverse zone" in the calibration tab. 2. You have the controllers active in P3D. You need to decide whether to use FSUIPC for assignments or P3D. If using FSUIPC then disable the controllers in P3D, otherwise you'll get conflicts. Pete
  6. The controls list is generated from information supplied by P3D itself. It is not concocted by FSUIPC. If there is no suitable control listed there are two possibilities: either A2A has not provided any control to operate that switch (more like a button by the sound of it), or they have done it by re-using an otherwise unused or "custom" control. If the former case is true then there are two conceivable ways of programming it: using a mouse macro, or seeing if there's an L:Var which does the job. Mouse macros are described in the FSUIPC user manual. To find LVars you can use the supplied Lua plug-in to log Lvars. Run that plug-in my assigning it to a keypress, then operate the button and see if an LVar value changes. The log you supplied shows nothing apart from the start of the session, so it isn't clear why you supplied it. To find out whether a control is being used after all, enable Event logging (FSUIPC Logging tab), then operate the button. If a control is being used it will be logged. Pete
  7. You must be making a mistake. All three parts must be exactly as originally supplied. Try cut-and-paste, carefully. Pete
  8. Good to hear. Thanks for letting us know. Pete
  9. I don't call that advanced! I'm 78 next month! Pete
  10. It isn't easy to be unsuccessful! you should tell us how you managed that! The User Guide contains all the help you should need, including pictures. As you are not using FSUIPC, only P3D assignments, then anything not working must be due to bad assignments in P3D, or something wrong with your controls. If you do one day start using FSUIPC then you should disable controllers in P3D or you are liable to get conflicts which will make you think you are 'unsuccessful'. Pete
  11. There are no assignments at all in your INI file except for these two odd ones for axes to the same control: 0=0S,256,F,66818,0,0,0 -{ TO SIM: STEERING_SET }- 1=1S,256,F,66818,0,0,0 -{ TO SIM: STEERING_SET }- So it looks like you aren't actually using FSUIPC for any switches at all, or any flight controls apart from the tiller. Pete
  12. Ah, of that I'm not completely sure. Worth trying though if you want our support. Save a copy of your FSUIPC4.DLL first, just in case. But for your original specific problem would probably be solved by you selecting the "Profile" option before assigning the button. Or just delete the button assignments in the Profile so that your existing general assignments prevail. Pete
  13. One other thing I notice. In the general button assignments you have the VOR1 OBI DEC control (65663) assigned to Joy 1 button 25: 19=R1,25,C65663,0 In fact you have a multitude of assignments to controls, not one to keypresses. But for the "2004 Cessna 2004" profile you just have keypresses assigned, no controls at all! Very strange. In particular for the same button you have: 8=P1,25,K120,10 which is a non-repeating CTRL+F9. If you were flying an aircraft using this Profile then any button assignment made for that profile must override that in the general assignments. That's the whole point of profiles. Pete
  14. FSUIPC terminated because MSFS stopped "running normally". It may have appeared to keep running but it stopped talking to applications via SimConnect. FSUIPC closed normally and tidily because of this, and of course tidily terminated the programs it was supposed to according to your configuration. There was no crash in FSUIPC -- if there was it couldn't have terminated tidily and closed the logging properly. Check the Windows Event Viewer. Pete
  15. I don't want pictures. If the Log file is too big, just ZIP it please. Text files zip up really small. The INI file appears to be unused -- none of the assignments have received the automatic annotation they would do when they are read. Without the log I cannot tell why, but the INI does show two significant things: 1. When this INI was created you were using the original buggy version of FSX. You need to update to at least SP1 level or preferably SP2. Both are freely available on the 'net. eg https://www.flightsim.com/vbfs/content.php?20588-Microsoft-FSX-Service-Packs 2. Your FSUIPC version 4.853 is also out of date and unsupported. Download and install 4.976 from FSUIPC.com. Please do both of these things before re-testing and supplying the correct, latest, FSUIPC4.INI and FSUIPC4.LOG files. I also see some button assignments to a joystick #2 which is not connected. You have no assignments to any axes at all. Do you only fly using the keyboard for flight controls? Pete
  16. The GUID probably changed. Generally the fix is to edit the assignments in the [JoyNames] section of your FSUIPC INI file to suit. Check whether the control is actually being sent by using Logging. enable Button & Key logging and Event logging in the FSUIPC options. if you also enable the console log you will see the effect in real time too. Then operate the button which works and, separately, the one which doesn't. For more help you need to supply your FSUIPC Log file and your settings, the FSUIPC INI file. They'll be in the same folder as FSUIPC. Pete
  17. It's always risky moving to the pre-release (Beta probably) of a new version of Windows, especially when also running what is effectively still a Beta version of FS. Anyway the Log file shows clearly that it is MSFS which is either crashing, or at least ceasing the SimConnect operations: 1225282 MSFS no longer running - exiting FSUIPC7 then proceeds to a normal tidy shut down (there's an option to keep it running without MSFS if you wish): 1238672 *** FSUIPC log file being closed Minimum frame rate was 22.2 fps, Maximum was 67.0 fps Average frame rate for running time of 1157 secs = 40.8 fps Maximum AI traffic for session was 3 aircraft Traffic deletions 0 aircraft Memory managed: 187 Allocs, 185 Freed ********* FSUIPC Log file closed *********** So, you need to check the Windows Event Viewer to see what sort of error is detected in MSFS. I note that you have a lot of unnecessary logging enabled in FSUIPC. I suggest you only enable log options when needed for specific reasons. You are also running LINDA which has a lot of its own drivers and modules. When checking into problems I think you should first disable Linda (rename Linda.exe and Linda.lua so they don't run). Pete
  18. Hi Ray, Having looked up the User guide for these options I note that: The feature for multiline displays may already automatically be enabled when P3D is first loaded, but it can be turned on and off (to use only ShowText for example) in that front option screen. There are two further options there:  One, which is removed if the multi-line FS window is enabled, and which when checked stops multi-line messages going to P3D’s default message window. Use this if you want to use ShowText to display the multi-line text, such as on another screen or even another PC via WideFS.  The other option which can be used to suppress the single-line messages routed through FSUIPC. FSUIPC cannot prevent messages displayed by programs using SimConnect directly. It seems to me, from this description, that the Window you want to suppress needs "ShowMultilineWindow=No", not "Yes". Quite honestly I doubt that there's any separate option for a "Multiline Window" as opposed to a "MultlineFS" window any more, but before I pore through the code could you try RC with the Show option changed to No. I'm not sure what other Windows you might be worried about. I don't actually have any ready-made programs which use any of these facilities, so rather than make one I'd first like to use you as my test bed, please! 😉 Pete
  19. Really Controls are Events -- the names of the regular controls in the SDK are "KEY_EVENT_ ....". Internally there are additional types like L:Vars and other "letter:Vars", and these can be used as controls, events, or merely data retainers (eg to remember the state of a switch). Controls are generally speaking the messages sent between parts of the Sim to make things happen. If they were all being sent via windows messages, as most of them used to be in FS9 and before, then we could possibly log them (and in fact before SimConnect that's how it was done) -- but distinguishing between those you are interested in and those you are not would still be the problem. But now they are all either sent direct to SimConnect, or direct between components. You can of course effectively log the controls you instigate via buttons, axis movements or key presses, if they are assigned via FSUIPC, otherwise all FSUIPC can detect is the resulting event(s) if any, courtesy of facilities to be so notified in SimConnect. Pete
  20. It might be able to keep it in sync with your PC's clock, but it doesn't read any internet clocks at all. The facility "Keep FS clock synchronised", top left in the Miscellaneous options, may work for you. It is best just left operating on the seconds -- the hours and minutes are up to you to set. I don't know about MSFS but in FSX and P3D you could set the sim to use the PC system time. Then it may only drift by seconds. But whether it works well in MSFS I'm afraid i don't know. You need to try it. In FSX and P3D it wasn't a good idea to sync more than the seconds or you could get a scenery reload occurring in the middle of flying! Pete
  21. There is no hacking into 64-bit P3D code used in FSUIPC5 or 6. All displays facilities are implemented using the SimConnect facilities instead. Previously, in the 32-bit world, they were implemented by hacks into the underlying functions and data structures within FS9, FSX, and P3D1-3 respectively. Pete
  22. But the one overall window in AllTexts accommodates all possible displays -- SimConnect ones (which include the RC one), the ActiveSky plan weather derived by FSUIPC, and an optional selected file like a log. The window is divided into two, one part from SimConnect Texts, the rest for SimConnect Displays, Menus, ActiveSky, or the scrolling text window. You just use a button or key to toggle through the latter but with an outstanding SimConnect Menu taking precedence automatically. You should really have mentioned it back then. I've really stopped FSUIPC work and development, and John is in a support-only mode for a little while, and is anyway otherwise mostly busy with MSFS these days. But, as I said, I'll take a look tomorrow. If it is still documented as working then it should -- or the documentation updated of course. I suspect the facility is only used by RC which is retired too, like me! 😉 Pete
  23. It suppresses messages but (unfortunately for me) not menus. As a WideFS user why not use the facilities to have all the displays in a client window in any case? The Lua file provided (AllTexts.lua) even provides an extracted ActiveSky report suited to your planned flight (provided you get AS to auto-load your P3D plan). Back onto the FSUIPC question, though, what were you using with P3D4? Did the option work then? I can have a look at the code, but not till tomorrow. Pete
  24. You can just suppress text in the P3D UI. Unlike in FSX and P3D1-3 the displays are standard SimConnect Windows. I don't know whether the old options for FSUIPC-instigated displays were linked up in FSUIPC5/6. If not I suppose they could be, but the whole code was simplified to use the SimConnect facilities. Pete
  25. Note that you have an unconditional assignment to the same button:So when B 1 is pressed button C2 will give two actions. You may want to put the opposite condition on this assignment: 24=CP,2,C66587,40002 -{ROTOR_BRAKE}- So when B 1 is pressed button C 2 will give two actions. You may want to put the opposite condition on this assignment: 24=CP(-B,1)C,2,C66587,40002 -{ROTOR_BRAKE}- 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.