« Story Games - My New Obsession | Main | Lying With Statistics, Here's How It's Done »

October 11, 2010



Was it const or not const?

Jamie Fristrom

Not const.

Jay K.

I wonder if you declare it volatile if it will fix the issue.

Chris Jurney

Wow, bizarre... what compiler is that in? Why would it choose to use a varible for .5 instead of an immediate value?

Jamie Fristrom

I'm sure it would, but there isn't really an issue other than we spent a lot of time trying to figure out what was causing a bug that wouldn't happen in the field.

And the compiler is visual studio for the xbox, and I don't know enough about the floating point unit to venture a guess.

Bryan McNett

round many global debug variables up into a singleton, and try not to let many compilation units know about its existence. let them see only a pointer or a function that "just happens to" always return the singleton.

if compilation units don't know about the singleton, they can't make dangerous assumptions about it... barring some really good global optimization.

The comments to this entry are closed.

Jamie's Bragging Rights

  • Spider-Man 2
    The best superhero games of all time Game Informer
    Top five games of all time Yahtzee Croshaw
    Top five superhero games of all time MSNBC
    Top 100 PS2 games of all time Official Playstation 2 Magazine
    1001 Games You Must Play Before You Die Nomination for Excellence in Gameplay Engineering Academy of Interactive Arts & Sciences
  • Schizoid
    Penny Arcade PAX 10 Award
    Nominated for XBLA Best Original Game
    Nominated for XBLA Best Co-Op Game