-
Notifications
You must be signed in to change notification settings - Fork 0
Ideas for Major Changes
This is a page to list ideas for changes we want to make to Overviewer, but may be very large or may break backwards compatibility with old maps.
Note: Breaking backwards compatibility means that existing maps will not look the same as newer maps. For small worlds, this shouldn't be a problem, since the time to re-render and entire map will be small. However, for larger maps, the time to re-render may be prohibitively long.
(Discussion originally spawned from Issue #242, which lead to the DTT overhaul.)
This would involve putting all the free-floating python files into a python package, and moving the front-end code out of gmap.py and into its own script (like overviewer.py or something). This is a minor feature, but a large code rearrangement, so this might not get done anyway. -- agrif
If you're going to be looking at invalidating previous caches, it may be worth while to add the option to choose a map orientation. Issue #48 Feel free to ignore since I'm not contributing code. --Contre
We should strive to make overviewer as fast as possible. Pigmap produces very similar output, but runs much quicker. We should try to achieve pigmap-like speeds (even if this means re-writing some code in C/C++) --eminence
One idea for this is to reduce (or provide an option to reduce) the detail of the closest zoom level. Right now Overviewer lets you zoom in really close, which is great, but reducing this detail by just a factor of 2 (one zoom level) would improve render speeds considerably for those who want this tradeoff. Suggested by ArmEagle in Issue #244 -- agrif
Or the ability to specify a maximum and a minimum zoom level. Then like chunklist you can render updates for a specific zoom level. -- BarryCarlyon
How about GPGPU using pyCUDA? You could move all the worker processes to the GPU which has far more cores than a CPU does. It would at least speed up the process on nvidia graphics cards. -- CounterPillow