Rolling Stock skinning ideas

[Gumboots]

Yes I think you are right about the fuel cost. The Riga shunters were only burning about $7k/year of fuel. It could easily be tripled, which is what would happen if you changed the current Very Good fuel rating to Below Average. That should still allow shunters to make over $100k/year.

I'll check some of the stats for the ones on branch lines too, since I also want it to stay usable in that application.

[Gumboots]

Hey I had a brainwave. Check this.
.

Camelback_skinstealer.jpg

.
Since the Pennsy H3 skin is already set up with layers and styles, and since some components which are transferable to the Camelback (wheels, etc) are already set up with UV mapping, there's an obvious quick and easy way of getting the Camelback looking slick.

The current screenshot is just bits of Camelback mapped to an unaltered Pennsy skin, along with the transferred wheels and drivetrain from the H3. It will need some tweaking of the skin here and there, but as it's mainly a matter of shifting and scaling some layers and changing a few colours it shouldn't be a huge gnarly deal.

The other advantage is that it won't need separate images for loco and tender. I was already thinking of doing the Camelback as a "double", with the loco and tender as two trucks, similar to the double cargo cars. Since it's so short, and since the loco/caboose combo goes weird around tight corners in RT3, the Camelback seems an obvious candidate for this treatment.

This means it will be possible to have double-headed Camelbacks.

[Gumboots]

Have been playing around with spreadsheets a bit, trying to balance stats.

Since the Latvia scenario was what got this thing started, the obvious question becomes: how does it compare with the S3 and P8 with that era's cargo?

After playing around some, I think I've got it sorted. With these stats the Camelback is about 10% cheaper to run than the P8 if annual mileage is low, but the P8 is about 10% cheaper if annual mileage is high. Obviously the speed advantage of the P8 makes it a no-brainer for longer runs, but the better acceleration (albeit to a lower top speed) and cheaper running cost for short hops will give the Camelback a viable niche.

Available: 1896-1956
Purchase price: $80,000
Annual maintenance: $5,000
Fuel economy: Above Average
Acceleration: Above Average
Reliability: Good
Pax appeal: Gruesome
Top speed: 23 mph
Free weight: 110
Pulling power: 9
Locomotive weight: 110
Tender weight: 0

Compared to the S3, the Camelback is always much cheaper to run but not nearly as fast with light loads on fairly flat terrain. However, it is as fast as the S3 up heavy grades. The S3 is still viable for intermediate pax service, where its good top speed with a light load and much better acceleration than the P8 give it an edge.

Haven't done a comparison to the Class 500 yet. I don't tend to use many of those anyway, due to their lower reliability. They need a caboose to operate reliably for any length of time, which cuts paying load compared to the others.

A quick and rough check against the Pennsy H3 stats indicates that the Camelback will work well with that locomotive too. Same deal: Pennsy is better for long hauls due to its speed, although it's more expensive to run. Camelback is better for short hops, due to being cheaper to run.

[Gumboots]

If anyone wants to test this out, I've added a zip with the relevant files. Note that this is the basic revamp as shown back in this post. I haven't got the flasher skinning (and new wheels, etc, etc) done yet, but even the basic revamp makes the thing much more appealing to use.

Also included are EngineTypes files, with the same stats as mentioned in the post just above. The only difference is that I decided to leave the stop year at the default 1926, since that will mean no possibility of conflict with events in existing scenarios. Naturally, the new Latvia map includes an event to make the Camelback available after 1926.

[Gumboots]

Had an idea this morning for a bit of fun. Those ships I was messing with a while back got shelved because it was pretty much impossible to make the tracks look decent when playing, and also due to several other issues. The whole moving-ships-carrying-cargo thing would really only work if an entire scenario and its assets were developed specifically for shipping. Which is possible, but gets to the point where you might as well buy a game that has working ships.

