Payware merging

If its from the Trainz store and Steam then no there is no way to remove the payware tag from a route.

Cheers
 
As said above, you can't merge DLC, but you can try this instead.

Clone the routes first.
Add in a track extension and install an iPortal on each one.

<kuid2:30671:23501:1> iPortalBasic
<kuid2:30671:23500:1> iPortalTunnel

What these allow, after configuring is to send consists between routes. Once an AI driver drives into the iPortal on one route, you then open the connected route and the train will emit from the iPortal if configured to do so. The consist will retain its commodities but you'll have to put in the driver commands.

I use this extensively now instead of merging huge routes together.

HowTo/Configure an iPortal


An iPortal is a scenery object with track and is placed and linked into your Route in the same way an industry is. The two iPortal assets can be easily found in the scenery items list as they both start with “iPortal”. To function in the Driver Session, the iPortal needs to be configured. There are no rules needed, just open the properties window for an iPortal placed on your Route. To get the iPortal working, not only must your TANE installation be configured to work with your Planet Auran account, but the iPortal itself also has several parameters that need setting as well.


iPortal id
Unique ID name that this portal is to be identified by.


Send to user
Name of the remote Trainz user that you wish to exchange train consists with. This setting isn’t needed if you are just transferring trains to other iPortals on your own Route but is needed if sending between different routes.


Destination iPortal id
Unique ID name of the destination iPortal that this iPortal is to exchange trains with. This can either be remotely located on another user’s system or from your own Route.


Send Trains
Specifies whether trains are sent over the internet and exchanged with another user or just transferred locally to another iPortal.


Check for trains
Enable this option if you want the iPortal to wait for trains that another iPortal may send to it.


Driver mode after create
Determines how trains emitted from the iPortal will be controlled on your Route once they have exited the iPortal. Trains transferred through an iPortal will retain their vehicle loads so one potential fun activity is to operate your Route such that it requires an incoming loaded train from someone else through the ==iPortal== Don’t forget to use iTrainz Chat so you can communicate with your friend and arrange iPortal exchanges. iTrainz Chat will also let you know if your friend is online.
 
If only copyright violations were that simple!

You can clone and save a payware (DLC) route under your own kuid code and then edit it as much as you want but it still will not allow merging. A cloned DLC route will only work as long as you still have the original DLC route installed (and enabled) on your system. You can even upload your cloned version to the DLS for others to use provided they also have the original DLC route installed.

There are a few exceptions to this where the DLC route is encrypted (a decision made by the creator) and cannot be cloned.

Merging a DLC route (if it was possible) will completely remove its copy protection which would make pirating so much easier. For this reason merging, even for personal use only, is not allowed.
 
How does the file know its from the DLC? What is it reading in the config file that needs to be changed?

There's a tag in the config file that states the item is payware. I don't think removing the tag will change anything, and I think it'll actually cause the asset to become faulty. While it is a bit annoying you can't merge routes, I do understand why.

And just to let you know, no, you cannot merge clones of payware routes, they still have the payware tag in the config and will break if tampered with.
 
A solution would be to allow merging BUT add a payware tag and prevent it from being uploaded to the DLS, as well as prevent it from being exported as a .cdp. If someone tries to export it, they'll get an error stating that the route has a payware route in it and that it cannot be exported. If it is somehow uploaded to the DLS, have something in the DLS software that detects the payware tag and prevents it from being uploaded. Cloning the route will preserve the payware tag even if you remove it in the config file.
 
A solution would be to allow merging BUT add a payware tag and prevent it from being uploaded to the DLS, as well as prevent it from being exported as a .cdp. If someone tries to export it, they'll get an error stating that the route has a payware route in it and that it cannot be exported. If it is somehow uploaded to the DLS, have something in the DLS software that detects the payware tag and prevents it from being uploaded. Cloning the route will preserve the payware tag even if you remove it in the config file.

I mentioned something similar this ages ago. Apparently, that's too much work.

Until that time comes, the alternative is to use the iPortals. Place an iPortal where you want the routes to connect and configure them to all the trains to run from one route to another. The cool thing with the iPortals is they'll "store" the trains in them up in the cloud until the next time you load up a connecting route.
 
Back
Top