Auto Drive Command Disabled

[AdvancedApproach]

Why is the auto drive command not usable in maximize performance mode but works just fine in compatibility mode? I'm talking about <kuid2:192081:4:5>.

 

[paulper]

My understanding is that switching from "maximise compatibility" to "maximise performance" can cause script errors. I certainly tried this mode but soon switched it back

 

[AdvancedApproach]

My understanding is that switching from "maximise compatibility" to "maximise performance" can cause script errors. I certainly tried this mode but soon switched it back

How would that cause the rule to not be accessible at all though? I'm having a hard time figuring that part out.

 

[p-dehnert]

With "maximise compatibility" some old, now obsolete scriptfunctions are still allowed. "Maximise performance" requires the use of the new, often async, functions. One function requiring the new methods, which is used by the Auto Drive Command, is GetTrackMarkList.

Peter

 

[AdvancedApproach]

With "maximise compatibility" some old, now obsolete scriptfunctions are still allowed. "Maximise performance" requires the use of the new, often async, functions. One function requiring the new methods, which is used by the Auto Drive Command, is GetTrackMarkList.

Peter

For me it doesn't work under the maximize performance option.

 

[p-dehnert]

It doesn't work, because it uses obsolete functions, which are not allowed with "Maximise performance".

Peter

 

[pware]

"Maximise Performance", as I have always understood it, is a developer only option and is not intended for use by general users. My advice, stay away from it.