Now a lot of you want to have pelicans, scarabs, ect. Just a plain better forge well that won’t really be possible unless 343 increases the frame rate. And don’t say it is not possible cause call of duty runs at 60 fps. So don’t let call of duty beat halo. Cause halo reach is already laggy so doing this would help the proble. discuss
Educate yourself on how a computer works.
Reach isn’t laggy, it just has connection problems. Just about everyone I know has their upstream bandwidth stuck on warning ever since Reach released. Reach is one of the smoothest running games I’ve played all thanks to Bungie deciding to rebuild the Halo engine from scratch. The network issues are the problem, not the framerate.
Another thing to take into account is that CoD has been using the same engine since 2007 and have had the time to polish it enough to get it to work at 60 fps since they don’t see the need to rebuild it. Halo has a brand new engine right now that will need some time before it is polished enough for that kind of talk.
> Educate yourself on how a computer works.
This.
> Halo has a brand new engine right now that will need some time before it is polished enough for that kind of talk.
False.
1. It suffers from the exact same discoing glitch that many people saw in Sandbox, though it now takes more objects in the field of view to trigger the bug.
2. It uses more-or-less the same tag system that every (non-spinoff) Halo game to date has used. Its innermost core has barely been touched since Halo 1.
3. Reach is subject to the same… illicit alterations… as Halo 3 was – right down to illicitly-altered map variants.
The problem isn’t that Halo’s engine is new. The problem is that the engine is old, and I think we’re right at the edge of its viability. The graphics engine in particular is bleeding-edge; it’s been extended so heavily that it is literally constantly on the brink of collapse, and when it does collapse, it does so spectacularly (discoing).
We don’t need an old engine. We need a new one – something to replace the decrepit, unstable foundation that is the current engine. I’ve no doubt that 343 will give us something that works, though.
> > Educate yourself on how a computer works.
>
> This.
>
>
>
> > Halo has a brand new engine right now that will need some time before it is polished enough for that kind of talk.
>
> False.
>
> 1. It suffers from the exact same discoing glitch that many people saw in Sandbox, though it now takes more objects in the field of view to trigger the bug.
>
> 2. It uses more-or-less the same tag system that every (non-spinoff) Halo game to date has used. Its innermost core has barely been touched since Halo 1.
>
> 3. Reach is subject to the same… illicit alterations… as Halo 3 was – right down to illicitly-altered map variants.
>
> The problem isn’t that Halo’s engine is new. The problem is that the engine is old, and I think we’re right at the edge of its viability. The graphics engine in particular is bleeding-edge; it’s been extended so heavily that it is literally constantly on the brink of collapse, and when it does collapse, it does so spectacularly (discoing).
>
> We don’t need an old engine. We need a new one – something to replace the decrepit, unstable foundation that is the current engine. I’ve no doubt that 343 will give us something that works, though.
343i are making a new engine thing for Halo CEA… And you should be able to spawn s acarab, it can be immobile so it doesn’t lag as much?
That’s an idea right there. A Scarab as a stationary building rather than a walking, firing vehicle. I could picture a map, like Boneyard, where old Covenent vehicles go to get broken down. There could be a half destroyed Scarab as one of the bases. Another location could be an abandoned war zone so there could be a mix of destroyed UNSC and Covenant vehicles.
> That’s an idea right there. A Scarab as a stationary building rather than a walking, firing vehicle. I could picture a map, like Boneyard, where old Covenent vehicles go to get broken down. There could be a half destroyed Scarab as one of the bases. Another location could be an abandoned war zone so there could be a mix of destroyed UNSC and Covenant vehicles.
Thats what I was thinnking 
> 343i are making a new engine thing for Halo CEA… And you should be able to spawn s acarab, it can be immobile so it doesn’t lag as much?
True, Halo Annie is getting a new engine… But that’s a new graphics engine, and nothing else. It’s still the same ten-year-old game engine with the same limitations in all other areas.
Part of the reason that Reach’s graphics engine is so fragile is because of the burden it carries. The Reach game engine allows for more AI, more weapons, more everything in a single 3D scene. The Annie engine could work perfectly given the burden that a ten-year-old game engine would place on it… But would it handle, say, 506* Forge objects in the field of view any better than Reach does?
As I said – I’ve no doubt that 343 will eventually produce a capable game and graphics engine. But Reach ain’t it, and at this time we can’t know if the Halo Annie engine is stable enough.
- This number may sound odd. 506 objects – and they need not all be Forge objects; Spartans, weapons, et cetera also count – will cause discoing in single-screen gameplay. They need not all be visible either; look in an object’s direction, and it’ll count toward the disco threshold.