However ships for eye candy in RT3 is a piece of cake. Turns out the A skin for docks is 512x512. Since the game handles 1024x1024 without dramas it would be simple enough to shunt the dock's UV mapping to the corner of a 1024x512 or 1024x1024, and then have the rest of the image available for extras.
.

Port_and_ship_basics.jpg

.
So I might whip something up for this sometime. The extra poly count wouldn't be an issue, and it would be kinda fun.

[Gumboots]

This is not rolling stock, but I couldn't be bothered starting a new thread. Windmills. Juriko included some in his original Latvia map, and they are apparently a traditional thing over there (get used as logos for lots of products) but the "space age" version that comes with the game doesn't really fit the 1930's. It's not even a good representation of real modern turbines, which have much more practical styling and structure. So I started wondering if anything could be done with the PopTop version.

It has the usual body .3dp file for the base unit, but the prop is done with RT3's mysterious Anim files. These come in pairs: upper case first letter "Anim1" and lower case first letter "anim" without the 1. The Anim1 does the prop's mesh and the other one (and I have no idea how it works) makes the prop turn around slowly.

So I looked at the hex for the Anim1 and it seemed to have the usual attachment point like any other .3dp file even though it had a different header. The attachment point, or pivot point, had hex that matched the centre of the prop's hub so I thought maybe it just works like wheels. As a quick test I took the prop's mesh, rotated the existing three blades around the hub until they were 90 degrees apart instead of 120 degrees, then added a fourth blade. I then moved the whole thing vertically down by 30 units, which is about as close to the ground as it can go. Exported that as a .3dp and edited the new pivot point height in, and dropped the file into UserExtraContent to see what happened.
.

Windmills.jpg

.
It works. Obviously the prop no longer lines up with the base structure, because I haven't touched that mesh yet, but they are four-bladed props and they turn nicely around their centres at the same speed as the originals. This means that if anyone wants to it is possible to hijack the PopTop windmill files to make anything that uses a similar basic structure and motion. For example, if for some weird reason you wanted a water mill it would be easy to make.

The obvious question now is are there any useful ways that other anim.3dp files can be hijacked? Just off the top of my head, the Auto Plant has them to move little cars around, and the Lumber Mill has them to move logs around, so maybe we can have cows wandering around our fields. Not that I would be likely to bother with cows, but just as an example. I'm sure it's possible with a bit of experimentation.

Edit: Oh and the other things is can Anim1 and anim files be used on moving objects? Can you add extra animated bits to locomotives? Probably not, but it may be worth trying. The in-game aeroplanes don't appear to use anim files, or not that I can see.

[Gumboots]

I had an idea which might work for revamping of default PopTop Locomotives. Could work with other assets too. It's pretty obvious in retrospect so I'll have to test it soon.

The hang-up with default locos is that you can't pack revamp files into PK4's if you want them to override the default files, which means you can end up with a lot of loose files floating around. This bugs me since I'm always pigging around in those folders testing things. Much better if everything can be neatly packed.

So the idea is that although the default loco name has to be kept for backwards compatibility with existing scenarios, the rest of the naming in the .lco and .car files might not have to be the same. If it doesn't (and given RT3 coding it may all turn to crap) then the way around the problem would be easy: just rename the .3dp and .dds files and change the calls in .lco and .car to suit, while leaving the default loco name and ID numbers alone.

