Acars ending flight automatically

[cdtssgtbradshaw]

Every other flight I do when you land with Autobrakes it ends the flight on rollout. 

[MattW]

I have kind of the same error. But it doesn't need autobrakes for me. Sometimes ACARS simply ends the flight after touch down and while taxiing to the ramp. Haven't found any pattern here yet other than it happens pretty much directly after touch down. Might have something to do with the ruleset and how it is enforced? I'll try to play around with the rules and see if I can find out something.

Edited November 7 by MattW

[DisposableHero]

4 hours ago, MattW said:

I have kind of the same error. But it doesn't need autobrakes for me. Sometimes ACARS simply ends the flight after touch down and while taxiing to the ramp. Haven't found any pattern here yet other than it happens pretty much directly after touch down. Might have something to do with the ruleset and how it is enforced? I'll try to play around with the rules and see if I can find out something.

 

Most probably it thinks the parking brakes are set (some simulators and aircraft report back braking as parking brake unfortunately). Try enabling the engine shutdown requirement for on block / arrival checks. (Admin > vmsAcars > Settings), maybe it helps.

 

 

If this fails, we may need to wait for v2 to be in beta state for a wider range of tests, then we can track it if it continues

 

Safe flights

[DisposableHero]

More info for future checks ;

 

https://docs.phpvms.net/acars/user-guide#flight-phases

 

"End Flight" and automation for it is possible after landing, during taxi in and at arrived states. There may be a bug in v1 code (worst case)

 

[MattW]

1 hour ago, DisposableHero said:

 

Most probably it thinks the parking brakes are set (some simulators and aircraft report back braking as parking brake unfortunately). Try enabling the engine shutdown requirement for on block / arrival checks. (Admin > vmsAcars > Settings), maybe it helps.

 

 

If this fails, we may need to wait for v2 to be in beta state for a wider range of tests, then we can track it if it continues

 

Safe flights

 

Good idea, but that option (engine stop) is already activated in my setup, and i can safely say that the auto-ending happens anyway.

[DisposableHero]

Ok, thanks for the feedback @MattW strange that I never had it but this definitely looks like something to focus on with @Nabeel

 

I saw similar reports with v1 in which the "arrived clicked" was present in acars logs for no reason, hopefully we will not have it with v2.

[MattW]

Unfortunately vmsACARS is becoming increasingly unreliable. I haven't found out what exactly the reason is, but about half of all flights I did the last few days end prematurely in ACARS, pretty much directly after touching down.

