Stuck start of chapter 6 (Fix posted by #12 Algray Solipso inside)

[[T3]RhOmicron]

I closed down the game yesterday (28th of Feb) and started it up again after reaching chapter 6. Had to fix my save like most people.
But when I continued I spawned inside the wreck of the Hermes and now I have an invisible wall blocking me from exiting the ship.

[[T3]RhOmicron]

https://imgur.com/a/Xk6lpzu in this link there is a picture where the wall is.

[76561199233623070]

Hey [T3]RhOmicron,

Happy to have a look at this issue!

the quickest way for us to help you here is to send us the affected safe game by creating a ticket here: {LINK REMOVED}https://playersupport.plaion.com/hc/en-us/categories/8704681887261-SCARS-ABOVE

[[T3]RhOmicron]

Submitted

[[T3]RhOmicron]

Got told to verify steam files.
Well that didn't work.

[76561199233623070]

Hey there,

Sorry to hear that, We will look further into this for you, and will update you as soon as possible.

[[T3]RhOmicron]

Got a mail that said I haven't responded and my request would be put as solved in four days. Sent a mail on the 1st and responded to that mail today.

[[T3]RhOmicron]

Last support mail suggested to restart from an earlier save point. Unsure how one goes around doing that as the game only holds one save. And I'm at the start of chapter 6.

Returning to pillar only sets me back inside the ship behind the invisible wall.

At this point I guess I will have to start a new game.

[[T3]RhOmicron]

Was told again to "load a previous save" after being "forwarded to the appropriate department". Guess there is no solution other than start a new game.

[Thane Bishop]

Here's a fun fact; this bug still exists, a full year later.

[[T3]RhOmicron]

Oh Lionheart, great of you to respond. I never started another game and uninstalled it.

[[deevice]]

nothing...

[Algray Solipso]

I got hit by this today and was disappointed I'd have to throw away my playthrough so close to the end. Thankfully, I've found a solution that works.

Here's how to use Cheat Engine to edit the player's coordinates and relocate yourself past the invisible wall:

1. Download Cheat Engine and the tables for Scars Above from here https://fearlessrevolution.com/viewtopic.php?t=23702

2. Run Scars Above. Load into the level and run up to the invisible wall that prevents you from leaving the ship. Alt-tab out and leave the game running.

3. Run Cheat Engine. Select Scars Above from list of processes. Select the tables you downloaded in Step 1.

4. In Cheat Engine, select the "Activate" entry, then drill down the entries until you find the "Saved Coordinates" section - there should be an entry for X, Y and Z each. Write down the values currently there. These are the player's current coordinates inside the game world.

5. Increase the values for X/Y in small increments (approx 100 at a time) and keep alt-tabbing back into the game to check if you've cleared the invisible wall. If you find yourself stuck inside the floor, increase Z to move above it. To avoid getting stuck in geometry, it's better to bump the Z coordinate and place yourself in the open air, then fall down to the map.

6. Fiddle with the coordinates until you've placed yourself outside the ship, past the invisible wall. If you find yourself falling outside the map, restore the coordinate values you've saved in step 4 and try again.

7. Continue the game as normal, but do not turn off the game or reload from checkpoint until you've reached the first Obelisk in the chapter.

[[T3]RhOmicron]

Great that someone have made a cheat table for this game so you can TP past the wall.
This wasn't available at the release of the game, as I'm pretty sure I tried searching for one.

[GamingWithADD]

This must be why the walkthrough I used said to avoid closing the game out until you reach a certain point, though they didn't mention why exactly.

Shame. I rather enjoyed the game and to learn a game breaking problem like this, isn't fixed is disheartening.

[fireryone]

Had this game on my wish-list for a while, was tempted by the current sale - but this bug is concerning. Nice to see the community now has a workaround, but disappointing the dev seems to have stopped responding after collecting examples of the issue. I think I'll keep waiting on this one.