[ Hmm, this is a rather OOC post sorry, but I was in game today and noticed dropped item guarding was committed to laanx... this means (test it first to make sure though) that you can drop items on the ground, and as long as you don't move more than about 5 units (near enough to meters) away from it, nobody but yourself can pick it up. ]

[ So, test to make sure it works first, use at your own risk, there may be bugs, bla bla... just for your information ]

Well, as I am unable to verify, even with a clean svn data directory with either stable or trunk... the next thing somebody could do if they can be bothered, is try compiling a clean checkout of the latest revision svn stable, without copying any data files over other than zoneinfo.xml and servers.xml, and see how it works... also the planeshift.cfg file in the root, try moving that and checking out a new one.

Well, part of the slowdown is because of unoptimized/buggy lighter2 code, it also uses more memory than previous versions, which makes it swap at times on my machine... some of the problems might already be fixed in later versions of crystalspace, bits that are in planeshift might be looked into sometime soon^TM.

So, my thoughts are don't throw away your old computer yet, planeshift should in theory still run on older hardware once things are fixed.

You run ps su root? I have not been able to reproduce this problem myself since the 019 release client, I don't have a 020 release client... but yes I do have svn installs

I dunno, maybe the perms are readable/writeable by no one, have a look through your ps install and check all files in data/options/, they should all be writable by your user, or a group you are in.

Also check out FS#486, I had this problem for a while myself when testing the tutorial.

edit:  I should really have read the previous post more thoroughly... post count +1 

Hi there. This could go into the wishlist, but also if you have thought it through, and can define fairly well what you want changed and how to change it, you could submit it as a 'feature request' on the bugtracker. It may not take much coding, to make it so you can mine for anything if you do not specify a resource, but the developers will probably never know about it if you only post here. The worst that can happen is the report being closed as "Won't fix"

Just all remember to think your report through well before submitting

Sorry Thom , I don't think it is due to lighter2 (at least not all) the other maps without grass seem to run just as fast for me, and I got very similar performance near the laanx temple in the grass with both versions of art (though I will test again to be sure). Though I think I have longer loading times, and greater memory usage with lighter2 maps.

edit: after testing multiple times each with both 019 and 020 art, on the maps hydlaa_plaza, arena and bdroad1, Framerates were about the same both versions in arena and bdroad1, but with hydlaa_plaza the 020 map was much slower in all places with new grass, it was maybe a tiny bit slower in other places without grass, and in the area around the laanx temple with grass in both versions, but very close.

Loading times were up by huge amounts for hydlaa_plaza: about 15 seconds with 019, 1 - 2 minutes with 020, and arena: 7 seconds with 019, 45 seconds - 1 minute, though bdroad1 was about the same both versions at around 15 seconds. This is probably caused by increased memory usage and more swapping out to disk, 020 used from 100-200MB extra on the combined rss + swap value of psclient measured in top compared to 019, tested with those three maps, done twice with each version, restarting the client in between. I was running a linux 64 bit cvs debug build, I will test with the release binary when I get it.

I have heard that removing the grass from hydlaa_plaza sped it up a lot for some people, I will try that later.