Revolutionary game play and graphics, quake champions doesn't stand a chance.

That beat got me in a trance.

STFU AND TAKE MY MONEY

the music is amazing! Dodging the lightspheres looked fun. Can you code it so that you have to shoot in the rythm of the beat, otherwise you don't hit - I think that would be fun, because the music is like 60% of the gameplay already!

free to use any sprites/textures from my mod if you want.

do you have a link?

Still better than doom4 haha.

QC/overwatch/UT/warsaw/diabotical and now this, what a good year for top notch AAA-arena-FPShooters!

reviving this thread to say that: a new version is released!

video:


download it here:
http://p.trumpshare.com/swk5/rw76.zip

Lmao models from wolfenstein. Love how that one baddy just keeps standing back up. Good evil dead perspective.

models are based on wolfenstien, i ripped them out of ZDoom forums ;]

thanks!

Make the shogun animation the same as Blood and you've got a sale.

Ballin' like it's '96

I'm not into programming or coding or anything in design so I don't know if this required a lot of effort or skill to make. If it did, good job man. If not, good job nonetheless doing what you like.

Thanks! These things only really take a lot of time. This game has been in development for a year.

Looks neat so far. Maybe my computer is just too told. It took over 30 seconds for any of my key presses to respond and accept a map choice. Do you have a link to the command prompt commands?

You can find a guide to the in game CLI in the readme. Your computer probably isnt too old to run it, it does this thing where the game will slow down on some computers at random. I'm not sure how to stop it since its hard for me to test when its hardware specific. I know on some hardware this bug will make it slow, but by changing the resolution or other things it can sometimes be fixed. (not sure why, i guess you cant trust win32 API functions to be 100% consistent)

When I first saw your videos I thought this engine was a joke, because your 'lets play clan arena' videos are pretty funny. It wasn't till I visited your site and saw the code that I realized it was a real project. Anyway, its coming along decently so great job!

The code quality could be improved, if you are willing to accept criticism from a 'random internet person'. I have an extensive collection of code on github that at least partially proves im not totally full of it, though. Let me know!

Pretty much all the programming is finished, i'm just finishing all the levels at this point.

I'll probably post a thread about my next game engine after I release this game, once there is some content. The codebase for this could be a lot better, but it works well for what it is. My plan is to not make the same mistakes in my next engine, because iv'e been working on this codebase for a year and by now all the mistakes have come around to bite me in the ass.

If you want to talk about programming stuff, or a link to the code, I use steam messenger a lot. my URL is: http://steamcommunity.com/id/ika_

Where on your site is the source code? I couldn't spot it. :c

I never uploaded the source code, i'll upload it shortly and edit my post with a link

Oh, sorry then! After reading kazzmir's post I thought it was somewhere on the site.

I never uploaded the source code, i'll upload it shortly and edit my post with a link

okay, this is the source code for the engine as of 11/1 :

http://p.trumpshare.com/f6st/ha3g.zip

i'll post the rest of the code, for the map editor and all that, once the game is finished

Maybe you are right that the source code for Sigma was not published before, I may seen some other source code from you, but not sure what.

Anyway, here are some quick comments from a 5 minute peek at your code

* you use #ifndef/#define in .h files which is good but you should put the #ifndef/#define part at the top, meaning don't do
#include "whatever"
#ifndef _THISFILE_H
#define _THISFILE_H

because then "whatever" will be included multiple times for each time the .h you are currently writing is included. This is a small thing for now, but in C++ it can become an extremely important thing to keep in mind. also put the #endif as the last line in the file.

* also about #ifndef stuff I can see why you chose the names _ENTH_ and such, its just the filename converted to all caps, but in the future when you have large projects you can accidentally get collisions between the names you choose. The name is completely arbitrary, so I have generally use GUIDS that are nearly guaranteed to be unique:

#ifndef _entity_425e93bc0dc145c386155d86a61cd936

Or you can go the slightly evil path and use #pragma once, which is not part of the C standard, afaik, but most compilers accept it.

* some repeated declarations, like draw_tex_quad in graphics.h and graphics.c

* you pass 'struct player p' to a lot of functions by value, but the player struct is quite large. passing a struct by value means copying the entire thing on the stack and can be quite slow. Almost surely you meant to pass the player as a pointer, struct player * p. entity.c uses a lot of non-pointer player types, but then player.c uses pointers.

* not sure if you know about 'static' or not, and its not a big deal for this project but if you have a function that is only used in a single file and nowhere else you can prepend static to it so that it becomes a local symbol to that file only. its a way of managing the symbols in your project in case of conflict.

static void whatever(){
}

* small tip, but for debugging purposes this is a convenient macro to use
#define xdebug(s) printf("%s:%d %s\n", __FILE__, __LINE__, s);

Instead of just printf(). It has the advantages of printing out the current file and line where the xdebug statement is used, and you can easily #define xdebug to be nothing so that all debugging goes away.

I used #ifndef because i didnt know about using #pragma once to fix the problems with it at the time. I also didnt know that when you pass large structures around it copied them when i was writing the bulk of the code.. :<

thanks for sharing the stuff about the static keyword, i didnt know about that one! That macro is also rather helpful, I didnt think of using those keywords.

Im hopefully going to avoid the pitfalls in the future, but i might send you more code on steam in a few months because its nice having a second opinion :]

no steam + vac? won't play.

wont download and run my .exe but WILL download the infamous "steam" virus onto his computer... :oo

nice work my g =]