search

dashdan / freerct

Automatically exported from code.google.com/p/freerct
0 stars 0 forks source link

Terraforming with mousewheel errors #14

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Terraform with mousewheel
2. Ground goes weird

What is the expected output? What do you see instead?
Ground should terraform smoothly, instead you get the attached picture

Original issue reported on code.google.com by CharlesP...@googlemail.com on 15 Dec 2012 at 5:20

Attachments:

GoogleCodeExporter commented 9 years ago 
I've had a look, and there are a few different bugs at work here. This patch 
should fix the one where a steep tile that isn't touching any other foundations 
has the top foundations missing. I'll have a go at the rest of the problem now.

Original comment by Powell....@gmail.com on 22 May 2013 at 1:18

Attachments:

GoogleCodeExporter commented 9 years ago 
Hello,

Thank you for your efforts. It's great that you started working on FreeRCT.
However, I am currently reworking the data stored in the voxels, so it becomes 
possible to store a rollercoaster in it.

  - Reference voxels and empty voxels will cease to exist.
  - Instead there is just one type of voxels containing all that must be drawn at that spot (ie every voxel has room for foundations). Your reference calculations thus will move to the point where the foundations are added to the voxel data.
  - The new voxel will have quarter parts, so you can claim part of a voxel for a ride, and have 1/4 flower beds (this introduces that a voxel is part of a 'ride').
  - For simple graphics, like paths, it should become possible to store additional information in the voxel about path decoration (lights, benches, litter bins, litter). Also, grass needs a counter to grow.
  - It will also have edge-information for hedges and fences.

The shops still need a little kick to open up the road for multi-tile rides, 
then the reference and empty voxels need to refactored out (to surface voxels 
containing nothing and a 'ride' respectively), then 'surface voxel' becomes a 
useless concept that can be deleted, then the additional data needs to be added 
(as described above).

While I have the global battle plan, I don't know all the details. I am sure 
there will be surprises (nasty ones no doubt).

So, your efforts are much appreciated, but your timing is a little awkward 
perhaps.
If you want, we can discuss in more detail how to move forward, in the 
FreeRCTgame group.

Original comment by Alberth2...@gmail.com on 25 May 2013 at 9:30

GoogleCodeExporter commented 9 years ago 
Ah, I thought that might be the case after reading the latest blog post...

Oh well. It was still useful for getting to know the code a bit better. I've 
applied to join the group so we can talk about what to do a bit more. 

I can't wait to see the project improve!

Original comment by Powell....@gmail.com on 25 May 2013 at 8:04

GoogleCodeExporter commented 9 years ago 
Fixed somewhere in the voxel changes

Original comment by CharlesP...@googlemail.com on 20 Jul 2013 at 3:12