New rule

Moleculor

Ok. Almost every post with a screenshot has about twenty posts asking "What are the r_speeds?" (And about half of the replies contain the -answers-, which people don't seem to be reading). Soooo... (And this has actually been in the Mapping FAQ for a while, though compared to the board's age, it's a recent addition) from now on, please only post shots with r_speeds in them.

It doesn't matter if the r_speeds haven't been optimized, or if they're over the limit, please just post the r_speeds in the pic, or in the post (preferably in the pic).

<span style='color:red'><b>***Ok, ignore this one... scroll down to my next post to find out the newer rule. Sorry.***</b></span>



<!--EDIT|Moleculor|Feb. 18 2002,16:39-->

ChromeAngel

Screenshots are often re-sized down from the mappers in-game resolution, making the r_speeds un-readable.  Mentioning the r_speeds in the post with the sceenshot should suffice.

realityisdead

I have been finding this quite annoying also. I have stated my own reasons for not posting r_speeds in the shots themselves, and am assuming (hoping) that these reasons may be respected. If people would actually <i>read</i> the posts, not just look at the pictures, it would help... seeing as the answer is usually two or three replies up from the question. Geez...

BTW, if you missed it, here is my reasoning:

"I hate showing r_speeds in my shots. It's misleading, as I usually would go for shots where the w_poly is as at its highest... but they are really a lot lower on average. I'm actually quite sick of talking about r_speeds right now. I'm just as aware about the limit as anyone else, and I don't need anyone to remind me of it, or try to enforce it upon me. If I don't get it right away, I <i>will</i>. If I just can't get them down in a certain area, I will cut the area. If it becomes too big of a problem all around, I'll cut the level."

Muu

I dont see why you should post r_speeds in a post eather there completly irrelivent during the development stage and the last thing you need when you post a question about lighting in a room is 30 responces about r_speeds! which has happend to me far too many times (not nessicerily here).
Mappers have the right to build a room with 2000 poly but if it doesn't play well it won't get into the mod! there for all mappers should be given restraints but not laws about how many polys they can have. I built a room yesterday with 250 polys at it max but it rendered at 7fps on my rubbish graphics card because it had to large glass arches - nuff said.

MonsieurEvil

I have to agree with the general concensus here: r_speeds are cool and everything, but as long as they don't exceed the mapping guidelines, it's somewhat irrelevant if they are 699 or 10. I don't think they should be required to be entered; if a mapper wishes to list them or not, it's really their call.

That being said, if you are posting information about a map that you feel is <b>done</b> or where you would like people to play on a test BSP, I feel you should provide that sort of information as a warning to people. Someone on a 56K modem who downloads your big ol' map only to find that it's averaging 1000 and that they have wasted an hour is going to be justifiably upset.

Relic25

It's a bit silly to hound the mappers for r-speeds anyway, unless the person asking is just curious.  99.9% of the time, mappers are well aware of what the r-speeds are in their own maps, so they don't need other people pointing them out.  The only circumstance where I can see including r-speed info as relevant is if the mapper is asking for ideas or advice on additions or subtractions to an area pictured in their screenshots, and they are including r-speeds so that other people who may have ideas are clear on what is possible given the current w-poly count.

realityisdead

If there is any sort of rule about this I think it should be more along the lines of "If you, out of curiousity, would like to know the r_speeds of an area in a screenshot, then please do the following:

1. <i>Read the post</i>. You might actually find what you are looking for there.

2. If it is not anywhere to be found in the post, ask in a polite and mature manner which specifies your curiousity.

On the other hand, if your intent is to keep everyone in line, and make sure they don't pass that forbidden line:

1. Stop and think to yourself: "I wonder if the level designer is aware of the r_speed limit, and if he knows whether or not his own r_speeds are under this limit."

2. Answer, "Probably".

3. Ask yourself: "If his r_speeds are well above the set limit, is he at least going to attempt to do something about it?"

4. Answer, "Yes."

5. Ask yourself: "Do I really need to remind him of this when it is already a huge burden for him?"

6. Answer, "No."

Flayra

Yeah I agree with everyone else too.  While posting r_speeds may cut down on some unnecessary posts, I'd hate to discourage people from posting their work.  I don't think there should be any rules, just keep in mind that people generally do want to know the r_speeds (though as per our conversation on an earlier thread, most people should be confident that any r_speeds problems will be taken care of in the final release of a map).

Moleculor

Ok, I feel I should post an explanation for this rule:

Threads are reaching full pages of nothing but:

"What are the r_speeds?"
"Oh, around 250"
"What are the r_speeds?"
"At maximum, 290, but on average 250 or so"
"Wow! Nice pics! What are the r_speeds?"
"Read the F-ing replies n00b!"

Ok, so that last line isn't showing up (thankfully/yet). But you can see why I posted this.

However, I understand the whole thing about 'taking shots from the highest r_speed areas' ('cause those are mostly the highest detail areas) sooo... scratch the rule.

<span style='color:red'><b>New rule</b></span>: Everyone realize that r_speeds are going to be fine. Mmmkay? Please, no more questions about r_speeds.



<!--EDIT|Moleculor|Feb. 18 2002,16:41-->

Moleculor

<span style='color:red'><b>Newer rule</b></span>: Just forget about anything about r_speeds. Ask, don't ask, I don't care. If'n you -do- ask though, and it's already been answered, expect a PM from me.