CodeImp
Moderator
Posts: 1495
Registered: 12-03 |
I see some clarification is in order here, because there seem to be some misconceptions.
My plugin starts at 64x64, just like andrewj's. It even uses the same dithering algorithm (andrewj lovely called this a 'butterfly' algorithm, that sounds sweet :) but since it is multitreaded it goes a lot faster and on small maps you may not even get to see the 64x64 blocks in the first frames.
The plugins spawns the same number of threads as the number of logical cores your CPU has and assigns each thread to one core. You want this, because you want your results as soon as possible (no?). The threads have a 'below normal' priority, which means they give up any and all CPU resources that any normal program would like to use.
My plugin focuses its effort on the area that is currently in view. So if you zoom in, the area you are viewing (in mappixels) will be smaller and you will get the details sooner. You can zooming normally, or by dragging a rectangle. The plugin will continue to increase resolution until 1x1 mappixels. After the current view is completely computed at that resolution, it will continue with the entire map (when you change view again, it will again try to compute inside the view first). In contrast with andrewj's VE, my plugin does not forget the data outside your view, so when you zoom back out (hint: press HOME for instant overview) you will still see what was computed there.
Bucket: Never noticed that. But I uploaded a new version of the plugin shortly after the DB2 patched version, so (although I didn't fix anything that could cause your machine to lock up) you could try downloading it again, who knows, maybe it downloads better this time :P
|
05-31-12 21:23 
