Questions about the new RMQ engine!

[Ezerhordren]

well, I know all of you guys are pretty busy either coding kick ass engines or playing the shit outta quake, so I'll go straigh to the point:

How can I use custom textures/models for the new RMQ engine? so far playing it vanilla (it's sounds a little bit weird since is a custom engine huh?) plays great, smooth and all... how can I load quake reforged enemies or rygel textures into it? Thanks in advance guys

BTW: I readed all .txt files in it and didn't find info about. Im quite a nooB on the new quake engines and never tried fitzquake (mostly directq) so sorry for being such a fucking moron.

[golden_boy]

Replacement textures for maps (QRP etc):

put the pk3 in quake/id1/textures and unzip it. I think the engine doesn't support .pk3s yet, but it will load tgas and it also supports the .link files used by the Quake Retexturing pack. Just gotta unzip the .pk3 for it. For now.

Replacement textures for models:

put in textures/progs/ and call them something like

/textures/progs/v_shot.mdl_0.tga

I think pk3 support is on the to-do list. This engine is a descendant of Fitzquake, which didn't support pk3s and all this newfangled stuff. It is slowly being added though.

You can run vanilla quake in it just fine. It is also very good at running HUGE maps (warpspasm etc). That's what it does best, really. Run extreme maps.

Post any bugs you encounter here it's the reason the engine was prereleased in the first place, we're trying to collect feedback.

[MH]

Yup, what GB said. Bear in mind also that this isn't intended to be a general purpose client but rather an engine built for the specific purpose of running RMQ. Therefore certain features which may be expected in general purpose clients may be lacking here. The longer term hope is that other general purpose engines will pick up RMQ features, and there will no longer be any reason for a dedicated RMQ engine to exist; instead you'll just pick the engine you normally use and run with that.

But we are always interested in hearing any bug reports or feedback of any kind.