"PC Prospect Breaker" Asset Missing Coronas

PARAILFAN

New member
"PC Prospect Breaker", <kuid:186372:190001> which was just put on the DLS yesterday, is missing a corona <kuid:-25:961>. I did a search on the internet and nothing shows up for that corona. I'm running Trainz 2009. Is this corona possibly built in content on Trainz 12 and that's why I can't find it?
 
That asset is a built-in, but it's only available in TS12 SP1. There are several other coronas that can be used though by swapping the missing KUID for another corona KUID in the config.txt.

Shane
 
It would help those without SP1 what color the corona might be. After changing the kuid will it show in TRS12 without the patches? Thanks.
 
Beings that it is a "Version: TS2009 SP4/TS2010" asset, it *REALLY* shouldn't be using a TS12SP1 only asset...

Just sayin'
 
Yeah, did someone took the liberty to point this out to pcas1986?
Seeing as he made a bunch of assets, I'm sure this is just a minor error that slipped through.
 
Beings that it is a "Version: TS2009 SP4/TS2010" asset, it *REALLY* shouldn't be using a TS12SP1 only asset...

Just sayin'

I agree! But I have seen this sort of thing happen before with other assets on the DLS. Too many to even remember actually.
 
Based on the name, I say white:
whitecorona,<kuid:-25:961>

I have never done this, so not speaking out of experience, but I say no reason why it should not work.

I've had to replace one corona with another on many occasions. Never had any problems but I usually do it on locomotives or rolling stock. The one issue is that some coronas are just brighter than others. They are not all created equal.
 
thanks obnotsen. my error message had a ? and then the kuid, did not label it as a white corona. hence, my question. thanks again
 
Yeah, did someone took the liberty to point this out to pcas1986?
Seeing as he made a bunch of assets, I'm sure this is just a minor error that slipped through.

Someone just did so I will look into it.

Beings that it is a "Version: TS2009 SP4/TS2010" asset, it *REALLY* shouldn't be using a TS12SP1 only asset...

Just sayin'

I totally agree. It would be nice if the validation process, being either manual (i.e. the content creator) or automatic, pointed it out. I wonder if trainzutil could be used for that purpose.

The asset is intended for the LWVRR route which, AFAIK, is not yet released for general usage. There must be a few coal route builders out there or those who like very large and ugly buildings. :hehe:
 
For the OP:

Was there a particular reason you wanted to run this in TS09? It was intended for TS10 and you have TS10 in your Trainz list. You can substitute the whitecorona asset <kuid:-3:10111> until I release another version. That will take a day or so to get through the DLS process.

All:

The whitecorona asset <kuid:-25:961> is marked as build 1.3 so I think if it was introduced in TS12SP1 then it should be build 3.6. I'd like some opinion on that.
 
The updates for this asset are pending at N3V. The updates have been there for a couple of days now awaiting approval.
 
For the OP:

Was there a particular reason you wanted to run this in TS09? It was intended for TS10 and you have TS10 in your Trainz list. You can substitute the whitecorona asset <kuid:-3:10111> until I release another version. That will take a day or so to get through the DLS process.

All:

The whitecorona asset <kuid:-25:961> is marked as build 1.3 so I think if it was introduced in TS12SP1 then it should be build 3.6. I'd like some opinion on that.

Not necessarily. What has happened in TS12 SP1 is that the KUID range has changed for most of the built-in content, and the builtins have been renumbered into that range, without any changes to them apart from the KUID.

Shane
 
Not necessarily. What has happened in TS12 SP1 is that the KUID range has changed for most of the built-in content, and the builtins have been renumbered into that range, without any changes to them apart from the KUID.

Shane
Well I believe if that content was only for TS12 SP1 and later, then the build number should reflect that rather than saying it was build 1.3.

Perhaps if I am building for TS10 then I should be committing into TS10 rather than TS12. In that case I would not have picked up the wrong kuid. This is going to force me to make all my new content for TS12 or later which will deny access to those wanting to continue with older versions.
 
Back
Top