3.4.4 Deletes iniBuilds A350 Aircraft Profile

[davidcherrie]

If you spent half the amount of time you do as posting needlessly on the forum, GSX would be a really great program.

Yes, you explained a month ago which I never once brought up since that it deleted any files but suggested that the cause must be an incomplete download/installation and hence pointed to your troubles with your CDN which is documented by many users to cause heaps of problems from updates. It is your constant fixation that I think something has been deleted when after being corrected, I have never said again but you keep harping on about.

The error was fixed after doing multiple redownloads of the GSX update 2 days later. I did not update the iniBuilds A350 for this error to take place nor was it updated to fix the issue, I didn't update iniBuilds until after all this happened. The issue occurred from the downloading of GSX 3.4.4 and was fixed after multiple redownloads of 3.4.4 which is why the number one cause would be a CDN issue of an incomplete or corrupted download.

Also just to say, GSX does touch things outside of its folders thanks to GSX Seated Passengers or did you forget this?

Finally, its taken you over a month to say this which is what I have been saying all along...

- A failed GSX update and an eventual possible "fix" could explain the lack of the GSX INTERNAL profile for the A350, because this was added fairly recently so yes, a CDN issue could have caused the lack of the INTERNAL profile

[virtuali]

The error was fixed after doing multiple redownloads of the GSX update 2 days later. I did not update the iniBuilds A350 for this error to take place nor was it updated to fix the issue, I didn't update iniBuilds until after all this happened. The issue occurred from the downloading of GSX 3.4.4 and was fixed after multiple redownloads of 3.4.4 which is why the number one cause would be a CDN issue of an incomplete or corrupted download.

The error wasn't fixed by updating GSX, correlation is NOT causation. Your file was removed from iniBuilds folder for other reasons (NOT by GSX) and it was restored for other reasons too (airplane update, very likely), NOT by GSX.

It's very easy to verify, even right now, your theory is wrong, because what you are saying is:

1) Some version of GSX for some kind of bug REMOVED the GSX profile from iniBuilds package folder by accident. I said this was impossible, you say it happened, I'm saying I believe it happened, but it's in the past, so we can't prove that.

2) You are also saying a GSX update fixed this after multiple tries. This would imply, a GSX update is somehow RESTORING the GSX profile in the iniBuilds package. I said multiple time that NOTHING in GSX writes/removes/restores file in other developers packages and yet you still insist not believing this, But, we CAN verify it now, try this:

- Go into the iniBudils A350 Simobjects folder, and manually remove the GSX.CFG file there.

- Run the FSDT Update.

If your theory that a GSX update "fixed" this, the file you just removed should reappear. If not, it was as I said, you updated the airplane, it restored the GSX profile you lost for other reasons, so it wasn't the GSX update which removed and it was the GSX update which restored it.

[davidcherrie]

I'm going to spend the rest of my life having this conversation.

I'm not saying any file was removed... I'm saying that there was an incomplete download which caused issues with GSX after the update and was fixed by redownloading a day later... The only variable was the GSX update. GSX worked fine with the plane before updating, then after the update, it didn't work so something caused and error and was not operating properly. Then doing a reinstall a day later fixed it. That was the only variable that changed.

[windshear]

I have both the ini A350 and the new PMDG 772 installed, and my GSX for 2024 looks like you can see in the screenshot below, is this normal? I don't have any seated passengers

[virtuali]

I'm not saying any file was removed...

Again ? You TITLED this thread as such!

I'm saying that there was an incomplete download which caused issues with GSX after the update and was fixed by redownloading a day later...

I explained MANY times this would explain the lack of the INTERNAL profile. Not the one in iniBuilds folder, which was clearly missing in your first screenshot: when GSX shows in Red is taking data from Simconnect, it's because the airplane own folder doesn't contain a GSX.CFG file.

[virtuali]

I have both the ini A350 and the new PMDG 772 installed, and my GSX for 2024 looks like you can see in the screenshot below, is this normal? I don't have any seated passengers

Of course it's normal, neither the A350 or the PMDG 777-200 are supported yet.

[windshear]

ok

[davidcherrie]

Again ? You TITLED this thread as such!

I titled the thread that because thats what I initially thought but when you then explained where the default version is... that was over a month ago. So ever since April 6th, I've never said anything was deleted.

I explained MANY times this would explain the lack of the INTERNAL profile. Not the one in iniBuilds folder, which was clearly missing in your first screenshot: when GSX shows in Red is taking data from Simconnect, it's because the airplane own folder doesn't contain a GSX.CFG file.

This is what I've been saying for a month! It was an incomplete / corrupted / not extracted version from the update (not specifically anything to do with the profile) caused the error and was unable to link the aircraft files whether that be apart of the main program or referenced profile. I assume this was due to a CDN issue as a day later, it was able to be installed and work fine...

[virtuali]

I titled the thread that because thats what I initially thought but when you then explained where the default version is...

You kept insisting it was deleted ever after I explained several time a CDN wasn't that. Maybe after realizing that, after all this time, still nobody else reported it, you started to realize that, maybe, the file in the iniBuilds folder might have disappeared (and appeared again) for other reasons.

