Logmate errors

[jevon]

I tried running LogMate to see if I could figure out why shudder was occuring at specific points in a scenario I created for the Newcastle-York route. While running LogMate I got hundreds of lines of errors similar to the following:

Code: Select all

[Content 6:45:44 PM] Trace C:\Dev\RailSim\Code\DLLs\DataManagement\cBlueprintLibrary.cpp : 270 = Blueprint set not found for: 

.. and there is nothing in the log text after "for:" Anyone know what this means?

I also get hundreds of lines of errors exactly like this:

Code: Select all

[Content 6:45:44 PM] Trace C:\Dev\RailSim\Code\DLLs\DataManagement\cBlueprintLibrary.cpp : 242 = Blueprint set not found : Scenery\Procedural\oxfo_padd_FenceScrub01.IGS, 

Is this a missing file or something? Odd that the filename is "oxfo_padd_FenceScrub01.IGS", as I'm running in the NY Route. Anyone else seen this in their LogMate results?

Both of these errors occur after leaving the York yards northbound where you first hit the 4 track stretch. I should mention also that when LogMate is recording multiple instances of these events, the sim shudders terribly and fps drops to 14. Logmate was recording so many of these errors that RailSimEditor eventually hung.

Thanks.

- Jev

[AndiS]

The first one with the nameless blueprint is a stupid one.
The only thing you can try is search the XML file of that tile for nameless references to blueprints.
When you search for <BlueprintID d:type="cDeltaString"> you should not find something like <BlueprintID d:type="cDeltaString"></BlueprintID>. Instead there should be something like
<BlueprintID d:type="cDeltaString">scenery\buildings\bath_temp_terrace_mid01.xml</BlueprintID> i.e., a relative path starting with scenery or something similar, and ending in .xml.

Regarding the second one, I suggest you look for this string in the same tile file(s). Normally, it should be Scenery\Procedural\oxfo_padd_FenceScrub01.XML. I am a bit surprised about the capital letters, but maybe this is not case sensitive. If you see all the other references to scenery in the file spelled with lower case letters alone, try correcting this entry.

Be sure to use serz.exe or RS-Tools to create a BIN file after modification, the modification of XML files does not influence the game.

If the above does not help, you could look into Scenery\Procedural\oxfo_padd_FenceScrub01.XML. There will be a line roughly looking like this:
<GeometryID d:type="cDeltaString">Kuju\RailSimulator\Scenery\Procedural\[00]FenceScrub01</GeometryID>
There should be no .IGS in the name.


The fact that the name starts with oxfo means nothing. A lot of assets are used in more than one route, which is quite reasonable considering the similarity of scrub near Oxford and near Newcastle.

[smarty2]

Glad i am not the only one suffering this

Mart

[jevon]

Very grateful for the replies. As a noob, editing XML files and using serz.exe is not something I'm skilled enough to do.

It seems I'm not the only one with the problem. I wonder if the issue is related to the base RS installation or to the RSDL Foliage Pack add-on? In any case, it seems to be something RSDL should take a look at and fix.

Thanks very much for the time you both took to reply.

- Jev

[smarty2]

Very grateful for the replies. As a noob, editing XML files and using serz.exe is not something I'm skilled enough to do.

It seems I'm not the only one with the problem. I wonder if the issue is related to the base RS installation or to the RSDL Foliage Pack add-on? In any case, it seems to be something RSDL should take a look at and fix.

Thanks very much for the time you both took to reply.

- Jev

Hi Jev,
Only response i had from RSDL was to reinstall which did nothing to resolve the stuff that is "Missing" As running logmate after install revealed the same items were still not there?

Regards

Mart

[jevon]

Mart,

Thanks for this info. At least I know the cause isn't something I did to screw up my RS setup. Did RSDL even look into it before suggesting a re-install -- as in, "we ran LogMate on that part of the route and we received no errors"?

With all of the "normal" shudder as RS operates, you'd think RSDL would want to fix something clearly identified as a problem. But, with RailWorks on the way, it's unlikely these missing bits and messed-up code will ever get resolved.

Thanks again.

- Jev

[smarty2]

Hi Jev,

No, they wouldn't look into it as there weren't enough people experiencing the problem, so it's a case of putting up with it

Regards

Mart

[AndiS]

This is how you get rid of the error.

In Scenery\Procedural open oxfo_padd_FenceScrub01.bin (using RS Tools).

Find this string: Scenery\Procedural\oxfo_padd_FenceScrub01.IGS

Delete it. The line will then look like this:
<Provider d:type="cDeltaString"></Provider>

Be sure that you did not delete the > and < shown in bold.

Save and enjoy.