December 1, 20223 yr Commercial Member 13 minutes ago, AnkH said: So, that is why all those addon publishers have a constant flow of users running into issues because of their totally bad update process. No wonder forums are full with issues that turn out to be modified files of an installation, NOW I understand /sarcasm off. I think I explained quite clearly why, for other kind of applications, when the most of the code is in the "main" gauge or the "main" .EXE, it's might be less necessary to achieve full fault tolerance of all files to have a reasonably working product. Sure, you might have a texture representing a passenger set in a cabin corrupted, but it might be hardly noticeable, and the product will still work. That might not work as easily for GSX, since we don't always update the executables, and the whole GSX logic is inside files that are not real executables, so they don't support the native Windows versioning, meaning they need to be hashed and checked individually. Not just that, if the GSX operator rules, for any reason doesn't match with the actual Simobjects variations installed (maybe a variant is missing, or just the SIM.CFG if not updated), GSX will crash when trying to create an object that is supposed to be there. And before you say "can't you check if an object exists before trying to create it", that would of course require rescanning the whole Simobject folder at each start, to be sure all files are there. Basically, doing at each start (in the sim) what the updater is already taking care of, the full integrity of everything. Edited December 1, 20223 yr by virtuali Umberto Colapicchioni http://www.fsdreamteam.com FSDT on Facebook
December 1, 20223 yr Commercial Member 8 minutes ago, chickster25 said: But your reliable button doesn't tell me if I need to update or not- I have to run it just in case there is a button and I dont know if it did update or not because it takes just as long. Are you even following this discussion and reading my replies ? As I've said, multiple times, this is an issue of getting an update NOTIFICATION, it doesn't have anything to do to the way the update is then PERFORMED. Please re-read my last reply, in which I already confirmed, several times, that adding a better way to NOTIFY you if an update is available, can surely be added, without having to change the whole concept of a fault-tolerant update. Until then, you have another button, the "Release notes", which lists all the latest update dates, so you have a way to know when you need an update, we only need to automate this, to provide a more obvious notification. Edited December 1, 20223 yr by virtuali Umberto Colapicchioni http://www.fsdreamteam.com FSDT on Facebook
December 1, 20223 yr Author 2 hours ago, virtuali said: adding a better way to NOTIFY you if an update is available, can surely be added, without having to change the whole concept of a fault-tolerant update. Would be great -thank you-. And thank you also for taking the time to provide help outside your forums! Gerald K. - Germany AMD 7800x3D / ASUS ROG X670E-Gaming / ASUS Strix RTX 3090 OC / 64 Gb RAM GSKILL. "Flightstick" = X56 HOTAS RGB Logitech
December 1, 20223 yr I love GSX but believe me when I say this….you are never going to get Virtuali to agree with anything you say. 😂😂😂 Thomas Derbyshire
December 1, 20223 yr Commercial Member 1 hour ago, sidfadc said: I love GSX but believe me when I say this….you are never going to get Virtuali to agree with anything you say. In fact, I'm disagreeing with you right now, since it should have been clear from my replies, that I AGREED to do something to make the update method easier to understand, namely the notification system. Umberto Colapicchioni http://www.fsdreamteam.com FSDT on Facebook
December 1, 20223 yr 35 minutes ago, virtuali said: In fact, I'm disagreeing with you right now, since it should have been clear from my replies, that I AGREED to do something to make the update method easier to understand, namely the notification system. 🤪 Thomas Derbyshire
Archived
This topic is now archived and is closed to further replies.