Hmm... No actually !Originally Posted by ravells
The numbers 1-8 perform changes in the resolutions to fixed amounts. It might take a second or two to generate it. You could tell whether the keys are working at all by using the '1' and '2' keys because they should be much faster but lower res. The res is displayed at the top title bar.
1 = 128, 2 = 256, 3 = 384, 4 = 512, 5 = 768, 6 = 1024, 7 = 1536, 8 = 2048
You can press 'T' and 'Y' to go up down in res too but its best if you go with a multiple of the native height map res. The one provided is 1024 height with 2048 color.
Some cards barf when going too big tho. Thats the GL driver throwing in the towel for trying to allocate too much memory. Some ATI cards start rendering the scene half white or all white even with a color.bmp file. From experience, only nVidia cards seem to get it right but my testing was a long time ago and I expect things have changed.
On my machine with a 7600GS it will do the 2048 but you can't have any other GL apps running at the same time. I have tested on a lower spec ATI card at lower res and its alright too.
Anyway, if pressing the '1' & '2' keys change res, all I can suggest is to run up the task manager and see if after pressing the '6' key it does a lot of processing and when that finishes does the title bar change to 1024 res.
The image wont change, just the quality of the height terrain.
Edit -- actually maybe whats happening is that 1024 is too much for your card and its failing one of the calls to generate and display it. I am using a pretty advanced feature of storing the entire terrain on the graphics card so that its much faster. You do need a big card for bigger res. Go up the scale and see if it stops working after a few. 512 square ought to be fine tho and thats seriously better than the 100 its starts up in.
Reply With Quote