Jump to content
The simFlight Network Forums

airforce2

Members
  • Posts

    204
  • Joined

  • Last visited

Everything posted by airforce2

  1. Quick question--if I use ipc,writeLvar in a Lua script to write to an Lvar that does not presently exist, is a new Lvar created or does it just ignore the write? If not, is there a mechanism in FSUIPC to create a new Lvar in a Lua script or macro? Regards Bob Scott
  2. To close the loop on this, I've flown over 20 flights now with the ButtonScanInterval setting at zero--no more crashes in WideFS. Regards Bob
  3. John; No, this is the first use of WideClient on this laptop (and WideServer on the MSFS machine, as I've moved MSFS off to a different computer). I've now had several successful flights after changing ButtonScanInterval from 20 to 0 in the .ini file. I have had several different HID controllers connected to the client laptop previously, but there are none presently connected, and the Windows "Devices and Printers" dialogue in the control panel shows none. It's a little early to declare victory, still--I'll keep the logging on for the time being. Thanks Bob
  4. John; I'm having a devil of a time trying to keep WideClient running. I have it on a Win 11 laptop, for use with Pilot2ATC connected to MSFS running FSUIPC 7.3.20 on a Win 10 desktop. I have used it successfully for years with FS9/X/P3D--this is my first attempt connecting to MSFS. I am getting mostly silent CTDs where WideClient just disappears. Many of the crashes show C0000374 heap corruption errors at offset 0x000ec67f. One today, a memory access violation, was trapped by WideFS. I have attached a file with the event log entries from a bunch of these crashes, as well as the log file from the event where the crash was trapped, and my WideClient.ini file. Most of the crashes showed nothing in the log file after WideFS starts and connects (no end-of-session summary etc). I've tried redownloading, uninstalling & reinstalling, UDP vs TCP, integrated ethernet vs WiFi vs a discrete USB ethernet adapter, elevated priority, run as admin, and have run sfc and dism to rule out Windows system corruption. It keeps doing the same thing--it runs for a while and then crashes with a silent CTD. Regards Bob Scott WideClient.ini WideClient - Copy (2).log Crash Event Logs.txt
  5. Argh...I think I had several folders open and I must have copied the wrong path for the executable into the post. Anyway, I have no opinion on which folder should be considered the "main" FS folder, but was just trying to understand why that folder was chosen, given that it differs from the old convention. Still trying to get my head around how a round FSUIPC fits into a square MSFS hole, so to speak... Cheers Bob Scott
  6. OK John, thanks. Can you shed some light on why the ...\Packages folder is being identified as the main sim path? In the past that main path has always been the folder where the sim's executable resides. That's the folder I had shared (located in "C:\Users\xxxxxx\AppData\Roaming\Microsoft Flight Simulator" on a Steam MSFS installation). Cheers Bob Scott
  7. Hi John/Pete; I've just noticed that offset 3E00 is reporting the server's local path to the MSFS packages folder on a WideFS client rather than the full UNC path (e.g. the path reported on the WideFS client is "C:\MSFS\Packages\" where it should be "\\HUD\MSFS\Packages\"). I'm using FSUIPC 7.3.7 and WideFS 7.160 -- as I understand it, when WideFS is connected the path in 3E00 should be the full UNC path to the folder on the server. Cheers Bob Scott
  8. This sounds like maybe the USB port powering down...check in Device Manager and make sure all your USB HID devices and hubs do not have "Allow the computer to turn off this device to save power" enabled. This option gets turned back on regularly without asking me when Windows updates on my machines.
  9. Seeing the same thing here. Works for a while, then MSFS becomes unresponsive to inputs via FSUIPC. I bring up the FSUIPC axis assignments window, which shows the axis inputs still moving, but the sim isn't getting them. In the log, there are hundreds of TransmitClientEvent failed! messages. Edit: This was using the default C208 Caravan.
  10. John/Pete; I've looked and cannot find any mechanism to allow programmatic control of FSUIPC's auto-save feature. If it already exists, would you please point me to it? If not, it'd be nice to have the ability to send an FSUIPC control to stop/start autosaves as set up in the FSUIPC menu. There are times, like on approach, for example, where it'd be nice to be able to have a LUA script disable auto-saves (e.g. below 5000' AGL) to prevent the auto-save stutter. Cheers Bob Scott
  11. Hi Pete/John; I've been trying to get OpusFSI to run using the FSUIPC Run= facility, and I kept getting an error=2 when I tried to run it with a command line parameter per the documentation. The advanced user doc says: "If the program needs command-line parameters these can be included by enclosing the whole value in quotes, so that the space(s) needed don't cause problems." It appears that guidance is in error...if the space and command line param are placed inside the quotes, it appears to be trying to use the parameter as part of the file name. If I use: Run1=READY,KILL,AM=XC0,"X:\OpusFSI_v5\FSISERVER.EXE" the program runs, but in its default (P3D) mode. To run it in FSX:SE mode, it needs the command line parameter " STEAM" appended to the command line. But if I try to run it with this line: Run1=READY,KILL,AM=XC0,"X:\OpusFSI_v5\FSISERVER.EXE STEAM" I get an unable to run line in the log with error=2, which I understand is a file not found error. If I add the command line param after the quotes, as below, it loads as intended, in FSX:SE mode: Run1=READY,KILL,AM=XC0,"X:\OpusFSI_v5\FSISERVER.EXE" STEAM Cheers Bob Scott
  12. Thanks Pete. I've been experimenting with it, and it's behaving rather unpredictably...with an airliner cruising at FL320, 310 KIAS and 492 KTAS, I write a 32-bit value of 300 to 0x0558, and the airspeed tape jumps...up(?) If I read IAS from offset 02BC soon after the write, I see values approximately 30 KIAS higher than written. I'm refining a utility that I use for repositioning the aircraft to skip ahead on a flight plan, and just moving the jet often results in a temporary but severe over/underspeed condition at the new location due to the difference primarily with winds, but also OAT and local pressure. It appears that correcting the current Z-axis body velocity for the delta in headwind component between old/new location and writing that back out to 3090 works better than using the IC facility. Cheers Bob Scott
  13. In the Initial Position set facility, offset 0558 is used to set the "airspeed". Is that TAS or IAS? Regards Bob Scott
  14. OK Pete, thanks. Turns out I had an (unintended) aircraft-specific button assignment that was masking/overriding the zapper's global button assignment...I must have bumped the wrong button at some point when I was programming one of the other buttons a few weeks ago. Cheers Bob Scott
  15. Hi Pete; I'm using P3D v4.3 and FSUIPC 5.132 -- seems that the traffic zapper has stopped working. I am using a joystick button programmed for the control. Cheers Bob Scott
  16. I just did a flight in the PMDG 747 in P3Dv4.2 with FSUIPC 5.123e installed, and the FSUIPC option did appear in the P3D Add On drop down menu, but selecting it did nothing. FSUIPC was still working in the background, though, as my flight controls and several remote apps that work via WideFS continued to operate. My Lua scripts stopped operating at that point, however. Oddly, one of the applications that uses the position freeze feature by setting a value in offset 3541 did freeze the acft position, which remained frozen indefinitely until I recoded the program to explicitly write a 0 to the offset upon exit. According to the docs, the value written to the byte at 0x3541 should decrement every 55 ms or so until it hits zero and unfreezes the sim--that wasn't happening. I couldn't look at offset 3541 using the logging function because of the aforementioned failure to bring up the menu when selected from the dropdown. The FSUIPC.log file shows no signs of trouble...I've included it here in case you want to look. Also, when running the PMDG 747 I am getting a consistent and reproducible CTD any time I try to start a program that writes to the simconnect window using FSUIPC...Radar Contact and PF3 in particular do this. Pro ATC/X, which does not use FSUIPC, works, albeit with the other issues present with keystroke capture new to v4.2. If I start a flight using the default F-22, start Radar Contact and get a normal simconnect window, and then switch to the PMDG 747, the Simconnect window stays open for the duration of the flight and works OK. I don't expect you to be able to fix this, but I mention it as perhaps it may lend a clue as to what's happening with FSUIPC, Simconnect, and P3Dv4.2 Regards Bob Scott FSUIPC5.log
  17. Understood...and I wasn't asking you to go backwards. I was more interested in whether or not there would be some advantage in capabilities to offset what sounds like increased risk (to stability) if using 5.123d over 5.122a for the time being. Cheers Bob Scott
  18. Fabrizio--you should run PMDG Operations Center, as PMDG released an update for the 747 in P3D v4.2 that deals with the CTD issue at startup. Regards Bob Scott
  19. Hi Pete; Welcome back to the maelstrom. ;-) After reading your commentary below the 5.123d download link, I have to ask if there's any good reason to move from 5.122a to 5.123d in P3D v4.2 given that there seems to be some uncertainty about whether the Simconnect issue with 5.123c is actually fixed (or fully understood). Cheers Bob Scott
  20. Hi Pete; Using P3D v4.1 and FSUIPC 5.123c It appears that auto-starting Lua scripts is not working. I have an aircraft-specific auto-start lua script that doesn't seem to want to start with P3Dv4. It's defined in LuaFiles, and in an "Auto.FSLabs A320" section of the FSUIPC5.ini...the "FSLabs A320" profile is defined and working OK for joystick calibration, axes etc. For some reason it just won't start with the sim. If I assign it to a button control and start it that way it works, and if I then kill it explicitly, it restarts again immediately. In fact I can't kill the script permanently...as soon as I do, it restarts again. I just tried it using a universal "Auto" section, and no luck there, either. But, again, if I fire it with a button, it runs. The FSUIPC5.log file shows no evidence of the lua script if I start P3D and then close it without manually starting the script, and it does not produce a script-specific log file, despite having the LogLua and DebugLua settings both turned on. I tried starting the sim with a much less intensive panel, and still no auto-start of the script at startup. Regards Bob Scott
  21. Pete; Ah...OK. In the axis assignment options, "Steering Set" is only available in the "Send to FS as normal axis" drop-down, and "Steering Tiller" is only available in the "Send direct to FSUIPC Calibration" drop-down. I had the misconception that I had to use the direct-to-calibration method if I wanted to apply calibration to the axis, but a careful re-reading of the docs makes it clear that I don't--calibration is, in fact, also available to axes (including Steering Set) assigned via "send to FS as normal axis". Great...that makes it a lot simpler than the gyrations I was going through to make this work. Cheers Bob
  22. OK, Pete...no hurries, no worries. I have things functioning well with my programmatic solution, but suspect other FSUIPC users may find themselves wanting something like this as a better way to work NWS in the 'bus. I suspect FSX/P3D v2-3 users of the FSL A320 might also find it useful, though I have never used this add-on in those platforms because of the heavy VAS footprint on a 32-bit sim. Have fun in Spain! Cheers Bob Scott
×
×
  • 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.