> I have been wondering this for awhile.
> Its almost impossible to make a succesful map in Reach without framerate issues.
> Its rediculous.
> Bungie in the “Once more unto the breach” Vi-Doc were bragging about there framerate if I remember correctly…yet I remember Campaign lagging alot, then multiplayer and sometimes even Firefight.
> What did they changed that messed it up?
> Also if I remember correctly framerate issues in Halo 3 were nonexistent.
> But to my previous question…could something be changed to fix all these framerate issues in the Titile Update.
Reach runs at a higher screen resolution than any of the other Halo games did. Higher resolution is much more demanding on the hardware, which is why the 360 has a difficult time keeping the framerate 100% smooth.
As far as I know, it would be impossible to improve the frame rate in a title update. The frame rate is directly connected to game engine performance. A title update can be used to tweak the way game elements work, but not the raw code that powers those elements. Kinda like putting new tires on your car: it will change how your car handles on the road, but it won’t give you more horsepower. They can adjust things like player speeds, weapon damages, menu options, etc, but their not re-writing the core game engine.
Aside from that, I really do think you are exaggerating the problem. I’ve done a fair amount of forging, and played hundreds of custom forge-made maps. Part of being a good map-maker is learning to work within the technical limitations of the platform you’ve been given. How to make an enjoyable play space, that looks good, while using the fewest pieces possible. Also learning how to control sight-lines. Sometimes an open window causes frame rate issues, since the the engine needs to draw the interior room and the outdoor space at the same time. Sometimes you need to build walls in specific places to block the player’s view of the background.
These are all issues that every game maker deals with every day. It’s part of map making.