I agree that it is buggy and I'm shocked that N3V would include it in the service pack.
Why are you shocked? It is a beta of the service pack and how else are they going to test this new feature?
I currently have the TRS19 SP1 beta, the non-Plus version, and the Driver/Surveyor combined edit feature is disabled in my SP1 beta but it is enabled in the TRS19 Plus SP1 beta for those who have opted to pay the $8 (US) per month. From what I understand, the SP1 final retail release will include the code for the "Edit Driver" option that will only be active in those TRS19 installs that have it. From a distribution point of view, this makes perfect sense - one SP1 package ("One Ring To Rule Them All") and not multiple different SP1 versions -but it is an added complexity that would have to be beta tested to death.
On another note, I am curious about the
Restart Rule feature that appears in the Session Editor when editing saved Driver Games. I fully understand its purpose (to reset a completed session rule in the edited Driver Game to its initial condition) but I am puzzled as to how this will work with rules that control variables.
To give an example - the
Variable Modify Rule which can add or subtract a value from that stored in a variable (e.g. add 2 to the value stored in a user created variable). To reset this rule the code will need to remember what value was stored in the variable
before the rule was executed. The code wizards at N3V, I am sure, would have already considered this but as a session creator who often makes use of variables I would just like to be reassured.
