By Robert Lee 1421859
#533766 Each time the simobjects of my Prepar3D are changed such as adding a new scenery, the advanced model matching section selects ALL simobjects again. Each time it scans for changes I have to go to settings and select only the simobjects I want active, in my case FLAi. I suggest to make it so vPilot does not default to selecting all simobjects after a change is detected since there is no reason for my SODE SimObjects to be selected as part of AI model matching. Thanks.
By Ross Carlson 887155
#533767 It should be retaining your selections (and de-selections) when the scan is repeated, so if it's not, there must be a bug. I will look into it.
By Robert Lee 1421859
#533773
Ross Carlson 887155 wrote:It should be retaining your selections (and de-selections) when the scan is repeated, so if it's not, there must be a bug. I will look into it.

For me every time it shows "scanning new simobjects" on start-up I go to the model matching settings and all selections are checked. It is with changes to SODE simobjects every time that happens. And before the changes only FLAi was selected. Thanks. Bob
By Robert Lee 1421859
#533851
Ross Carlson 887155 wrote:This is fixed in version 2.2.3, which is currently available in the Beta updates channel. Can you test it out?

Installed a new scenery that added its own SimObjects and when vPilot scanned for new changes, it checked the box for that simobject but remembered my checkbox settings for all others. Is this how it is working now? Will still need to uncheck each new simobject box when installing new scenery.
By Ross Carlson 887155
#533863 Yeah, new sinobjects are enabled by default so that if you install a new model set you don't have to manually enable them. (This is how it has always worked.)

You don't need to worry about disabling non-aircraft scenery objects ... vPilot isn't going to try to use them for model matching aircraft.
By Robert Lee 1421859
#533867
Ross Carlson 887155 wrote:Yeah, new sinobjects are enabled by default so that if you install a new model set you don't have to manually enable them. (This is how it has always worked.)

You don't need to worry about disabling non-aircraft scenery objects ... vPilot isn't going to try to use them for model matching aircraft.

Thank you! Bob