[mrmosky]

I had a thought that this feature may be able to be used to get a moving river into OR. So that's what I've been working on.
I created a flat surface in TSM and copied it twice. Then I applied a water texture that I had from the internet. The three surfaces are not exactly coincident, I moved one laterally with respect to the others. This was to exploit the z-buffer problem. Now this is usually something to avoid, but here it makes the water shimmer.

Then I made a MSTS object, and added it to the carspawner. The carspawner speed was set to 3 in TSRE, and the repeat rate set to 1. In the carspawner list file, I set the gap parameter to 0.1 so that there should be no gaps between "vehicles" (water objects). The carspawner used Goku's recent feature where you can place a path using marrkers. This means you can quickly create a path for your river.

Anyhow, it is still experimental, but here's a link to the video.

https://youtu.be/mu7zLGiPWnI

[Jovet]

mrmosky, on 26 July 2017 - 08:15 AM, said:

I had a thought that this feature may be able to be used to get a moving river into OR.

Not to "throw cold water" on your innovative idea, but it seems far fetched to me to, at some point in the future, expect OR to support this methodology. For one thing, a flowing body of water is quite far removed from car spawners. Second thing, OR is already still using MSTS's extremely outdated form of "water" and we should be looking forward to outgrow that versus looking for ways to perpetuate it.

That said, your video does look like the idea works (if a bit swiftly), but I wonder how it'd seem on a curved or larger area.

[Coolhand101]

It's nice to see animated water in OR, well Done! Also, your animated horses and carts are excellent!

Thanks

[Csantucci]

Well, this seems a genial idea!

[mrmosky]

Jovet, on 26 July 2017 - 11:05 AM, said:

but it seems far fetched to me to, at some point in the future, expect OR to support this methodology. For one thing, a flowing body of water is quite far removed from car spawners.

OR does support this method right now. That's what I have used, as shown in the video.
Now we can use multiple carspawners, and we can define a path that is not a road that will take a carspawner (refer animated people thread). Then it could be that the carspawner list might include a dedicated one for a river or stream. Then in your route, you can define a path, using markers, and add a carspawner of that type.

Ok, it's a bit of a fiddle, but there is no other way to get moving water at the moment, is there?

Anyhow, as I said, it is just an experimental idea. I am happy to upload the shape if anyone else would like to play with it.

Cheers,
Geoff

[slipperman]

Hi Geoff,
It's brilliant that you've associated moving water with moving vehicles and linked it with a car spawner! The fact it uses existing technology is what makes it great!!

... and as for your horse/s and cart - well, you seem to have a real aptitude for that kind of work, so please keep it coming :)

Cheers,
Ged

[Jovet]

mrmosky, on 26 July 2017 - 11:51 AM, said:

OR does support this method right now. That's what I have used, as shown in the video.

I meant that, as OR's feature set evolves, sacrifices or special accommodations necessary to support this usage (should it become an accepted and established practice) may have to be made which have unintended consequences. It also does not address the fact that OR's representation of water is 15 years behind the curve. I agree with others that it's a novel idea, but to me the relative effort to desired effect ratio just isn't there. But that's me. Contrast that with the animated horses, which brought MSTS/OR's horse models out of the 1970s.

[thegrindre]

Why wasn't this idea of Geoff's thought of 15 years ago??? Fantastic idea. http://www.elvastower.com/forums/public/style_emoticons/default/good2.gif

http://www.elvastower.com/forums/public/style_emoticons/default/oldstry.gif

[mrmosky]

Thanks for the comments. I am planning to do more horses, I may put a rider on one next. Then I may look at a bicycle and rider. There were a lot of cyclists back in the day, when railways were king.

I may have a further play with the river idea. It does have some potential.
I would agree with Joseph, that to do this properly might need some new feature in OR. On the bright side, the code that is already there for Carspawners could possibly be a good start point for a Riverspawner; and we have already seen that paths can be made for these in a very quick and versatile way. The texture for a river could be varied in colour and complexity. Anyway, that is up to others to develop.

More animation in route scenery has got to be good.

Geoff

[Garry]

I think this looks really good. I hope you will put up full instructions as I would like to try this myself.
Garry

[mrmosky]

