 News | Forum | People | FAQ | Links | Search | Register |
Log in |
|
|
Hmm, I did decompress it.
Sounds & textures: we are aware of the issues and working to fix them. Ruthlessly cutting half of the sounds would unfortunately again require replacements, and these types of sounds are very hard to acquire if you have no budget (licenses for use in video games are $$$$). Surprisingly few people (none) have stepped up to help us with voice acting, too. ;-) -> We're working on it. Yeah. Here is 7z-ed part2 of the demo, it works.
http://www.quaketastic.com/upload/files/demos/rmq1b.7z cool, sorry if I came off as an ass with that comment. I can only imagine how hard it is to find or make good quality sfx and textures!
Just curious, will you guys consider using any of the originals though? I know if you run at 16-bit/44100Hz the quake resampler sounds pretty awful, but if they're resampled properly they sound good to me when mixed with other 16-bit/44100Hz sound or music. If it's any help, I have a patch in the Quakespasm patch tracker which improves the built in upsampler, getting rid of the high-pitch "grunge" when upsampling 11025Hz to 44100Hz: http://sourceforge.net/tracker/?func=detail&aid=3467305&group_id=304914&atid=1285038 Are you kidding me http://i.imgur.com/xgSQl.jpg
How is that even possible? The map has some ridiculous amount of verts and lightmaps. It's fully vised at level 4, which only took 13h. I didn't think that was too bad :O I was using the computer for vids and browsing at the same time. But yeah - r_speeds are high (naturally), hence the new engine which used much more modern rendering tech :)
so what about glithces?
http://pix.academ.org/img/2012/01/11/0304affa1789410b7ab56bd72b777614.jpg http://pix.academ.org/img/2012/01/11/6d8542ce32312a5d9fe24ecae37d5e65.jpg condump: SDL_net TCP/IP initialized Exe: 23:24:51 Dec 28 2011 128.0 megabyte heap Video mode 800x600x32 initialized GL_VENDOR: ATI Technologies Inc. GL_RENDERER: RADEON X600/X550 Series x86/SSE2 GL_VERSION: 2.0.6590 WinXP Release FOUND: ARB_multitexture FOUND: ARB_texture_compression FOUND: ARB_texture_cube_map FOUND: ARB_texture_env_combine FOUND: ARB_texture_env_add FOUND: EXT_texture_filter_anisotropic FOUND: EXT_compiled_vertex_array FOUND: ARB_vertex_buffer_object FOUND: GL_EXT_swap_control FOUND: GL_ARB_vertex_program FOUND: GL_ARB_fragment_program 8 bit stencil buffer Created gl_postproc_texture at 1024x1024 Created gl_motionblur_texture at 1024x1024 Sound Initialization SDL audio spec : 44100 Hz, 1024 samples, 2 channels SDL audio driver: dsound, 65536 bytes buffer Audio: 16 bit, stereo, 44100 Hz SDL detected 1 CD-ROM drive CDAudio initialized (SDL, using E:\) CDAudio_Init: No CD in drive ========= Quake Initialized ========= execing quake.rc execing default.cfg execing config.cfg VID_Gamma_SetGamma: failed on SDL_SetGammaRamp Video mode 640x480x32 initialized GL_VENDOR: ATI Technologies Inc. GL_RENDERER: RADEON X600/X550 Series x86/SSE2 GL_VERSION: 2.0.6590 WinXP Release FOUND: ARB_multitexture FOUND: ARB_texture_compression FOUND: ARB_texture_cube_map FOUND: ARB_texture_env_combine FOUND: ARB_texture_env_add FOUND: EXT_texture_filter_anisotropic FOUND: EXT_compiled_vertex_array FOUND: ARB_vertex_buffer_object FOUND: GL_EXT_swap_control FOUND: GL_ARB_vertex_program FOUND: GL_ARB_fragment_program 8 bit stencil buffer Created gl_postproc_texture at 1024x512 Created gl_motionblur_texture at 1024x512 execing autoexec.cfg execing scrama.cfg 3 demo(s) in loop RMQ Engine 0.85 (Dec 28 2011) SERVER (42813 CRC) Termination: Cerebral couldn't exec maps/e3m1rq.way Saving game to done. ]condump I'm getting some very odd graphic glitches (what looks like long rectangular arms stretching out to a shotgun that's pointed toward the ceiling) but I forgot that shubbyhubby doesn't like
gb - regarding sounds and voice acting, my home studio was topped off by a copy of SoundForge 10 Pro at Christmas time so I'm ready to make, change, and generally screw with any sounds or music you need. As for voice acting, my actor friends at the theatre company would be keen to get involved, me too of course. So, let's start a conversation...email is in the profile. Are for each unique object\texture (ie 900 grunts = 901 draw call)
To put that in perspective this _entire_ map with r_novis is ~5000 draws (yeah it's a heavy map). There is no way to have 900 draws in that scene alone. The polycount is insignificant, 100k with 10 draws would run faster. You may have found one of those rogue spots where vis doesn't do it's thing as effectively. It's also the case that the engine alpha sorts absolutely everything that needs it, including individual sprites if necessary. It will batch sprites but switching textures or to a different object type needs to break a batch, of course. Even aside from that, any kind of texture, lightmap or object type switch in the main renderer also needs to break a batch.
(Note the ~7000 epoly count in a scene where you can't see hardly any MDLs.) Finally, it's not beyond the bounds of possibility that you have found a genuine bug with my draw call batcher. Worth noting that the main skill selction area in ID1 start.bsp comes in at 35 calls in the absolute best case - including using instancing where possible for torches and zombies. @81.23.195.106 - can you explain these glitches a little better? I'm not sure what I'm supposed to be seeing here. there's a guy over on quake3world forums called Odium who is the lead artist/modeler on a long in the making free q3 engine game called Overdose. Since that game will be free, some of the weapon models/skins etc that he has done for that may be able to be shared with you guys.
Worth an email I reckon. Tons of glitches coming to light, this is very cool and exactly what I hope to get from demo releases.
Distrans: Cool, I'd be delighted to get help with the audio and voice acting. I'll mail you. Nitin: Thanks for the heads up, I'll definitely look at it. Quoted from the internal forum;
I lowered fall damage again - with the arrival of special moves, and seeing we have the visual damage feedback/blur now, less fall damage is ok and fits better with the idea of a superhuman player. I'll also tame the underwater weapon punishment somewhat and probably allow all weapons to function underwater, with an amount of harmless jamming varying from weapon to weapon. I'm thinking to reduce the backfiring (which damages the player) a lot. The destroying of backfiring weapons was already removed a while back. Part of me sees this as "dumbing it down" since it makes the player suffer less consequences / allows them to switch off the brain while playing. It's difficult to strike a good balance. http://negke.slipgateconstruct.com/files/rmqwinter11_negke.7z demos
Many nice and cool things, and also quite a few not so nice ones. The maps look great, though some have issues with the lighting. Too dark or too colorful in some places, and E3M3RQ with terrible minlight. E2M1RQ goes a bit overboard with reinterpretation and adding new areas, so that only 60% through Quake2 you finally enter the actual e2m1 part. The other ones were mostly recognizable with neat additions. Not sure about the ship part. It certainly looked cool though (with better light). I experienced a couple of slowdowns in E2M1RQ - this shouldn't happen, but it was bearable. E3M1RQ, on the other hand, was barely playable. Something caused a major hit on performance, possibly the rain. Also I'm not sold on the Glados AI thing, felt tucked on and out of place. 'Regular' (non-humorous) AI broadcasts may be better for the level. New stuff... the hires textures look surprisingly good. The new sounds, well, I don't like them because they are no improvement on the older ones, but seemingly only added because you felt everything has to be updated to higher resolution. Pew pew laser etc. And what's with the monster calling the player "noob" when he dies - I mean seriously.... Environmental sounds are good. The new monsters are nice, though also pretty powerful. Seems harder to avoid taking damage. Those Madfox squids work surpringly well (if not overused). They seem even harder to dodge though. The drones look somewhat out of place with their non-brown skin, a bit Shrak/Malice-like. Their explosion should be toned down visually. Zombie knights stay dead a tad too long in my view, could get back up faster. Gameplay was mostly okay on Normal, was low/out of ammo/health and died a few times. Hardly any secret found, but it's great there are so many in each map. Did you nerf the DBS? Somehow felt weaker than before. I don't like the laser rifle, the v_model looks cheap, and I don't see a good gameplay reason to replace the nailgun with it. I missed the SNG. Still don't understand why you don't just use the chainsaw model from Zer, it looks very badass - unlike the RMQ one. The 'drunk' effect in E3M3RQ was annoying and felt like a random idea forced into the map. At least tone it down a little and put a centerprint explaination in the area (poinsonous gas or something). Please change the autosave system to name the files "autosave.sav" instead of overwriting the quicksave file! I encountered a few glitches, even two gamebreaking ones. After dying in rising lava, the orange screen tint didn't go away on reloading. The ladders on the ship in E3M3RQ are parially nonsolid. At one point I reloaded and the fog was gone for the rest of the map. Best watch the demos so you can see it for yourself... and have more immediate (and possibly aggravating) comments. Sometimes I only look at something that's wrong but don't type a message. You'll probably get the idea. Bottom line, enjoyable beta maps, many good features as well as controversial bullshit. The damage blur, interesting effect, but somewhat annoying. It blurs your vision too much if you take lots of damage from different sources. Makes fighting back unnessarily difficult. I sighed at the fall damage a couple of times as well, because there are areas where you are required to jump down (less than 256 units) but can't avoid taking damage from it.
I noticed that the nailgun sometimes jams underwater but still functions. This is good, better than completely disabling it. What you regard as "dumbed down" actually is what makes Quake fun. The opposite of what all those realism shooters do, and what RMQ, to the dismay of many players, has started to incorporate, eg. damage blur, fall damage, autoregen health etc. Perhaps optional gameplay settings to cater to all kinds of players could make it easier to balance? Btw. I'm not sold on the new powerup behavior either. Not to mention that you didn't explain how the new versions work now. In effect, I wasted to Quads going wtf at the shorter duration. And ZQF didn't benefit from his Pent, either - quite the contrary. I'd say maybe makes those new version extra items and use them in situations where they can be utilized properly, rather than using them as replacement for the old ones and forcing the players to make due (for in my view, the new ones, at least as much as I understand their behavior, are much less versatile now compared the others). Zer Chainsaw - ok. Ideally I want the player to swing with it. The current version is an Ogre's saw, which is why it looks so crap.
The DBS has a slower fire rate but much more damage, and spread. Up close it makes mincemeat of enemies, although more feedback of that is probably in order. Increasing the stutter effect for some weapons underwater seems fair. We're still working on the gameplan for the underwater combat. Same for the powerups - we know the direction, just not all of the specifics yet. I'm also thinking to add print messages for these to make it crystal clear what is going on. The Quad duration for example increases with each kill. The Blaster model I finished the day before the delivery. A very important aspect of its behaviour is that it increases in power under sustained fire, but becomes more inaccurate. After firing for a short while it'll gib zombies, but at the cost of ammo wasted. So adding visual / audio feedback to show that better is a good idea. So the pew-pew could get more bassy the more powerful the shots are. Poisonus gas - I'd hoped the fog raising to pea-souper levels would confer this :) I did have a message in there saying 'argh my head' but it seems to have gotten deleted in the shuffle. Distrans, that'd be great - there's a lot to be done, especially with voice acting. We have a lot thats not included in the demos yet, but vital to the vision. Good points.
The old chainsaw model sucks, and will be replaced (not with the zer one though, but we can easily make a good looking model now). The blaster vmodel was added at the last minute, and it shows. The explanation for the player to have the blaster is that the Episode 3 player character is an Enforcer - the idea is that you get the enforcer's gun etc. Yes, it needs improvement, no question. The new powerups: the pent does suck and shouldn't have been in the demo because of this. The quad takes some getting used to, but if used right can outlast the vanilla id quad (killing streak feature). Needs tweaking. e3m1 slowdowns: Same here, this is due to the sounds. Too many GlaDOS sounds - the rain alone doesn't cause this. Realism: Yes, as I said earlier I'm cutting back on this stuff. Autosave overwriting quicksave: It was actually doing what you want, but was changed so you can use quickload to go back to the latest autosave after quitting and restarting the engine. This was done because most people were in favour of the change. SSG was nerfed compared to Demo 2, yep. There might be a - permanent - weapon upgrade thing sometime later, where you collect an item and it just buffs a weapon. We plan no alt-fire or anything like that. Will watch demos now, thanks a lot for those. What you regard as "dumbed down" actually is what makes Quake fun
This! I feel a lot of what is being done in RMQ is against the fundamental spirit of the kind of experience old iD shooters embodied. A fast, tight action game with simple weapons and mechanics that gives variety and complexity through level design and monster variety. Things are being made too complicated, a feel of 'this would be cool' rather than 'this would be appropriate'. The engine tech and sheer degree of work is very impressive, but the design is muddled. Ultimately Negke is spot on. a lot of what is being done in RMQ is against the fundamental spirit of the kind of experience old iD shooters embodied.
Please, concrete examples would be helpful. The core gameplay is still "kill monsters, press buttons". RMQ weapons are very powerful, so the game actually favours a rush-in approach. Stuff like pushable crate puzzles can usually be bypassed in the typical ways (trickjumps etc). There are a ton of buttons in e3m3rq for example, but I've got to say pressing buttons has been an established gameplay mechanic in Quake all the time. Give examples, please, instead of roundhouse kicks. ;-) But it's a daunting task when you're faced with it. Watching Negke's demos (of my map, naturally) was actually quite cool. He doesn't miss much! A agreed with almost 100% of his comments.
I generally feel that e2m1rq needs to be tightened up. Trust me I've been tightening the sh*t out of it for the last two or three months. Releasing these demos is good when it's actually your own work which is on the line because it makes you look at it from other people's perspectives. I mean I've been testing my own map a lot, of course, and I can whizz round it and get four quad runs on skill 3 and it's great. But watching people wandering round it for the first time is almost unfathomable for me by now. ZQF I know where you are coming from for sure. 'Against the fundamental spirit of the kind of experience old id shooters embodied' is a roundhouse kick, agreed, but, having watched a couple of player demos (three infact) from this release, I have been considering way which I can make the experience of playing my map more fluid, basically just putting more gameplay into the same distance travelled. I need to keep the player pumping rounds. I need to keep them more worried about what is round the corner. More worried about what is going to be in their face in two seconds time, rather than standing way back and picking monsters of from a distance. Or something like that. More manic. It's all coming. The extra features and tech I don't think are the problem though, it's just using them in a balanced was so as not to interrupt the carnage too much. Yeah that was a bit over dramatic of me, just that laser thing really took me out of the feel in a bad way... I'll try and come back with something more helpful later ;)
You should think "what it adds to the game and gameplay?"
Damage is a way of punishing the player for doing wrong or failing at the game. What's wrong about jumping from a ladder or 250 high platform? Add to that the way your maps are build, typical quake scale with no consideration for the altered falling damage. Its damage=punishment for nothing. You should increase the threshold hight where only the bigger hight gives significant damage. Where it would be quite clear: don't fall here, you'd break your legs. Obvious danger is good. Guns not working in the water - again why? And backfiring is just dumb - random punishment. Its not realistic (if you want realism you should disable chainsaw in the water if anything). This adds nothing to the game, only taking away from it, because now you have to avoid in-water combat in your maps, knowing that the guns would malfunction. This could work if you wanted to use water as a barrier, like HL does, forcing the player away from it. But then why not just use slime, which explicitly tells the player to 'stay away'. Clear game rules are good. But if you have lots of accessible water volumes that offer exploration allowing combat there would only benefit the game. I missed my dopefish slaying. Or just lighting the dark corners with some shots. Haven't played all the other maps yet, will comment later. SOUNDS
I'm making a patch changing the monster and most weapon sounds back to the original. Bad sounds ruin otherwise good mod. Simply removing grunt\enforcer wavs made the first map more enjoyable its not even funny.
|
|
| You must be logged in to post in this thread. |
|
| Website copyright © 2002-2024 John Fitzgibbons. All posts are copyright their respective authors. |