Halo Dev Tracker

Thanks for the tip! Any chance you've also tried turning off v-sync? Some other players are reporting that when they do that, input feels much better.

this is a great place to share in discussions and get insights and perspective, but it's quite difficult to quantify and it doesn't scale well when volumes increase. We're pretty excited to also be beta testing and eventually launching a support site to streamline issue reporiting and prioritization here in the studio. We'll continue to be hanging out here and around social, etc.. to hear opinions and thoughts and we do our best to aggregate what we gleam from reddit, twitter, waypoint, etc..

thank you!

Win7 support is still not currently included in this flight - the team is still testing some potential fixes to the blocker they've been dealing with.

For now, two things you can/should try (if you haven't already) - disable uncapped framerate and try turning off v-sync. We're aware that uncapped seems to be adding a slight amount of input delay and I've seen some other players online say that disabling v-sync made it feel much more responsive for them.

At least a week, potentially longer, will really depend when the patch is ready and when it gets out the door and then how much time we need with that in the wild / how well it addresses some of these issues...

FWIW I'm told that Reach PC is using raw input...

There are numerous known issues pertaining to locks and crashes - I'm told a lot of these are already addressed (keep in mind the flight build is several weeks old by this point). Hopefully you've been able to file a support ticket regarding your specific issue?

I didn't say this was the solution. It's currently one known contributing factor. And, despite all the noise here and on twitter, the amount of actual tickets being filed for mouse input by people actually in the flight is quite low. This doesn't help the team quantify and understand the scope of the issue. Meanwhile, other players are saying "it feels great." It's somewhat challening to wade through the subjective feedback and noise, but it's currently a top priority with the team and they are continuing to investigate.

I'm really curious how that post was interpreted as 'brushing off' this issue? I'm asking folks to try disabling uncapped and see if that helps the situation. It's one of many areas the team is working through.

Uncapped and FOV sliders were always a goal but given the state of the game and how old the code is and how it was never natively built to do this, the team always knew it could have mixed results and unforeseen consequences. It's definitely still something they're working through.

This issue is definitely being looked into. I'm seeing a lot of folks just jumping to conclusions that this is somehow being 'brushed off' - which it's not. We've made dedicated threads here on Reddit to get more info. Getting to the bottom of this is a big priority. The team has found that uncapped FR is introducing a frame or two of extra input latency, so the suggestion is for folks to try disabling that and see how it feels. Is that the ONLY culprit? Hard to say, but it is a constant with most every report we've received. It's a tricky issue since we have a lot of vocal folks on reddit and social (and no way of knowing how many are actually playing/speaking from first hand vs. just piling on - I have to believe a lot of noise is the latter) and many folks here in the studio haven't personally experienced this (including 343's "pro team" which is all former Halo pros who are very sensitive and aware of these types of things). Further, the amount of actual tickets filed on the Ha...

We're going to get some deeper insight from the team around this as we've been having discussions with them about this feedback. While it's "true" to OG Reach, I personally agree that in today's world, particularly with M+KB, it's not a great mechanic. That said, it's not entirely trivial and has cascading affects across the game. It's something they are going to dig into more and explain and share how they're thinking about it but at this stage I don't personally expect this aspect of the game to change by launch.

Thanks, that was what I was trying to say. I get that folks are pretty worked up and ready to pounce. This is a flight, this issue wasn't reported in the last PC flight. The team is certainly working on better understanding what is happening under the hood. One early culprit is believed to be uncapped FR - that's not to say it's a silver bullet solution. I really wish more folks who are actually in the flight (it's impossible to tell who in this subreddit is actually playing and speaking first hand vs. just piling on - I feel a lot is the latter) would file tickets/bug reports via the Halo Support site. I just checked this AM and overall, despite how vocal folks are here on reddit, mouse input 'delay'/issues don't have very many tickets filed. Obviously we're here and on on social looking for feedback but the support site tickets are the source of 'truth' for the team and the only real quantifiable/data-driven way they have to assess what's going on. If you're playing in the flight...

We'd like to see people turn off uncapped and see if it helps their experience. Not sure how you guys jump to that as "brushing off" bugs?