Driver Command Error in TS2010

[Sean_Gwynn]

Hi All,

Hope someone can help me out with a problem I am having with TS2010.

When I try to edit the driver commands, to add any additional rules e.g. WaitUntilTime, UnCouplez, etc, I get the following error:

Error: PropertyBrowserRefresh() not handled.
A script error occurred while attempting to edit the properties of this asset.

As the stock driver commands in TS2010 are pretty limited, can anyone help me out?

 

[Dap]

Even in 2009, not all driver commands were available in Surveyor. They were initially designed to be used in Driver and some of the early commands like WaitUntil are only available in Driver. I beleive the WaitUntil command is being updated and should be on the DLS shortly.

The upshot is this: To support driver command in surveyor rule edit mode, you need to support null driver parameter, which needs a special tag in the config file and several modifications in the code.

I'd suggest you email the creator of the rule you want updated and ask the author to do the fix or get permission to make the corrections.

 

[TheStoon]

Hi All,

Hope someone can help me out with a problem I am having with TS2010.

When I try to edit the driver commands, to add any additional rules e.g. WaitUntilTime, UnCouplez, etc, I get the following error:

Error: PropertyBrowserRefresh() not handled.
A script error occurred while attempting to edit the properties of this asset.

As the stock driver commands in TS2010 are pretty limited, can anyone help me out?

This happens because you have a driver rule installed (although not necessary in use) which has an error - you must check ALL the driver rules - and their dependencies - you have installed in CM and correct any errors or delete the broken rules.

 

[Sean_Gwynn]

Thanks for the help. :Y:

Had deleted any rules I had installed that were faulty, but still had the problem. I then realised that I hadn't checked any scripts installed. Found a couple of these that CM was showing faulty and deleted them. This worked a treat, as I can now edit the driver commands in surveyor.

:clap: :clap: :clap:

 

[AndrewofWare]

This happens because you have a driver rule installed (although not necessary in use) which has an error - you must check ALL the driver rules - and their dependencies - you have installed in CM and correct any errors or delete the broken rules.

I have the same problem. How do I check the driver rules (and their dependencies) in CM, which I presume is Content Manager?

 

[itareus]

How do I check the driver rules (and their dependencies) in CM, which I presume is Content Manager?

In Content Manager set the filter to:

Faulty = true

Category = rules

OR

Category = scripts

(the above is from memory - I may not have got this exactly right - just experiment).

This should then list just the faulty rules/scripts. Right click on one to view errors & warnings or to view dependencies.

 

[pcas1986]

In Content Manager set the filter to:

Faulty = true

Category = rules

OR

Category = scripts

(the above is from memory - I may not have got this exactly right - just experiment).

This should then list just the faulty rules/scripts. Right click on one to view errors & warnings or to view dependencies.

I have the same problem as well. I've tried the filter
Faulty = true
and
category = rule (and script as well)
and
location = local

But I'm not finding any errors.

My understanding was that the scripts are only run when the asset is loaded by the session. Thats when I get the error.

I'm guessing that the error is in a script for a 3rd party asset that I am using. So my next step is to snapshot my route and test session and start eliminating assets that might be suspect. There are a couple of log files in the game directory that might be of some use for debug purposes.

Paul

 

[itareus]

....My understanding was that the scripts are only run when the asset is loaded by the session. Thats when I get the error........I'm guessing that the error is in a script for a 3rd party asset that I am using.

Hi Paul,

I believe there are two different problems here. The OP was talking about Driver Commands / Rules and supporting scripts which could not be added. This is usually due to a faulty (command type) rule / script being in use and can be solved by deleting the faulty rules / scripts as noted in earlier posts.

Your problem with an assets script is, I think, slightly different. If you would like to post full details of the error you are getting we might make some sense of it.

Note: It is not uncommon for assets to be wrongly categorised (e.g. Rules not shown as Rules). It may well be worth going into CM3, listing all you Faulty assets and having a quick visual scan down the list to see if your earlier searches have missed any.

Cheers

 

[pcas1986]

Hi Paul,

I believe there are two different problems here. The OP was talking about Driver Commands / Rules and supporting scripts which could not be added. This is usually due to a faulty (command type) rule / script being in use and can be solved by deleting the faulty rules / scripts as noted in earlier posts.

Your problem with an assets script is, I think, slightly different. If you would like to post full details of the error you are getting we might make some sense of it.

Note: It is not uncommon for assets to be wrongly categorised (e.g. Rules not shown as Rules). It may well be worth going into CM3, listing all you Faulty assets and having a quick visual scan down the list to see if your earlier searches have missed any.

Cheers

Actually I had a couple of errors, one of which was the error reported in the original post (i.e. trying to add commands available for the driver). The other error was being reported as an error relating to saved consists.

The discussion in this thread suggested there was a problem in a script somewhere and, in my case, it turned out to be the QuickDrive rule. When I removed it from the session the errors disappeared and I can now add rules for the driver.

I think QuickDrive is a user contribution and I cannot remember why I had it in the list anyway. It doesn't seem to be needed for what my session is currently doing.

All the searches I did for faulty assets were for locally installed stuff. I haven't downloaded much so far from the DLS for TS2010. I did delete some assets for problems with meshes but AFAIK I wasn't using any of them. My conclusion is that the faulty indicator in Content Manager is only detecting problems with building (displaying?) the asset and not for scripts. But I could be wrong

Anyway this thread indirectly solved my problem so I'm happy with that. I've been chasing this issue here and in other threads since before Christmas.

To reiterate my errors:

The first was when the session was loaded. The thread dump seemed to be reporting that there was a problem initialising an asset in a saved consist and the exception was output by QuickDrive.

The second (like the OP) was the inability to add rules available to the driver (Options Menu).

When I removed QuickDrive both problems were solved!

Cheers
Paul

 

[celje]

waituntiltime

After installing 09 the rule WaitUntilTime don't work anymore in 06 and now after 10 all three edition have the same problem. Assigning rule don't open hour and minute. In CM2 and CM3 rule have not any error. I tried to delete them and install again but problem still remain.

celje

 

[JCitron]

After installing 09 the rule WaitUntilTime don't work anymore in 06 and now after 10 all three edition have the same problem. Assigning rule don't open hour and minute. In CM2 and CM3 rule have not any error. I tried to delete them and install again but problem still remain.

celje

What kind of errors are you having? The fact that this is happening is indicative that you maybe doing something incorrectly. Each install works seperate from the other so there's no reason why all should not work.

John

 

[celje]

As i said, it's impossible to set hour and minute and if i click on rule he disappear.
Maybe Atilabarut will be so kind and look this rule.

regards

 

[celje]

JCitron, i'm sorry, i forgot that this rule need Inputtable.

Years, years, years......