Jump to content
The simFlight Network Forums

Pete Dowson

Moderators
  • Posts

    37,997
  • Joined

  • Last visited

  • Days Won

    158

Everything posted by Pete Dowson

  1. I put that in for MSFS to allow/enforce Windows to accept pathnames greater than 256 (MAX_PATH), since using the default install paths, especially for the Store version of MSFS, easily generates what would otherwise be overlong paths. See https://docs.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=cmd "To specify an extended-length path, use the "\\?\" prefix. For example, "\\?\D:\very long path"." Pete
  2. You should set "no repeats". Unlike using a button press, using a keyboard creates multiple presses automatically. You'll be sending a stream of KeySends so invoking continuous F12 presses! I have this in my WideClient INI: Run2=C:\Pilot2ATC\Pilot2ATC_2020.exe Close2=Yes UseSendInput=Yes KeySend110=112,16 ; F1 Press PTT for P2A KeySend111=112,24 ; F1 Release PTT for P2A KeySend112=121,16 ; F10 Press Sayit for P2A KeySend113=121,24 ; F10 Release Sayit for P2A KeySend114=117,16 ; F6 Press Sound device for P2A KeySend115=117,24 ; F6 Release Sound device for P2A All of those KeySends are assigned to buttons in my cockpit -- the PTT to the PTT button on the yoke. Works fine. Of course, also be sure you have it set correctly in P2A. Pete
  3. This normally implies a firewall stopping the connection. It might be on the Client PC or the Server, more likely the latter. You'll either need to disable the firewall, or at least tell it to allow FSUIPC7.EXE (on the Server firewall) and WideClient.EXE (on the Client). Pete
  4. I don't know exactly what the Lorby program does but the first few entries in your Scenery.CFG file look bad: [Area.001] Title= Local= Active=FALSE Required=FALSE Layer=1 [Area.002] Title= Local= Active=FALSE Required=FALSE Layer=2 [Area.003] Title= Local= Active=FALSE Required=FALSE Layer=4 [Area.004] Title= Local= Active=FALSE Required=FALSE Layer=5 [Area.005] Title= Local= Active=FALSE Required=FALSE Layer=6 [Area.006] Title= Local= Active=FALSE Required=FALSE Layer=7 I suspect it is those which stop the scenery export program doing its job. Having entries with no name and no folder path is pretty obviously wrong. I don't know how this happened, but you need to correct it. Maybe the AddonOrganizer can do the job for you -- delete those areas? Or delete them manually ang get the AddonOrganizer to do the renumbering then needed? Pete
  5. That was for you to look at to see which file to look at — in this case MakeRwys_scenery.cfg Anyway this shows that MakeRwys and the Lorby program ran ok but that there’s something wrong with your P3D scenery.cfg file. Some scenery updater has probably corrupted it. That file is in the Windows ProgramData folder, in the P3D section. You can show me that if you need help. Pete
  6. I moved your support question to the Support Forum. Please do not post such into reference subforums. There is absolutely no difference in how MakeRunways works for P3D 5.2 to any previous versions. Check the Runways.txt file -- see what scenery cfg file it is using (it'll say within the first few lines). Then see if that file is correct. Maybe you have a broken main scenery.cfg file which messes the Lorby scanning program up. If you aren't sure, show me the scenery.cfg file (the file itself, not pictures!). Pete
  7. It sounds like you have Windows power management enabled on the relevant USB sockets. To fix that run Device Manager (enter that in the start/run box in the task bar), then look at each of the "Universal Serial Bus Controllers" Properties for those with Power Management tabs and uncheck the option "allow the computer to turn off this device to save power". Pete
  8. I'm not sure about MSFS -- the situation there is always changing -- but in FS/P3D generally there are only ON and OFF controls for Panel Lights and Landing Lights, so how are you assigning the others? An alternative to using the Controls is to change the bits for the lights in offset 0D0C. For NAV lights you can assign ON to offset word setbits with a parameter of 1 and OFF similarly to offset word clearbits, same parameter, both for offset 0D0C. Pete
  9. Well that is far too restrictive. Perhaps you should talk to FSC about that and get them to improve their throttle quadrant driver? There is one other possibility not involving programming: use the offsets in the range 3BA8 - 3BC4. Check the List of Offsets document to see which of those to use. Then you should be able to assign the throttle axes in the FSUIPC Axis assignments tab, and calibrate if necessary too, just as for a proper Windows Joystick type device . That's only for writing. Leave the read offsets as they are. Pete
  10. 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
  11. 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
  12. 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
  13. 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
  14. 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
  15. 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
  16. 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
  17. Go here: https://secure.simmarket.com/john-dowson-fsuipc7-for-msfs.phtml and "Add To Cart". Proceed through to complete payment. Pete
  18. 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
  19. 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
  20. 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
  21. 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
  22. 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
  23. 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
×
×
  • 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.