Jump to content
The simFlight Network Forums

Pete Dowson

Moderators
  • Posts

    37,910
  • Joined

  • Last visited

  • Days Won

    155

Everything posted by Pete Dowson

  1. The X axis is evidently very sensitive and you are unable to press a toe brake without that rudder axis being seen first. This is exactly why that ignore button is provided. Press that THEN operate a toe brake. When you calibrate the rudder axis be sure to set enough dead zone to avoid the rudder moving when you press a toe brake -- i.e. set the "centre" with the rudder pressed a bit each way, to create a dead zone. Yes, same thing as above. Pete
  2. Sorry. why? You are currently using ipc.write functions to write the axis value to offsets. What is so hard changing those functions to use ipc.control instead, to send the axis values to the relevant axis controls? Where is there new coding to learn? You are using a control number instead of an offset. The only difference is that the Axis control values run from -16384 (idle) to +16383 (full thrust) instead of 0 to 16383, so you need to change the value (n) being written to 2*n - 16384 Pete
  3. The sort of complex add-on aircraft you have those problems with tend to do their own thing with some controls, especially throttles. I recommend you use the Axis Throttle1 Set and Axis Throttle2 Set controls via ipc.control, as these are what the aircraft coding is expecting to see. I don't understand why you consider that "worst case". Pete
  4. Sorry, I really have no idea. The COM library just uses standard Windows API functions, and only handles the defined serial port. Can you get any help form OpenTrack? after all it is their software which is freezing. Pete
  5. Best I can make out is that exception FD is to do with a hardware driver. The log you appended actually shows a good session with FSUIPC closing normally after 365 seconds (6 minutes): 365797 === Closing session: waiting for DLLStop to be called ... 388578 === DLLStop called ... 388578 === Closing external processes we started ... 389578 === About to kill any Lua plug-ins still running ... 389719 === Closing global Lua thread 390719 === About to kill my timers ... 390922 === Restoring window procs ... 390922 === Unloading libraries ... 390922 === stopping other threads ... 390922 === ... Memory checking ... 390922 === ... Button scanning ... 391031 === ... Axis scanning ... 391125 === Releasing joystick devices ... 391125 === Freeing macro memory 391125 === Removing any offset overrides 391125 === Clearing any displays left 391125 === NOTE: not calling SimConnect_Close ... 391125 === AI slots deleted! 391125 === Freeing button memory ... 391125 === Closing my Windows ... 391141 === Freeing FS libraries ... 392141 === Closing devices ... 392141 === Closing the Log ... Bye Bye! ... 392141 System time = 31/07/2021 20:18:01 392141 *** FSUIPC log file being closed Minimum frame rate was 32768.0 fps, Maximum was 0.0 fps Minimum available memory recorded was 32768Mb G3D fix: Passes 8266, Null pointers 0, Bad pointers 0, Separate instances 0 Maximum AI traffic for session was 0 aircraft Memory managed: 4 Allocs, 4 Freed ********* FSUIPC Log file closed *********** The meaning of error FD isn't clear, but if it is at all related to FSUIPC then it seems likely to be down to a driver for one of the devices you have connected. You don't appear to be using FSUIPC for any joystick devices. Are you using any Lua plug-ins? Maybe you should show us your FSUIPC4.INI file which contains your settings. Also, look further in the Windows Event Viewer to see if there's a preceding FSX crash. If FSX is immediately restarting (which it shouldn't!) then a new log would be created when FSUIPC is loaded, so you reall need the Prev log, which is also saved. You don't really supply enough information for me to help you further at present. Pete
  6. WideFS is a facility to run FSUIPC client applications on a different PC to the Sim, across a network link. It is a separate purchase. If you don't have it simply leave that entry blank. Pete
  7. Don't you mean a French version? Why not just search using Google? I did and found several sources. Here's just one: https://www.fileplanet.com/archive/p-15328/Flight-Simulator-X-SP1-Update-French Pete
  8. Go here: https://secure.simmarket.com/john-dowson-fsuipc7-for-msfs.phtml and "Add To Cart". Proceed through to complete payment. Pete
  9. What is "opentrack"? Is there a support forum for it? I assume your Lua script for Arduino is using the Lua Com library over a serial link. So the thing you would need to investigate is how the use of that serial port interacts with whatever method this "opentrack" program uses. I would have thought opentrack support would be in a better position to advise you on that. Pete
  10. You are using the very first buggy version of FSX. Please update to SP1, or better SP2, of FSX. Then you won't have such a problem. Get them here: https://flyawaysimulation.com/downloads/files/1950/microsoft-flight-simulator-x-service-pack-1/ https://flyawaysimulation.com/downloads/files/2796/flight-simulator-x-service-pack-2/ Pete
  11. I've moved this support question to the Support Forum so it can be answered. There are de-icer switches for each of up to 4 propeller de-icers, and one structural de-icer switch. But no read-out for any "de-icer pressure". Are you seeing such a read-out in the cockpit? Pete
  12. I've moved your support question to the Support Forum so it can be answered. The reason for providing 4.70 is because some Win7 and earlier Windoows systems reported problems running the latest ones. If more up-to-date versions load and run on your system, then that's fine. I guess your Win7 is more up to date than the reporting users, Pete
  13. The Win10 Device Manager is almost the same as it has always been since Win XP days. But the notes above are for the Registry Editor (REGEDIT), so maybe you are loading the wrong program? In the Registry editor just use Find (in the Edit menu) to find entries for Saitek, using VID_06A3 and also VID_0738. Pete
  14. What does the Joy number and Axis letter show in the assignments window for each of the three axes (rudder, left brake, right brake). It sounds like you are inadvertently moving the rudder axis at the same time as the brake axes, making FSUIPC think you are reassigning. If this is the case, just press "ignore" for the wrong axis and press again. The "ignore" option only operates for the duration of that setting attempt -- it cancels when you exit from the options. If you still have problems, please show us your FSUIPC7.LOG and .INI files. Pete
  15. You'll really need to check with FSLabs about their aircraft. Test with a default aircraft first. Pete
  16. I confirm this: once minimized there seems to be no way back except to close it via the task bar and start it again. Until it is fixed, best to just use the X (close) button, top right. That effectively sends it to the system tray in a state where ALT+F will re-display it. It doesn't close it -- that is done by using the "Exit" option in the File menu. Pete
  17. I attach install packages for versions 4.971 and 4.974. Try those -- but i am at a complete loss as to how the Simconnect.DLLs cannot be seen. That makes no sense at all. Pete Install_FSUIPC4971.zipInstall_FSUIPC4974.zip
  18. All those axis control defines are old methods of controlling the aircraft when the real relevant controls aren't available. I think they are all pretty much redundant now, and could probably be removed along with the supporting code, should that still exist. Pete
  19. Is your logon name to Windows really "NAME"? That seems really unlikely. Your log-on name should be there instead. The error means bad folder name so something there is wrong. You could try replacing the C:\Users\NAME\AppData part by %AppData% Pete
  20. It's a real puzzle. One of the changes for FSUIPC 4.976 was, to quote: It also allows the SimConnect.DLL in the FSX folder to be used if it is installed there by the latest non-beta installer (version 62615). That location appears to be the new alternative to using the troublesome WinSxS methods. That has been 100% successful till now. But if it saw the DLL there it would not go searching for the WinSXS copies. I am wondering whether it isn't compatible with the basic Win7 now. How is it you've not updated it? I could probably find an older version of FSUIPC4 which you could try. Everything has been so Win10-oriented for years now. Pete
  21. 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
  22. 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
  23. 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.
  24. The "course" display/dial is the "Omnidirectional Bearing Selector". Look for OBS controls in the list. 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.