mapthis - map of germany too large (5,29GB)

[finalmagic2]

3 days oO!!! WTF!?!?!?

then i need a whole week oO $#@!...
my girlfrind will killing me xD

ok but if theere no faster way i must do this ^^ xD

other options would be helpfull, otherwise i will die if she coming home xD


EDIT:

Is there a possibility to start and stop the progress or is the only way to let it run xD??

[Codaz]

Lol i think it's time to make a topic called:

Who has the biggest Mapthis map :thumbup:

5,29 GB loooool

Yes you can resize the map with MIB.42's tool, but it will take a long time depending on your computers speed.

For best results:

Intel Quad Core machine
A lot of memory (2GB+)

[fischauge]

2Gb RAM and a Intel C2D 6300 @ 3ghz should be enough :P?

[finalmagic2]

@fischauge

hey you have a fast cpu xD i upload the 5,29 GB and you convert it xD hihi ^^

[fischauge]

Ok final, I would do it ^^, cuz i would like to have the map too ^^ and i would reupload it for you.

I have 1mbit Upload. If you need space to upload the map, I can arrange something. So PM me .

[MIB.42]

Hi Guys,

I understand the frustration of taking a long time, that's why I added the Q-Create for the PNG type maps.

If you think about it, reducing the maps is a very compute intensive process. For each tile, it has to
1. Load the map ( and uncompress the image )
2. with PNGs it has to do color-reduction ( from 256 to 16 is not an obvious task. It is a lot easier to do from x million to 256 than from 256 to 16 since the less color you have, the bigger the information loss can be and harder to find a suitable match with interactive adjustments...).
2. with JPG based maps, it has to recompress ( several times during analysis stage )
3. After the color reduction it has to do the file write. I also added buffered file read and write ( maximizing the IO speed ).
4. If you do not uncheck the "No Visual", it also has to do all the screen updates which includes memory transfer, screen transfer and sync.

In some cases this is done on hundreds of thousand of tiles, so you do the math... ;-)

Actually, since color reduction requires a lot of memory access, the most important thing is not necessarily the CPU speed, but your memory R/W characteristics, like using DDR3-1866 instead of the usual DDR-266 or DDR2-667 would give you faster performance...