If that works (and doesn't all turn to crap just because it can) then it would be easy to revamp default .3dp and .dds files, and still be able to pack them up the way we want them. Which would be very cool. I'd much rather have a Camelback.PK4 than a pile of loose files.

I'm gonna try this and see what explodes.
.

---

.
Hey it works! Nothing exploded. The game just ran normally, and recognised the Camelback even though it was calling different .3dp and .dds files with different names. All the CamelbackL files were renamed to CamelbackGBL, and all the CamelbackT files were renamed to CamelbackGBT. The relevant bytes in the .lco and .car files were changed to match, and that's it. Only took a few minutes.
.

Camelback2_EngineTypes.jpg

.

It_works.jpg

.
This is great, because it means bugfixes for most default assets can be packed up nice and tidy. There may be some exceptions, but offhand I can't think of any.

It will even be possible to have bugfixes for multiple default assets in one PK4, because the game doesn't care what a PK4 is called or how many thing you cram into it. All the game cares about is that the files inside the PK4 have the correct syntax and calls everywhere. So a Camelback bugfix could be packed with a Penn462 bugfix or a Connie bugfix or a Big Boy bugfix, or anything else, and it should be fine with one Fixes_for_cruddy_PopTop_choofers.PK4 sitting in PopTopExtraContent. Or they can be done as separate PK4's. Either way will work.

Dunno why I didn't think of this before. In retrospect it's a no-brainer.

[Gumboots]

I was looking at the default port & port upgrade models in Blender, and after a bit of thinking realised it would be possible to save enough tris to easily cover one ship. This is without making the port itself more basic. It's just different use of mesh to amalgamate a lot of pointless faces into fewer separate units, by taking advantage of a bigger texture image (which would be needed to add ships anyway). It may even be a bit better for performance, because it would get rid of a lot of draw calls.

[Gumboots]

Got to thinking about flatcar cargoes again. The default PopTop weapons cargoes bug me, at least the late era ones do, and the thought of having to do anything with them was an irritation. Obvious solution: don't anything with them, and do something else.

Some time back I mentioned the idea of using missiles for late era weapons loads. They fit the post-WW2 timeframe, and I figured they would be easy to model and skin. Turns out they are. Started out playing with the idea of using Tomahawks. I've never seen pix of these being shipped on flatcars, presumably because the military don't want people nicking them, but this is RT3 so why not? Tomahawks are easy to model and skin, being basically just just a hemisphere with a tube stuck on it and a couple of fins. Engine nacelle too, but that's not a big deal. After playing around with it a bit I got 6 Tomahawks stacking nicely on a 75 foot flatcar. All good.

Only catch is that the poly count was getting up over 900, which is a bit more than I'm really happy with for a cargo car. Obvious solution: shorter flatcar and not as many Tomahawks. Four of them fit nicely on a 60 foot car, and the poly count is much more reasonable. It'd probably be possible to get away with the higher-poly 6 missile car, because it's rare to ship oodles of loads of weapons anyway, but having a lower poly option makes sense.

Tomahawks only started being deployed sometime in the 1970's, so they really fit the post-1990 time slot for my cargo revamp scale. That's when they've had the most use. For the period before that something else is needed, so I looked around a bit and found drawings for the old Nike Hercules. These were first deployed in the late 1950's and were in service until the late 1980's. This thing also turns out to be easy to model and skin, and has the advantage of seriously looking like a weapon. If I saw one of these heading towards me I'd definitely get the impression that somebody wasn't happy. It fits nicely on a 60 foot flatcar, only has a poly count equal to the two default PopTop post-1950 guns (or less than two Tomahawks) and looks a lot better. It would even be possible to bung two of them on an 89 foot flatcar and still have slightly fewer polys than a 60 foot car with four Tomahawks.

Weapons_stuff.jpg

[Gumboots]

Played around with it some more. Managed to cut the polys on the Tomahawks and Nikes without making them look gruesome. Then I started thinking some more about arrangements on flatcars, and wondered what other missiles were around. I've pretty much settled on this one for the 21st century era: https://en.wikipedia.org/wiki/BrahMos

More_things_that_go_bang.jpg

It's an interesting piece of kit, and it seems to work, and it looks better than Tomahawks and can be done with fewer polys. It's also easier to skin. Half a dozen of these things looks good on an 89 foot flatcar, so I'm going with them for post 1990 and the double Nikes on an 89 for 1965-1989. If I'm gonna do this stuff, I gotta have fun with it.

Old_things_that_go_bang.jpg