
Everything is to make the track more realistic, eg. we want to make a shooth-crossing canyon, while we can't, cause we can't go outside the editor field. What do you think?
Moderator: English Moderator
Mape size (file size on disk) isn't a problem. A quote by Hylis ...isamu wrote:Why have a limit at all? Surely we all have hard drives that can fit humungous size maps?
Hylis wrote:The 32x32 is better for the 'octree' than using inbetween power of two size, so we optimise also like this (instead of selection another dimension between 32 and 64) and if we move from 32x32 to 64x64, it makes 4 times more blocs on the ground (1024 to 4096) Then if you want to fill 3000 additionnal spaces to have your scenery 'not flat', the bloc costs too much for this on Canyon. It may create trouble in memory as well for the 2 Go 32 bits limit, or a least make it too difficult for small configurations.
We have then decided to go with 32x32, like the first TM and stadium. We feel it safer to start with even if I recognize that having bigger construction field is cool. We even developped a special technology to optimise it for 64x64, but I still feel it too risky to do it.
The bloc size of Canyon are 64x64, like Island indeed, but the car speed is quite lower from it.
Users browsing this forum: No registered users and 2 guests