Additionally it doesn't seem to like landing outside of a regular runway. I've created a tour for my VA where people have to land on a small island names Grimsey north of Iceland (https://maps.app.goo.gl/LTuqS61v5tNMyLni7)

Of course I did the tour myself first to test it, and immediately after touch down on the ground (which is not registered as airfield in MS) ACARS again ended the flight. It's starting to get a little bit frustrating overall...

Edited Saturday at 11:02 PM by MattW

[DisposableHero]

18 hours ago, MattW said:

Unfortunately vmsACARS is becoming increasingly unreliable. I haven't found out what exactly the reason is, but about half of all flights I did the last few days end prematurely in ACARS, pretty much directly after touching down.

Additionally it doesn't seem to like landing outside of a regular runway. I've created a tour for my VA where people have to land on a small island names Grimsey north of Iceland (https://maps.app.goo.gl/LTuqS61v5tNMyLni7)

Of course I did the tour myself first to test it, and immediately after touch down on the ground (which is not registered as airfield in MS) ACARS again ended the flight. It's starting to get a little bit frustrating overall...

 

Even though development ended for v1 series of vmsAcars, I would kindly suggest you to upload your logs as described here. Maybe they will give us some clues and they can be checked against during v2 alpha releases. (Like trying to re-create the same conditions, same aircraft, same airport etc.)

 

Best wishes,

[MattW]

affirm, i'll do that next time it occurs

[MattW]

The forum anti spam artificial stupidity drove me nuts right there.

Tried to post a log extract inline as code. Wouldn't let me post, says it's spam.

Tried to shorten the extract and remove redundant lines. Wouldn't let me post, says it's spam.

Tried to attach a txt file, wouldn't let me, only images allowed.

Tried to post regular text without attachment, wouldn't let me, because I've tried too often, wait a couple minutes.

Didn't say HOW MANY MINUTES.

Tried again after a couple minutes (like 4-5), wouldn't let me, because I've tried too often. Wait a couple more minutes.

Tried again like 15 minutes after that. Still blocked.

 

For crying out loud. What kind of ungodly chastisement is this?!

 

Anyway. I put a log extract here to download. https://www.icefireair.com/assets/ifa/files/log.txt 

The log contains lines with "11-12 22:30:37|INFO; Arrived clicked", I didn't click anything, vmsACARS ended the flight on its own, prematurely, while I was still taxiing.

 

All ACARS rule violations were deactivated, by the way, to have the least possible friction.

 

Apart from that: You said, the current version of vmsACARS wasn't supported anymore. But it's still being sold. That doesn't necessarily build much trust towards future versions, really. There may be reasons why support for v1 ended, but then I wouldn't sell it anymore until v2 is out. Or state CLEARLY on the product page, that the software isn't supported anymore but a new version is being worked on and the buyer will, through buying the old version, help accelerate the development of the new version. Or something. Anything.

 

Edit: adding infos about my equipment for debug reasons:

* MSFS 2020 on Windows 11

* FSUIPC 7 (latest version)

* Logitech G Yoke (no drivers, works out of the box)

* Thrustmaster T-Flight Pedals with latest drivers from Thrustmaster (but no Target software)

Edited Wednesday at 07:19 AM by MattW

[ProAvia]

While I don't speak directly for the developer of vmsACARS (who is also the developer of phpVMS) - I wouldn't say support for vmsACARS v1 ended, but further development of v1 has stopped. Likewise, minor fixes for issues in v1 are unlikely as v2 is presently in the alpha phase. Hoping v2 sees beta phase soon. V2 isn't stable enough for production use at present.

 

The issue you have experienced in v1 has only affected a very small number of users. But we do need input on the issue - as @DisposableHero indicated - to check it against the v2 alpha releases.

 

As for the anti-spam, it's a necessary evil. It can be a pain at times.

 

[MattW]

Well, being the grumpy old man I am, for me support has effectively ended if there won't be any more development to fix issues. I guess the reason probably is a lack of capacity if phpvms/vmsacars is a one man side project show, but for the customers affected by bugs the reasons do not really matter, and it's unsatisfactory, as you can imagine. After all, we paid for the software without getting a clear hint that there wouldn't be any support. Maybe I should have become wary at the no-refund-clause.

Anyway, I'll help however I can. Are there similarities between the small number of users in terms of setup or software? Did it happen to X-Plane users or only MSFS?

[DisposableHero]

35 minutes ago, MattW said:

Well, being the grumpy old man I am, for me support has effectively ended if there won't be any more development to fix issues. I guess the reason probably is a lack of capacity if phpvms/vmsacars is a one man side project show, but for the customers affected by bugs the reasons do not really matter, and it's unsatisfactory, as you can imagine. After all, we paid for the software without getting a clear hint that there wouldn't be any support. Maybe I should have become wary at the no-refund-clause.

Anyway, I'll help however I can. Are there similarities between the small number of users in terms of setup or software? Did it happen to X-Plane users or only MSFS?

 

Nobody told you that "support" is ended, that is your own conclusion  I told you that "development ended for v1 series" and this is not something to stop sales or support. We are testing v2 series and it is "hopefully" near to being released (best kind of support, is an improved new version) as "beta" (at least stable to be a beta and to see how many more bugs will be found by a wider range of users), so no need for being a grumpy old man

 

When it gets to beta, you can download it and use as you wish, but also you can stick with v1, nobody will stop you doing that but the best support you will get for it will be "please upgrade to v2" because nobody will go back to an old code, fix it and release again while a new version is out and live

 

And please until v2 gets released to public (as beta) be patient.

 

11-12 22:30:37|INFO; Arrived clicked
11-12 22:30:37|INFO; Moved into on block
11-12 22:30:37|INFO; Flight ended manually on taxi on

 

Since you did not shared the entire log, I need some more info;

 

* Which sim was this ? (MSFS, XP11, XP12, Prepar3D, Fsx)
* Which aircraft was in use ? 

* Which airport you landed ?

 

Safe flights.

[MattW]

Point taken, everyone's view on the support matter is clear, no sense in arguing any further for me.

 

Sim is MSFS

Aircraft was C208 GC EX

Airport was BITO

 

Thanks.