Search results

  1. E

    The Next Gp*x Revision

    I'm much more interested in what can be done with original software. That said, a design with an ARM-based processor should achieve much better battery life than the PSP.
  2. E

    Blasphemy! New Favourite Handheld = Psp?

    Full speed? Nope. With sound? If you don't mind it running slower than it already was, sure.
  3. E

    The Next Gp*x Revision

    I'll be frank. If as a programmer I have to 'defeat adversity' as an excuse for the hardware being fucked up right from the factory, nay, the drawing board, my dollars are better spent somewhere else. I imagine this is not an uncommon sentiment.
  4. E

    The Next Gp*x Revision

    I'm probably living proof that most developers don't want to code for platforms that won't have a decent user base who will enjoy their work. You just wouldn't move enough units at that price. And honestly, even for a high-end machine, there's no reason for it to get that steep.
  5. E

    The Next Gp*x Revision

    That sort of price isn't necessary. I'm sure a system with the i.MX31 and a 320x240 touchscreen could fit under a $300 price point if the production run was large enough.
  6. E

    Too Many Firmwares

    Oh, my point was he didn't design the GP32...
  7. E

    The Next Gp*x Revision

    You've got GPH and GamePark mixed up-- GPH consists of some people who split from GPH to make a media player. Only 1 person, who was an intern at GP during GP32's development, was actually involved in the GP2X's internal design. At any rate, the GP32 was based on a System-on-a-Chip as well. It...
  8. E

    Too Many Firmwares

    GPH only has 1 'engineer' from GamePark, the company that made the GP32. He was an intern when the GP32 was made... :P Edit: reworded. Makes more sense now.
  9. E

    Too Many Firmwares

    Direct your complaints to WarmfluffyUK who insisted on my response which you deemed inflammatory. I did not begin this debate of my own will. My opinions were requested. If there's someone with sense at GPH, it's not the engineer. He did a pretty horrible job, and he was copying an...
  10. E

    The Next Gp*x Revision

    I kind of doubt it's going to happen the way I'd hope, since Craig seemed so .. resistant to logic, shall we say. Strange fixations on software rendering, high-clocked CPUs for 'big numbers for marketing value, like big engines', and no 2D or 3D acceleration of any sort. Logical, right...
  11. E

    Too Many Firmwares

    The problem isn't that one user has the godly dexterity required to effectively use such a terribly designed stick. (By the way, it was made to be a media player, not a game machine, as you hint at) The problem is that most users lack that sort of dexterity apparently, including myself and...
  12. E

    Too Many Firmwares

    Let me get this straight, you chalk up the GP2X stick to not being poorly selected for a game system, but just requiring 'skill' to use? :lol: That's hilarious. Remember, MK1 and MK2 use the same stick. It's just turned 45 degrees. It still has the swing distance of an 8-direction lightswitch...
  13. E

    Too Many Firmwares

    Orkie summed up my views on the MK2 stick perfectly. Not enough improvement since it's the same stick, and in the end, I can't code for hardware 99% or more of the GP2X user base doesn't have. Otherwise, I'll get comments like 'why do the controls feel broken' and be unable to fix them because I...
  14. E

    Too Many Firmwares

    Alex-- My apologies for my rash assumption that you hadn't written a game using SDL before. I see you do have experience there. However, you should know it is very possible to write a game engine with it that achieves the same framerate on a PC as on a console. Of course, vsync will limit it to...
  15. E

    Too Many Firmwares

    GP2X. Things were REALLY promising for a long time. But once we went past 2-3 graphics layers and added all the game sprites needed in an average scene things really started to go downhill. I could've dealt with it to a degree, though how much we'd have to scale back would be very disappointing...
  16. E

    Too Many Firmwares

    THANK you. That was excellent. This forum needs more people like you who can recognize that an effective conversation requires people who don't have an immediate knee-jerk reaction to label anything that doesn't cast their opinions in a positive light as "trolling". Otherwise threads just turn...
  17. E

    Too Many Firmwares

    I can't think of why it'd make any difference which model you had since they both use the exact same chipset. Weird. They weren't pushing as many layers and their graphics were much simpler-- a palletized affair with perhaps 16 unique colors per image in most cases. When you're looking at...
  18. E

    Too Many Firmwares

    I love it when things happen just as I predicted not 2 posts ago.
  19. E

    Too Many Firmwares

    You're the one derailing a thread here with your own personal agenda. You're calling me out on a totally unrelated topic just because you have a personal vendetta. How hypocritical of you. You set a very poor example for other mods to follow. I'm glad they're not all as terrible as you are at...
  20. E

    Too Many Firmwares

    Being non-biased doesn't mean you don't make any sort of judgment call of any sort-- e.g. a preference. It means you give the appropriate amount of opportunity to each side of the issue to present itself before you make a decision. My opinions do not match those of many members of this board...
Back
Top