On a second leg, when inserting TRIP FL at PERF INIT page, gizmo crashes

[vinileite]

I did a search but found nothing about this bug below.
On a second leg, when inserting TRIP FL at PERF INIT page, gizmo crashes and needs clear and reboot (Boolean error). 

[Litjan]

Thanks for the report!

I will try to recreate this so we can find and fix it - do you happen to have a screenshot of the error message or the GizmoLog.txt file?

Thanks, Jan

[vinileite]

18 hours ago, Litjan said:

Thanks for the report!

I will try to recreate this so we can find and fix it - do you happen to have a screenshot of the error message or the GizmoLog.txt file?

Thanks, Jan

Jan, where i can find Gizmo Log's? It's inside XP root folder? I can't find any gizmo log file to upload, but i'm attaching an screenshot with my XP's log file here to a better look or understanding into this:

 

PS: This aircraft is a masterpiece, Jan! Here in Brazil we have some still flying for freighter logistics contracts, but they are slowly being replaced by the NGs BCF.

Log.txt

[Ben Russell]

GizmoLog.txt was retired. All info is reported in log.txt

[Litjan]

Thanks for the screenshot and the log.txt. Ben is right, the error can be found in the log.txt - this will help in finding and fixing the problem.

Greetings to Brazil, I fly to SBGR once in a while, but I would imagine that the classic 737´s hang out in Viracopos?

Bom dia, Jan

[tkyler]

On 10/2/2023 at 7:40 PM, vinileite said:

On a second leg

Do you mean a second flight?   after landing and then putting new information into the CDU? for a next flight (2nd leg?)    Or literally "the 2nd leg of a flight plan route you are currently flying"?

Thx.

[vinileite]

Quote

after landing and then putting new information into the CDU? for a next flight (2nd leg?) 

Exactly! After finish a flight and start another in sequence (without any reload), always when inserting the cruise FL at INIT page.

[Litjan]

9 minutes ago, vinileite said:

Exactly! After finish a flight and start another in sequence (without any reload), always when inserting the cruise FL at INIT page.

Thanks for confirming that - I will replicate this tomorrow and give Tom detailed reproduction steps.

[Litjan]

I have tried to replicate this problem - but was not successfull. For me this works as expected (no error).

Since you are the only one reporting this so far, there is the chance that you do something very unique to trigger this error, I doubt that it is interference from another plugin (although flywithlua and volanta are known to cause problems sometimes).

If we can not get to the bottom of this, one solution would be to trigger the "reboot gizmo" function (right-side pop-out menu, the small "flash" symbol) to reset the logic for the second and subsequent flight...

Cheers, Jan

 

[vinileite]

On 10/16/2023 at 5:50 AM, Litjan said:

I have tried to replicate this problem - but was not successfull. For me this works as expected (no error).

Since you are the only one reporting this so far, there is the chance that you do something very unique to trigger this error, I doubt that it is interference from another plugin (although flywithlua and volanta are known to cause problems sometimes).

If we can not get to the bottom of this, one solution would be to trigger the "reboot gizmo" function (right-side pop-out menu, the small "flash" symbol) to reset the logic for the second and subsequent flight...

Cheers, Jan

 

Hmmm, good to know about Volanta interference.

 

 

No problems, Jan! Cheers!

[dr_anthony]

+1 had same problem in second flight. Gismo crashes on fl enter on init ref page

[Litjan]

Thanks for the report - I am still trying to replicate it.

The gizmo problem said: Number expected, boolean received or something to that effect. Do you remember what you entered for cruise flight level? Did you enter FL240 or was there maybe a character still in the scratchpad (maybe a "space" that was not visible)?

[dr_anthony]

Confirmed, Jan!  It's Flywithlua problem. In my end. Without it plugin all works fine. I used beta of FWL

[Litjan]

7 hours ago, dr_anthony said:

Confirmed, Jan!  It's Flywithlua problem. In my end. Without it plugin all works fine. I used beta of FWL

Thanks for reporting back on this!

[dr_anthony]

Oh, no. Its happend again. I tested it near field, flying in circuit. But in flying from one field to another it happend again. All plugins are off. Try in to enter 330 to trip fl window. Going to crz page causes another gizmo error.

[dr_anthony]

It alows enter trip FL on CLB page, but with no effect on altitudes on legs page. And when trying to switch to init ref page, it crashes 

Edited November 17, 2023 by dr_anthony

[dr_anthony]

And if gizmo not crash, pos init page on 2nd cdu stays blank 

[dr_anthony]

Gizmo not crashed, when destination apt near departure apt (aprox 100-200 nm), when more, it crashes. Its not an another plugins, twice checked

Edited November 17, 2023 by dr_anthony

[Litjan]

You are entering the cruise altitude on the CLIMB page??

[berilojr]

4 hours ago, Litjan said:

You are entering the cruise altitude on the CLIMB page??

Can't answer for him but in my case it is in perf page and having the same issue, just made some circuits and didn't happen in this case. I don't know if it is time, distance or just the flow of the use of the code that at some point tends to brake it but it is happening a lot.

Edited November 18, 2023 by berilojr

[dr_anthony]

5 hours ago, Litjan said:

You are entering the cruise altitude on the CLIMB page??

It possible to enter cruise altitude on CLIMB page with no effect on altitudes on legs page. In this case gismo not crashes. When i enter cruse fl on perf init page as it should be, it crashes.

[dr_anthony]

"Can't answer for him but in my case it is in perf page and having the same issue, just made some circuits and didn't happen in this case. I don't know if it is time, distance or just the flow of the use of the code that at some point tends to brake it but it is happening a lot."

You god dam right )

Edited November 18, 2023 by dr_anthony

[Litjan]

Ok, guys, thank you for the additional information - I will try to recreate the problem on my side so we can fix it.

For now - after you finished one flight - maybe hit the "reboot Gizmo" option (right side pop-out menu) before you start the second flight. That should help with avoid the crash.

Thanks again, Jan