Payware Not Active?

[boleyd]

Does Built-in Payware not Active just indicate that no loaded route uses that asset?

 

[JCitron]

Does Built-in Payware not Active just indicate that no loaded route uses that asset?

No. That means anything route, even one's you worked on yourself and included payware will be missing assets.

If you want to fix this you can try:

1) Removing and reentering your username in the settings.

This may force a reconnect to the server.

or...

2) Open up the Packages folder located in your T:ANE data folder. (The same applies to TRS19).

Ex. E:\TANE_DATA\Packages - the location of my own T:ANE data and packages folder.

Delete all the SC folders.

When done, defrag the hard drive (Close Launcher first).

Start up again and at the Launcher, run a database repair.

When completed, download purchased items - click on File menu Download purchased items, to force a download when starting up Trainz again.

 

[Forester1]

Or, it could mean, could it not? That you downloaded a freeware route or asset that someone inadvertently put payware into, and so it will not be useable.

 

[PC_Ace]

When encountered in TRS2019 Early Access, these are most likely T:ANE Built-ins or payware that haven't yet been prepped for porting to TRS2019.
Eventually these will be re-packaged and ported to Early Access before the final launch.

 

[JCitron]

Or, it could mean, could it not? That you downloaded a freeware route or asset that someone inadvertently put payware into, and so it will not be useable.

Not usually. This error message usually means that the person has that payware installed, but for some reason it's not activated. That was a problem with T:ANE SP3 off and on.

 

[valbridge]

I have disabled payware from my CM as it was causing some issues with others downloading any route I had uploaded to the DLS. Anything I now construct will not use payware assets. Have I made a mistake in doing this?

 

[Forester1]

Thanks John. I was assuming, because I have some of those assets. I guess I will have to try your other course of action. I have SP3, but noticed them in SP2...