How to Fix Damiane or Oongka Turning Invisible in Crimson Desert

If Damiane or Oongka turns invisible in Crimson Desert, Pearl Abyss already has a real workaround for it. The official known-issues page says you can resolve the problem by either:

• switching back to Kliff through the ring menu
• or saving and reloading

That is the current official answer as of March 28, 2026, and it is much better than guessing through random companion or quest workarounds.

The quick fix

If Damiane or Oongka disappears:

1. switch back to Kliff using the ring menu
2. if that does not restore things cleanly, save the game
3. reload the save

That is the support-safe order because it is the exact recovery path Pearl Abyss currently publishes.

Why this bug matters

This is not just a cosmetic nuisance.

Damiane and Oongka are tied to:

• combat presence
• character swaps
• party-state clarity
• progression confidence in their related questlines

So when one of them goes invisible, the player reaction is usually "is my save broken?" The official notice is useful precisely because it separates that fear from the actual status:

it is a known issue, and Pearl Abyss does publish a recovery step.

What the official notice says

The known-issues page says:

• Damiane or Oongka can become invisible under certain conditions
• if it happens, switch back to Kliff via the ring menu
• or save and reload

That wording is practical because it gives you a first-response action instead of only acknowledging the bug.

Why switching back to Kliff makes sense

Pearl Abyss' fix path suggests the issue is tied to character-state handling rather than a permanent content loss.

That is why you should not jump straight to heavier troubleshooting like:

• reinstalling the game
• abandoning the entire questline
• assuming the companion is permanently gone

The official workaround points first to refreshing the active character state.

When saving and reloading is the better option

If the ring-menu swap does not fully clean up the issue, save and reload is the next official option.

That is especially sensible if:

• the invisible character state keeps lingering after the swap
• the screen state feels visually broken
• you want the cleanest reset without moving deeper into support steps

Because Pearl Abyss already lists save-and-reload as valid here, it is worth trying before anything heavier.

When you should report it

If the same invisibility problem keeps returning on the latest build, it becomes worth documenting and reporting.

Useful report details include:

• whether it was Damiane or Oongka
• what you were doing right before it happened
• whether ring-menu swap fixed it
• whether save-and-reload fixed it
• whether it keeps happening in the same quest or combat state

That turns a frustrating bug into a much cleaner reproducible case for support.

Why this is different from a generic known-issues page

The general known-issues article is useful when you do not know what class of bug you are dealing with. This page targets a much tighter search:

• Damiane invisible
• Oongka disappeared
• character invisible after swap

That tighter search intent is why the official workaround deserves its own article even though the bug also appears in the bigger status roundup.

What not to confuse this with

Do not confuse the invisibility bug with:

• not having unlocked the character yet
• a story sequence where the character is intentionally unavailable
• a separate interaction bug after switching back to Kliff on PlayStation, which patch 1.00.04 targeted

Those are different issues with different official statuses.

If your question is actually about unlocking the characters, use How to Unlock Damiane and Oongka in Crimson Desert, Crimson Desert Damiane Guide — How to Unlock, Abilities & Best Build, and Crimson Desert Oongka Guide — How to Unlock, Abilities & Best Build.

Is this still active after patch 1.00.04?

As of the latest known-issues page checked for this article, yes, the invisibility issue is still listed there. That matters because 1.00.04 solved a different PlayStation problem involving actions and interactions after switching back to Kliff. It was not advertised as a global Damiane or Oongka invisibility fix.

So do not assume all character-switch problems are one bug.

The best response sequence

Use this order:

1. confirm the disappeared character is Damiane or Oongka
2. use the ring menu to switch back to Kliff
3. if needed, save and reload
4. if it keeps returning, compare against the live known-issues page and report it

That is the cleanest sequence supported by official guidance.

It also keeps you from overreacting. The official workaround exists precisely so you do not mistake a recoverable visibility bug for a permanently damaged character state.

FAQ

Is Damiane or Oongka turning invisible a real known bug?

Yes. Pearl Abyss still lists it on the live known-issues page.

What is the official workaround?

Switch back to Kliff via the ring menu, or save and reload.

Does patch 1.00.04 fix this?

Not according to the official notices checked for this article. 1.00.04 addresses different character-switch and Mac Steam crash issues.

Should I reinstall the game for this?

Not first. Pearl Abyss already gives a simpler official recovery method, so use that before considering heavier troubleshooting.

What to do next

Use the ring-menu swap first, then save and reload if needed. After that, keep the broader status pages nearby: Crimson Desert Known Issues and Best Workarounds, Crimson Desert Patch Notes 1.00.04 Hotfix Roundup, and the character guides for Damiane and Oongka.