Hi Garry,
I will post up fuller instructions, but maybe on a new topic thread, rather than hijacking this one. Give me a day or two to write some notes.
Geoff

[mrmosky]

Hi Garry,

I have started a new topic as promised, and added a new video. I will be able to set out the steps in that topic.


http://www.elvastowe...animated-river/

Cheers,
Geoff

[mrmosky]

After diverting into moving water animations for a few days, I am back on the horse.

Here is the one I am currently working on. A horse with rider.



I will be posting progress over on UK trainsim, but I will share on here when it is finished.

Sooner or later, I must get back to building my locomotive model and my route. So much interesting stuff to do....

Cheers,
Geoff

[sanjeeb]

Csantucci, on 03 June 2016 - 12:54 PM, said:

Blueprint has been filed https://blueprints.l...r-spawner-lists .
A beta release is available. To test it, update x.3551 with the files included in this .zip
MultipleCarSpawnerLists.zip
To use it, two files have to be created in an Openrails subfolder of the related route.
I have created a stupid test example for USA1 route, for two of the four carspawners that pass over the tracks with a viaduct just after the station on Philadelphia.
The first file is a file named extcarspawn.dat that contains all additional car spawner lists (additional because the one included in carspawner.dat is still valid and used). Here the file I used:
extcarspawn.zip
In this case I used only a new shape (postbus.s) with respect to the ones of the standard carspawn.dat. Of course to see it you need to have that shape, or to replace it with another shape you insert in the shapes folder (together with .sd file, and with needed texture files in the textures folder).
The second file is a file named carspawnerstolists.dat. I used following sample file:
carspawnerstolists.zip
An entry in this file must be created for every car spawner where it is desired to use a car spawner list different from the one of carspawn.dat.
The structure is self-explanatory: the car spawner is identified with world file and UiD (they may derived using track viewer and uncompressing the related .w file), and the CarSpawnerList parameter identifies the index of the car spawner list (zero is the car spawner list of the standard carspawner.dat, so that the indexes of the lists included in extcarspawn.dat start from one).

By the way these .exe files include also this http://www.elvastowe...rations-window/ .

Sir How to add this? is there any tutorial? I can't add multiple Carspawner in my route. please help

[ebnertra000]

sanjeeb, on 22 June 2018 - 06:36 AM, said:

Sir How to add this? is there any tutorial? I can't add multiple Carspawner in my route. please help

Following an extremely short search in the OR manual, I discovered this:

Quote

15.5 Multiplecarspawnerlists

With this OR-specific feature it is possible to associate any car spawner to one of additional car lists,there-
fore allowing e.g. to have different vehicles appearing in a highway and in a small country road.
The additional car lists have to be defined within a file named carspawn.dat to be inserted in an Openrails
subfolder within the Route’s root folder. Such file must have the structure as in following example:

SIMISA@@@@@@@@@@JINX0v1t______
3
CarSpawnerList(
ListName ( "List1" )
2
CarSpawnerItem( "car1.s" 4 )
CarSpawnerItem( "postbus.s" 4 )
)
CarSpawnerList(
ListName ( "List2" )
3
CarSpawnerItem( "policePHIL.S" 6 )
CarSpawnerItem( "truck1.s" 13 )
CarSpawnerItem( "postbus.s" 6 )
)
CarSpawnerList(
ListName ( "List3" )
2
CarSpawnerItem( "US2Pickup.s" 6 )
CarSpawnerItem( "postbus.s" 13 )
)

The first 3 defines the number of the additional carspawner lists. To associate a CarSpawner block to one
of these lists, a line like this one:

ORTSListName ( "List2" )

has to be inserted in the CarSpawn block, in any position after the UiD line.
If the CarSpawner block does not contain such additional line, it will be associated with the base
carspawn.datfilepresentintheroute’srootdirectory.
Caution: If the route is edited with the MSTS route editor modifying the .w files referring to the addi-
tionalcarspawners,theabovelinewillbedeleted.
To avoid this problem, two other possibilities are available to insert the additional line. One is described
here. The other one is to use the OR specific TSRE route editor, that natively manages this feature. Also
in the latter case, however, if the route is later edited with the MSTS route editor, the above line will be
deleted.

With this information, I've been able to set up multiple car spawner lists in a couple of routes of mine