No, there's no option to restart a section other than loading a save. I've looted midair a lot, it can be done. If you're using KB&M, try spamming "f" after the jump.
THIS IS NOT A SOLUTION.
IT ONLY WORKS IN A SMALL NUMBER OF CASES.
FIX IT
This is a game breaking bug that has been known since shortly after the game was released, see this thread: http://forum.bioware.com/topic/522745-in-hushed-whispers-lyrium-shard-bug/. I encountered this bug today, 6th December 2015, playing the game on PS4. I've looted 4/5 lyrium shards, but the last one is stuck up on a wall out of reach. My autosaves are both from after the group in this room was killed. My last manual save is from before I went to Redcliffe, and reloading means I will lose an entire evening of game play.
These days I don't have that much time to play computer games, so replaying an entire evening is not going to happen. I'm a big fan of Bioware games. but when a GAME BREAKING bug that's been known for more than a year is still not fixed, well, then I become extremely disappointed.
As it stands, unless someone can provide me with a workaround for this bug that does not involve reloading a savegame several hours of gameplay earlier, then my DA:I progress comes to a full stop here. If it does, this will also be the last Bioware game I buy, unless I get a full refund for this broken game.
I've contacted Playstation Store regarding a refund for this broken game. They require a confimation from the game developer that they authorize such a refund. Since this thread already got a so-called "accepted" answer (which is nowhere near a solution) I guess EA won't reply to it again. And since I've found no way of contacting either EA or Bioware direcly I doesn't seem like I will be getting anywhere with my claim.
A boycott of future Bioware games it is then, however much it pains me. I was, among other titles, looking forward to the next Mass Effect installment. But I can't support a developer that doesn't fix their broken games.
@Balerion74 These are community driven boards, not a method to contact EA or Bioware. You can contact EA here.
I've played this game probably 10 times, the majority of which I've sided with the mages, and I've never encountered this bug. It doesn't affect most players (look how few posted on this thread), so there wasn't a huge demand for it to be included in one of the patches, while there were many game breaking bugs impacting the majority of players which did need to be addressed. It's also an easily avoidable issue if you save regularly, meaning it's nowhere near 'game breaking'.
@Leora85 Thank you for responding. Strange, I had already tried contacting EA via the link you provided, but I only got the option of posting on these boards. Perhaps it was due to the time of day I tried it or the subject I chose. Now I got the option to initalize a live chat as well. I would have preferred an email option, though.
Since you have had time to play this game 10 times it looks like you have a huge amount of time to play computer games. Redoing a whole evening of game play is probably insignificant in that sense. For me it usually takes a couple of months completing a game of these proportions, so a setback like this feels like game breaking to me. The game was released more than a year ago, so I expected that any bugs that stopped game progress would have been fixed by now. Had I known about this bug I would of course have saved the game regularly, but since the autosave happened quite often I didn't see the need for it.
The number of people reporting this bug on this thread/board is only a small indication of how many it affects. It could affect countless players who doesn't care for various reasons (for example they don't mind replaying a whole evening), or they can't find their way to this particular board. I've found the same issue being reported on several other forums. Do you play the game on the same platform as me (PS4), by the way? If not, the perhaps that explains why you've never encountered the bug.
I'm sure there have been other game breaking bugs that needed to be adressed before this. However, the game is well over a year old now, so it should have been fixed by now.
