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.


Don't forget to read Tuesday's email newsletter for your chance to win a free copy of Construct 2!


BertS

Member Since 26 Feb 2004
Offline Last Active Jul 02 2011 05:18 AM

Posts I've Made

In Topic: why did they decide to point Z up in quake?

13 February 2011 - 03:28 AM

do u know which is up in valve source games?
im still messing with quake3 levels
cause i dun kno how to render edges vs vertices



HL2 uses a standard righthanded coordinate system if I remember correctly. +X right, +Y forward and +Z up. Best to double check this in the SDK though.

In Topic: why did they decide to point Z up in quake?

13 February 2011 - 03:20 AM

It's not weird, it's just a convention. Z being up is a result of Quake 3 using a righthanded coordinate system. If I remember correctly the Q3 coordinate system has +X pointing forward, +Y pointing left and + Z pointing up. Though that could very well be Q2 and Q3 is using +X right, +Y forward and +Z up. It's been too long since I've worked with either code bases :)

[edit]

Realised that this could be misleading people a bit. It's not because the coordinate system is righthanded that Z points up, but because of how the X and Y axes are laid out that forces Z to point up in a right handed coordinate system.

In Topic: OpenGL Memory Overwrite

15 October 2010 - 10:45 PM

Add a data breakpoint to img->height, that way you can see exactly where that memory gets overwritten. Can't tell you how to do it since you didn't specify which IDE you're using :) And if I had to guess I'd say you have to make sure your data array is large enough to hold your image data.

In Topic: Efficient 3d character animation

22 August 2010 - 11:18 PM

Vertex interpolation is going to be faster than using bones. If you want it faster you can always offload the interpolation to a vertex shader (ie pass the frame position and next frame position as vertex attributes).
The only problem might be memory consumption as it adds up fairly quickly as your models get more complex, you add more animations or you add more frames to your animations. You can always keep them compressed in memory and decompress in a vertex shader, but at that point it's probably better to switch to bones.

In Topic: Deferred shading issues?

20 June 2010 - 05:17 AM

As Wiegje said, you need to make sure all your data is in the same coordinate space. Store everything either in eyespace or worldspace.

PARTNERS