FSDreamTeam forum
Products Support => GSX Support MSFS => Topic started by: davidcherrie on April 04, 2025, 02:26:02 pm
-
iniBuilds A350 aircraft profile is not existent in 3.4.4.
-
You don't say which simulator you are using. I tried it in 2024, and it works.
-
2020 and 2024. Does it matter what simulator? Looks like your CDN is failing you.
-
2020 and 2024. Does it matter what simulator?
Of course it does, the airplane is located in completely different folders, both the airplane itself, and the
Looks like your CDN is failing you.
Not sure what you screenshot of your custom profiles folder has anything to do with this or how you relate it to a CDN issue. Your custom profile folder is not supposed to contain anything about a certain airplane UNLESS you start customizing it.
The iniBuilds A350 is internally supported by GSX AND it comes with its own profile in the airplane package, which means:
- It's normal you don't have anything about the A350 in the %APPDATA% folder, things will appear there only if you customize the airplane or download a profile shared by somebody. We never install *anything* there with our installer EXCEPT airport profiles for FSDT airports, nothing else.
- Even if your GSX was outdated, suggesting a possible CDN issue, in the worse case you would be missing the Internal profile, which sets up a few specific things which are not possible to set with a normal profile but, the airplane would WORK and would be IDENTIFIED thanks to the profile supplied by iniBuilds.
So, your screenshot seems to indicate as if the airplane was completely unknown, with no GSX profile, no developer-provided profile and no user-made profile, which is very strange.
Which is why, I asked the simulator, because I only checked 2024 and there it works, now you said you use both, I'll check 2020 too.
-
After doing another install of GSX, the aircraft profile is back. Your CDN is failing you because you release updates however the updates that get downloaded are missing files and have further problems hence why you have so many people complaining that your updates don't work.
-
After doing another install of GSX, the aircraft profile is back. Your CDN is failing you because you release updates however the updates that get downloaded are missing files and have further problems hence why you have so many people complaining that your updates don't work.
It's not a failing CDN, it's the incredibly strange way the file management system he wrote works. It treats anything that doesn't pass his checks of files that should exists as "hostile" and removes it, forcing us to keep a repository of "Things The FSDT Installer Deletes" so we can replace them back once updating is done. It's been like this since P3Dv4 and it's just as annoying now.
-
It's not a failing CDN, .
You are both wrong, let's deal first with the "CDN is failing you first" claim, which I already explained, but apparently my explanation wasn't clear enough, so let's try again:
- The GSX internal profiles are stored in the \Addon Manager\couatl\common\AircraftDb.pye file. Let's assume the "CDN is failing" and for some reason, it served a version older than the first time we added the iniBuilds A350 in version 3.3.7 released Feb 28th. What would happen in that case ? GSX would have used the profile supplied by iniBuilds, which is stored in the AIRPLANE own folder, and we DO NOT TOUCH THAT!. The airplane configuration page would have shown a "developer-provided profile" instead of the internal profile.
So, the only possible way one would end up with NO profile at all would require the following TWO conditions, all happening at the same time:
1) Having received a version AircraftDb.pye file older than Feb 28th. Since we had several updates after that, I find this unlikely, but I guess it might be possible.
2) Having removed the profile supplied by iniBuilds as well, maybe because at a certain time, the GSX internal profile was newer/better.
It's not possible a completely "unknown" airplane page would show UNLESS BOTH these conditions happened at the same time. This thread started with "3.4.4 Deletes iniBuilds A350 Aircraft Profile", which surely doesn't, we surely don't touch the airplane own installation folder, and the iniBuilds A350 surely come with a GSX profile.
it's the incredibly strange way the file management system he wrote works. It treats anything that doesn't pass his checks of files that should exists as "hostile" and removes it, forcing us to keep a repository of "Things The FSDT Installer Deletes" so we can replace them back once updating is done. It's been like this since P3Dv4 and it's just as annoying now
- The installer surely removes anything that doesn't belong to the standard installation, but you are omitting the key issue here: it doesn't it ONLY in ITS OWN folders. If it's not entirely clear what this means, I'll try to make it as clear as possible:
1) The installer will NEVER remove anything you customized or downloaded, like airplane profiles or airport profiles. NOTHING under %APPDATA% is ever removed by the installer. These are your preferences, so the installer obviously follows the standard practice that none of the file you created or added are removed in your preferences folder.
2) The installer will NEVER remove anything in other developers folders! Like airplane or airport profiles that come with that developer products (airplane or airport).
THe FSDT installer will ONLY operate on everything that is inside its own folder, that is the main Addon Manager folder. This is the installation folder, and you are not supposed to touch anything there, and this is not strange or weird: it's the ONLY way to ensure you can screw up with files and being always able to go back to a working situation. It's not "incredibly weird" either, is EXACTLY the same function of the "Check Integrity" on Steam, for example. The main install folder is not a place where you are supposed to touch things.
Now, before say "but I want to modify some GSX files" with some custom settings. You still can do that, using better methods, and the installer will never touch these changes, for example:
- You can change the operator and model assignment rules using custom rules files which will override stock rules file, without having to touch these. GSX Manual has a whole chapter on Pages 100-103 explaining how they work.
- You can create new set of vehicles using an EXTERNAL PACKAGE. This is a Package that can be stored in the Community folder and can contain new vehicles, liveries, and custom rules. These packages won't be touched by the installer either.
-
Happens again...
-
Not only it doesn't happen here, but GSX never removes anything from folders outside its package so, even if for some reason you had an outdated GSX internal profile, the airplane would WORK with the one supplied by iniBuilds.
So, no matter the reason why the iniBuilds profile disappeared from inbuilds own folder, you can be sure it wasn't GSX or the FSDT installer that removed it.
-
It's obviously a problem with GSX since its the program... It isn't a new livery downloaded nor was it after an update of the aircraft. You just load in sometimes and there is no profile.
-
It's obviously a problem with GSX since its the program...
And again, it's not "obviously" a problem with GSX, because as I've said already, GSX never removes anything from folders outside its package so, even if for some reason you had an outdated GSX internal profile, the airplane would WORK with the one supplied by iniBuilds.
-
Except nothing changed... I updated GSX to the latest version and for some reason the profiles aren't there. If the only thing that changed is GSX, why do you think your program isn't the problem? Another CDN issue again?
-
GSX, why do you think your program isn't the problem? Another CDN issue again?
Because as I've said, multiple times, it will never, ever, remove anything from folders outside its own (=iniBuilds in that case) so no, it's not a CDN issue, because it never did that and it surely doesn't do it now.
-
Then why don't they work after updating GSX?
-
Then why don't they work after updating GSX?
It works here. You said it happens in both MSFS 2020 and 2024, this is from 2024.
-
Thank you showing me that it is working on yours but do you ever contemplate that issues not on your computer may appear on others for reasons you may not have foreseen? Or is it always the users fault?
-
Thank you showing me that it is working on yours but do you ever contemplate that issues not on your computer may appear on others for reasons you may not have foreseen?
And it's precisely why I cannot foresee those, which I can't give you any further explanations than those I already have. If I know what's causing the problem on your system, I would have told you so.
Because, AGAIN, if it was "just" a problem of GSX not updated (CDN issues), you wouldn't see the GSX internal profile, but the airplane would use the profile from iniBuilds. Which, again, GSX will NEVER, EVER touch. Nothing outside GSX own folders is ever touched in any part of the GSX code, this is not under discussion.
Or is it always the users fault?
I never said it was "your fault". On the contrary, you seem to be convinced it's GSX fault, when the fact is:
- It doesn't happen here.
- Nobody else reported this.
-
The reason I bring it up because every single time someone points out something to be a bug they are getting it is always "It doesn't happen here, no one else has reported it". Rather than investigating any bug that a user may come across you dismiss it as they have must have done something as to why it's not working problem. Never encounter support anywhere with that kind of service except here Umberto.
This issue occurred after an update of GSX, the problem resolved itself when downloading again. This isn't a conspiracy or anything but as a software developer, you have to admit the problem was caused by your own update and fixed by the next so it has to have been something corrupt in the download or how it has extracted into the program that has caused GSX not link to existing files. It can't be anything else other than GSX being faulty.
-
it is always "It doesn't happen here, no one else has reported it".
And have you seen anything that contradicts these two statements ? You might not trust my screenshot but, have you seen other reports about this other than yours ? Do you think you are the only one using GSX with the A350 ?
Rather than investigating any bug that a user may come across you dismiss it as they have must have done something as to why it's not working problem
And what you think is starting the sim, trying to replicate what you are reporting and posting a screenshot showing it doesn't happen, other than investigating ? Let alone spending my time always replying to this thread.
Never encounter support anywhere with that kind of service except here Umberto.
That's exactly the opposite. You are getting the best support possible because, not only I fully explained you why this cannot possibly happen unless there something external to GSX, and I spent time investigating and confirming the problem doesn' t, but I also haven't insulted your intelligence like "other support" might have done, by saying "we'll investigate this", which is a codename for "never".
Instead, I gave you the proper service, by ensuring you the problem is not GSX, so you can proceed in the correct way, like finding why there's no GSX profile anymore in the iniBuilds folder.
It can't be anything else other than GSX being faulty.
By keep repeating this, you are just losing your time. I'll repeat it again, for the last time:
- If GSX was outdated, this would explain the lack of seeing the A350 Internal profile.
- But NOTHING in GSX can possibly explain the lack of the profile inside the inibuild's own folder because, again, GSX will never, ever, touch anything in the airplane own folder.
Of course, if you posted a diagnostic log, I might say something more about it. GSX will take the airplane folder from Simconnect so, a problem there might cause the airplane to be reported as something else, or not at all.
-
At any point did you suggest trying to redownload GSX... which is usually the first kind of support any one looks to because something may have happened during an update? The equivalent of technical support defaulting to turning it off and turning it back on again. I pointed this to be another example of the CDN but instead of you saying "sometimes these things happen when downloading updates and installs" but instead you have gone onto explain over and over again it couldn't have possibly been anything to do with GSX.
Then after I said that after having redownloaded GSX, it is working as normal, you continue to go on that it couldn't possibly be GSX to blame despite the issue being caused by an update and the fix being a redownload of that update. Very obvious that something happened in the download, extraction or installation phase right? Or we still going down the path of sticking our heads in the sand because the CDN issues that many people have because they download your updates before your CDN has fully got everything it needs to that update. Don't you see how that could affect the program? That maybe the profile was still there but something that the updated depended on wasn't downloaded because of the CDN issue and caused the program to not find the profile?
Just because you decide to spend massive amounts of time replying to users how it could possibly not be GSX fault isn't productive nor helpful to the end user.
-
At any point did you suggest trying to redownload GSX... which is usually the first kind of support any one looks to because something may have happened during an update?
Again with the CDN ? You still not getting the point, which I made many times ? Let's try again:
- A CDN issue or any other reason why GSX might be outdated, will ONLY explain a lack of the GSX Internal profile for the A350, because you were stuck with an old version made before support was added to it.
- A CDN issue or any other reason why GSX might be outdated CANNOT be explained in any way not the failure to read the GSX.CFG file in the iniBuilds own folder! This is how users create profiles for airplane not included in GSX!
Just because you decide to spend massive amounts of time replying to users how it could possibly not be GSX fault isn't productive nor helpful to the end user.
What was productive or helpful was my last suggestion, which you have ignored:
GSX will take the airplane folder from Simconnect so, a problem there might cause the airplane to be reported as something else, or not at all.
As you ignored my other suggestion to post a diagnostic log, which would show this. So, where is it ?
-
Well the problem was created by an update and fixed subsequently with a redownload where it happened again on another aircraft and fixed by another redownload.
Issues don't just happen out of the blue when the only variable that changed was the program was updated yet alone fixed by with multiple redownloads. Can't blame another program for that but I'm sure you continue to in your reply.
The fact there was an issue but you say its impossible yet it happened so we are just going around in circles. Reason I haven't posted a diagnostic cause it was fixed 2 versions ago so don't have the logs anymore... But maybe instead ask for the logs rather than dismissing users saying "no it doesn't, mine works". Of course yours works, but we are the ones continually downloading updates which have problems that manifest so maybe be more productive and you can get to the bottom why? Majority seems to be your CDN with missing packets.
-
well since your the only one by the looks of it that has this issue, if you would have sent the logs in as was asked to, maybe the issues would have been found
-
well since your the only one by the looks of it that has this issue, if you would have sent the logs in as was asked to, maybe the issues would have been found
I guess we will never know. But until then, it isn't GSX's fault it ain't working properly after an update.
-
well since your the only one by the looks of it that has this issue, if you would have sent the logs in as was asked to, maybe the issues would have been found
I guess we will never know. But until then, it isn't GSX's fault it ain't working properly after an update.
than when it happens again send the logs in
-
The fact there was an issue but you say its impossible yet it happened so we are just going around in circles.
We are running in circles only because you keep ignoring my suggestion which I already posted twice, to post your log when this happens. You are still the one and only with this, so YOUR log is even MORE useful because, even if you refused to provide it, if the problem happened to anybody else, we would have seen a log from somebody by now.
-
We are running in circles only because you keep ignoring my suggestion which I already posted twice, to post your log when this happens. You are still the one and only with this, so YOUR log is even MORE useful because, even if you refused to provide it, if the problem happened to anybody else, we would have seen a log from somebody by now.
I think you have lost why I posted this in the first place as the obvious reason to the issue was the download/installation to further point the issues with your CDN.
Plus the logs no longer exist as I said because your log writes over itself every time you launch Couatl... maybe date your logs so they don't overwrite important information you are trying to get from users?
-
I think you have lost why I posted this in the first place as the obvious reason to the issue was the download/installation to further point the issues with your CDN.
You lost when you failed to read what I posted multiple times that, the removal of a file in the A350 own folder cannot possibly be caused or explained by any CDN issue because again, for the last time, GSX will NEVER, EVER touch files outside its own Addon Manager folder.
Plus the logs no longer exist
But if the problem can be repeated, it shouldn't be a problem getting a new log.
-
You lost when you failed to read what I posted multiple times that, the removal of a file in the A350 own folder cannot possibly be caused or explained by any CDN issue because again, for the last time, GSX will NEVER, EVER touch files outside its own Addon Manager folder.
I'm not saying it deleted a file. Something in the update that was incomplete from downloading that made GSX cause this error. Just like the heaps of other issues that get reported after updates that turn out to be CDN issues because they have not received all of the update.
But if the problem can be repeated, it shouldn't be a problem getting a new log.
Have you not read anything? The issue was fixed on the 6th of April with redownloading GSX. You didn't ask until 23 days after the issue was fixed before you mentioned anything about sending a log. This is the best example of lack of support when issues arise. You spend 90% defending your software as if its under a personal attack when you should be doing the first thing about asking for logs and asking for the specific circumstances that it happens in rather than touting a month saying "IT CAN'T HAPPEN" when it has.
-
I'm not saying it deleted a file
You titled this thread saying that! And your posted screenshot of the airplane configuration page confirmed it: when you took it, you had NO iniBudils profile, so that's probably why you assumed GSX deleted it.
But you kept insisting it was GSX, even after I said multiple times that, whatever GSX is doing, it CANNOT affect a file in the iniBuilds folder, and even if I had to repeat, you kept insisting with "the CDN"
Something in the update that was incomplete from downloading that made GSX cause this error. Just like the heaps of other issues that get reported after updates that turn out to be CDN issues because they have not received all of the update.
Again ? How many times I need to repeat that, the disappearance of the iniBuilds-supplied GSX profile CANNOT in ANY way, be caused by a failure to update GSX ?
Have you not read anything? The issue was fixed on the 6th of April with redownloading GSX.
You seem to fail to understand what I write, assuming you even read it. Like your constant fixation with the fact a profile can possibly disappear from the airplane folder because of a GSX update. It JUST CAN'T, this is not open to discussion.
And now, you are making another assumption: you think that updating on April 6th "fixed" this. It hasn't or, more precisely, it wasn't the GSX update that "fixed" it, it must have been just a coincidence. IniBuilds released an update on April 4th so MAYBE, you also update the airplane, and that restored the missing profile which was gone for OTHER reasons.
Again, for the last time, GSX doesn't touch ANY files outside its own folders, it never did that, ever, so NO CDN issue can possibly cause this.
You didn't ask until 23 days after the issue was fixed before you mentioned anything about sending a log
Shouldn't be common knowledge that sending a log should the one of the first things to do ESPECIALLY when it was clear (and still is), your problem was unique to you, because as of today, you are still the one and only who reported it.
This is the best example of lack of support when issues arise. You spend 90% defending your software as if its under a personal attack when you should be doing the first thing about asking for logs and asking for the specific circumstances that it happens in rather than touting a month saying "IT CAN'T HAPPEN" when it has.
This is the best example of twisting the meaning of what I say. I don't doubt your lost the iniBuilds profile, you surely have and your screenshot proved it and nowhere I ever said I don't "believe" it happened.
But even if it clearly HAPPENED, that doesn't automatically mean "GSX deletes iniBuilds A350 Aircraft Profile", which is the title you decided to give to this thread. Now, I fully understand that, before hearing my explanation, you might have reasons to assume it was GSX that delete the profile, your problem is that you keep insisting it did, even after I explained to you it couldn't possibly be caused by a GSX update or a failure to complete it.
Again, don't you think if GSX really deleted a profile in the airplane folder, we would have seen OTHER reports by now ? And by saying this, I'm not saying "it didn't happen", I fully believe it happened to you, but it wasn't GSX or the update, it must have been something else, antivirus, files system issues, anything but GSX.
I'll make it clear for the last time ( I hope )
- 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
- NONE of this can possibly cause the disappearance of the developer-provided profile, which is located in the airplane own Simbjects folder inside the airplane own package, something GSX will NEVER write to.
-
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
-
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.
-
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.
-
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
-
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.
-
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.
-
ok ;)
-
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...
-
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.
-
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.
-
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.
-
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.
-
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!
-
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...
-
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.