This is what I've been saying for a month! It was an incomplete / corrupted / not extracted version from the update (not specifically anything to do with the profile) caused the error and was unable to link the aircraft files whether that be apart of the main program or referenced profile. I assume this was due to a CDN issue as a day later, it was able to be installed and work fine...

And for the SAME month, I kept repeating a CDN issue could surely explain a lack of the Internal profile (because support for the A350 has been added recently), but NOT the iniBuilds missing.

I assume this was due to a CDN issue as a day later, it was able to be installed and work fine...

That's the issue: you lost all this time because you "assumed" that and, basically, because you decided not to TRUST my explanation. Something that happens together with another event is not necessarily caused by it. Correlation is NOT causation! It just happened for some reason, but it wasn't caused by the update and it wasn't fixed by the update either (the internal one, yes, it might have fixed by an update).

The whole point of a developer-provided profile (the one in the iniBuilds foder), is that it doesn't NEED GSX to be updated to support the airplane, otherwise we would need to update GSX every new unsupported airplane comes out, which of course is not required.

That goes without saying, that precisely because there's no need to update GSX to support an unsupported update (even before GSX knows anything about it), it's impossible a GSX update would cause a plane with a developer-provided profile to suddenly become "unrecognized" and a further GSX update could "fix" that. If the iniBuild came a year ago, the year's old GSX will still work with it with the iniBuilds profile.

[davidcherrie]

This is a marvelous thread of two brick walls talking to each when they have agreed with each other for the past month.

Again after you explained where the aircraft profile is located, then I said every time after that time that it was a conflict, corrupt, incomplete updated version pointing to CDN issues causing the app to not work properly. I have changed the subject to remove the world delete so you can stop saying I'm insisting it was deleted when I haven't since 4th April.

Again we both agree that the CDN I was downloading from didn't have the complete update and we both agree that a lack of internal profile from this issue could be the cause for either the main program not finding it or for it to be corrupted from the incomplete update.

[virtuali]

Again we both agree that the CDN I was downloading from didn't have the complete update and we both agree that a lack of internal profile from this issue could be the cause for either the main program not finding it or for it to be corrupted from the incomplete update.

That's precisely why I said so many times.

But ALSO always accompanied by the fact that NO CD, NO GSX "corruption" could possibly explain the disappearance of the GSX.CFG file from in the iniBuilds OWN FOLDER.

This is not under discussion, yet not only you titled this thread as such, not only you posted a screenshot clearly showing the file from iniBuilds folder WAS gone, but you took a month just to finally admit that yes, the CDN could have caused a problem with the internal profile so MAYBE, you might try to accept what I've been trying to tell you for such a long time: you HAVE lost the GSX.CFG in iniBuilds profile (your screenshot proves it), but it wasn't due to a "GSX update", it must have been something else, because, again:

- A GSX update couldn't possibly cause the disappearance of that file.

- A GSX update couldn't possibly "fix it"

WE DON'T MODIFY GSX PROFILES GSX FOLDERS!

We DO change something in the airplane folders: .XML exterior to support Seated Passengers, but that's a completely different file, in a different location, and nowhere in the whole GSX code or the FSDT Installer there's anything that acts on developers GSX.CFG files.

[davidcherrie]

Except the only thing that changed was updating from 3.4.3 where it did work and 3.4.4 where it didn't, nothing changed. No iniBuilds updates, no new liveries etc. I understand only edited GSX profiles appear in the folder I attach as a screenshot which I understood now 1 and a half months ago and that it wasn't deleted there.

[virtuali]

Except the only thing that changed was updating from 3.4.3 where it did work and 3.4.4 where it didn't, nothing changed.

You said this so many times. You simply didn't noticed the file was gone for other reasons, that's why you are *sincerely* convinced you "did nothing". Yes, I believe you didn't do anything other than updating but:

- Correlation is NOT Causation. It just HAPPENED you lose the file during an update, it wasn't caused by it, and surely an update CANNOT possibly bring it back!

[davidcherrie]

Except the correlation is the causation in the instance you just described, because it was lost in the update and redownloading that update did bring it back...

[virtuali]

the correlation is the causation in the instance you just described, because it was lost in the update and redownloading that update did bring it back...

And you keep saying that it's precisely what confusing correlation with causation means.

You THINK this caused it, but it just happened for another reason, no matter how many times you repeat it, NOTHING in GSX can possibly remove a GSX.CFG profile from the airplane folder and NOTHING can restore it!

I already told you how to get proof of this, but apparently, you don't want see the evidence, because it will prove you wrong. Try this:

- REMOVE the GSX.CFG from iniBuilds folders.

- Update GSX again. If your theory is right, this should bring back the file you removed, right ? Because that's what you just said it happened.

I'm only referring to the iniBuilds profile, the one in the iniBuilds folder, the one which if it's missing will cause the airplane config page in GSX saying "Data from SIMCONNECT" in RED, as in your first screenshot. How many times I need to repeat that, if you HAVE a GSX.CFG file, it would allow the airplane to show as supported REGARDLESS the GSX version, the updates, or their failure ?

The Red text can ONLY mean the GSX.CFG in the airplane folder is missing, nothing else. So, again, if your theory is right, removing it manually and updating GSX should bring it back.