Logbook Version

[Eryn]

Howdoes the Steam version work in that respect? I imagine it like other a Steam titles with 3rd party DRM. You buy, and download on Steam, then when the game launches you log in to your Ubisoft account, or whichever.

I do know there have been a lot of complaints from people that had tried out the game pass version and bought all sorts of aircraft and scenery and even the Deluxe or Premium upgrade while on gamepass and then for some unknown reason bought the full version with a new MS login and new gamer tag and lost all their addons and upgrades they purchased.

Yes I logged in with the same Microsoft account and Xbox gamer tag, but I think it makes sense for both versions of the game to have separate cloud data, at least to track the achievements on each platform.

There is absolutetely ZERO there.

No record of me owning the game (despite having to login using their service daily)

No record of any of the transactions made using their microsoft credits, through their in game marketplace.

No record of game progress, achievements, hours logged etc.

And the worrying thing is that it appears that Steam does not log items purchased through the marketplace either. It logs that I had to buy and then spend microsoft credits (through Steam) but it does not list the items I have purchased.

However, this is exactly what is happening with the current version of MSFS on Xbox (1.18.15.0) and it makes the game simply unplayable, unflyable. This is a major problem and one that will happen to you sooner or later.

The situation is quite comparable to what happened with Cyberpunk 2077 at Sony, and if Microsoft had as much courage as its competitor, it should purely and simply temporarily withdraw this title from its store.

What exactly is going on?

For the third time in less than a month of use, my logbook has been completely erased (with loss of 10 hours, 25 hours and 40 hours of flight respectively). This is not acceptable, especially since it happens regularly and under clearly identified circumstances.

I myself, opened a zendesk ticket #118094 and a forum topic in the bugs section. This major issue has also been discussed here.

In what case does this happen?

Often times, Xbox Live servers are saturated evenings and weekends. This is a known issue, and it is very difficult to play on Xbox (not just MSFS) during these times. There, we easily understand that it is the influx of users that saturates the servers.

During the day, however, I never have any problems connecting to the Xbox live servers.

When this happens in the evening, there are several disconnections and reconnection attempts.

I am an experienced simmer, I started with the version of Sublogic on TRS-80 and used all existing versions on PC. I also spent an incalculable time on IVAO in simulation on network.

I resolved to use the Xbox version, because I wanted to avoid investing in a high-end PC, only for MSFS, and I believe that in the end, it is certainly the best choice that I have made.

No way to edit logbok on XBOX.

Note that there is a similar issue with FLT files: on XBOX, you have no way to delete them, and this (very, fundamental) function has been forgotten by the MSFS developpers.

This really demonstrate the poor level of quality of this game.

On PC, you have the advantage that you can sometime overide the bugs, using external tools. On XBox, you cant do that. And now, all the previous bugs (and more precisely, all that have been baddly implemented) appears, and there is no way to surround them.

as I can read on the forum (e.g. here), other users are also frustrated with never knowing what a new update brings, sometimes breaking features that have worked. There are reported issues with memory leakage of the app (e.g. here) and not responding apps (e.g. here, and here).

Anyhow we know the story. I recently went to my range just to find that the latest update (2.12.3) completely broke my setup and I was not able to record any shot. Only a complete removal of the app and the bluetooth connection settings as well as a new install and pairing (that was three hours I could have practiced golf) made it work with the result that the app always told me

That window is now there all the time and I can't use the app (and the R10) on the range. So I had to roll back to 2.11.3 to make it work again. Also with a complete de-install, re-install, bluetooth de-pairing, re-pairing routine. I also have checked if that app uses too much memory, but it does not, so it is most likely a bug in the software when the unity 3D landscape is used.

Maybe you all want to join in and maybe Garmin-Cody can join in as well and do the least of customer service and release a version history (A PROPER ONE!!!) so that we can keep track of what happens. This is interesting for us users (see here) and its outrageous that there is only the same old generic "whats new" text in the app store.

