Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Here is a screenshot showing as high as I can aim.[www.cdmfabrication.com]
IGN's website clearly shows an image with their aim in the middle of the bag. So what are we doing wrong?
I wanted to make sure I came back to this, as I even opened up a bug report with EA about this, as I was ready to refund this game over this, as it's game breaking. As it turns out, Cody just can't aim to this part. You must be May to aim the vacuum high enough. The bad part is there is no checkpoint really, that you can just reload, so you pretty much have to replay most of this level, and make sure you end up with May on that side of the level to aim the beads.
Holy cow, they were beyond useless. I also tried contacting them.
Between this bug, and the bug where I completely lost my savegame for no reason, this game kind of pisses me off. Which is sad because the game itself is just a masterpiece. Glad you figured it out and hopefully this thread brings more awareness to this bug.
I agree with you it's shown in many videos. However in my play through, and many others, something happens and it seems game breaking. Cody will not aim high enough. Both my wife and I tried. We tried various controllers, we tried restarting the level, we tried keyboard / mouse instead, nothing fixed it. Swapping the characters around however, worked first try. Googling this same issue, I came across many others stuck on the same problem (you'll notice I didn't start this thread). I posted the same solution in an EA thread, and another user confirmed it worked for them. No idea why.
Thank you so much! We’ve been stuck on this for awhile, and this is the solution we need! You are our hero!!!
THANK YOU !!!
Temporarily going from 144Hz to 30Hz fixed it.