Jump to content
The simFlight Network Forums

Cockpitbuilders

Members
  • Posts

    30
  • Joined

  • Last visited

Posts posted by Cockpitbuilders

  1. Pete,

    I am sure you already know this, but in the cameras.cfg file adjust these...
     

    Quote

    InitialXyz = 0.37, -0.15, 1.35
    InitialPbh = 1, 0, 10

    I do this in the [CAMERADEFINITION.0] Heading

    These are for the king Air.

    Trev

  2. Hi Guys,

    While trying to get sound.play and sound.path to work, I was trying to locate if my sounds were playing, and I came across something strange when turning on the "Event Logging" Now, keep in mind I tried searching all of my .lua scripts for the effective controls being sent, but wondered if you were aware of something hammering FSUIPC.  Can you confirm the attached log, event logging occurs on your end with the King Air, or is this something that is happening strictly on my machine?

    What I am referring to is the 2 lines hammering control event logging.

    734782 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 19 (0x00000013) FUEL_SELECTOR_SET
    734782 *** EVENT: Cntrl= 66523 (0x000103db), Param= 20 (0x00000014) FUEL_SELECTOR_2_SET

    Please see the attached log, this seems odd to me.FSUIPC7_prev.log

    Thanks guys.

    Trev

  3. Enrico,

    There is a bunch of files in the aircraft directories that have "Defaults Set in them" ie apron.flt Seems there is a .flt file for every "Start point for the aircraft", and it defaults the frequencies. So regardless what they are set to the aircraft seem to revert to these values, I haven't tried, but perhaps if you delete those lines of code in the .flt files, they may not revert.

    Just letting you know.

    Trev

  4. I am going to add to this, because this is what I am experiencing.  Today was the first day I got to experiment with the new patch, and this seems to happen often.

    Here is my Log.

    Quote

    ********* FSUIPC7, Version 7.0.0-Beta (8th September 2020) by John & Pete Dowson *********
    Cannot open UserCfg.opt at 'C:\Users\XXX\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\UserCfg.opt'
    Windows 10 Home 64 Bit reported as Build 18363, Release ID: 1909 (OS 10.0)
    Reading options from "D:\Program Files\FSUIPC7\FSUIPC7.ini"
    Checking the Registrations now ...
    User Name="MSFS Tester"
    User Addr="Time Limited 311020"
    User WideFS Name="BLANK TO PROTECT INNOCENT"
    User WideFS Addr="BLANK TO PROTECT INNOCEN"
    FSUIPC7 Key is provided
    WideFS7 Key is provided
           62 System time = 12/09/2020 13:44:46
           78 FLT UNC path = "\\SERVER\Users\XXX\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\"
          156 -------------------------------------------------------------------
          171 Registered HotKey 'InvokeFSUIPCOptionsKey' (key=0x46, modifier=0x1)
          187 FS UNC path = ""
    Cannot open UserCfg.opt at 'C:\Users\XXX\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\UserCfg.opt'
          218 ---------------------- Joystick Device Scan -----------------------
          218 Product= Arduino Leonardo
          218    Manufacturer= Arduino LLC
          218    Serial Number= HIDNH
          218    Vendor=2341, Product=8036 (Version 1.0)
          234    GUIDs returned for product: VID_2341&PID_8036:
          234       GUID= {0CB38CF0-2BB5-11EA-8001-444553540000}
          234       Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R-32767,U-32767,V-32767,X27193,Y32767,Z30460
          234 Product= FDS-FC1
          234    Manufacturer= TEKWorx Limited
          234    Serial Number= A00531
          234    Vendor=1FD1, Product=03ED (Version 1.35)
          234    GUIDs returned for product: VID_1FD1&PID_03ED:
          234       GUID= {13AE15B0-2DC3-11EA-8001-444553540000}
          234       Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R1014,U978,V931,X1023,Y1023,Z1023
          234 -------------------------------------------------------------------
          234 Device acquired for use:
          234    Joystick ID = 0 (Registry okay)
          234    0=Arduino Leonardo
          234    0.GUID={0CB38CF0-2BB5-11EA-8001-444553540000}
          234 Device acquired for use:
          234    Joystick ID = 1 (Registry okay)
          234    1=FDS-FC1
          234    1.GUID={13AE15B0-2DC3-11EA-8001-444553540000}
          234 -------------------------------------------------------------------
          250 LogOptions=00000000 00000001
         3171 Simulator detected
         8218 SimConnect_Open succeeded
         8218 Running in "KittyHawk", Version: 11.0.282174.999 (SimConnect: 11.0.62651.3)
         8218 MSFS version = 11.0.282174.999
         8218 Initialising SimConnect data requests now
         8250 \\SERVER\Users\XXX\AppData\Roaming\Microsoft Flight Simulator\MISSIONS\Custom\CustomFlight\CustomFlight.FLT
         8250 SimObjects\Airplanes\Asobo_KingAir350\aircraft.CFG
         8250 User Aircraft ID 1 supplied, now being used
         8296 Aircraft loaded: running normally now ...
         8812 System time = 12/09/2020 13:44:55, Simulator time = 12:29:36 (16:29Z)
         8828 Aircraft="Beechcraft King Air 350i Asobo"
        14812 -------------------- Starting everything now ----------------------
        14812 Starting WideServer now ...
       482593 LUA: "1.lua": killed
      2079250 TransmitClientEvent failed! (Event=65820, Param=2268, nGroup=0, fSame=0
      2079250 TransmitClientEvent failed! (Event=65821, Param=1812, nGroup=0, fSame=0
      2079265 TransmitClientEvent failed! (Event=65820, Param=1936, nGroup=0, fSame=0
      2079265 TransmitClientEvent failed! (Event=65821, Param=1471, nGroup=0, fSame=0
      2079281 TransmitClientEvent failed! (Event=65720, Param=1, nGroup=0, fSame=0
      2079281 **** Too many TransmitClientEvent errors received! Re-connecting now ... ****
      2079281 TransmitClientEvent failed! (Event=65820, Param=1630, nGroup=0, fSame=0
      2079281 **** Too many TransmitClientEvent errors received! Re-connecting now ... ****

     

    Trev

  5. Enrico, that’s actually how I had accomplished this. When I saw the cameras.cfg file did that right away. 
     

    just have to be cautious to see if PM functions will interfere with the built in ones. Ie the MCP fighting with the one in the panel.cfg

     

    Trev

  6. Gobsmacked. - If I could package up the experience and veterans in this thread right now I would probably fall over. 
     

    for those of you unaware, this thread is listed with comments from many years of experience. 
     

    Thanks Pete and John for your hard work on this. 
     

    James, Torsten, Enrico, Thomas, Pete. 
     

    we couldn’t have any of this if it weren’t for you guys!

     

    Trev

    • Like 1
  7. James...  Glad to see I wasn't the only one having an issue..  I chalk it up as "OLD AGE" LOL

     

    John and Pete..  I am so far not seeing some of the (RED) Unable to write to Generators, Avionics switches, or Radios Offsets that was specified in the attached "functionality Excel sheet"  So far the majority of stuff I have been able to test (which is limited due to the frame rate issues) seems to work with the exception of the radios, seem to adjust the Active freq, rather than the Standby Freq function wise.  But Will report in more detail as things get repaired with MSFS (ASOBO) Simconnect booboo.

    Lua scripts all transferred without issue and I was up and running with my Project Magenta within minutes.

    I will say though, my PM MCP really was having troubles trying to keep the aircraft from proposing all over the place, but I attribute that to the frame rates and simconnect connectivity issues, seems the MCP can't compensate smooth enough at this point.

     

    Trev

  8. Pete, My apologies

    Whilst changing from P3DV4 to P3Dv5 and Running my electric Trim It appears the Coupling between the encoder and Stepper has come loose.  With your post Above I thought better of a software issue and re-evaluated my troubleshooting process and found the failure.

    This teaches us to re-evaluate the issues and don't make assumptions until you have fully verified the causes prior to posting possible Bugs. (With new versions many of us tend to make assumptions that waste others time) again my apologies.

    Trev

  9. Wonderful, Thanks as always Pete.

    I will just utilize the ipc.display function for monitoring for now.  All I can say is trim works in P3DV4 and not working in P3Dv6 with the same LUA File..  But of course, perhaps My Lua file has something else in it that P3Dv5 doesn't like.  I will continue with the troubleshooting.

    Perhaps, there is something overwriting the Trim Value.  I have external Controllers disabled in P3D as I only use UIPC for Controls. Perhaps there is something else holding it out.

    Best regards

    Trev

  10. Evening Gentleman,

    Just to report a couple of issues since installing V6.

    #1 The following ipc.control for Trim does not seem to have any effect anymore. Would something in the Lua IPC.Control facility have changed with V6?
    Alas, I however can report that the keyboard assignments still work to change the trim in the Project Magenta FMC, which brings me to the second issue.

    I thought I would change from the IPC.Control to value = ipc.readUW (0x0bc0);  Value = Value + 200; ipc.writeUW ((0x0bc0), value); for Increase Trim. I however wanted to check if the offset was changing with the ipc.control command first to identify what was going on. I decided to Launch Interrogate to make sure that the offset was working, and alas can't run setup fields in the 3-scan locator, due to the following access violation error. I am running the Interrogate facility with administrator privileges.

    Thanks,

    Trev

    LUATRIM.PNG

    interrogate_Error.PNG

  11. Thanks Pete for the quick response. 

    I appreciate the more urgent needs that are upon us, and I am so thankful for your support over the years.  I commend you for your retirement, I still have a few years to go prior to me being able to think about that.  I will also thank you for passing the legacy on, so many of us will still be able to benefit from that which has made this hobby a possibility. Please Sir, Enjoy your retirement.

    In the interim, for those people researching this topic in future, I got around this by abandoning the simconnect window and instead using the lua facilities to write to a text file, then manipulating the text file to suit my needs.

    Best regards to all.

    Trev

  12. Hi Pete,

    With Regard to

    ipc.lineDisplay(“Failure Message”, -5)

    Are there any facilities at present to set background color and text color in the simconnect lua Message window? in p3dV4 at this time? I read in the manual ipc.display had colour settings but appeared based on your notes to not be available to V4 at this time.

    Thanks,

    Trev

×
×
  • 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.