On the forge “budget” ~ I know the forging community is a small one. But, if a feature is going to be included and hyped it ought to work properly. The much hyped forge budget is complete BS. Sure, I can place 650 objects. But it comes at the expense of performance. I currently have a map near completion with only 400 objects placed. I am seeing performance issues even while so far under budget. Constant frame rate dips make forge maps “challenging” to play. The budget is BS. Halo 4 forge had performance issues as well. Whatever 343i is doing with forge they ought to stop. Reach Forge remains up top of the list so far as forging is concerned.
This is yet another example of the sloppy work done in MCC.
> 2533274907934539;2:
> … Did you think that a large budget would come without potential performance constraints?
It’s serious performance constraints. Do I expect it to actually be playable? Yeah. I have a map I have been building since Halo 3. I CAN NOT build it in this game. It just will not run well. No matter how much I reel it in. Sloppy work if you ask me.
I keep a close eye on the performance bar at the top of the screen. It doesn’t take much to set it off. It seems when their are visible layers. So, I have a visible structure and then some other objects beyond that. If I place a wall in between them I kill the sight line and the performance issue. This kills open map design.
We seem to be limited to VERY simple open maps or Chill Out style maps.
You would think. I hate to say it, I would put this squarely on Certain Affinity. HCEA has bad split screen frame rate issues. H2A has bad split screen frame rate issues and forge performance issues. Their work feels sloppy. Maybe they set a visual bar and go from there. Kind of laughable actually. Bungie had 30 fps locked and went from there. I would think the foundation would come first.
> 2661949065465166;8:
> You would think. I hate to say it, I would put this squarely on Certain Affinity. HCEA has bad split screen frame rate issues. H2A has bad split screen frame rate issues and forge performance issues. Their work feels sloppy. Maybe they set a visual bar and go from there. Kind of laughable actually. Bungie had 30 fps locked and went from there. I would think the foundation would come first.
It is a hardware issue not a game issue. The graphics card in the xbox isn’t very powerful. It’ the equivalent to the 7790. This is why when you block sight of other objects it’s fine. Xbox = limited render power. Split screen = extra rendering
> 2533274796867934;9:
> > 2661949065465166;8:
> > You would think. I hate to say it, I would put this squarely on Certain Affinity. HCEA has bad split screen frame rate issues. H2A has bad split screen frame rate issues and forge performance issues. Their work feels sloppy. Maybe they set a visual bar and go from there. Kind of laughable actually. Bungie had 30 fps locked and went from there. I would think the foundation would come first.
>
>
> It is a hardware issue not a game issue. The graphics card in the xbox isn’t very powerful. It’ the equivalent to the 7790. This is why when you block sight of other objects it’s fine. Xbox = limited render power. Split screen = extra rendering
Shouldn’t a developer know this and build the game accordingly? Forged maps ran as normal maps did in Reach. What has changed?
> 2661949065465166;10:
> > 2533274796867934;9:
> > > 2661949065465166;8:
> > > You would think. I hate to say it, I would put this squarely on Certain Affinity. HCEA has bad split screen frame rate issues. H2A has bad split screen frame rate issues and forge performance issues. Their work feels sloppy. Maybe they set a visual bar and go from there. Kind of laughable actually. Bungie had 30 fps locked and went from there. I would think the foundation would come first.
> >
> >
> >
> > It is a hardware issue not a game issue. The graphics card in the xbox isn’t very powerful. It’ the equivalent to the 7790. This is why when you block sight of other objects it’s fine. Xbox = limited render power. Split screen = extra rendering
>
>
> Shouldn’t a developer know this and build the game accordingly? Forged maps ran as normal maps did in Reach. What has changed?
The forged maps in reach appeared to because we were used to low frame rates. If you go turn on your 360 I promise you will be astounded at the 20 fps average. It looks like a slide show. What has changed is the graphics. They are simply too good for the xbox to max out in forge. Now, this is only true for h2a and maybe h4.
As graphics improve, so does the efficiency of them. This is why games get better and better as time goes on for consoles even though the hardware is the same. Better soft, algorithms, etc, allow for less resources to be used while at the same time providing better graphics and higher limits. That being said h2a is running off a slightly modified h4 engine. If they had used a more graphically modern infrastructure there might be no problems. I can’t say that for sure though. Regardless, the xb1 is simply not that powerful for what is being demanded of it. The graphics card is pretty weak even compared to the mid range cards out right now.
So gameplay>graphics isn’t actually the case. What a joke. Frame rate is paramount. As for Reach dipping to 20fps… idk. I am very sensitive to issues like this and vertical tearing (Titan Fall). H2A will give me a head ache after a night of playing on forged maps. Like I said in the OP, I can’t run a map I built in Halo 3, Reach, and Halo 4. (though it did dip in H4)
This theory also doesn’t explain the frame rate issues in HCEA when in split screen. It’s a 360 game. It shouldn’t make the XB1 breake a sweet.
> 2661949065465166;12:
> So gameplay>graphics isn’t actually the case. What a joke. Frame rate is paramount. As for Reach dipping to 20fps… idk. I am very sensitive to issues like this and vertical tearing (Titan Fall). H2A will give me a head ache after a night of playing on forged maps. Like I said in the OP, I can’t run a map I built in Halo 3, Reach, and Halo 4. (though it did dip in H4)
>
> This theory also doesn’t explain the frame rate issues in HCEA when in split screen. It’s a 360 game. It shouldn’t make the XB1 breake a sweet.
When running split screen you are running two simultaneous renders. Basically like running the game twice graphically but with lower resources being needed. together though, the sum is greater. HCEA is also running a higher native resolution which is then downscaled since it’s on the xb1. If you’re seeing framerates drop below what they would on the 360 in split screen often, then there is something else wrong. Framerates dropping in combat while running split screen should be expected sometimes. If this is a constant problem, I’m not sure. Hard reset?
As for h2a, I can confidently say the xb1 is simply not powerful enough.
> 2533274796867934;13:
> > 2661949065465166;12:
> > So gameplay>graphics isn’t actually the case. What a joke. Frame rate is paramount. As for Reach dipping to 20fps… idk. I am very sensitive to issues like this and vertical tearing (Titan Fall). H2A will give me a head ache after a night of playing on forged maps. Like I said in the OP, I can’t run a map I built in Halo 3, Reach, and Halo 4. (though it did dip in H4)
> >
> > This theory also doesn’t explain the frame rate issues in HCEA when in split screen. It’s a 360 game. It shouldn’t make the XB1 breake a sweet.
>
>
> When running split screen you are running two simultaneous renders. Basically like running the game twice graphically but with lower resources being needed. together though, the sum is greater. HCEA is also running a higher native resolution which is then downscaled since it’s on the xb1. If you’re seeing framerates drop below what they would on the 360 in split screen often, then there is something else wrong. Framerates dropping in combat while running split screen should be expected sometimes. If this is a constant problem, I’m not sure. Hard reset?
>
> As for h2a, I can confidently say the xb1 is simply not powerful enough.
HCEA does it most of the time. Out door areas seem to be the worst. No combat. Just walking. Not just my console.
“As for h2a, I can confidently say the xb1 is simply not powerful enough.” This is crazy to me. Build a game to suit the hardware. I chalk this up to sloppy game developing or graphic bars being set unrealistically high in part due to publisher pressure.
So we can dump H2A forge in the can. Better luck next time.
> 2661949065465166;1:
> On the forge “budget” ~ I know the forging community is a small one. But, if a feature is going to be included and hyped it ought to work properly. The much hyped forge budget is complete BS. Sure, I can place 650 objects. But it comes at the expense of performance. I currently have a map near completion with only 400 objects placed. I am seeing performance issues even while so far under budget. Constant frame rate dips make forge maps “challenging” to play. The budget is BS. Halo 4 forge had performance issues as well. Whatever 343i is doing with forge they ought to stop. Reach Forge remains up top of the list so far as forging is concerned.
>
> This is yet another example of the sloppy work done in MCC.
So wait, wouldn’t this mean that most launch and/or early titles would have similar issues? The original HCE had no such issues on XboX. That just doesn’t hold water. It’s sloppy.
> 2533274979150779;15:
> > 2661949065465166;1:
> > On the forge “budget” ~ I know the forging community is a small one. But, if a feature is going to be included and hyped it ought to work properly. The much hyped forge budget is complete BS. Sure, I can place 650 objects. But it comes at the expense of performance. I currently have a map near completion with only 400 objects placed. I am seeing performance issues even while so far under budget. Constant frame rate dips make forge maps “challenging” to play. The budget is BS. Halo 4 forge had performance issues as well. Whatever 343i is doing with forge they ought to stop. Reach Forge remains up top of the list so far as forging is concerned.
> >
> > This is yet another example of the sloppy work done in MCC.
>
>
>
>
> What map are you forging on?
Awash and Skyward.
Edit: The Skyward map is 150 pieces under budget. So it’s not even close to the limit set by Certain Affinity.
I like how in its first year of existence, the Xbox One just … well it just can’t. If games are already coming out that are pushing its limits then I think we’re in trouble. Unless they release an Xbox One Slim that’s all kitted out with upgrades that force us to upgrade as well.
Because if year-one games are maxing out its capabilities … well, you remember how the year-one games looked on the 360 compared to say Halo 4? The amount of growth there is incredible. And I guess this means we’re not going to be seeing this, are we? Unless I have no idea what I’m talking about and simply basing this off of what some of you guys just said. I find it hard to believe they released a console that would be obsolete in a year. And yes, I know about PCs and how awesome they are.
Anyway, that’s unfortunate OP. I haven’t really messed around in forge yet (other than to create sets with effects for screenshots that I can’t upload anywhere) so I haven’t seen this, but it is a bit discouraging.
Like it makes a difference. Any map over 300 objects is doomed to crash/lag/despawn. It happens all the time and it drives me insane. I can’t make YT videos for my channel due to it. 343 need to fix custom games.
> 2533274824886620;19:
> Like it makes a difference. Any map over 300 objects is doomed to crash/lag/despawn. It happens all the time and it drives me insane. I can’t make YT videos for my channel due to it. 343 need to fix custom games.
Don’t hold your breath. 343i made it clear with Halo 4 that customs are far down the list.
Edit: Wow… @ despawning
I didn’t connect the dots. I would place a hog and then go back thinking " I know I placed that… I think". Crates despawn for me too.
