• Content count

  • Joined

  • Last visited

Community Reputation

394 Neutral

About trojanman

  • Rank
  1. Direct X vs OpenGL revisited... revisited.

    tl;dr All kidding aside, a fantastic article. Really well written and makes great arguments on an incredibly inflammatory subject.
  2. Direct X vs OpenGL revisited... revisited.

    tl;dr All kidding aside, a fantastic article. Really well written and makes great arguments on an increadily inflammatory subject.
  3. Can old people break into the game industry?

    Quote:Original post by jpetrie Places that "expect" overtime, that include them as part of the requirements, are poorly managed. That doesn't mean they are not successful or popular, only that they have the inertia and control over their workforce that it's hard for them to be challenged. Or they they simply haven't been challenged to do something different. The presence of successful studios that manage 40-hour weeks is an indication that is possible. It is, quite frankly, complete and utter bullshit for our industry to be considering itself so important, to view our release dates as so absolutely critical that we have to push our employees so hard. We're not saving lives or curing cancer, here, we're making video games. Let's get some perspective. It is not required, not everywhere. It is endemic, perhaps, but the only way it will ever be corrected is if we are willing to stand up for ourselves and say -- in interviews, for example -- that we will not accept unreasonable, obligatory, uncompensated overtime. I feel sorry for you. Quoted for truth and emphasis.
  4. I have 23 Google Wave invites

    I'll throw my additional 17 into the pot once those run out...
  5. salary expectation at job interviews

    A good answer is something along the lines of "I am open to any competitive offers". This will usually throw the ball back into the employers court and get you away from saying hard numbers unless they press the issue more. As have been mentioned previously, if it gets that far than do some research before hand and be prepared. Talking specific salary ranges can be good or bad. Good because you know what you want and you can say how much you think you are worth. Bad because it can either knock you out right away because you are asking for too much or even worse you can undervalue you're worth and the employer isn't going to argue because they could have offered more.
  6. Do you have the J2ME SDK installed? if so, it lives here: <location>/WTK2.5.2/docs/api/midp/index.html
  7. What is that cartoon called?

    Quote:Original post by Lode Hey, this show with this mouse with big round black ears, what's it called again? Mighty Mouse, obviously.
  8. Quote:Original post by pinacolada Quote:Original post by cache_hit By the way, never use variables whose first characters are underscores. Why not? Preceding underscores are reserved by the implementation. To quote the C++ Standard: Section of the C++ standard reserves any name which contains two consecutive underscores, which begins with an underscore followed by an uppercase letter or begins with an underscore and is in the global namespace. [Edited by - trojanman on August 6, 2009 6:14:24 PM]
  9. Quote:Original post by programmermattc Obviously someone hasn't read the Requirements on most game development jobs. Yup, requires a beard. College graduate? Who cares. Beard? You're in. Score. I'm in. [grin] If only that were really true. I'd totally have another job.
  10. fast sin/cos

    The fastest inaccurate sin/cos calculation is going to be a lookup table. You can create a static array that you populate once (on application load for example) and then use that for all of your math calculations.
  11. Unfortunately the differences between the traditional mobile gaming platform (see J2ME based since you've specifically mentioned Android and Eclipse) and the iPhone is pretty vast. J2ME does not run on the iPhone and if you are looking for a single 'engine' for all your platforms, you simply aren't going to find it unless you build one youself (and this is a nearly impossible, daunting task). As Matt_D said, for the iPhone however you can take a look at Unity, SiO2, and there is also the Oolong Engine, created by our very own Wolf. For traditional mobile, OpenGLES is not supported. In terms of J2ME, you have a couple of options for 3D; Hi-Corp Mascot Capsule and JSR184. I am not aware of any off the shelf 3D engines for either.
  12. [C++] stringstream

    Some more source code, and perhaps what error you are seeing would certainly help. As godsenddeath said, you are likely not dealing with the std namespace correctly.
  13. Fraagmented Mobile Space

    Indeed. The mobile space is still as fragmented as it always has been. It doesn't look to get any better any time soon. There are a couple ways to handle code organization. The cleanest way, which means a little bit more front end development is to build an abstraction layer to whichever generic platform you are delivering to. For the case of most mobile phones, android, blackberry, etc. the base code will be written in java and the underlying abstraction layer could hide the relevant details of the platform. The same works well for all native platforms, i.e. BREW, Symbian, WinCE, and I suppose OS-X Mobile (though if this is iPhone/iPod touch you'll probably want something fairly separate). The abstraction layer would create a nice public interface to make the game in and under the hood the relevant details of each platform are taken care of.
  14. I'm curious as this seems a bit odd. Is the course in Kentucky? An online web course? Do attendees have to book travel to attend the course? Is it a US thing only? I'd say you need a lot more information here. Especially to justify the cost of 2k which, if I recall correctly, is more than the product itself costs to license. Also, do you expect them to have a particular version of this already purchased since Unity itself isn't free?
  15. Half of all marriages end in divorce

    Quote:Original post by BeanDog Quote:Original post by LessBread The Most Frequent Cause of Divorce 1.) Financial "Till debt do you part", right? It's certainly been one of the root causes of most divorces I've seen. A disagreement over money can ruin any relationship. That's why one of my primary rules of money is to never expect a friend to repay a debt--you'll lose your money, your friend, or (more likely) both. In a marriage, though, it's much more complicated. You likely have shared bank accounts and other assets, and both spouses feel entitled to use those assets to some degree or another. Without very open and frequent communication about money, it's a recipe for catastrophe and divorce. Amen to that. With many friends and relationships the money tends to equal itself out. A lunch here, dinner there, drinks sometime else it always tends to even out. Also, its been a common policy for my wife and I to regularly discuss finances, especially when they get difficult.