STOP!
Before you write another line of code, design. Sit down and write out the goals - in detail - of your game. Devise the architecture of subsystems, using use cases (imaginary scenarios of what would happen in the software in response to a user''s action) to focus your effort. Get the specifics down, or you''ll be back here in another six months with nothing to show for it.
NeoEngine
My primary question was moreso the first one (which wasn''t even addressed)... has anyone actually used it who frequents here?
---------------------------------------------------
laziness is the foundation of efficiency
anomicworld.net | llamas! | megatokyo | gamedev.net | google
Tiffany_Smith fanboy
---------------------------------------------------
laziness is the foundation of efficiency
anomicworld.net | llamas! | megatokyo | gamedev.net | google
Tiffany_Smith fanboy
Oh right, lol. I played with it for a week or two. It was very nice in terms of general architecture and features.
The main thing that turned me away was that they were having serious rendering pipeline problems, particularly in OpenGL (speed related). This wasn't acceptable for me since I needed a cross-platform (read: OpenGL) engine at the time. I don't know if those problems have been resolved; if they have, I need to go take another look myself. But yeah, it's a pretty solid engine as far as I can tell.
Time to pull out the 20 odd pages of powerpoint slides on use cases and UML from that SE class I guess.
[edited by - Promit on March 22, 2004 10:28:33 PM]
The main thing that turned me away was that they were having serious rendering pipeline problems, particularly in OpenGL (speed related). This wasn't acceptable for me since I needed a cross-platform (read: OpenGL) engine at the time. I don't know if those problems have been resolved; if they have, I need to go take another look myself. But yeah, it's a pretty solid engine as far as I can tell.
quote:
Before you write another line of code, design. Sit down and write out the goals - in detail - of your game. Devise the architecture of subsystems, using use cases (imaginary scenarios of what would happen in the software in response to a user's action) to focus your effort. Get the specifics down, or you'll be back here in another six months with nothing to show for it.
Time to pull out the 20 odd pages of powerpoint slides on use cases and UML from that SE class I guess.
[edited by - Promit on March 22, 2004 10:28:33 PM]
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement