3.4.4 Deletes iniBuilds A350 Aircraft Profile

[davidcherrie]

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?

[virtuali]

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.

[davidcherrie]

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.

[virtuali]

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.

[davidcherrie]

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.

[virtuali]

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 ?

[davidcherrie]

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.

[pete_auau]

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

[davidcherrie]

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.

[pete_auau]

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

[virtuali]

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.

[davidcherrie]

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?

[virtuali]

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.

[davidcherrie]

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.

[virtuali]

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.