Have they said strictly pvp matches, or will bot ones also count? I'll probably do 10 pvp ones no matter what anyway but it would still be nice to know.
It's 10 multiplayer matches - so Social Arena, Bot Arena, BTB all count. Academy (Training Mode and Weapon Drills) will not count.
Performance, optimizations, and networking all have an impact on aiming / input / responsiveness. And there are WIP elements to all three of those in this build. This is why some opinions are in such contrast or why someone said aiming felt 'great' during Training but terrible in PVP (there's no difference within the game so that implies a network-related cause). And mechanics within the game also impact aiming and perception of aiming - Sidekick and Commando have an accuracy penalty component, there's not a red reticule on PC, Halo Infinite overall does not feel exactly like H5 or MCC (diff networking model for starters), etc. Lastly, some folks have had wildly different experiences based on how they've tinkered with their settings (deadzones, acceleration, etc..)
Feedback is being heard and we'll get some good data as well to help people far smarter than me make sure the experience aligns with the design goals for the game.
They haven’t said it’s for M&K but I think it’s going to be aiming in general, just because they are aware of it on controller as well. Ske7ch responded with this to a tweet about aim issues on controller so here’s hoping they’ll be addressed and fixed.
Dude I hear you 100%, at it’s core I’m loving Infinite and how the gameplay and everything is, but the aiming is one huge issue. If that can get sorted out though, Infinite would be absolutely amazing to me.
I’ve thought about this a lot, like seriously what the hell would this game have been if it did launch last year…? Goddamn :/
Have definitely heard feedback from controller players, too. You're covered! We've heard negative - and positive - feedback from both M/KB and controller players (who play on PC or Xbox).
It's a little frustrating for them to claim it was a known issue after the fact. Like, I don't think it would have been that damning to be like "We've had some internal issues regarding aiming, so we would really like player feedback regarding that so we can get more data from more people", and no one would have been upset. Aiming is such a fundamental part of the game that we're only hearing about there being known issues after three days is weird.
There's a Known Issues list on the support site that's been there since we began. I didn't have the character count but as I've expressed elsewhere, there are "known issues which can negatively impact aiming." Performance issues, optimization, and networking, for example, all have big impact on aiming/input/feel. That's what I'm referring to, not that we expressly "knew there were issues with aiming."
Thanks for acknowledging the issue.
Can you at least confirm aiming/aim assist operates the same in PVP as it does in training and weapon drills? If the intention is yes, something isn’t right. Training and weapon drills were absolutely perfect. 10/10. PVP was not the same game in my experience (PC, controller)
Under the hood there's zero difference in aiming between Academy and PVP. So in your case, my (non-engineer/non expert) assumption is that what you felt was network related. Academy is local, PVP is not.
If he genuinely doesn't believe that there is an issue here, then he's delusional. Infinite felt terrible on the Series X.
For me personally, I didn't have any issue. Does that mean YOU didn't have an issue? Nope. Are others saying it felt good for them on XSX? Yep.
It's a hot topic, clearly, and something the team is aware of and monitoring. I'm not a sandbox engineer so lucky for most in this thread, it doesn't matter what I think. :) I'd just like to find a balance where the majority of folks are feeling good (we'll get more conclusive data than just some tweets and reddit posts).
Aiming felt fine to me and my K/D was in the 2.2-2.5 range across ~15 games on xsx.
I do think aim assist is much weaker than other modern shooters like CoD: Warzone. I think infinites aim assist is similar to H3, but it's much harder to hit shots bc the movement is much more responsive and less floaty. I also feel like I need to play a much higher sensitivity in infinite than h3 (6 vs 3) to leverage the more advanced movement mechanics so that also makes it harder to track.
I think people are conflating issues with bloom and other stuff like the jarring difference in zoom when unscoped (120 fov) and first level scoped sniper with the aiming mechanics.
There are a lot of factors that come into play here for sure, including bugs/pre-release nature of the build even.
Sketch and team - please go back and play Halo 5 for a few sessions. To me the difference is night and day. Unless the jagged behavior is intended, the difference is obvious.
Nobody is saying it's the same as H5, it's not. Also to be clear, I'm not trying to minimize anyone's feedback or frustration. To me, it feels 'fine' but I'm very used to it. I also see M/KB players who swear we need to reduce aim assist on controller because it's OP and plenty of controller players saying they need more aim assist because M/KB is OP.
This is clearly a negative theme for a lot of players so it's something the team is watching closely. Unfortunately there are also known issues in this build which can definitely impact aim/input. I've chatted with our Sandbox team and for now they're waiting until they get data coming out of this preview and can compare with current builds before wading into this. There are a number of factors that can be at play including game performance, network performance/latency, behavior of certain guns (Commando and Side Kick in particular), differences with past Halo games, red reticule not being present on PC, and so on.
...
Read moreSo, they upload a set of off brand "bootleg" figures made to be like LEGO while they could have just used their own mega bloks/construx figures and cross promote. Then they removed comments because it caused a minor controversy i think. I just hope we dont lose the megabloks halo brand.
This was a fan-made custom figures #HaloSpotlight submission. Now that you mention it, I have no idea what's going on with the comments. Very odd. Megabloks is still a great Halo partner and nothing is changing there that I know of. Just a case of an unfortunate case of Spotlight content kind of creating a little dust-up as it featured a competing product.
I mean, hopefully. But very recently he replied saying he thought it felt fine on Xbox. And this statement is reeeeally hedged. I’d give it 50/50 odds the flight is working as intended and how it was planned to launch
To me personally, it does feel fine - and I also acknowledged I'm well acclimated by now. But clearly enough folks are expressing frustrations that it's a key theme and something the team is indeed monitoring closely.
I know it’s the same exact build but I was hoping they’d at least patch the BXB glitch. It was getting quite annoying to deal with last weekend.
It's unfortunately far from trivial and not realistic to release a significant patch for this weekend (we are also working hard to finish and ship the entire game in parallel). We may, however, have a small PC-only update coming that has some modest perf updates and addresses a cause of some frequent hitching. As long as that gets a clean test pass, we expect that update to land before the flight re-opens (PC only).
Tickets are for bugs and issues please, not feedback. We've heard the feedback from players who don't like this. If there are any changes in this area going forward, we'll be sure to provide an update.
does crtl + shift + winkey + B fix it and are your graphics card drivers up to date? I've heard updating drivers have fixed quite a few issues.
not sure what GPU you're on, but the known issues list cites a specific AMD driver (or newer) is highly, highly recommended. (or latest NVIDIA might also help)
Are you also aware of those with laptops that have integrated graphics cards aren't getting invites? I have a Razer Blade 15 with an rtx 2060 and I haven't been invited for either flights. Did the dxdiag well before 9/12.
Edit: just saw the #2 edit. Thanks for addressing, ske7ch. Appreciate the hard work your team is putting into resolving these issues.
Just updated my main post up there but yes, digging into this more - it does indeed look like an issue where only the integrated GPU is detected, not the dedicated GPU. Unfortunately I'm told this is not a trivial issue to resolve and as such, very unlikely we can address for this flight. Wish I had better news, very sorry for that.
Here's a question: last flight I had a GTX 970, in between flights I upgraded to a RTX 3070 Ti. I forgot to update my dxdiag file on waypoint. Do I not get into the flight now that I've updated it? If not, no biggie, that's on me. Just wondering what to expect.
If you had the updated DXDIAG with your 3070 in your profile before the query was run, which I believe was 9/12, then you should get picked up in the batch today.
If you updated it after that cut-off, we won't be able to get you in this weekend but hopefully you'll be able to slip in next week via the expanded options I mentioned above.
This is EXACTLY the kind of response we were looking for. Porblems will always occour in beta builds, and obviously fixing the game ITSELF is a priority. Just giving your fans the feeling that their voice is heard, and that they're NOT forgotten by any means, is very important.
Please keep in mind we have thousands of people tweeting at us, tens of thousands of support tickets pouring in and we're just a few people doing the best we can. Everyone cares, we can just only do so much, so fast.
I'm very glad the team was able to sort out the 3080 card issues and steps are underway right now to remedy that along with the invalid steam keys - combined that's a decent chunk of players and trust me, we want all of them in this flight because that group alone could be the difference between us hitting our concurrency goals or not!
An issue was identified where 3080 and similar cards did not get recognized correctly. Looks like that's less than 2,000 people who fall into that category. Updated invites/keys should be going out to these folks who should've been included today (this work is underway now).
There are several thousand Insiders with 900-series GPUs who were invited last time but really shouldn't have been given the known issues and level of support in the game. For this preview, the call was made that this build doesn't officially support those cards, which means those folks did not get invited.
Additionally, we do have reports of a subset of Insiders who have reported that their profile was inexplicably wiped/reset. This is a new issue still being investigated with no obvious root cause and is not expected to be resolved during this preview.
There are admittedly a variety of less than ideal aspects to this entire flow and we recognize that. Unfortunately, tinkering with the ...
Read moreI did not see the door being the surprise star of the stream / multiplayer preview / entire game, but here we are. :) It is an awesome door.
Good news, we think we're in the clear here and Training Mode should be back on the menu.
Any word on whether it'll run on 900 series GPU's this time around? Sucked getting in but not being able to play at all.
hey, I got an update on this - unfortunately, it sounds like some 900-series card issues are still present in this upcoming preview build. The team did indeed address the major crash problem that was present during the last technical preview but as is often the case with game development, other issues have surfaced. I'm sorry to say that for this next preview, 900 series cards are not supported. I'll share more info as I can get it, the team is continuing to work on bug fixing and polish for this and other areas of the game on the road to release.
devtrackers.gg