Jump to content
The simFlight Network Forums

Scotfleiger

Members
 View Profile  See their activity

  • Posts

    392

  • Joined

  • Last visited

  • Days Won

    2

 Content Type 

Everything posted by Scotfleiger

  1. Scotfleiger
    Thank you Pete. As the 'LINDA person' I will investigate further. Is it just LINDA that is having these issues with no closing correctly?
  2. Scotfleiger
    Users are reporting problems with the LINDA add-on not closing when closing P3D 3.4.9 with FSUIPC4 4.9.5.7b. Having just done this update myself I am having the same problem. I note in the FSUIPC4 release notes that a new option TimeForLuaClosing has been added with a specific mention of LINDA. I have tied setting this value to 10 and 20 but neither LINDA not AS16 are closing when P3D is exited. With P3D 2.3 and previous version of FSUIPC4 the following FSUIPC4.ini statement correctly closed the add-ons: [Programs] RunIf1=KILL,C:\Sim Support\AS16_P3D\AS16.exe RunIf4=KILL,C:\Sim Support\VAInterface Lite\VAInterfaceLite.exe RunIf2=CLOSE,C:\P3D\Modules\linda.exe Any suggestions on what the problem can be? Note: the release notes (para 18) refer to TimForLuaClosing not TimeForLuaClosing (as appears in the .ini file).
  3. Scotfleiger
    That was what was causing the Nil errors. I was using readLVar and not readLvar. My apologises for the hassle.
  4. Scotfleiger
    Thank you for the confirmation and information Pete. I was beginning to pull my hair out (and there is not much on top to come out). PS. You are correct. I was trying to type the non-word "ipc" but autocorrect kept changing it to "pic" fast they I could see that it was doing it.
  5. Scotfleiger
    Yes thank you aua668. I tried using 'L:' (optional) and I get the error 'attempt to call field 'readLVar' (a nil value)' in the line with the statement: epr = pic.readLvar("L:TURB ENG1 EPR").
  6. Scotfleiger
    Thank you Pete. That is strange. In a LINDA module LUA function I have used the instruction x = ipc.readLvar("TURB ENG1 EPR") which returns a nil value and flags an error. When I trace the same Lvar (with spaces) in the LINDA tracer it works correctly and I can see the returned values. The missing 'L' in ipc.readLvar was caused by autocorrect.
  7. Scotfleiger
    MOVED TO THE FSUIPC SUPPORT FORUM Hi Pete Some of the Lvars for the Aerosoft Airbus contain spaces (e.g. TURB ENG1 EPR) instead of the usual convention of using underscore (_). When these particular Lvars are used with ipc.readvar() FSUIPC4 returns a nil value (not found). However, when I can trace these Lvars using LINDA. Does the ipc.readLvar() command strip out the space characters?
  8. Scotfleiger
    Sorry forgot paste the lines: 3554233 ## SimConnect_Text: fWhite=0, 0x3303=0 3555356 ## SimConnect_Text: fWhite=0, 0x3303=0 3556339 ## SimConnect_Text: fWhite=0, 0x3303=0 3557244 ## SimConnect_Text: fWhite=0, 0x3303=0 3558258 ## SimConnect_Text: fWhite=0, 0x3303=0 3559147 ## SimConnect_Text: fWhite=0, 0x3303=0 Pete, LINDA logs its activity to the LINDA Console window through FSUIPC4. This is used for reporting and debugging purposes.
  9. Scotfleiger
    Since updating to FSUIPC4 4.95 I am seeing the following line repeatedly included in the FSUIPC4.log file (and in the LINDA console). Nothing else has changed in my configuration (P3Dv3.2, PMDG737 NGX, ASNv4.1, LINDA 2.7.x). Can this be inhibited?
  10. Scotfleiger
    Will do. Thank you for looking. I'll report back. Andrew
  11. Scotfleiger
    Thank you Pete. It may only be A2A but P3D who have moved the goal posts. A2A may just be using the P3D definition for AP Alt and VS for both platforms. Looking at the Lockheed Martin definition (http://www.prepar3d.com/SDKv2/LearningCenter/utilities/variables/simulation_variables.html#Aircraft%20Autopilot%20Data): AUTOPILOT ALTITUDE LOCK VAR Selected altitude ("Altitude bug") Feet Y Shared Cockpit AUTOPILOT VERTICAL HOLD VAR Selected vertical speed ("VSI bug") Feet/minute Y Shared Cockpit I will inquire further with them.
  12. Scotfleiger
    Hi Pete I am the support developer for LINDA and have found an interesting issue with the offsets for Autopilot Altitude (07D4) and Vertical Velocity (07F2) with A2A aircraft add ons in FSX and P3D. I wonder what your view is. The offsets are: 07D4 4 bytes Autopilot altitude value, as metres*65536 07F2 2 bytes Autopilot vertical speed value, as ft/min ​The altitude is quoted as being in metres and the vertical speed in ft/min. ​I have found through detailed tests that the conversion of Altitude from metres to feet is required only if the A2A A182 or C172 aircraft are used or when using P3D (alt = round(0x07D4 * 3.2808399 / 65536)). The reverse applies to the Vertical Speed. If not A2A or P3D, VS= round(0x07F2 / 3.2808399). In all other cases (FSX and non-A2A), the offsets are defined as AP Alt in feet and AP VS in metres/sec. This is opposite from the FSUIPC4 Status of IPC Offsets for FSX document.
  13. Scotfleiger
    After over a year with any problems, my joystick HAT POV set up has gone crazy. The view has all of a sudden started resetting itself to the straight ahead (eye point reset) view on releasing the hat switch. I have tried reassigning the Pan Left/Right/Up/Down to the Hat buttons with repeat in FSUIPC 4.937, but as soon as I release it springs back to view ahead. All FSX assignments have been deleted. Can anyone suggest what has gone wrong?
×
×
  • 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.