...is that you're pushing the solution on to the player. 99% of the time the player won't take up the solution and then it's going to be your fault anyway. Deervedly so, because you didn't fix it proper nor proive a sensible default to begin with. 

But you choose the default that works with most old cases, and place the onus on new modders to choose the one that they want in their rc or whatever. 

Here is a zip rotate.zip

Do -game rotate, map rotate or map rotate2

There is an old Mark V in there "fitzquake_mark_4.exe" which has rotation working and under both 666 and 668.

Rotate2.bsp only works right under DarkPlaces, I'm not sure why and I swear that ages ago I had that working in engine tests. I don't think even the RMQ engine does that map right. Try DarkPlaces and you will be standing on rotating platform to see the correct behavior.

Try Rotate.bsp with the provided fitz under 666 and 668. Pay particular attention to shooting the "drawbridge" and standing on it when it raises and lowers with 666 and 668 and try DarkPlaces too doing the same. 

The Problem With Cvar Controlled Stuff...
...is that you're pushing the solution on to the player. 99% of the time the player won't take up the solution and then it's going to be your fault anyway. Deervedly so, because you didn't fix it proper nor proive a sensible default to begin with
Haha :) Fix it proper for 1000 Q1 maps/mods ?
Sensible defaults vary according who to joe dick and harry are. Roughly - QS tries to provide sensible defaults and interface for the Average Joe, and *document* cvars, workarounds, etc, for more technical users/features. 

gb made a bbox rotation demo map back in 2010 that has a bit more stuff to play with:
http://www.quaketastic.com/upload/files/misc/rmqrotate_patch3.zip

It works well in the engine baker attached in #1508, or here is a test build of QS with rotation:
http://quakespasm.ericwa.com/job/quakespasm-ericwa-sdl2/62/artifact/quakespasm/quakespasm-r4daaebe3ea8cf5a23dc5c3530a9abc3f59cbe564.zip

(sorry about the url..) 

Works great!

And in Quakespasm if I noclip onto the top of the rotate continuous it works fine with the rmq_rotate/rotatetest.bsp (and it works in the old Mark V I provided, so I'm not losing my mind that standing on top of a rotator works fine in a correctly compiled decent .bsp)

[Perhaps my rotate2.bsp in rotate.zip is "wrong" or the map compiler used (unknown what it was) did a poor job.

I've not thought much about rotation in quite some time ...] 

Version 0.90.1 of QuakeSpasm is released.

http://quakespasm.sourceforge.net/download.htm
http://sourceforge.net/projects/quakespasm/files/

Changes since the previous version:
http://sourceforge.net/p/quakespasm/news/2015/06/quakespasm-0901/ 

Thanks Oz and Eric 

Thank you guys for all your hard work on this. It really is appreciated by those of us who enjoy playing Quake. The new games have _nothing_ on the classics. 

hi all!
thanks for the new version of the engine!

found this visual glitch with the teleporter and the secret door on the start map of 'contract revoked' pack:

http://imgur.com/VdnkXE3

i was using 0.90.1 windows version, seems to happen on both x32 and x64 executables. doesn't happen with quakespasm 0.90.0. graphics card is nvidia gtx 550 ti with recent drivers. 

thanks for the report. Was trying to be clever and sort the bmodels by texture to gain a bit of performance, but it breaks that scene.

I guess the entities were ordered in the bsp file so that the teleporter entitiy would draw after the bookshelf. 

I've noticed some rendering issues with certain models and fog in the map:

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

Feature Request: Write stdout so that it is line-buffered or unbuffered or something. This would allow grepping the output and have the Quake Injector's engine output log update while playing.

Darkplaces does this well, no idea about other engines. 

In Jackhammer textures animate depending on which is their assigned frame. So you can do an animation that looks cascading inside of the JH viewport (for example with having a bunch of brushes with slip textures with increasing framenumbers.)

This looks pretty cool, but it seems this is not the way the engine handles things, since they all seem to start at +0. This is kinda lame (esp seeing as in Doom having them at different frame offsets is possible. Step back :|)

Would there be a way to implement this easily somehow? r_animtexoffset maybe? 

Duplicate the textures and offset them by hand. 

Well yeah, that is the obvious hack. Have the same textures a whole bunch of time with different offsets. Would be nice if it was possible in a non-stupid way :/ 

Why not just offset the UVs on the brush? 

How would that help with which animation frame is played? 

But it could help hide the fact they're all marching in unison, depending on how tall each brush is.

If you have large flat wall, it's always going to be visible. however, if you break the wall up into steps or multiple slopes and have the liquid flow over each one, this will also help hide the repetition.

Especially if you scale the textures as they 'flow' over the different angles to give them different flow speed. You will get some misalignment between brushes doing that.

If you do want them to move at different speeds (even though physics don't do that) you can just scale the textures on each of your flat brushes. A minor range of variation, say between 0.9-1.1 in Y. 

I think you misunderstood me slightly. As in what I wanted to do.

Imagine a slipgate with that animated red grate texture, +0slip and following.

Imagine now you want to have 4 of these grates next to each other, but starting at different frames, +0slip, +1slip and so on. That would give a nice effect of the pulse going through the machine, not all as once, but flowing through it.

But the animation does always start on +0 no matter which frame you actually put on a brush.

So you would actually have to duplicate the brush and change the frames so that +1slip in the new animation becomes something like +0slip2. pita. 

http://i.imgur.com/rcEbBnK.gifv 

clever! 

I don't really see any reason why this wouldn't be possible in-engine, but I'm trying to think of how it could possibly break compatibility with other content. A cvar isn't the answer because that other content might be in the same map. 

The simplest solution would be a variable which starts animations at the frames which is actually set on any given brushface. Of course this depends on how stuff is handled by the compiler? Does the compiler by any chance set all animation textures to +0?

But if that was possible something like r_textureanimframeoffset 1 or something would work well enough. 

I think the way to do this right now is changing the texture names to suit your needs. There's no way of staggering the start points of the animation cycle.