I was sitting on my Throne of Contemplation this morning (which, co-incidentally happens to be my Throne of Gaming and Throne of Downloading Smut) and with all the maps I've been seeing lately that look great and run like crap, I was just wondering where you (yes, you...) knock points off for that, and also how the fairness rating comes into play.
Here's my problem...I don't have a stellar gaming rig, but I can pretty much run UT2K3 with all the levels above NORMAL, and most graphics options on HIGH (thank you GeoForce4! I love you!) on a properly optimized map. I have NO problems running anything that came with the game with most of the graphics goodies on, so when I see these 'screenshot gorgeous' maps that play like crap, where should I hit them? Do you knock off points for Construction, because of a lack of optimization or just plain putting way too much stuff in a map? Or gameplay, because although the layout and weapons placement is great, it runs like a dog and effects the game play?
Or do you hit them on both?
Perfect example: I downloaded DM-NamelessMap today...layout was wonderful, skyboxes rocked, placement of weapons was decent...WAY too many static meshes onscreen at once dragged the framerate (and playability) into the dirt! Ouch! My first impression is to hit the author in CONSTRUCTION, simply because they should have set certain static meshes to be displayed only in HIGH, and certain static meshes to be displayed on SUPERHIGH detail. Do mapmakers have a responsibility to make a map that is fun for everyone who has the game and can run it decently? Being a mapmaker, and a guy with crummy gear, I feel they do. It doesn't take much to say 'hey, I'd better turn this mesh off if they don't have the details set to SUPERHIGH or it will kill the game'. Thats why UT2K3 has the settings in the first place.
But here's the kicker...someone with a killer gaming rig is going to look at that map, possibly run it with no problem and then I get hit with an UNFAIR rating. And that would make me angry. :[
What would be really neat (F.B., pay attention here...) is if we could make a very brief comment when you submit your rating so that if there was something in particular you hit the map on, other people can see your rationale before calling you UNFAIR and thinking you're a jerk. I got hit with at least 2 UNFAIRS in very popular maps, that if I had a chance to explain myself, I think everyone would have understood. Even if it's just 2 lines where you can say RAN LIKE A DOG ON MY SYSTEM or TOO MUCH PURPLE LIGHT! YUCK! or whatever...
Just wondering what everyone else does in this situation...or am I the only one with these issues?
Thanks,
EvilVey
This is a tough one to answer... and it's a question that I've had myself.
My gut tells me that all you need to do is account for your "throne" when making your score. At least, this is how I do it myself. If I can't even run the map on my computer, then there's a good chance the someone with a good gaming rig is going to have some kind of fps issues. If it runs on my computer, but at 10fps, then it will probably run decently for someone with a good rig.
This argument does have another side: Some maps, even though filled with meshes, run REALLY well even on my crap box (like most of the official maps and BR-Biohazard, which I couldn't believe ran as well as it did). So what now? If it's possible to do that with a map, then like you said, the other maps should get hit hard in the "construction" rating.
... but even still, I rely on my gut (even though this map shows how possible it is to make an interesting map run well) because not everyone has a crappy box like me ...
As the case with DM-CrookedForest. This map's originality and construction is outstanding! The optimization though is horrid, and it runs very poorly on my machine. However, I still gave it a good construction rating because I realize that my machine is the problem, and not necessarily the map -- especially when I see in forum discussions that most people are running it without problems.
So as I already said, I guess my answer is to simply account for your machine in your rating.
Yes, this might prove to be an interesting twist to the moderation process. But I don't know if it would actually end up swaying that many votes. It may have "ran like a dog on your system" but if it ran good for me, I wouldn't care. In the case of "too much purple light" I think it would boil down to how much of a negative hit you gave the map. To me, something like that shouldn't significantly affect the score by itself, so even if you had made that comment, I might still vote unfair if your rating was too low overall.
One thing to remember is that as more and more people join the system, the number of moderations it takes for each rating increases. The chances of unfair votes like this happening will become less and less as the "average computer stats" among the members evens out a bit... so the problem may fix itself.
Again, great post, and a great question. You're definitely not the only one with this issue, and this situation is unique to Mapraider since it has this moderation system in place.
Maybe we can find an equally unique way that will address the problem if we need to :)