"Error setting Client Data Calculator Code" when using execCalcCode

[Fragtality]

  On 11/27/2023 at 6:19 PM, John Dowson said:

Can you test with the main window open - I would like to know if the UI responds when you get this hang/freeze.

Expand  

It does not response any more (Windows displays even "No Response" in the Windows Title)

 

  On 11/27/2023 at 6:19 PM, John Dowson said:

You access the logging console via Log->Open Console. This shows a real-time view of the FSUIPC7.log file. I would like to know if messages are till logged after the freeze, so keep that open.

Expand  

That is interestingly still active, but seems to be stuck in a Loop. (Like in previous Logs)

 

 

Logs.zipFetching info...

[John Dowson]

Ok - that log shows that there is an issue with the lvar values lock/mutex:

  Quote

   203000 17556  [DEBUG]: # Requesting lvM lock...

Expand  

That lock us never obtained. This looks to be due to successive config updates being received before the previous one is fully processed. Hopefully this is corrected in the attached version.

Any issues, can you attach the log file again - maybe two copies, one the file when you get the hang, and again after you have killed/stopped FSUIPC7. Thanks.

John

FSUIPC7.exeFetching info...

[Fragtality]

  On 11/28/2023 at 11:42 AM, John Dowson said:

Ok - that log shows that there is an issue with the lvar values lock/mutex:

That lock us never obtained. This looks to be due to successive config updates being received before the previous one is fully processed. Hopefully this is corrected in the attached version.

Any issues, can you attach the log file again - maybe two copies, one the file when you get the hang, and again after you have killed/stopped FSUIPC7. Thanks.

John

FSUIPC7.exe 661 kB · 2 downloads

Expand  

Looks promising after a quick Test, Thanks! 🙂

[John Dowson]

  On 11/28/2023 at 2:47 PM, Fragtality said:

Looks promising after a quick Test, Thanks! 🙂

Expand  

Great! Thanks for all your help tracking this one down!

I will release a new beta tomorrow, as a full installer (including WASM + updated documentation). The additional log messages I added for this will be removed, and input parameter values will be logged correctly. Please update to this version once released.

I will probably release this version officially the following week, if no other issues are reported.

Cheers,

John

 

[John Dowson]

  On 11/25/2023 at 5:06 PM, Fragtality said:

Even though my Tools don't have a Problem with that (they're designed to be even started before the Sim): Would it be possible to have an additional RunIf Option in the Future - maybe let's call it "PROC" or so. It would start the given Program when SimConnect is ready to process.

Expand  

The next beta release, 7.4.0b, which will be released tomorrow, will allow for an additional parameter for [Programs] section entries: CONNECTED. This will delay the start of programs until FSUIPC is connected to MSFS (via SimConnect) and has received the initial data to populate the offsets.

John

[John Dowson]

  On 12/5/2023 at 4:35 PM, John Dowson said:

The next beta release, 7.4.0b, which will be released tomorrow

Expand  

Now released...a bit early....!

[Fragtality]

  On 12/5/2023 at 4:35 PM, John Dowson said:

The next beta release, 7.4.0b, which will be released tomorrow, will allow for an additional parameter for [Programs] section entries: CONNECTED. This will delay the start of programs until FSUIPC is connected to MSFS (via SimConnect) and has received the initial data to populate the offsets.

John

Expand  

Hmm, I see no Difference with the new CONNECTED compared to READY - the Programs are only loaded after Read to Fly was pressed 😕

[John Dowson]

  On 12/5/2023 at 9:52 PM, Fragtality said:

I see no Difference with the new CONNECTED compared to READY - the Programs are only loaded after Read to Fly was pressed

Expand  

Are you sure that you are using the latest beta release, 7.4.0b? Please check this as your browser may have cached the download file.

If that is not the issue, please show me your .log and .ini files...

John

[Fragtality]

Hmm, the ini reports "UpdatedByVersion=7400b" and the changes.txt reflects the new Parameter. Everywhere I look tells me I have the Bravo-Version 🙂

 

FSUIPC7.iniFetching info... FSUIPC7.logFetching info... FSUIPC7_prev.logFetching info...

[John Dowson]

  On 12/6/2023 at 5:08 PM, Fragtality said:

Hmm, the ini reports "UpdatedByVersion=7400b" and the changes.txt reflects the new Parameter.

Expand  

Good, I was only checking...

I see you are using RunIf. I haven't tested with this - I will check this and update if needed....

John

[Fragtality]

Ah! Yeah found it to be more reasonable to have it that way ^^

I'll cross-check with Run in the meantime 😉

[John Dowson]

Your log also shows lots of other errors which are rather worrying.... There is an SDK update with the latest release to SU14 last night/today. I am currently in the process of updating to the latest SDK and will make a new release when done and tested, hopefully tomorrow.

John

 

[Fragtality]

  On 12/6/2023 at 5:30 PM, John Dowson said:

Your log also shows lots of other errors which are rather worrying.... There is an SDK update with the latest release to SU14 last night/today. I am currently in the process of updating to the latest SDK and will make a new release when done and tested, hopefully tomorrow.

Expand  

 Uh oh 🤔

 

Using "Run" does not work either. Programs were only started after Ready to Fly was pressed.

[John Dowson]

  On 12/6/2023 at 5:35 PM, Fragtality said:

Using "Run" does not work either. Programs were only started after Ready to Fly was pressed.

Expand  

I don't understand this at the moment... it was all working as expected when I tested this. I will test further and let you know when an update is available.

Quite a few issues with the latest SDK. Pain in the ass... xmas lunch today with quite a bit of wine. I will look into this tomorrow 😉

John

[John Dowson]

  On 12/6/2023 at 5:39 PM, John Dowson said:

Using "Run" does not work either. Programs were only started after Ready to Fly was pressed.

Expand  

No programs are started now here, with Run or RunIf. It looks like the latest update has broken quite a few things. I have a lot of work to do tomorrow...

[John Dowson]

Everything is working as expected here today, with both Run and RunIf. Not sure what happened yesterday, strange...

Anyway, I have just released a new beta version re-compiled against the latest SDK. Please update to that and re-test. Any issues, please attach your files.

John

[Fragtality]

Totally strange ...

Still the Programs are only started after Ready to Fly was pressed. This time it even forgot to start one Program (Fenix2GSX).
But it can start the Programs without Problems with the old READY before and now with DELAY=60 🤔

FSUIPC7.logFetching info... FSUIPC7.iniFetching info...

[John Dowson]

Looks to be a timing issue between two threads, hopefully fixed in the attached if you could try it. I have also updated the beta download to include this version.

John

FSUIPC7.exeFetching info...

[Fragtality]

YES! 😃

Okay, I only quickly fired the Sim up and did not really looked when exactly the Programs where started. BUT, when the Sim was in the Main Menu, the Programs were started.

FSUIPC7.logFetching info... FSUIPC7.iniFetching info...

[John Dowson]

The DELAY option with CONNECTED wasn't reliable in the previous version, corrected in the attached.

John

FSUIPC7.exeFetching info...

 

[Fragtality]

Oh, never combined them. I used either DELAY or CONNECTED - but good to know ^^