FSUIPC read wrong offset value if load in mid flight.

[Mugz]

Step to reproduce:

- Script for read offsets: OBEC, 0BF0, 0BF4 (then print value to log)
- Autorun script in FSUIPC7.ini
- Run Simulator in midflight (MSFS for me)
- Exit FSUIPC (simulate crash)
- Start FSUIPC.

When FSUIPC start and load script - he read offsets with value 16383 (gear's full down), but in simvars i have '0' value, what means all gears is up.

It's happen only if run in mid flight. Sometimes with already running FSUIPC. But always if start FSUIPC after starting flight.

[John Dowson]

4 minutes ago, Mugz said:

Step to reproduce:

- Script for read offsets: OBEC, 0BF0, 0BF4 (then print value to log)
- Autorun script in FSUIPC7.ini
- Run Simulator in midflight (MSFS for me)
- Exit FSUIPC (simulate crash)
- Start FSUIPC.

So MSFS crashed?
If you restart FSUIPC7 and the sim has crashed, there will be no simvar values available.

5 minutes ago, Mugz said:

When FSUIPC start and load script - he read offsets with value 16383 (gear's full down), but in simvars i have '0' value, what means all gears is up.

But is the sim running (you say it crashed)?
Also, when/how are you reading this? i,e, how do you know 'in simvars i have '0' value'?
Could it be that yoiu are reading the offset before the initial offset data is has been received?
 

Please explain your issue more clearly, and show me the script and and FSUIPC7.log that shows your problem.

[Mugz]

7 minutes ago, John Dowson said:

So MSFS crashed?

Nope. MSFS still work and flight is continue.

7 minutes ago, John Dowson said:

But is the sim running (you say it crashed)?

No, i mean simulate FSUIPC crash. Sometimes FSUIPC closed and exited without any error

 

7 minutes ago, John Dowson said:

Also, when/how are you reading this? i,e, how do you know 'in simvars i have '0' value'?

I using SimWatcher (by Asobo SDK) to watch SimVars values. 

for LUA i'm using

  noseGear = ipc.readUD(0x0BEC)
  leftGear = ipc.readUD(0x0BF4)
  rightGear = ipc.readUD(0x0BF0)

in Poll function then print values through ipc.log

[John Dowson]

2 minutes ago, Mugz said:

No, i mean simulate FSUIPC crash. Sometimes FSUIPC closed and exited without any error

If FSUIPC is crashing, please show me your FSUIPC7.log (from when it crashed), together with any event information from the Windows Event viewer.

5 minutes ago, Mugz said:

I using SimWatcher (by Asobo SDK) to watch SimVars values. 

for LUA i'm using

  noseGear = ipc.readUD(0x0BEC)
  leftGear = ipc.readUD(0x0BF4)
  rightGear = ipc.readUD(0x0BF0)

in Poll function then print values through ipc.log

Could you be reading the values before they have been received/initialised? As I said, please show me your script and a log file showing your issue.

[Mugz]

5 minutes ago, John Dowson said:

If FSUIPC is crashing, please show me your FSUIPC7.log (from when it crashed), together with any event information from the Windows Event viewer.

I don't have FSUIPC7.log, because it's overwrites every time when i start FSUIPC. There is attached VPC scripts.

In ini i have
```

[LuaFiles]
1=VPC_Base
2=VPC_LP_#2
3=VPC_LT_MT50CM3
4=VPC_RCA_MT50CM2

[Auto]
1=Lua VPC_RCA_MT50CM2
2=Lua VPC_LT_MT50CM3
3=Lua VPC_LP_#2 (Gear state in this script)

```

 

VPC.7z

[John Dowson]

11 minutes ago, Mugz said:

I don't have FSUIPC7.log, because it's overwrites every time when i start FSUIPC. There is attached VPC scripts.

If FSUIPC crashes, you should save the log and show it to me. The log is also renamed FSUIPC7_prev.log when FSUIPC7 is restarted, so you will still have your previous log rvrn if you restart FSUiPC7. I cannot help you if you do not show me your logs...

The windows event viewer information you posted shows a fault, not a crash. You also seem to have many such errors in your windows event viewer - are they all from FSUIPC7?
How many are produced when FSUIPC7 crashes/disappears? Can you show me all such events produced (from anything, not just FSUIPC7), in order, when this occurs.

 

[Mugz]

Just now, John Dowson said:

are they all from FSUIPC7?

Yes, all of them is FSUIPC

I have only FSCUIP error for last 10 days in my event log.

3 minutes ago, John Dowson said:

If FSUIPC crashes, you should save the log and show it to me. The log is also renamed FSUIPC7_prev.log when FSUIPC7 is restarted, so you will still have your previous log rvrn if you restart FSUiPC7. I cannot help you if you do not show me your logs...

Ok. I will try to save log and show it to you.

[Mugz]

There is crash of FSUIPC with log:

********* FSUIPC7, Version 7.2.1a (14th June 2021) by John Dowson *********
Checking for FS path in 'C:\Users\Mugz\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\UserCfg.opt'
FS path found = E:\Sim\MSFS2020\
WebSocket server found: C:\Apps\FSUIPC\\Utils\FSUIPCWebSocketServer.exe
Windows 10 Pro 64 Bit reported as Build 19043, Release ID: 2009 (OS 10.0)
Reading options from "C:\Apps\FSUIPC\FSUIPC7.ini"
Checking the Registrations now ...
User Name="Maksim Brykov"
User Addr="mixmugz@gmail.com"
FSUIPC7 Key is provided
WIDEFS7 not user registered, or expired
      125 System time = 14/06/2021 15:55:12
      125 FLT path = "C:\Users\Mugz\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\"
      187 -------------------------------------------------------------------
      234 No hot key defined to open FSUIPC main window - this is ok
      281 FS path = "E:\Sim\MSFS2020\"
      281 ---------------------- Joystick Device Scan -----------------------
      281 Product= R-VPC Stick MT-50CM2
      281    Manufacturer= VIRPIL Controls/20210102
      281    Vendor=3344, Product=4130 (Version 0.1)
      359    GUIDs returned for product: VID_3344&PID_4130:
      359       GUID= {FBB6C6E0-C8A9-11EB-8001-444553540000}
      359       Details: Btns=31, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U16384,V16384,X16384,Y16384,Z16384
      359 Product= VPC Rudder Pedals
      359    Manufacturer= VIRPIL Controls/20210102
      359    Vendor=3344, Product=01F8 (Version 0.1)
      359    GUIDs returned for product: VID_3344&PID_01F8:
      359       GUID= {FBB73C10-C8A9-11EB-8003-444553540000}
      359       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U16384,V0,X0,Y0,Z16384
      359 Product= L-VPC Panel #2
      359    Manufacturer= VIRPIL Controls/20210102
      359    Vendor=3344, Product=825B (Version 0.1)
      359    GUIDs returned for product: VID_3344&PID_825B:
      359       GUID= {33742FA0-C8AA-11EB-8007-444553540000}
      359       Details: Btns=42, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0
      375 Product= L-VPC Throttle MT-50CM3
      375    Manufacturer= VIRPIL Controls/20210102
      375    Vendor=3344, Product=8194 (Version 0.1)
      375    GUIDs returned for product: VID_3344&PID_8194:
      375       GUID= {31F3AA20-C8AA-11EB-8005-444553540000}
      375       Details: Btns=62, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R16384,U16384,V16384,X16384,Y16384,Z16384
      375 -------------------------------------------------------------------
      390 Device acquired for use:
      390    Joystick ID = 0 (Registry okay)
      390    0=RIGHT VPC Stick MT-50CM2
      390    0.GUID={FBB6C6E0-C8A9-11EB-8001-444553540000}
      390 Device acquired for use:
      390    Joystick ID = 1 (Registry okay)
      390    1=VPC Rudder Pedals
      390    1.GUID={FBB73C10-C8A9-11EB-8003-444553540000}
      390 Device acquired for use:
      390    Joystick ID = 3 (Registry okay)
      390    3=LEFT VPC Panel #2
      390    3.GUID={33742FA0-C8AA-11EB-8007-444553540000}
      390 Device acquired for use:
      390    Joystick ID = 2 (Registry okay)
      390    2=LEFT VPC Throttle MT-50CM3
      390    2.GUID={31F3AA20-C8AA-11EB-8005-444553540000}
      390 -------------------------------------------------------------------
      406 ### Note: AI Traffic related facilities and data are inhibited!
      406 LogOptions=00000000 00000001
     3218 Simulator detected
     8234 SimConnect_Open succeeded
     8234 Running in "KittyHawk", Version: 11.0.282174.999 (SimConnect: 11.0.62651.3)
     8234 MSFS version = 11.0.282174.999
     8234 Initialising SimConnect data requests now
     8250 flights\other\MainMenu.FLT
     8250 SimObjects\Airplanes\Asobo_TBM930\aircraft.CFG
     8312 User Aircraft ID 1 supplied, now being used
     8406 Aircraft loaded: running normally now ...
     8484 System time = 14/06/2021 15:55:20, Simulator time = 12:55:20 (12:55Z)
     8484 Aircraft="TBM 930 Asobo"
    16078 E:\Sim\MSFS2020\Official\OneStore\asobo-aircraft-tbm930\SimObjects\Airplanes\Asobo_TBM930\aircraft.CFG
    16234 LUA.1: Init LED state!
    16312   [INFO]: **** Starting FSUIPC7 WASM Interface (WAPI) version 0.5.1
    16312   [INFO]: Connected to MSFS
    16375 LUA.2: Init LED state!
    16390 LUA.3: Init LED state!

[John Dowson]

4 minutes ago, Mugz said:

There is crash of FSUIPC with log:

I could be an issue with your lua scripts. Do you get the crashes if not running your lua scripts?
If not, could you activate logging for Lua Plugins and try again (i.e. make it crash), and show me the new crash log.

[Mugz]

6 minutes ago, John Dowson said:

I could be an issue with your lua scripts. Do you get the crashes if not running your lua scripts?
If not, could you activate logging for Lua Plugins and try again (i.e. make it crash), and show me the new crash log.

Crash FSUIPC is not issue for me, i always can start them again 😃

Problem for me only with not correct data for gears if i start flight from midflight and then run FSUIPC.

example script:
 

-- Test

Pollrate = 25

function Poll(time)
  noseGear = ipc.readUD(0x0BEC)
  leftGear = ipc.readUD(0x0BF4)
  rightGear = ipc.readUD(0x0BF0)
  ipc.log("Gear L-N-R state: "..leftGear.." "..noseGear.." "..rightGear)
end

event.timer(1000/Pollrate, "Poll") -- Poll values 'Pollrate' times per second

 

[Mugz]

There is always error in event viewer if i just exit FSUIPC.

Faulting application name: FSUIPC7.exe, version: 7.2.0.0, time stamp: 0x60c73d2e
Faulting module name: FSUIPC7.exe, version: 7.2.0.0, time stamp: 0x60c73d2e
Exception code: 0xc0000005
Fault offset: 0x0000000000019884
Faulting process id: 0xf9cc
Faulting application start time: 0x01d7611fa2106f1f
Faulting application path: C:\Apps\FSUIPC\FSUIPC7.exe
Faulting module path: C:\Apps\FSUIPC\FSUIPC7.exe
Report Id: 7621b18c-399e-4d4c-a003-36d930aca76e
Faulting package full name: 
Faulting package-relative application ID: 

 

FSUIPC7.log.7z

[John Dowson]

 

4 minutes ago, Mugz said:

Problem for me only with not correct data for gears if i start flight from midflight and then run FSUIPC.

The full log would be more useful.... But the log extract you showed shows the log message was produced 21 seconds after FSUIPC7 started. Do you not see these values change as the data is received from the FS? Of not, please show me you full log, not an extract.

You are posting so many messages/problems its difficult for me to keep track, and I can't investigate as I'm spending all my time responding to you!

4 minutes ago, Mugz said:

There is always error in event viewer if i just exit FSUIPC.

Well, that shouldn't happen either. But lets look into your other issues first...

[Mugz]

1 minute ago, John Dowson said:

Of not, please show me you full log, not an extract.

Full log in previous post.

[John Dowson]

9 minutes ago, Mugz said:

Full log in previous post.

That log was from your crash - I have asked you to activate logging for Lua Plugins and repeat your test and show me an update log for that issue.
The values being logged is a separate issue (and the one you raised this topic for). I see no 'Gear L N R state:...' log lines in the log you previously posted. You are logging the gear state every second - I am interested in seeing the other log statements, to see if these values change once data is received from MSFS.
Its easier for me if you can always attach your full log file, rather than pasting extracts (or even the full log).

[Mugz]

2 minutes ago, John Dowson said:

That log was from your crash - I have asked you to activate logging for Lua Plugins and repeat your test and show me an update log for that issue.

Yes. I disabled my LUA plugins and keep only one Test.lua for get values

[Mugz]

I dont change anything SimVariables. I just read them and writefeature to USB. I post my all LUA's above

[John Dowson]

Can we please look at one issue at a time. It is starting to get very confusing as to what your actual issue is...
So, lets use this topic for your issue with the the wrong values being reported.
So, disable your other luas for now, and lets concentrate on this one issue.
And, for this issue, please show me your full log file, where you start FSUIPC7, your script starts, and then the offsets start to be logged. Let it run for a minute or two, then exit FSUIPC7 and show me the generated log file.
 

...and I don't want Lua Plugin logging activated for this issue. That was for your other issue (i.e. the crash issue) - please disable while investigating this issue .

[Mugz]

Okay. Let's start.

First iteration:
- MSFS2020 is running, FSUIPC is not.
- I'm in World Map menu
- Starting FSUIPC
- Select departure from sky

- Press FLY button
- Can't wait for 2 minutes, because FSUIPC crashed for now and exited.

1st-FSUIPC7.log.7z

[Mugz]

Second iteration:

- MSFS2020 is running, FSUIPC is not.
- I'm in midflight from previous iteration
- Starting FSUIPC
- Waiting 2 minutes
- Exited from FSUIPC

Log from session and SimVars values is attached

2nd-FSUIPC7.log.7z

[John Dowson]

But the log you posted shows that the offsets you are logging held 0

Quote

   141453 LUA.1: Gear L-N-R state: 0 0 0
   141515 LUA.1: Gear L-N-R state: 0 0 0
   141562 LUA.1: Gear L-N-R state: 0 0 0
   141609 LUA.1: Gear L-N-R state: 0 0 0
   141656 LUA.1: Gear L-N-R state: 0 0 0
   141703 LUA.1: Gear L-N-R state: 0 0 0
...

So, is this the correct value? If so, there is no issue with 'read wrong offset value if load in mid-flight', but the crash is an issue.
Could you maybe try disabling the WASM module and test again, to see if that is causing the crash. I will also test here to see if I can reproduce. Also, please show me/attach your FSUIPC7.ini file.

[Mugz]

Third iteration.

- State from previous iteration
- MSFS2020 is running, FSUIPC is not.
- I'm in midflight from previous iteration
- Starting FSUIPC
- Waiting 2 minutes
- Exited from FSUIPC

Log from session and SimVars values is attached

3rd-FSUIPC7.log.7z

[Mugz]

Just now, John Dowson said:

So what is the issue you are referring to? The log does not show FSUIPC7 closing/exiting properly. Did it crash again?

Yes it crashed

 

Just now, John Dowson said:

The log shows the value in the offsets was again 0:

Yes. As i said. If FSUIPC running before i start flight, all work correct. If i start FSUIPC (after crash) in exist session, it's show not correct values.

[Mugz]

ini fileFSUIPC7.ini.7z

[Mugz]

13 minutes ago, John Dowson said:

So, is this the correct value? If so, there is no issue with 'read wrong offset value if load in mid-flight', but the crash is an issue.

Forgive me, I seem to be very bad with the English language, but I really ask you to pay attention to the fact at which moment the incorrect data is given.
Loading steps:
- MSFS2020 -> FSUIPC -> Select the departure in the air -> Press FLY (the data is correct)
- MSFS2020 -> Select airborne departure -> Press FLY -> start FSUIPC (data will be incorrect).

At the moment, I only noticed this for Landing Gear Position.

[John Dowson]

2 minutes ago, Mugz said:

I really ask you to pay attention to the fact at which moment the incorrect data is given.
Loading steps:
- MSFS2020 -> FSUIPC -> Select the departure in the air -> Press FLY (the data is correct)
- MSFS2020 -> Select airborne departure -> Press FLY -> start FSUIPC (data will be incorrect).

Yes, I know - I am looking into it...

One thing you could/should do is delete the contents of the [General] section in your FSUIPC7.ini file and let that get rebuilt, as some of the values need updating. Once you've done this (and ran FSUIPC7 at least once), change back the following parameter:

Quote

ProvideAIData=No

I will look into the offset value issue, when I get a chance...