One can stop the Opportunity subquest Ark Boss from resurfacing; use Return to Checkpoint. The other can render the player character incorrectly in some event scenes under specific equipment conditions.
Issue status board
| Issue | Evidence | Current action | Status |
|---|---|---|---|
| Opportunity / Thicket Visgo does not re-emerge | Official 1.0.3 notes | Use Return to Checkpoint and retry. | Open; future fix planned |
| Incorrect player rendering in event scenes | Official 1.0.3 notes | Finish the scene, change equipment and retry from a safe point. | Open; future fix planned |
| Original Sin black screen | Community report | Retry with the reported partner set. | Community workaround |
| Unable to access during an event | Player reports | Check event state and reload safely. | Under investigation |
Opportunity subquest: boss does not re-emerge
During the Opportunity subquest, an attack can hit the Ark Boss “Thicket Visgo” while it is digging and leave it unable to re-emerge. The publisher's stated workaround is Return to Checkpoint. Use that option before abandoning the quest or repeatedly reloading unrelated saves.
- Pause once it is clear the boss will not return.
- Select Return to Checkpoint.
- Repeat the encounter and avoid committing an attack into the digging transition.
- If the issue repeats on a later game version, record the platform, version, and exact action sequence before reporting it.
Player model looks incorrect in an event scene
The official notes also acknowledge that the player may not render correctly in some event scenes when specific equipment is used. This is presented as a visual issue, not as evidence that equipment or save data has been deleted. If it persists after the scene, return to normal gameplay, change equipment, and restart from a safe point before considering more disruptive troubleshooting.
What is not an officially confirmed issue
Crashes, frame-rate drops, controller problems, regional store errors, and quest confusion may have many causes and are not automatically covered by the two items above. Confirm your installed version, compare the official notice, then reproduce the problem with minimal variables. Avoid publishing or following a destructive fix—such as deleting saves—without platform-specific official support guidance.