Jump to content
The simFlight Network Forums

airforce2

Members
  • Content Count

    197
  • Joined

  • Last visited

Community Reputation

0 Neutral

About airforce2

  • Rank
    Advanced Member
  • Birthday 01/01/1970

Contact Methods

  • Website URL
    http://

Profile Information

  • Gender
    Male
  • Location
    Colorado, USA

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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.
  2. 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.
  3. 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
  4. 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
  5. 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
  6. In the Initial Position set facility, offset 0558 is used to set the "airspeed". Is that TAS or IAS? Regards Bob Scott
  7. 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
  8. 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
  9. 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
  10. 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
  11. 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
  12. 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
×
×
  • 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.