- Thu Feb 25, 2016 8:29 pm
Ryan Parry 965346 wrote:Could you explain how the scanning and model matching works a little better in regards to a custom rule set having precedent over the scanned one? Are you saying it will create one no matter what, but try to pull matching from the custom set first and then the scanned set?
That's right, if you have custom rule sets loaded, vPilot will look for a match in your custom rules first, before looking at the rules that it generated as a result of scanning your installed models.
Ryan Parry 965346 wrote:If so, could you include an option to turn that off completely, please? I don't want vPilot scanning my system, that's one of the things I hated about FSINN.
Why did you hate that feature? I can't say for sure since I never used FSInn, but I suspect you'll find that vPilot's scanning of your models is very unobtrusive and infrequent. The scan only happens in one of three circumstances:
1) You run vPilot 2.0 for the first time.
2) vPilot detects new folders in your SimObjects paths. (Meaning new models have been installed.)
3) You trigger it manually, such as if you want to use a different simulator on the same machine.
Ryan Parry 965346 wrote:I really enjoy the current method of model matching and I have spent a tremendous amount of time incorporating an insane amount of detail into my ruleset, I really don't want any interference with that.
Since the custom rules will take precedence, nothing will change for you. All the time you've invested creating custom rules will continue to pay off with version 2.
Ryan Parry 965346 wrote:I see where this could be beneficial to some though, so I think an option to disable it would be smart.
It's too early to tell, of course, but I suspect you are in a minority in this regard. Most users just want model matching to be automatic. That's why I'm making this change to begin with. I must resist the temptation to add features that are only helpful for a small number of users ... that path leads to bloatware and/or confusing user interfaces.
That being said, disabling the automatic rule generation would be pretty simple, code-wise, and very low-impact, UI-wise (just a checkbox in the settings) so it wouldn't be a big deal. However, you're basing your request for disabling the scanning on your negative experience with FSInn, so my inclination would be to determine whether or not you would have the same dislike for this feature in vPilot as you did for FSInn. So if you could elaborate on what you hated about FSInn, that would be very helpful.