my guess is 0.5 puts a vertex on the center of a pixel, rather then the vertex being on the corner of 4 pixels. I can't say why it's there unless it was to emulate winquake, and obviously you're saying it doesn't. 

http://i.imgur.com/AJIHWYpl.png 

 

Bear in mind you're gonna make some people unhappy by changing that 0.5 pixel offset - for example sock took advantage of it on some of his models to create "half-width" highlights on a skin at double the resolution the skin size normally allows details. The Quoth .mdl format ammo models are also textured with the assumption that UVs sit at the centre of the pixel - which prevents them being a pixel perfect match to the bsp versions, but they're gonna be a whole pixel adrift on the right hand edge after the patch.

If you say it's closer to winquake then that might justify it, but just be warned that the GL rules might have become the defacto standard in the mean time...even the software renderer in QME uses the centre point. 

that makes a huge difference. 

God, I hate GLQuake. 

Yeah, I guess glquake's behaviour for the texture alignment is probably more of a de-facto standard than winquake's at this point 

This "different standarts" situation is rather sad. It pretty much eliminates the idea of pixel-perfect detailing. Even if you align everything for one engine, it will look like ass on another. 

 

Runic Monster 

Sock working on a quoth map?! Nowai 

Keep it burning! 

This "different standarts" situation is rather sad

I feel like I just had a discussion with someone about this.

also: yay sock 

if every GL-based engine uses the 0.5 offset, and QME (the only native authoring tool for quake models?) uses the same offset, then it seems like this is probably worth keeping.

Probably if you want to "fix" this you should have a cvar that can restore the behavior of all other GL engines, since a lot of content has been made now with qME and tested in a GL engine. In fact what content HASN'T been made with qME? 

Yeah, glquake and winquake are just incompatible in this small way. I'd give the tiebreaking point to glquake, only because winquake alias rendering has a bunch of artifacts when it renders far away models and large polygons - the distortion is very high. It's harder to make the case for an exact standard based on an inexact renderer - even though it has seniority.

Disclaimer: I may be biased, on account of having carefully accounted for the glquake behaviour on several models and tools, not knowing that winquake behaved differently.

ps: Loving those force-field walkways sock! 

HAIL SOCK 

fuck, you're just so good at this!

Also Lunaran, what ever happened to the grimy medieval map you posted shots of years ago? 

Sock, that looks awesome. 

Sock, you've made look that even more fucked up and cool than what Neggers does with space maps. Sweet. 

Kind of a Negke vibe. 

yay socks back and has been mapping all this time!

never been a fan of floaty space maps, but it looks sweet. fog is very atmospheric. 

has the most notes of any map I have posted on my quakeguy blog and I only posted it a couple hours ago (35 notes so far) 

http://i.imgur.com/3Z9BSUN.png 

sock is back 

Stop being the better negke!