Thanks for the feedback guys! Quite a lot to address here...
My only suggestion is to allow movement with arrow keys, not just WASD (I'm an arrow man), and to increase the rate at which movement happens, it seems too jerky and kinda slow at the moment. Some of the tree models could probably use a little work as well, a couple have stretch-mark artifacts on the leaves and branches, doesn't seem to be my system doing it.
- You can set the movement keys using File->Set Keys (this will save between sessions) but I can add arrow keys as a second default option.
- I forgot to mention that SHIFT speeds up camera movement. The amount of acceleration can also be controlled with the sliders. There is no smoothing so movement will be jerky at the mo.
- The tree models are certainly dodgy. I have absolutley 0 modelling skill so all the models are the best I can get for free off the net (or in some cases badly generate). Unfortunately these models came in an undocumented format (Torque Engine) and the only available converter screwed them up. Any better models will be happily be used instead, but otherwise there isn't much I can do.
- faces above fortification missing
- bridges, windows (;
- maybe changing the direktion of the lighting?
- trees/boulders on/off did not work
- maybe scaling of the tree sizes?
- I think I know what you mean here.
- I'll get to it. It's not easy you know
- Try +/- on the numeric keypad or change SUN_ANGLE in the .ini file
- Known issue, will be fixed very shortly
- Doing this dynamically causes some problems, but I'll think about it. You can permanently increase the tree size by editing Data/objects_natural.csv. The last column is the model size in percent, so doubling it will double the tree sizes. I didn't want the default to be too large as it will cause problems with overlapping into neighbouring tiles/tile above.
Most excellent bug report!
Thanks, I'll try and reproduce it. Presumably it's to do with generating the slice geometry.
Not sure what I can do about it crashing in Wine, I have no way of testing it. Does the log file indicate that it crashed at a particular point during initialisation?