CM Error

dricketts

Trainz Luvr since 2004
How can this be? I'm getting this error when the asset is clearly on the DLS. <kuid:1776:300001>

qQlfxij.jpg
 
Last edited:
Bad internet connection maybe?

It's definitely on the DLS and not a brand new upload, so CM should be able to get it.

Hmmm. Doesn't make sense. I had the same issue with this kuid about 4 days ago. I am able to download other assets just fine. I should probably add I'm using TS2010 build 49933. CM 3.3
 
Last edited:
I'll see if I have the same problem, back shortly....

I also have build 49933. My CM 3.3 found, downloaded and installed the asset OK, but then showed this fault message "Error: This asset has a trainz-build number which is not recognised by this tool."

On inspection, it is a build 3.4 asset, which I thought (perhaps mistakenly) was TS12. Why am I able to download a 3.4 asset that my version (3.3) of Trainz can't in theory recognize? Maybe your copy is doing the right thing and mine isn't? I'm confused.
 
Last edited:
Trainz-build 3.4 assets require either TS2010 with the multiplayer beta patches installed , or TS12 (or the Mac equivalent).

Shane
 
Trainz-build 3.4 assets require either TS2010 with the multiplayer beta patches installed , or TS12 (or the Mac equivalent).

Shane

That may be so, but how do you explain why 2 people with the same Trainz build have CM's that behave differently with respect to downloading the same build 3.4 asset? Why are we even seeing it on the DLS? I thought the system was geared to blocking higher build assets from being seen, since they can't be used.

And should we be patching with SP4 (the TS2010 multiplayer patch) if we have no intention of using multiplayer? Are there hidden problems with that patch that make it of questionable value?
 
Last edited:
I'm not personally aware of any issues with said patch apart from the fact that there is no compatibility mode once the patch is installed (only native mode, which means that assets that require compatibility mode will not function or look correct).

As for your other question, it may be related to how the asset is downloaded and installed, as if it's downloaded outside of Content Manager and installed from a .cdp file, then it behaves differently to if the download is attempted within Content Manager.

Shane
 
I'm not personally aware of any issues with said patch apart from the fact that there is no compatibility mode once the patch is installed (only native mode, which means that assets that require compatibility mode will not function or look correct).

As for your other question, it may be related to how the asset is downloaded and installed, as if it's downloaded outside of Content Manager and installed from a .cdp file, then it behaves differently to if the download is attempted within Content Manager.

Shane

Both Derrick and I were downloading (or attempting to) from within CM.
 
That's interesting in that case. Looks like either your version or Derrick's version seems to be misreporting itself to N3V's servers.

Shane
 
hang on - some confusion here. CM blocks the download of a higher buid number, but has never stopped you seeing the asset. Image from CM3.3, note all the 3.4, 3.5 and 3.6 builds....

cm.jpg


Crickey seeing all the stuff you can't download is a marketing ploy to encourage you to upgrade! They'd be nuts to stop you seeing it....

:)
 
That's a point! sh - don't tell anybody...

Although I think the only thing that sets yours apart is that CM will download a higher build. You can install a higher build using CM, but it reports an unrecognised build number error and therefore won't use it. Curious what yours reports after install....
 
Last edited:
Back
Top