[kapteeni]

I'm not really very concerned with updating the Zapolar map. It's very nice as it is.

Think you are missing the point a wee bit. This isn't about updating the Murmansk map, which I agree is spot-on as it stands. What's happened is that Mixx has repainted a lot of the stock objects, but hasn't created new objects for them. So now EVERY other map that uses these objects has them in Mixx's paintschemes. You'll have grassy tracks in deserts; pink barrack blocks instead of black; walkways on the harbour (port base) objects that look stupid if they've been used in another map at 90 degrees to Mixx's.

Now I like Mixx's repaints, he's done a fine job, but they need to be additional to the stock objects rather than instead of.
Right now, if you've installed Zapolar'e you can use Mixx's trees and objects without altering the static.ini or anything else; in fact if you go back and look at some other maps you'll find them already there, because they've OVERWRITTEN the previous paintjobs. Whether you want them or not. The same thing happened with IJ's Palembang maps; another map I'd installed previously changed the colour of the PCP runway plates from dark grey to sand. IJ had placed grey plates - I get sandy ones, and will do on EVERY other map that uses them.

Any mapmaker repainting objects MUST create a new object file for them, or this will happen over and over again.

:cheers:

Unfortunately, that is true...
That is why we need to obey the rules that we will not overwrite default objects and textures, It takes some time to create new objectpack like canonUK did. But it is a must. Same goes with textures, That is why we must use own prefixed texture folders too.
Arctic map is a beauty and you can always backup your original objects too... It Is another option. But if i were Mixx, i would do a own objectfolder and lines for static.ini.
I always make backups before installing new maps in case of things like this.
Kap