Duplicate Scenario GUID

[JustRight]

Hi All,

Whilst attempting to resolve SBHH errors on my system with rosgar's latest mega scenario, I ran LogMate to have a look at what was going on.

The first thing I found were heaps of errors saying: "Duplicate Scenario GUID in SerializeDatabase"

I recall Mike Simpson mentioning something about all GUID's having to be unique across all Routes now, but as usual LogMate gives you no idea just which GUID is duplicate. Has anyone here come across this, and found a way of simply identifying the offending scenarios?

Cheers.

[chrisreb]

Sorry no - i gave up with the scenario after 20 mins of swapping DT carriages and loads more to do. Goodness knows which DT ones this uses as I have tons and tons of coaching stock including loads from DT.

[JustRight]

I should point out that it is probably not rosgar's "Canadian in Newcastle" scenario that is duplicate here. More likely some old scenarios created before RSC made this global unique restriction on scenario GUID's. I'm just trying to find a 'simple' way to identify the culprits. I wonder if Mike Simpson has done anything in RWTools that might be able to analyse all the scenario GUID's and identify the duplicates?

Also, I get heaps of messages like the following in Log Mate: "DT\DT_4MT_loco\latecrest_4iron\engine\4mt_steam_engine.xml" missing node "bo01wh02". For a variety of stock from DT, xxx, and RSC.

Does anyone know what the 'Missing Node' error is trying to say?

Cheers.

[gptech]

bh01wh02 would be "bogie number 1, wheel number 2", could be a missing texture or an incorrect reference in the .bin file.

[scefhwil]

Hasn't that "bo01wh02" error always existed since Railsimulator days? I had always thought it was because that node name is one of the special ones that is automatically animated and represents the second axle on a bogie.

http://www.railsimdownloads.com/wiki/ti ... t=bo01wh02

The error arises for loco's with only one axle on a bogie (ie 2-6-0 engines, like the 4MT?) because the sim is looking to automatically animate something that doesn't exist.

[AndiS]

I am pretty sure this is the message you get whenever you use a default 7F. It is with us since day 1 and RSC never found it worth fixing, so it should not be important.

For the duplicate scenario IDs, I guess the fastest would still be stepwise elimination of causes. Move half the routes to a safe place, see how much duplicates are left. Either move some back (if there are no duplicates left), or move away half of the remaining half. And so on.

Within the routes, you apply the same nasty procedure to the scenarios.

In practice, this is best combined with some detective work like "Which routes feature very early scenarios that were cloned?" or "Which scenarios did I download from people who may not use RW Tools for scenario duplication?" It was always possible to simply duplicate the folder containing a scenario, the rename the clone, but make no further adaptation. If the resulting duplicate GUID now is interpreted as error, people may not have realised that earlier. And maybe if you only have one such duplicate in your installation, you never know unless you fire up LogMate (which few scenario creators will do).

[gptech]

Wouldn't it be easier just to give "A Canadian in Castle" a new GUID ?

[JustRight]

Wouldn't it be easier just to give "A Canadian in Castle" a new GUID ?

Nah, it's not rosgar's scenario that is at fault. I just happened to be trying to get that scenario to run when I saw all these errors in LogMate.

[gptech]

Nah, it's not rosgar's scenario that is at fault. I just happened to be trying to get that scenario to run when I saw all these errors in LogMate.

So, these logmate entries haven't actually been errors as such, more notifications of an odd occurence that hasn't actually stopped anything working?

[JustRight]

So, these logmate entries haven't actually been errors as such, more notifications of an odd occurence that hasn't actually stopped anything working?

Don't know. Until I can identify one or more of the duplicate GUID's and then try and run one of those scenarios, I can't say what the nature of the problem would be. I distinctly remember Mike Simpson saying something about all scenario GUID's having to be unique now across all installed routes. It's not clear just what the problem would be if you try and run one of these 'duplicates'. Once I find one I can report back.

[gptech]

Don't know. Until I can identify one or more of the duplicate GUID's and then try and run one of those scenarios, I can't say what the nature of the problem would be.

Unless you're in the habit of installing scenarios and not running them it'd be safe to assume that if it caused a problem you'd have run into it the first time you played a scenario that duplicated an existing GUID.