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.


krokko

Member Since 17 Aug 2007
Offline Last Active Jan 12 2012 02:42 PM

Topics I've Started

Which way to go?

03 May 2010 - 05:55 AM

Hey there, I've become intent on making a 3D game for the first time and I'm trying to figure out the best way to go about it. I thought about using something like UDK, but I've been checking it out today and I realized that working with something like that would drive me insane. I know I will run into so many problems that would simply come down to RTFM and figuring out how they decided to do something instead of figuring out how to make something on my own. The other option I'm considering is making something from scratch with SDL + OpenGL. I've made 2D games with SDL before but just software rendered, no OpenGL implementations. Writing a 3D renderer doesn't worry me that much because I'm pretty sure I have more than enough math knowledge to handle it (studied some projective geometry which might be put to use!). What worries me more is stuff like file-types / data structures for levels, models, making an animation system etc. A basic tile map is the most advanced data structure I've ever written to a file so I have very little experience in that area. I'm a horrible graphics artist so at some point I'm going to have to solicit the help of someone who's better at that stuff and that means being able to handle data formats their tools of choice spit out etc. I know you can handle a lot of that stuff with libraries, but still, there's a lot I would have to learn and I don't want to get in too far over my head. I know there's XNA but I don't know much about it other than that it uses C# which I haven't tried. Would it be a better option? Thanks for any advice :) /teo

problem with memory addresses

17 August 2007 - 01:39 PM

Hi everyone, I'm having quite a bit of trouble with arrays and variables declared after them.
 class Block
{
      private:
              
      SDL_Rect squares[3];
      
      blockType kind; 
...
The problem is that the 'kind' variable gets the same memory address as the last element in the array I declared ( actually, the same address as the first member variable in the last element ), which really messes everything up. It's been spooking me for a really long time and I've redone loads of stuff because I couldn't figure out why my variable was changing without being explicitly changed. There must be some kind of way to avoid this, please help! I'd be grateful for any :) Thanks teo

PARTNERS