ske7ch343

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?

I'm not sure at what point my comment "brushed off bugs." I stated that the team is aware of uncapped FR having a negative impact on mouse input.

Cool, thanks for this. The team is definitely aware of a known issue where enabling uncapped framerate does introduce additional input delay. For players experiencing issues, we do suggest disabling/returning to 60FPS. Pursing variable frame rate support and non-standard FOVs were always known to be a risky proposition and results will definitely vary given the underlying foundation of the title (content and systems authored for a specific FOV and specific frame rate).

hey Rabirx - Thanks for sharing your feedback/experience. As you can imagine, stress and tensions have been high as folks have been trying to keep up with hundreds of support issues that mostly seem to involve a core issue of participants not carefully reading/following the instructions sent to them.

We have found that multiple email addresses/wrong email address is a key leading cause of issues for many people (agree it's something we should look into at a higher level and see what measures we can take to try and prevent players from getting into that situation to begin with). As for the web page, the support site itself is in a beta stage, while I don't disagree a more 'formal' error page would be helpful, reality is that it's out of scope (and this is the only instance of this feedback I've personally seen out of tens of thousands of participants).

That said, regardless of the frustrations or conditions anyone here is going through, we're always expected to ope...

Hi folks -

First, apologies for branching off of the main Halo: Reach PC flight feedback thread but we wanted to make sure this didn't get lost as there's already been a lot of discussion in that thread over the past few days. If you have general feedback and thoughts about your experiences with the current PC flight, please share that HERE.

This thread is specifically for gathering more focused feedback pertaining to MOUSE INPUT. If you have experienced this, please read this thread below which I'm posting on behalf of 343 pub team senior producer ...

For players who feel the mouse input isn’t performing as expected - one note we wanted to pass along was to please turn off uncapped framerate. We have seen that this does introduce a bit of input latency. Would be cool to hear if anyone who has this issue notices a change when they turn off uncapped FR... the team is still digging into these reports but wanted to make sure players are aware of that specific aspect.

The 'issue' as I understand it is currently accurately recreating the way it worked in the original Reach for Xbox 360. That may or may not be desirable by players, but at the moment it is true to the original. Feedback has been passed on. (I agree it feels jarring in today's day and age, but priority for the team was accurately translating the original game to modern platforms)

Appreciate everyone sharing feedback, suggestions, and flagging issues. Please please try and file official tickets at the support site if/when you can. We do parse through posts here but the ticketing system allows the team to better quantify the scope and extent of issues and allows for easier creation of a bug in the team's database (when warranted). We have relayed feedback around push-to-talk (great suggestion) and the reports of mouse movement feeling "off." We've also flagged the audio concerns some have raised and the 'getting stuck and unable to back out of a menu/screen" is now a known issue the team is tracking.

Sorry to rain on the parade but this is actually a weird unintentional issue we encountered today as part of work prepping for the upcoming PC flight. There’s nothing to see or do with the build. It will be deactivated soon with a required download for anyone who managed to get the errant update. You truly are free to and encouraged to delete any old MCC insider builds and reclaim the HDD space as we have no current plans for further flights / updates with that content on Xbox.

Working through kinks and intricacies of build release through different stores/ecosystems is one of the reasons why we flight. :)

The Pc MP flight is currently in Ring 2 validation.

Highly variable. In numerous cases the build goes to Ring 1, issues are found, work is done to fix issues, new build is kicked off, restart ring 1... It really just depends on what, if any, issues arise and if they're deemed serious enough to be a 'ring 3 blocker.'

once it does come out, it should last roughly a week like the Xbox MP flight did.