about error "problem raised by addon <unknown>"

[ACSoft]

Hello,

This is just a feedback which, I hope, might help you to solve a recurrent problem of GSX Pro.

On the occasion updates of my 3 FS2Crew equiped aircrafts, I have tested consecutively these 3 aircrafts after the update. I started with the Fenix A320, no problem with FS2Crew and GSX displayed immediately the menu.

After that, I exit the flight to MSFS2020 menu and I changed my aircraft to FBW A32NX, adapted my Simbrief flightplan and launched again a flight. But this time GSX won't start properly !!!

It may happen that you get an infinite loading of the menu and if you restart couatl it don't solve the problem ! In fact, you hit the error "problem raised by addon <unknown>", even maybe during the flight loading, before to press "ready to fly" (see included images).

To solve the problem, I had to fully exit the flight simulator 2020 and restart it.

[virtuali]

Your error log shows you don't have the latest version, because it refers to an error that has been fixed a few updates ago. The another update CHECK or use the Offline installer.

[ACSoft]

Sorry, but you are wrong, I have the latest version installed.

Look at the image.

[virtuali]

Sorry, but you are wrong, I have the latest version installed.

If I said you don't have the latest update installed, it because it's obvious ( to me, but interpreting the log is not your job, it's mine ) you don't have it.

There have been some hotfixes in the past week or so, so even if the version number is reported to be the latest, if you don't do an update CHECK now, you won't have all the latest files. That's why I asked to do that.

And to cover even the chance your local cloudflare node might not have the latest file, I also added to my suggestion, the additional suggestion to use the OFFLINE Installer, which will surely won't be affected by a possible network replication delay.

So, if you just did what I asked to do (either solution, try the normal update first, then the offline if that doesn't work), it would have solved that error, as I've said it would.

[ACSoft]

Do you realise what you say ?

Personnaly, I always run the offline installer, as a last step, after any version update. It was the case with this 3.5.8 !

So even doing so, I cannot be sure that everthing is OK !!! My good !!!

--------------

OK, I just executed the the Manager "check" function now, followed by the offline installer and I got again an infinite loading (see the picture), but this time, I was able to kill & then, restart couatl without the dead loop on the error "problem raised by addon <unknown>" and finally, the menu screen loaded, after multiple loading info message poped in the menu window.

To resume, the "check" followed by the offline installer seem to have partially solved the problem, but it remain that it is impossible to be sure a version is 100% correctly installed after a Manager update, followed by a systematic offline installer and even a "check". There is not explicit message to tell you that, after these functions and that's a shame.

[virtuali]

Do you realise what you say ?

I surely do, you probably don't.

I always run the offline installer, as a last step, after any version update. It was the case with this 3.5.8 !

First, you didn't say that, so how I could have possibly know you "always" do that ?

followed by the offline installer and I got again an infinite loading (see the picture), but this time, I was able to kill & then, restart couatl without the dead loop on the error "problem raised by addon <unknown>" and finally, the menu screen loaded, after multiple loading info message poped in the menu window.

Let's not confuse two completely different things:

- The ERROR in your previous log will surely gone if you perform an update. If your local cloudflare node is normally updated, it will be gone after a normal update, but if it's not, the Offline installer will surely fix it because, again, that error has been fixed several days ago, and you can be sure the Offline installer contains the fix. Obviously, you must download it again, it's offline, so you can't expect one you downloaded last week would somehow update itself with the fix so, clearly, when I say "Use the Offline installer", always means "Download again the Offline installer now, and install it"

- The infinite loop sometimes happens in MSFS 2020, but it normally goes away if you restart the Couatl engine as explained at Page 97 of the manual and, as that page suggest, don't keep restarting over and over, because after an update (online or offline), it must regenerate the models cache once, so the FIRST start after an update will take longer, and it's normal, and you shouldn't restart before it's done, otherwise you'll abort the model cache creation and you'll force it to restart it from scratch, over and over.

So, just restart and let it load. Normally 15-20 seconds before trying another restart it's ok, but after an update, it might take up to a minute.

[ACSoft]

Ok, I notice all this,but personnaly, I cannot agree neither admit that you may do hidden fix in the current version, including in offline installer, without to change the version No, in order users may be aware of that change.

For the present case, I have now redowloaded the offline installer and effectively, they have different sizes, as you can see on the picture, but both say: Version 3.5.8 – June 22nd, 2025.

[virtuali]

The main reason why we have released several hotfixes without bumping the version, is because we are trying to fix this problem:

https://www.fsdreamteam.com/forum/index.php/topic,33441.0.html

Once this will be fixed, the version number would be increased. Clearly, being the offline installer an "offline" installer with no capabilities of updating live (it's offline!), you must download it every time there's an hotfix. Again, you don't have to wonder there is an hotfix, I just said that:

There have been some hotfixes in the past week

So, when I say that, it means:

- Download the offline installer AGAIN

- Install it.

But that's not really the point.

The point is the Offline installer is a BACKUP method to use ONLY if you are sure the Online update failed (because of network replication delays), you should ALWAYS try Online first (that's why I listed them in that order) and the Offline ONLY if the online fails. In your case, if you still got the same error after performing a normal Online CHECK.

[ACSoft]

I am not your beta-tester ! 

If you want to proceed the way you describe, please open a beta branch that user can choose to joint or not.

By the way now, I have run again Manager CHECK, followed by the execution of the last offline installer and, for your infomation, I still get the infinite loading. Fortunately, a RESTART Couatl allow to break the dead loop.

[virtuali]

If you want to proceed the way you describe, please open a beta branch that user can choose to joint or not.

We already did that.

Due to network replication delays, some users are still seeing stuff in the Beta channel that don't exists anymore anywhere on our server, but cloudflare has cached for them, even if we purged the whole domain many times. So the beta channel should be reserved for really major changes that requires a long period of testing by many users.

By the way now, I have run again Manager CHECK, followed by the execution of the last offline installer and, for your infomation,

So the ERROR which was subject of this thread, was gone exactly as I initially suggested ? I was quite sure of that...

I still get the infinite loading. Fortunately, a RESTART Couatl allow to break the dead loop.

That's a whole different issue, for which we'll have a fix soon.

[ACSoft]

So the ERROR which was subject of this thread, was gone exactly as I initially suggested ? I was quite sure of that...

Of course, Umberto, you known things that we , the users may not known, even when they have updated correctly to the last version and even more than that, by security, systematically executed the offline installer as the last update step  !

The fact that the version we use may be already obsolete, because FsDreamTeam has aready made some "secret fixes", eventually mentionned in a forum thread you do not follow, is not very professional to my humble opinion !!!

If I were you, I would introduce in the Manager, a notion of build reference No, that the program can check, to verify if you have the last build of the current version installed. Take the example of the open alpha Star Citizen. you often have update with a new build, during the life of a specific version.

[virtuali]

If I were you, I would introduce in the Manager, a notion of build reference No, that the program can check, to verify if you have the last build of the current version installed. Take the example of the open alpha Star Citizen. you often have update with a new build, during the life of a specific version.

We already have that, and it's the version number. But we control when to change it.

But that's not really the point. What the CHECK button does, is verifying the Checksum of each and every file of your installation, because this is the ONLY way to be sure you really have the latest version. Because checking "just" the version number (you can call it "build number", it's the same), will only ensure you have the latest version of the manifest.json file, nothing else), only a proper check which is what the Check button does will ensure a proper installation of the latest files.

That of course if your local cloudflare node won't play tricks on you, by serving an outdated version of the file. This is not THAT common, but it's the reason why we have an Offline installer.

[ACSoft]

This does not change the fact that, I have no easy way to know if the actual version received some fixes. A comparison with a build reference number would do it. This is what I was thinking about. Checking the integrity is something different.

[virtuali]

This does not change the fact that, I have no easy way to know if the actual version received some fixes.

That's the version number. Again, we decide when to bump it and I already explained why we decided NOT to bump it THIS TIME.

A comparison with a build reference number would do it. This is what I was thinking about.

"build reference number" is just another way of calling the version number we already have, see above.

[ACSoft]

Of course it is the same, but apparently YOU fell the need to add sometimes fixes without to change the version number.

Can-you understand  that I feel the need to always know, from the Manager app, if the actual available version has changed ?

Finally, do whatever you want with your horrible version management system, I give up.