Railworks America

If I create a route and offer it up for sale in some form or another, what are the guidelines for using scenery content etc. that I did not author? I've heard that it's okay to use RSC stuff for instance. I'm creating a lot of my own scenery objects, but there are a few out there from other routes that would be nice not to have to 're-invent'. Any thoughts?

You have to use your own items with your own textures, no textures off of the internet, such as Google Images.

No using other freeware creator's scenery, and no using assets from other payware routes, it is actually not ok to use RSC items in a payware route because they don't want their assets given away, especially in another payware route if you're not paying them a decent share of the profit.



If you can make every asset yourself and make your textures completely from scratch, such as taking a picture of a local brick texture and then make that a usuable texture you'll be ready to start on a payware route if you can make a route.

When it comes to a payware route people expect at least high detail assets, and works decently on their computers without too many performance problems.

I'm not so sure big Jay- I do remember seeing something written stating what certain things are considered 'community property', like kuju stuff. Some of these routes have 7000 object files in them . We have to at least be able to use rocks and trees!

I think you can use any payware or freeware item in your route, provided the items' authors have not forbidden it, but you cannot distribute the items with the route.
So for example you can use buildings from the Horseshoe Curve, and people who have bought the HSC will see the buildings in your route.

Chacal wrote:I think you can use any payware or freeware item in your route, provided the items' authors have not forbidden it, but you cannot distribute the items with the route.
So for example you can use buildings from the Horseshoe Curve, and people who have bought the HSC will see the buildings in your route.

That makes sense. I sent a few emails out right to the source, Dovetail and Railsimulator for clarification. I'll report back any responses.

Correct. As long as you do not distribute the payware assets, you can reference them in your route. Then the people who get your route will also have to have the payware for it to work or they will see little milk bottles in the asset's place. That is how the work shop routes work also. And there you can only reference DTG's payware.

artimrj wrote:Correct. As long as you do not distribute the payware assets, you can reference them in your route. Then the people who get your route will also have to have the payware for it to work or they will see little milk bottles in the asset's place. That is how the work shop routes work also. And there you can only reference DTG's payware.

Ah, so to be safe, is it right to assume you would only want to use objects from routes that come included with the sim, such as Cajon Pass?

dogrokket wrote:

artimrj wrote:Correct. As long as you do not distribute the payware assets, you can reference them in your route. Then the people who get your route will also have to have the payware for it to work or they will see little milk bottles in the asset's place. That is how the work shop routes work also. And there you can only reference DTG's payware.

Ah, so to be safe, is it right to assume you would only want to use objects from routes that come included with the sim, such as Cajon Pass?

Safe from what? If you tell the purchaser that they need the xyz route for all the scenery objects to show up you can use anything. You would not be including them in your route assets, the user would have to have them purchased from DTG or where ever using that path for them. You will find that a lot of the free stuff has a statement on there that specifically prohibits their use on a payware route.

You can reference any route, but as Bob and Buzz point out, you cannot distribute the assets (freebies or otherwise without written consent). Keep in mind that for a payware route, however, that the more assets you reference, the more of a PIA it is for the end user to track down, and they might not be too happy if one of those sets referenced is not available.

Have you done a little research as to the chances of actually selling the route? Does it fill a niche you've found for yourself or is it appealing to a wider audience?
Creating a route and a lot of unique and original assets can take a very long time, even for a small regional route that has to portray the character you envisioned.

With the recent DLC offerings, us US routes customers have been well served and perhaps even spoiled with a certain level of quality expected as standard. The standard is quite high now, and will be hard to match if you are only an individual who has to do everything himself, experienced or not.

There could be licensing issues with real world operators if you want to use their logos.

AFAIK, the only commercial creator of US routes besides DTG and their partners that sell through Steam is Eyein. Perhaps you could ask him how he proceeded in matters of copyright, use of freeware/commercial assets, etc.

Good luck with your adventure, good and needed routes do sell.

Edwin you forgot about the excellent VNHRR.

buzz456 wrote:Edwin you forgot about the excellent VNHRR.

And perhaps some other small vendors, sorry.

VNHRR is by an experienced small team who earned their laurels in the MSTS world. They have their own stock of unique assets to draw from, down to the most basic of a railroad: the track.

Yes you have to be careful about selling a route with freeware. That's why it is called freeware, you don't have to pay for it. So you can not make money with it. We have 1.8 gig of assets in the Lafayette route, all freeware. Can't even think about selling it. But that was not out goal, we wanted the route to be free from the get go. All the rolling stock included with it is also freeware.

Then there is after the route is done, where are you goinig to sell it from? You need a way to collect the money. Then the best part comes, SUPPORT for the many problems people will have and discover. And the ones who can not get it installed or working properly. With a freeware route you do not have to guarantee anything. Selling it makes it all on you.

I do know that most freeware creator's don't even want their assets referenced in a payware route because when a user looks at the route they expect it to be completely professional, if they see an asset that they don't like and it's not quality enough, guess who the problem is on.

My assets are good for a freeware route, but using the textures from Google Images they can't be sold, or even used on a payware route and I wouldn't call them exactly quality enough for a payware route.

If one really wanted to use a freeware asset on a payware route they'd best write and ask the creator of the asset, but there might be a small fee in order to use the asset. Most creators do expect to get paid if the route builder gets paid and their assets are also used on the route that's sold.

Lots of good comments and a lot of nay-sayers too! No doubt, making a worthwhile, quality pay route is a monumental undertaking; especially without a team of experienced people. One can see how this could take years!