I was doing some GLQuake skin optimizations, because the target engine is QS. Now I remember why I hate GLQuake. 

https://drive.google.com/open?id=0B9DxOfPvG2G1Z3pGNHVGTmF0Qkk

GL-friendly. Don't like the lever, may still try and do something with it. 

https://drive.google.com/open?id=0B9DxOfPvG2G1Sms0N25CZ3NmbDQ 

If anyone is using my qmdl python module or the standalone fbxtomdl.exe converter, I recommend you trundle over to my blog and download the new versions.

https://tomeofpreach.wordpress.com/

The new versions incorporate several fixes to make exported models compatible with software-based engines, ranging from optimisations to visual corruption and even crashes! Thanks to Sock for his help in identifying the issues. 

Can you add a fix for the skin normals?
A while back I've posted <a href="https://youtu.be/a73Z4JxKPko";this video</a> showing the problem. 

What tool are you using which creates models with the backwards normals? Is it the fbxtomdl tool? Because I don't have the same issues with models I create from the main library. 

Those models aren't from me, they're from Skiffy and Capnbubs.

According to the readme, Skiffy used your MD3toMDL tool:
http://www.celephais.net/board/view_thread.php?id=61285&start=92 

If the normals are backwards does that make them abnormal? 

Hi mankrip, can you drop me an e-mail? My address is on my profile. I wanna send you a model which you can check that the normals are correct on. If that's so, I'll need to get in touch with Skiffy and find out what's going wrong. Unless they have the pre-2013 versions of the tool which did have a bug in calculating normals... 

E-mail sent. 

https://drive.google.com/open?id=0B9DxOfPvG2G1akY3SXFMV3BaSkE

I'll shove everything in one archive from now on. Making two versions of every model is rather butt, maybe I should stop.

Contains recent versions of shotgun, double shotgun, and nailgun. The shotgun has a pickup model that's useless outside of mods. 

I have a question. What are *.ms2 files generated by GLQuake? 

Nothing anyone should ever care about anymore. 

GLQuake reorders the model into the form that it sends to OpenGL (tristrips and fans), the ms2 file is that form cached that to disk.

Both the caching-to-disk (presumably it was faster in '97 to load the file from disk than to reprocess the model) and the rearranging into tristrips/fans are useless nowadays, so no engines do this anymore. 

Okay, thanks.

I was just searching for a way to include GLQuake-optimized models with regular models in a single package that doesn't require tinkering in order to play with different engines. It was a stupid idea, but I wanted to make sure.

This situation with model skins does bad things with my motivation. I wish the habit of shifting texture coordinates died with vanilla GLQuake, but important engines retain it (while other important engines don't), and it's some sort of a standart now (just like not paying attention to garbage fullbright pixels). 

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

Grenade launcher? Like the model. 

What do you mean with shifting tex coords? First time I've heard of that. Just being curious... 

Software Quake (as well as several source ports, including darplaces, strangely enough) places tex coords between pixels. GLQuake shifts them half a pixel right and half a pixel down, placing them at the pixel centers. Elaborate detailing goes out the window. Fitzquake/Quakespasm are also affected. 

Find the Quakespasm thread, do "show all posts" or start at 1 or whatever it is to see every one of the 2000+ posts.

Then in your browser Find look for the word "coord" and you'll find an informative discussion on this from a couple of years ago that discusses the differences that dwere refers to between software Quake and the hardware renderer versions. 

Do you have techniques to minimize the damage? Or do you just work with one engine and hope your model won't look too broken with another? If it's the latter, then which standart do you prefer?

I was thinking about the former, and I can see a way to preserve symmetry where it's needed, but it'd require constructing the model in a certain way. Simply making something decent is hard enough for a novice, and then I have to worry about all this compatibility nonsense.

Why, GLQuake, why? 

When I made the static entity for a convoybelt the hardest part was to make the cell_ammu blocks correspond to each other.

When they all four made the simultaneously movements and I had it right counting on the framenumbers the different engines all made their own movements.

Framegrouping helped, but as each engine treated it accordingly strange effects was the result. 

I'd go with designing your models with GLQuake in mind, for two reasons. The first is that so many more ports are based on glquake, and they're so much more widely used, that they've become the de facto standard now - even if the software vertex placements came first. Secondly, the software renderer has so many approximations and wobbles when it comes to alias models that it's not going to benefit from that level of care and attention.

As your screenshot seems to be going for a pixel-art look, I wondered if you could try doubling the scale of your skin. So each "pixel" on the visible skin would actually be a 2x2 block of pixels. Sure, you've effectively wasted 300% memory compared to the original, but the GL and Software renderings will be more alike. As a bonus, it might look less "muddy" for people not using nearest neighbour in the GL world. 

DirectQ and Darkplaces are using the original way of interpreting tex coords, so it's not that simple.

As for your second suggestion - IIRC, the software renderer can't work with skins taller than 128, so I'd have to redo a lot of things. In any case, I'd rather not resort to something like this.

Thanks for your thoughts anyway. 

I believe the limit is 192?