well oh shitI wouldn't have done that. By giving away your key you risk being blacklisted from future flights.
Which mode?My friend is telling me that the sound on CE is different than the console version. How are they messing this up so bad?
Campaign but I'm sure it's messed up all around.
Campaign cutscenes animation run at 30FPS on Xbox, there's a simple mod on original Halo PC to fix this. I was really hoping 343 would fix this with this port but looks like they haven't among all the other issues with classic CE.The cutscenes in H:CE still seem messed up at 60fps or unlocked. I've tried fullscreen, windowed, and borderless. The gameplay itself is perfect.. but the cutscenes have a weird stutter to them which looks like 30fps animations trying to be interpolated to 60 or unlimited fps and it doesn't sync properly.
The only thing I didn't try, which I guess I should have, was changing my monitor to 60hz instead of 165hz. Maybe that will fix the issue?
Is it like that on Xbox?
I got the Steam code/invite. This pre-release version of CEA is ALARMINGLY poor. Right-click is non-functional, sound is constantly popping (especially in menus), and I have a bizarre amount of stutter on a 144hz VRR display on a high-end system in both gameplay and cutscenes. This should not have been sent out. I legitimately can't zoom with the sniper rifle on Mouse 2, which to my taste, is unplayable. I've played this at length on Xbox, and these issues are specific to PC.
I'll say it again: This should not have been sent out.
This is an interesting take considering It's a test flight. Submit a ticket on the Halo support site.
I got the Steam code/invite. This pre-release version of CEA is ALARMINGLY poor. Right-click is non-functional, sound is constantly popping (especially in menus), and I have a bizarre amount of stutter on a 144hz VRR display on a high-end system in both gameplay and cutscenes. This should not have been sent out. I legitimately can't zoom with the sniper rifle on Mouse 2, which to my taste, is unplayable. I've played this at length on Xbox, and these issues are specific to PC.
I'll say it again: This should not have been sent out.
I think you should reconsider your participation in these test programs. :p
I think basics like controls (not nuance like"feel", but buttons working in a default environment) should be handled before sending out to test groups. I care enough to ticket the issue in their Zendesk system. I don't think I'm being unreasonable to question whether they're making their own jobs harder by sending out versions where that level of problem will eat up time and energy all around. This issue was reproducible for me on two different devices.
Most of the time these tests are targeting specific aspects unrelated to the issues you are refering to. In addition they may already be aware of it but it's a non-issue for testing purposes.
Just saying, you are making a mountain out of an ant hill. This is an early test build and has no set release date yet. If they were expected to have every issue ironed out before flighting then the game will either never release or they will skip flighting altogether.If you're following the flights, they have a list of known issues in the builds so they don't get redundant tickets to run through. This was sent out without any outward sign they were aware of it. We can agree to disagree that control inputs for something like zoom are an issue for testing, but you don't need to act like I'm unaware of things you obviously aren't following, yourself.
Just saying, you are making a mountain out of an ant hill. This is an early test build and has no set release date yet. If they were expected to have every issue ironed out before flighting then the game will either never release or they will skip flighting altogether.
Zoom in with the scope is broken because its bound to the same button as the secondary vehicle fire and that causes an issue for some reason. If you rebind the conflicting vehicle fire itll zoom fine. Not a perfect fix but thats why its a testI got the Steam code/invite. This pre-release version of CEA is ALARMINGLY poor. Right-click is non-functional, sound is constantly popping (especially in menus), and I have a bizarre amount of stutter on a 144hz VRR display on a high-end system in both gameplay and cutscenes. This should not have been sent out. I legitimately can't zoom with the sniper rifle on Mouse 2, which to my taste, is unplayable. I've played this at length on Xbox, and these issues are specific to PC.
I'll say it again: This should not have been sent out.
Zoom in with the scope is broken because its bound to the same button as the secondary vehicle fire and that causes an issue for some reason. If you rebind the conflicting vehicle fire itll zoom fine. Not a perfect fix but thats why its a test
My friend is telling me that the sound on CE is different than the console version. How are they messing this up so bad?
He was on remastered for both.Thought I didn't make it in, but I received the invite at 2:55 AM my time.
Tell your friend that there is a toggle for Classic and Remastered Audio in the Options:
I got that tooThis is making me so much more excited for Halo 2 and 3. This already feels so much better than Reach.
I didn't read my emails. When do I get to play matchmaking?
Cool stuff! Got in. Shame the limited play times and the ungodly hours they chose.
You can play whenever you want. Those play sessions detailed in the E-Mail are just when 343i needs everyone to be online for a stress test.
Yeah I shoot the plasma pistol and it does the charging sound despite me never charging it up.Finally, some good fucking food.
Plasma Pistol sound effects are broken as all hell
this is getting out of handDamn Halo Combat Evolved is so fucking good
Just imagine if they made a sequel......
Like the missing fog in AOTCR? Looks borked still to me.are the transparency effects and lighting that were broken in the original mcc fixed now? i saw some other similar stuff had been was wondering if they went the whole way
As frustrating as it is, it is figured out in regards to Reach. They have to re-encode audio and have a small team.How have they not figured out the audio issues by this point, are they all playing off tv stereo speakers in a loud room over there or what?