• Advertisement

Archived

This topic is now archived and is closed to further replies.

POLL: Most difficult part do code in a game?

This topic is 5435 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

I''d like som straight answers in this question, please: What do you think is the hardest part to code in a game? I think the sound is the hardest thing while graphics and physicst belongs to the more easier done stuff.

Share this post


Link to post
Share on other sites
Advertisement
I''d say the hardest part for me is the user interface. The reason is because i''m so busy and so interested in doing everthing else that i never want to bother with a menu system or graphics displaying the stats. The real hardest thing is probably a good artificial intelligence.. making a balance between speed and accuracy.. and a balance between intelligence and stupidity

Share this post


Link to post
Share on other sites
Yeah... It is hard to create a stupid AI - too often, it ends up looking like badly-programmed AI instead.

500 x1

ToohrVyk
-------------
Extatica - a free 3d game engine
Available soon!
Click here to learn more

Share this post


Link to post
Share on other sites
I have a hard time coding the simple stuff. I usually start a project for a challenge, but once I finish the challening part, I have a hard time forcing myself to code the rest of it. So far, I''ve only completed 1 game, and that was a long time ago and it was a very simple game (only about 5000 lines total. It used BGI for graphics and a borland function to make PC speaker sounds).

Share this post


Link to post
Share on other sites
quote:
What do you think is the hardest part to code in a game?


When you''ve done 90% of the game, the last 90% is really the toughest...|8-}

-cb

Share this post


Link to post
Share on other sites
not sure where you get the idea that physics is among the easier things to code in a game ? but i guess it depends how advanced your physics engine is


[edited by - gowron67 on March 2, 2003 7:20:26 PM]

Share this post


Link to post
Share on other sites
The external things. Map editors and whatnot.

--------------------------------------------
Yunalesca: MEGA DEATH!
Anima: *shrugs off Mega Death* PAIN!
Yunalesca: Gahh! You killed me with your EYE!

Share this post


Link to post
Share on other sites
it depends on what kind of stuff you''re programming. sound is much easier than writing a full fledged ray-tracer but sound is harder than writing a small 2d game. so it depends, you should ask which is harder in ___ type of project.

but overall i''d say AI. especially with a very arbitary level. making a big calculator think (well) can be difficult.

Share this post


Link to post
Share on other sites
quote:
When you''ve done 90% of the game, the last 90% is really the toughest...|8-}


I like that one! It''s true though.
The hardest part is programming the parts that give very little visible effect and convincing yourself to keep going.


''Your theory of a donut shaped universe is intriguing Homer'' - Stephen Hawking

Share this post


Link to post
Share on other sites
Smoothing out the rendering pipeline.
Keeping FPS up with computations of lighting/shadowing
External Editors (map/particle)
Expandable design
Keeping up with the next gen of graphics


~Main

==
Colt "MainRoach" McAnlis
Programmer
www.badheat.com/sinewave

Share this post


Link to post
Share on other sites
quote:

What do you think is the hardest part to code in a game?



AI and physics.

And making everything work together without flaws.

That bug somewhere in a static global constructor of some obscure library some employee wrote before he quit the company months ago, that makes the game randomly crash, and that you discover three days before the deadline...


[edited by - Yann L on March 2, 2003 8:53:49 PM]

Share this post


Link to post
Share on other sites
The hardest part for me is the polishing at the end so your game don't look like a half baked attempt at a game. Also very important is sound timing.

GRELLIN

"I installed a skylight in my apartment...The people who live above me are furious."

[edited by - grellin on March 2, 2003 8:58:35 PM]

Share this post


Link to post
Share on other sites
Physics is probably the hardest. Rendering is fairly easy once you get used to it (and if you have decent file formats), as are input and sound. But the underlying physics (and also the AI) take a lot of thought.

|.dev-c++.|.the gimp.|.seti@home.|.dbpoweramp.|.torn.|.=w=.|

Share this post


Link to post
Share on other sites
Well, in my opinion the whole danged thing _can_ be hard, depending on where you specialize. I would say that Yann L came up with a good answer in "And making everything work together without flaws."

Share this post


Link to post
Share on other sites
Guest Anonymous Poster
It''s not a very meaningful question. Any part can be arbitrarily hard depending on the game. And "hard" is relative to your knowledge and experience.

Share this post


Link to post
Share on other sites
Writing easily understandable user documentation?

Regards,
Sharky


[edited by - Sharky on March 3, 2003 3:09:41 AM]

Share this post


Link to post
Share on other sites
quote:
Original post by Anonymous Poster
It''s not a very meaningful question. Any part...


It is atleast more meaningful than complain and then be a coward and post anonymously. [offensive]Grow up.[/offensive]

Share this post


Link to post
Share on other sites
The last 10% of the game, and optimizing the game...
It''s a real pain in the ass sometimes

// Jonas Ericsson

Share this post


Link to post
Share on other sites
Probably working on graphics code with coder art, because no matter how well I code it still lokks crap

Share this post


Link to post
Share on other sites
90%+ rehusable/scalable/portable code for a game engine.

Share this post


Link to post
Share on other sites

  • Advertisement