Original Post — Direct link

The game is in a horrid state right now from the current flight. Network lag is awful. Having a PC game in 2019 that can only be limited to 60 FPS or else the mouse feedback breaks is unacceptable for release. Also the startup audio earrape shouldn't even have made it into a flighting test. I really want the game to be GREAT and only hear positive things when it releases, but I feel like if 343 get too excited and release it in 2019 without fixing these things above especially we are just going to have a repeat of the original MCC release 5 years ago.

In all honesty I'd rather have Reach in 2020 and be blown away, than have it in 2019 and just be disappointed by 343 yet again

I think 343 and us can all benefit from more flight tests, or even a constantly updated test environment so that hundreds if not thousands of people can all help to find bugs and state problems they find

External link →
over 4 years ago - /u/ske7ch343 - Direct link

Originally posted by ChieftaiNZ

The game has a number of bugs, some of which may have been brushed off, like the audio bug and /u/ske7ch343 's recent comment on mouse lag.

I just read that comment, yikes bro, gives me 2014/2016 343i vibes when they just ignored MCC's issues. Not good at all.

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.

over 4 years ago - /u/ske7ch343 - Direct link

Originally posted by staryoshi06

To me it reads like 'Use this as a temporary fix during this flight, as we do not patch flights since they only last a week.'

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?

over 4 years ago - /u/ske7ch343 - Direct link

Originally posted by digita1catt

What its actually saying is that a game designed for a certain fps and fov 10 years ago was never was intended to be used beyond those constraints and that the engine is struggling with irregular fovs and framerates, causing input lag.

He then provides a temporary solution for those suffering with the input lag. At no point does he suggest it will just be left as is, its an unfinished product and there are known bugs to still squash.

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 and you have mouse input issues PLEASE file a support ticket.

over 4 years ago - /u/ske7ch343 - Direct link

Originally posted by WhiteKnight3098

It would appear nostalgia has clouded my vision. Why not improve it now then anyway?

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.