FSDreamTeam forum
August 21, 2019, 03:00:49 AM *
Welcome, Guest. Please login or register.

Login with username, password and session length
News:
 
   Home   Help Login Register  
Pages: [1]
  Print  
Author Topic: DONOTUPDATE logic  (Read 213 times)
Dimon
Sr. Member
****
Posts: 461



« on: August 13, 2019, 03:04:38 PM »

Is there any FAQ how to deal with it or some sort of practical example?

Thanks
Logged

[email protected], Z170 Delux, 980Ti-6GB5700, 2TB EVO850, 16GB DDR4 RAM Win7/64 PRO.
virtuali
Administrator
Hero Member
*****
Posts: 35504



WWW
« Reply #1 on: August 13, 2019, 08:16:39 PM »

No, because I'm firmly against it, so it's intentionally undocumented, hoping only advanced users that know *exactly* what they are doing will use it, so we won't lose effort to support someone that didn't fully understood where and how to use the DONTUPDATE feature that would report a problem that happened only because he placed that file everywhere and prevented our updater to do its job.

It's not so difficult: every folder that has a file named like that, will be skipped by the updater. What's in the file doesn't matter. The type of the file doesn't matter. The size of the file doesn't matter. The only thing that matters is the name so, it can even be an empty file.

If you just want to protect your AFCAD modifications ( which is also something we don't suggest, because we can modify them at any time, and they usually *must* go together with a GSX customization ), don't use the DONTUPDATE method, because AFCADs will be overwritten only on request and a backup will be made.

Don't use the DONTUPDATE, except in *exceptional* cases. And even in these cases, it would be much better if you simply told us which kind of modification you made and we might consider adding it as a permanent fix.
Logged

Dimon
Sr. Member
****
Posts: 461



« Reply #2 on: August 13, 2019, 08:30:00 PM »

I'm more worrying AFCAD modifications. With all due respect FSDT is a way far behind in terms of proper coding, taxiways allocation, parking types and radiuses and too many other small items to mention. I'm not blaming anyone, just suggesting to leave that area to the users (if they want to)
Logged

[email protected], Z170 Delux, 980Ti-6GB5700, 2TB EVO850, 16GB DDR4 RAM Win7/64 PRO.
virtuali
Administrator
Hero Member
*****
Posts: 35504



WWW
« Reply #3 on: August 13, 2019, 11:07:23 PM »

I'm more worrying AFCAD modifications

Then you don't need the DONTUPDATE at all, as I've said.

Quote
With all due respect FSDT is a way far behind in terms of proper coding, taxiways allocation, parking types and radiuses and too many other small items to mention. I'm not blaming anyone, just suggesting to leave that area to the users (if they want to)

Are you referring to old sceneries ? Because, all our recent sceneries have proper coding, proper taxiway allocation, proper parking types and proper radiuses and, in fact, the reality is exactly the opposite and, while working on GSX, we found most of the problems you are reporting, are happening with *other* sceneries, which are full of error.

And "far behind" compared to what ?

To what other scenery developers do ? I don't think so, just have a look at the GSX sharing forum how many things Cartanya have to fix in *other* sceneries.

To what you could do by yourself ? In this case, if you have something to say about an FSDT AFCAD, please post it in its appropriate section, indicate each and every problem, post your considerations on why you think it's wrong, and we'll go through them, one by one, fixing what really needs to be fixed.
Logged

Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!