I recommend completely removing the APK unauthorized backdated version of the app you mentioned installing, with a full removal from storage, and then power cycle the Android device, and reboot so the changes to storage reflect adequately...then reinstall to get the new 2.12.4 update for GGA for AndroidOS which should sort out any crashes, or issues you were previously experiencing.

As you're probably aware, Garmin does not recommend our users to backdate to a previous version for any Garmin application...as a matter of safety, as we do not offer credible backdate options for any of our apps.

The R10 firmware does not change, so these issues are 100% in the Garmin Golf App, and release after release comes with new issues. And the answer is not to revert to a working version but to wait for a fix?

Thanks Garmin-Cody for the fast reply.I have installed version 2.12.4 from the play store directly and this version works very well. Huge improvement over previous versions with respect to stability and performance.

First off, I can confirm, version 2.12.4 does work again! I just hit a few balls into my net at home and if works. There are major (!!) improvements with respect to stability and performance. The golf sim part (virtual driving range and such) has never worked so smooth and responsive for me, so some things must have changed under the hood. Which ones we do not know.

Which brings us to the main problem. After what I have just experienced (the updates 2.12, 2.12.1 through to 2.12.3 stopped me from using the R10 for a couple of weeks). Now after the latest update I de-activated the auto-update for Garmin Golf. Today I will test the app at the range and if it performs well and does all I want, then I see NO reason to update the app. Especially not knowing what comes next.

Regarding the comment of Garmin-Cody on reverting to a older version I just want to say this. Well Garmin leaves us no choice. When app updates continuously break the core functionality of the app (The R10 was useless) we can only roll back to an older version. For me I have a clear understanding of possible security issues, but I understand the safety concerns of Cody. Everybody is responsible on their own for what apps they install from where.

You see Garmin, point #3 is really the issue. What I am left with is that I could not train Golf with recording my stats for several weeks, just to end up with an app where I am not sure what changed and why. The latest version 2.12.4 is indeed better so I congratulate Garmin on that. But what did versions 2.12.1 2.12.2 and 2.12.3 do in the meantime. Could you not have tested everything better and just released 2.12.4 now, basically going from a functional app to a better functional app?

I do not agree that the question has been answered, that is why I have rejected your answer suggestion. If you look at the initial post and the following thread we (at least odd tore and myself) have at least asked for:

Checked version 2.12.4 yesterday at the range and can confirm that it works also on a long session very well. Definitely a version to archive as a working one, at least with respect to the virtual driving range part.

Our devices in the beta program for outdoor wearable products have a detailed outline of the changes for the developmental software leading to the public versions of software for those products specifically, here within the forums.

The change log listed for updates to the Garmin Golf app, along with the Garmin Connect mobile app, and other Garmin apps offered for iOS and AndroidOS do not outline every single change we made...as this is commonplace for the update description outlined on the download page for many app developers.

I am sure you and Garmin do/does not mind that we keep posting to this thread version numbers that work for us users and version numbers which break functionality. Especially as you state that Garmin does not intend to

However, I am certain you and Garmin do/does understand that it is important to us users to have a functional system (App and R10) every time we go practicing golf. Thus we are interested in keeping track of versions which work as intended for the product we bought from Garmin.

This is not the case. Our terms of service prohibits users from providing links to external sites, especially links that instruct other customers to use our products in a manner that is not support by Garmin.

The links we referred to is Garmin Golf App. It's not software not supported by Garmin, it is Your own product. The only reason we as users have to use other sites is because You don't offer this service Yourself. All of us would be very happy if You gave access to earlier (and new) releases on Garmin web site. Then we would not have to be worried about downloading and installing tampered versions.

Another external link that is "banned" is a useful program developed by a forum user. This program only uses the exported files Your golf app provides. How can a program using an exported file not be considered as supported? If I want to use this file in Excel, do I need Your permission to do so, or is Excel not considered as supported reading text files?

3a8082e126