Jump to content

  • Log In with Google      Sign In   
  • Create Account

We're offering banner ads on our site from just $5!

1. Details HERE. 2. GDNet+ Subscriptions HERE. 3. Ad upload HERE.


gsamour

Member Since 03 Jul 2009
Offline Last Active Nov 09 2012 04:47 PM

Posts I've Made

In Topic: Writing a game engine

06 December 2011 - 02:28 PM

Agreed; however I'd argue there is a valuable lesson in writing fault tolerant code too.


Agreed Posted Image

In Topic: Writing a game engine

06 December 2011 - 02:20 PM

At least if I know how to make the user able to make the GameEngine object only once without a singleton. Is this even possible?


You'll be the only user, right? I'm sure you can keep yourself from making more GameEngine objects ;)

Ok and thanks, I will progress on this forum but where? Should I post it here ir is there a special topic for WIP's?


Not sure about this, my guess is on this same post, but maybe posting progress would be off-topic...

In Topic: Writing a game engine

06 December 2011 - 01:23 PM

The 'engine' I got from school I don't like because:
- it don't have any performance at all / terrible names for datatypes ( maybe because we need to understand it )
example in header:
Code I use: Object* m_pObject;
Code the 'engine' have: Object* m_MyObjectPtr;
- The WinMain we never wrote because this was already implemented in the engine. Almost no one of my class knows how WinMain works.

These are the 2 things I don't like. I know the priority is to make the game. But I want to do more.. I am already 3weeks ahead with the lessons.


-How do you know "it don't have any performance at all" ? Are you getting high frame times / low framerates?
-I can see how the variable naming can be a turn-off...
-Why do you dislike the fact that the engine already implements WinMain? Does that prevent you from doing something?

I think it boils down to this: you WANT to write an engine, and you dislike the existing engine because it's not yours... So you will write your own and can't be convinced otherwise (nothing wrong with that). No one can tell you what to do, but the suggestions you've seen are based on previous experiences.

It won't be a wasted effort, because you will learn a lot. However, just be careful and follow a schedule to make sure you meet the requirement for the course instead of finding yourself implementing engine features forever. It's fun to work on "engine code", but at some point you will have to make a game with it. It sounds obvious but it's easy to forget.

Good luck, I'm looking forward to seeing your game. If you want to, post your progress on this forum. It's always interesting to see how things begin and how they end up. I mean this in a good way (you're probably going to make changes to your original design/framework/etc). And this info can be very valuable to others.


EDIT: I also suggest adding time for "engine bug fixing" to your schedule. Some bugs will be noticeable with simple tests, but other bugs will only show up until you start writing the real game. I've seen bug databases for some software products end up with hundreds of bugs.

In Topic: DirectX draw after minimize

05 December 2011 - 11:43 AM

It looks like you've got a "lost device":

http://msdn.microsoft.com/en-us/library/windows/desktop/bb174714(v=vs.85).aspx

You can test this by using IDirect3DDevice9::TestCooperativeLevel(). If the device was actually lost, then you'll have to send your resources to the GPU again (vertex buffers, textures, etc)

In Topic: Writing a game engine

03 December 2011 - 09:57 AM

Out of curiosity, why don't you like the engine you got from school?

Also, I agree with the comments. Writing an engine is not an easy task. I suggest you focus on the game and use what has been given to you. You say you can write an engine in one month and finish the game in the remaining months... let's assume for a moment that it's an accurate time estimate. That's one extra month you can use for making the game shine. IMO having a polished game will cause a bigger wow factor than having your own engine.

It's also good practice for you if you break in to the industry. Unless you become an engine programmer, you will be using an engine written by another team (or company altogether). Even if you are an engine programmer, you probably won't be writing all the code yourself and will have to deal with code from other developers.

So again, what is wrong with the engine you got from school?

PARTNERS