1. Statusbar shows wrong icons/values for the new Hipnotic/Rogue weapons

2. Buzzsaw traps in one of the mission packs are not interpolated

I use the the latest x64 QuakeSpasm (version 0.85.9) 

1. Did you use the -hipnotic / -rogue switch? 

I settled it, only the problem #2 remains. 

Which mission pack / episode is this in ? 

DoE (Rogue) mission pack. Map name is "Blood Sacrifice". There are three buzzsaws in a corridor, which go back and forth. They are the only thing that's not interpolated. 

R2M6 

Yes, and any other map where such buzzsaws are present. If they managed to lerp weapons and all the models in general, I believe they can do the same for the buzzsaws. 

The animation is probably interopolated. It's hard to tell with all the twitchings. Not that it would be of much use - said animation is not very lerp-friendly.

The movement _should_ be interpolated too, but it isn't. My guess is that the problem lies in the implementation of the buzzsaws, the way they function, but I could be wrong. 

But try r_lerpmodels 2 in case the buzzsaws are on the nolerp list? 

Correct, the buzzsaws themselves are interpolated - their movement isn't. When I said "buzzsaws are not interpolated" I actually referred to their movement.

Buzzsaws move on their exact designated routes (lines), they are not like enemies who can roam wherever they want. This is just my guess, as I don't know much about engines and editing. 

@onetruepurple

r_lerpmodels is already on 2, and the nolerp list is already empty. 

The buzzsaw doesn't actually move in the normal way. What it looks like (only from looking at the QC) is you make a func_train or something that the player can't see. Then you target the train with the buzzsaw. Every 0.1 seconds, the QC sets the origin of the buzzsaw to the targetted train. This is why it doesn't interpolate, because it's not supposed to-- the QC call is setorigin. 

I think because if it was one big buzz-saw which moved as part of its animation then the bounding box would be this massive impassable thing. 

So, no way of making it smooth? 

The problem lies with QC. The engine is working as intended. Here is a patch:
http://mobile.sheridanc.on.ca/~jonescor/temp/RogueBuzzsawPatch.zip

Just unzip pak1.pak into your .../quake/rogue directory. (next to the pak0.pak file) 

Works like a charm, thanks! 

there is a bug in fitzquake where monsters riding lifts don't interpolate motion correctly. I wonder if this is related to that.

AFAIK, the client-side interpolation doesn't care what method is used to update the entity origin, and it should work correctly, but obviously there are some holes in this based on the buzzsaw problem and the enemies on lifts problem.

So i'm not ruling out that this is an engine bug. 

where certain textures look like absolute shit. Namely carch03, the red circle stain glass window seen in E1M5. Looks fine in DirectQ though. I have a feeling it's something to do with resolution of the texture. 

Fitz V

You're going to have to elaborate on that. 

AFAIK, the client-side interpolation doesn't care what method is used to update the entity origin, and it should work correctly, but obviously there are some holes in this based on the buzzsaw problem and the enemies on lifts problem.

There must be limits to this though, like when monsters/players teleport? It would look weird if that was interpolated. Is it based on a maximum distance/threshold? 

It may be due to the solid and movetype settings:
self.solid = SOLID_TRIGGER;
self.movetype = MOVETYPE_FLY;

I believe I've had problems with interpolation when using SOLID before.

The code uses the stock path_corner functionality that monsters use, but instead of using a movetogoal (that would not work for vertical differences) there's a single think function that does:

dir = self.goalentity.origin - self.origin;
dir = normalize (dir);
dir = dir * self.speed;
setorigin (self, self.origin + dir);
self.angles_x = self.angles_x - 60;
self.avelocity_x = 60;


Note also that the frames are not actually use and that the model is rotated via code so interpolation for rotation shouldn't be a problem. 

This is what I mean.

DirectQ -
https://www.dropbox.com/s/l03v8gop65zp17k/dq.png

Fitz V -
https://www.dropbox.com/s/jvpqijeux9wdeyh/fitzv.png

Fitz is garbled. I think it's trying to stretch the texture somehow so both sides are the same length/width. There are lots of examples of this, pretty much all the door textures, the slipgate textures, a lot textures I used in q-deck.

People tend to revere Fitz but, as good as it is, it's still far from perfect. It's a shame Baker no longer works on it really. 

That looks like the effect in stock glquake of resizing textures to be power-of-2 dimensions. Which is odd as fitzquake was one of the first engines I can remember addressing this problem, by padding the textures rather than scaling them. Unless I've misremembered and that was only performed on models and not on wall textures - or could it be that when you apply nearest neighbour render mode the fix gets reversed out somehow? 

it does look effed up, in both FQ085 and QS 0.85.9 

needs support for GL_ARB_texture_non_power_of_two.
basically find the rounding code and bypass it if that's supported. no more uglyness.
directq, dp, fte should all support this, no idea about rmqe.

@Preach, the fitzquake padding hack thing only works on non-tiling surfaces, which means 'not on world'.