I have put my old Omnisphere 2 User patches folder in the correct place:
STEAM/Omnisphere/Settings Library/Patches/User/, however Omnisphere 3 doesn't see them even after hitting the Refresh button. The whole STEAM folder has been reset with Batchmod so it's not a permission issue. Factory patches are all there and work fine.
I'm obviously doing something wrong.
Anybody has a clue?

 

You should have combined your custom presets into a single .omnisphere file beforehand. Omnisphere has an "Install .omnisphere" button in the menu that allows you to import your presets as a .omnisphere file. This is the best method because it restores all the presets without errors. This is described here:

Sharing
https://support.spectrasonics.net/manual/Omnisphere3/30/en/topic/sharing-index

Adding Sounds
https://support.spectrasonics.net/manual/Omnisphere3/30/en/topic/sharing-page04
___________________________________________________________________________
I consulted the AI, but I can't say if it's true or if it works:

Spoiler: Source: Grok KI

It sounds like a common hiccup with the upgrade process and the revamped browser in Omnisphere 3—especially since the new interface defaults to curated factory views and can hide user content until you tweak the settings. Since factory patches load fine and permissions are sorted, the issue is almost certainly in how the browser is configured to display your migrated Omni 2 user patches. Here's a step-by-step troubleshooting guide based on Spectrasonics' docs and user reports from recent upgrades:

1. Verify Folder Structure (Quick Check)

• Your placement in STEAM/Omnisphere/Settings Library/Patches/User/ is correct, but Omni 3 (like Omni 2) requires patches to be organized in subfolders inside User/ for visibility. These subfolders act as "categories" (e.g., User/Arp/, User/Bass/, User/Pads/, etc.).
• Open your file explorer and navigate to the User/ folder:
  • If your Omni 2 patches are dumped directly into User/ (no subfolders), that's the problem—they won't scan. Move them into category subfolders matching their type (you can create new ones if needed).
  • If they're already in subfolders from Omni 2, proceed.
• Patches must be .omnisphere files. If any are corrupted or in the wrong format from the migration, Omni 3 might skip them.

2. Force a Full Refresh and Rescan

• Launch Omnisphere 3 standalone (not in your DAW) to avoid host conflicts.
• In the Patch Browser (bottom panel), click the Refresh button (circular arrow icon) twice—once for patches, then restart Omni and do it again. This rebuilds the index.
• Close and reopen Omni 3 completely. Sometimes the first refresh caches old data.

3. Adjust Browser Settings to Reveal User Patches

• The Omni 3 browser is tag-based and directory-limited by default, which often hides user/legacy content. Switch to a view that includes it:
  • In the Browser's Directories dropdown (top-left of the browser panel), select User to isolate your custom patches.
  • If nothing shows, toggle to View All Directories (look for this option in the browser's filter menu or utility gear icon—it's a checkbox or button in the upper toolbar). This scans everything, including user folders.
  • Alternatively, select All Legacy if your patches reference older Omni 2 soundsources (they'll appear under a "Legacy" category).
  • For a folder-tree view like Omni 2 had, enable File Directory mode: Click the folder icon in the browser toolbar. This lets you drill down into User/ subfolders manually.
• Pro tip: If you're in "enhanced" or "curated" browser mode (new in v3), switch to Classic or Omni 2 Mode via the browser's view options (gear icon > Display Settings). This mimics the old layout and forces user/legacy visibility.

4. If Still Not Showing: Backup and Restore User Folder

• The upgrade installer can sometimes glitch the user index during STEAM folder updates. Back up and swap:
  • Copy your entire User/ folder to a safe spot (e.g., Desktop).
  • Delete the current User/ folder in STEAM.
  • Paste your backed-up User/ back in.
  • Refresh as in Step 2, and check the browser as in Step 3.
• This preserves your Omni 2 patches without overwriting factory content. (Spectrasonics confirms v3 is backward-compatible, so no conversion needed—just reindexing.)

5. Other Common Gotchas

• DAW-Specific: Test in standalone first. In hosts like Ableton or Logic, rescan plugins after changes (e.g., Ableton: Preferences > Plug-Ins > Rescan).
• Soundsources: If patches load but sound wrong (distorted/empty), ensure your Omni 2 soundsources are in STEAM/Omnisphere/Soundsources/User/—migrate those too if missing.
• Conflicts with Third-Party: If you have expansions (e.g., Keyscape), they might shadow user folders—temporarily move them out and test.
• If none of this works, hit up Spectrasonics support with your STEAM path and a screenshot of the User/ folder contents. They're responsive for v3 launch issues.

This should get your patches loading—most users report it boils down to the browser toggle. If you share more details (e.g., OS, DAW, or a screenshot of the browser/User folder), I can refine this further!