devtrackers.gg
So good. Right in the feels
So good. Right in the feels
We've gotten some great bug reports, but sure, it's a fraction of the audience. It's too be expected though and I do think all of the key issues are covered. The challenge starts to come when we have much lower volume/percentage of tickets for an issue compared to the noise we see on reddit/Twitter - in that case, it's tough for the team to really understand the scope (is it just a few people? is it really everyone? are these people even actually in the flight?). This is a new resource for us building out our own dedicated support/ticketing site - we're learning a lot along the way and this should become a really great tool for us and players moving forward.
Curious on the latest status of the Halo: Reach PC flight and what's next? Check out this week's Insider update HERE.
RIP "no-name Twitter user named Josh." How is this "news" ? :)
Technically, that's exactly what happens at E3.
Technically it's no different than the 25-30K people who are playing in the PC flight right now. These folks will basically be playing the flight.
nov 12th release?
Nope. We're making great progress, but Reach is not launching next week.
Just re-confirming that no progress or unlocks from the flight will carry over to the retail release.
Nope. Sorry.
The progression system and values definitely weren't final in the flight - and I doubt they are yet, TBH, but the team is using flight data to help inform tuning. Glad to hear the initial adjustments are being positively received!
I am hoping this means you are looking into getting rid of the input delay still.
All of the issues being reported around mouse input/latency/'feel' are absoutely still being investigated and worked on.
I personally haven't noticed the aim issues that much but I just wanted to say I absolutely love how you all are handling this. :)
Good to hear! Appreciate you taking the time to play in the flight and share feedback.
Any chance you are going to send out more invites?
Possibly - still TBD at this point.
Just wanting to say thank you.
I can see you guys are taking this port very seriously so I'm very hopeful for the final release. I just hope you can get the server issues figured out before then that are plaguing the console version as well. Out of 20 games I have been on 1 or 2 EU servers.
For sure the team is taking the whole thing seriously. Server latency-related reports are also a top priority for the team and a number of things have been happening behind the scenes as they keep working on this. As for matching NA most of the time, I do think that's largely due to the vast majority of the flight population being in NA. But we know this is a longstanding pain point for players outside of NA and it's something the team isn't giving up on. I do believe eventually (potentially post launch) there will also be a manual option to just select a server of your choice (though you'd likely be opting to wait longer for a match). The mouse issues being reported by players are also a top priority. It's been interesting seeing some of the work-arounds and solutions some players have been trying and reading that some have seemingly dramatically changed how mouse feels. Heck, some players even thought we stealth patched the game because it 'felt so much better!' (nothing has been...
Read moreIf the filter's gonna be this heavy-handed, then it absolutely needs a toggle option. In its current state, it makes basic communication more trouble than it needs to be or should be.
You can't even say "rude". "Rude" is censored. Explain that to me.
If your filter is censoring sentences like "Yeah, map change is per map", because the f**kin filter thinks you're trying to say "sperm", then yes, there is absolutely a problem there that needs to be resolved. I couldn't care less about not being able to swear on in-game chat, but when you end up censoring basic stuff like this, you're almost doing more harm than good.
Please 343, make this filter toggle-able, or at the very least, make your non-toggle-able filter actually usable.
Definitely something the team is working on - my understanding is that this is utilizing a shared platform level service so there's some intricacies and potential hurdles to work through regarding implementation. I do believe this is working more aggressively than intended - but regardless, FWIW I personally would prefer 'on by default' and the option to disable. We'll share more info when we have it.
This is a great video. /u/ske7ch343 please make sure this gets seen by the right people!
Yep, it's been flagged and forwarded. The team is actively investigating reports of server latency.
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.
I'm just used to using Reddit for feedback purposes given how active 343 is here.
Things like that (community interaction) make me hopeful for 343's future.
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..
I've tried to report every bug I find not in the known issues list.
thank you!
i think they sent out steam versions of the flight which i have to assume are playable on windows 7 (someone had a vid comparing the two versions) though i do not believe they sent out more invites and this is just more an extension to see if they can figure out the input mouse delay people are reporting.
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.
Ayyy, hopefully the mouse input gets fixed up. I can't really play it right now because of how floaty it feels for me.
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.