Do You want some fences or bins?

[usuario]

If You need, I can try to create them.
Also, I can create other simple sprites.

[Richard Wheeler]

It would be great if you could help. Would you be able to model some simple objects/fences in blender? If you post the .blend file here I can import them into the render template, texture them and make the sprites.

[Alberth]

Regarding fences, I have a question where to allow them.
Obviously, they should be between two tiles (afaik). Also, I think a fence should be placed at the highest tile.

The question is what to do with corner cases like the following.

Say you want to build a fence at a NE edge. The tile closest to you has its northern corner raised, and the tile furthest away has its southern corner raised. You'd need a fence with a 'bend' in the middle to make it fit.
The simplest solution seems to be to disallow building a fence at such a position (or fail to raise land if the fence is already there).

[Hazzard]

In the original games fences would be placed on the side of a tile, and since their were two tiles for each edge, fences could be doubled-up. I also think that it was possible to place more than one fence on a tile, but I can't be sure.

[Zuu]

In RCT2 it was possible to stack fences. It was even possible to right click to remove a fence below another fence without it falling down.

I am unsure if RCT1 or any of its expansion packs allowed this.

[Zuu]

That being said, I don't know which is better. The RCT way allowed you to create a fence with different appearance at each side. On the other hand you had to make sure a stretch of fences followed the same side of tiles something that at all instances might not have been possible due to roller coasters, shops, rides etc.

Players that play for appearance and painting their theme park on a canvas will probably like the RCT-way while some other may like the simplicity by the solution proposed by Alberth.

[Alberth]

Giving each tile a possible fence at each edge is simpler from an implementation point of view, since you don't have to look what another tile has while rendering.

It also solves my corner edge in the sense of "user, do what you like", and it removes the need for additional fence sprites, like my bending example. I like it.

The stacking of fences is new to me; the simplest solution is probably to add higher fences to higher voxels, which seems like a good approach to me.

[Richard Wheeler]

I vote for matching the rct behaviour: a different fence sprite on each side of each tile. Stacking fences would be a low priority on my list for now, partly because of the restrictions it would place on the graphics design.

Bins, lamps and benches on paths are simpler. Each tile can have just one of these and they are automatically placed on all non junction sides of the path tile. Benches couldn't be placed on slopes.

[Hazzard]

What are the dimensions of a voxel in Blender?

[Richard Wheeler]

[Richard Wheeler]

I'm doing most of the graphics at 2x2x1.2, though scaling the graphics obviously isn't much of an issue. Anything more than flat colours for textures isn't needed at the scale bins and similar are likely to be at.

[usuario]

I have modeled a simple bench. I have used the path blend file as reference.

If you like It I can model a broken version and I can adjust the position, so the steel structure will have 2 px widh when rendered and not 3 (but I think that alpha transparency will leave this unnecessary)

There are two blend files, the second have some colors added, the colors could be CC colors that could be selected by the user. I think that the camera position is not 2:1 perfect, because I get some misplaced pixels, even on the ground tile, but this is not a problem, because the bench can be imported in a different blend file.