yeah, http://www.celephais.net/board/view_thread.php?id=60279&start=248&end=248 

I remember reading that and being disappointed that you didn't like it :( 

Does the random enemy placement also happen when I load a savegame? Because I could have sworn that after I loaded a savegame, there were enemies there which I had killed before. 

but I believe that the enemies which have already spawned at the start of the map will remain in the same place, but the enemies which are randomly spawned that are triggered as you progress are chosen at the point that they are triggered, so there will be some enemies which are in the same place when you load a savegame, but some which would be triggered later on which could theoretically spawn differently. 

gb

The topic has text in it that says:

"Let us know what you think"

If you aren't actually interested in feedback, then please don't put that in your news topics. Or change it to, "Praise is welcome and nothing else" or something like that. 

I mean, ffs, stop whining about you being the ones doing all the work. You chose that! Nobody is forcing you to work on this thing.

And if you're going to be a pissy prick every time you release a demo and people start telling you what they like and don't like, DON'T RELEASE DEMOS. Just work on your game in isolation and be happy. 

It's a 'corona' light blob, just like in bad'ol glquake. Cant turn it off, unfortunately. 

It seems more pronounced, or maybe QuakeSpasm doesn't have it so I'm not used to it anymore.

On a different note, I seem to be able to walk through the ladders to and on board the ship in e2m3rq. Is that a bug that's in the Windows version, too? For the ladder that leads up to the ship, I had to noclip to get aboard. 

r_show_coronas 0 

r_allowerrors_0 :) 

I will be busy trying the milk out the enjoyment of this mod.

I do realize the Func people are easily startled, but will be back and in greater numbers. 

I'm not 100% sure either tbh, but I think that monsters are all set at the start of the map and never change.

It's using Preach's old I3d tutorial, the same method in Quoth so the monsters don't actually spawn in, they're still placed, just turned off.

Then when triggered they appear and do whatever their little brain desires.

There are some other factors that can make things different though, like roaming, and some monsters also have teleportation abilities. 

So I guess if a monster shows up on map load that was not there when I saved that is either related to bad memory on my part or a bug. I'll see if I can reproduce this. 

whats the plan regarding introduction to the player of changed/new behaviour of monsters/weapons etc from standard quake? Just via readme or in game? 

I'd like to do a Manual, but that'd just be for fun - the player should be able to learn everything they need from the game itself.

In any case, they're still not that complex, and I see things like how randomized spawning or roaming work being of more interest to the mapper than a regular player.

One major difference (that wouldn't be visible to someone completely new to the game) is that monsters get better at using their abilities and attacks on harder difficulties.

What I mean is there's lots of stuff thats new to Quake, but you'd take for granted in any other game made after 1996. 

e3m2rq demo
http://www.quaketastic.com/upload/files/demos/e3m2rq_ankh.7z 

 

I couldn't watch all of e3m1rq - there was a disconnect cable error about halfway through and it locked up.

Nice e3m2rq demo - you figured out how the blaster worked and even seemed to be having fun, in a pants wetting terror sort of way :)

A hint about the secrets - in e3m2rq at least they're usually where they were before, although with a slightly different access method. 

I didnt mean features like random spawning or roaming but meant core mechanics (that I've read about) like Shamblers teleporting or ogres with different attacks etc.

I'm not sure how you would introduce the vhanges personally but is the plan that players will just work it out? 

If an Oger fires a rocket at you then its pretty obvious what is going on - same for one with double chainsaws or whatever.

Shamblers only dimension door when at a higher skill level and specifically flagged to do so by the mapper. And they're Shamblers - one of the high-tier enemies and as such players who see this happen are already going to have a good enough understanding of the world in order to understand what's going on.

Basically, yes, the idea is for the player to figure it out on their own.

As you'll remember the original monster descriptions were very rudimentary:

http://quakeone.com/q1files/documents/q1manual.pdf

Probably an added explanation there of the the Shamblers being able to telport in special circumstances on high skills would be a single sentence. 

http://www.quaketastic.com/upload/files/demos/e3m3rq_ankh.7z

e3m3rq demo. It stops somewhere in the middle of the map after I died from squishing (twice).
The map is very quake'y. Too long though.
What is it with the 4th button that can't be pressed?
The fog-poison area wasn't a nice experience/ 

Just yet - technical issues.

I've rethought this map quite a bit, the next version will be shorter and more objective driven.

4th button - I assume you mean one that has a 'rusted' message. The idea is to weigh it down to depress it. 

Is a bug... I'm assuming the shutters that raise there in the middle gibbed you - maybe they're off-axis or something.

The second one is intentional, just unfortunate the NPC placement - he's supposed to show you the danger by getting squished. 

... But I can't seem to quickload (or even load). Engine says "Hunk_Alloc: failed on 4194336 bytes". What's up with this? Any workarounds? I restarted the freakin' thing like 15 times...

Yesterday e2m1rq worked just fine... 

That's most likely one of the 1024x1024 textures. If you can get to the point where you can at least see the console and menus I know that it's not the post-processing textures (which would only be loaded at this size if you were running a video mode of something like 1024x768).

That leaves the replacement textures supplied with the pack. You could try either deleting or renaming your "textures" directory and see if it will load then; that would confirm that it's one of those.

RMQ allocates a 128mb heap by default, so options for you if that succeeds would include specifying a larger -heapsize (try 256mb).

Also, if you're using any other replacement content (e.g. in ID1) kill that to see if it fixes it.

Finally, if you're running Quoth with RMQ (unlikely but I have to check) then don't. Quoth isn't compatible with everything out there, and has been observed to break other mods (ARWOP is one I can remember from recent-ish).

And don't rule out something else on your PC as a possible trouble-maker. If nothing in RMQ content or it's engine has changed, and if it worked yesterday, then it's always possible.