# EditorSync issues

**URL:** <https://forum.needle.tools/t/editorsync-issues/2522>\
**Category:** 🌵 Needle Engine\
**Tags:** bug\
**Created:** [May 8, 2025, 11:44am UTC](https://forum.needle.tools/t/editorsync-issues/2522 "2025-05-08T11:44:41Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![krizzl0r](https://forum.needle.tools/user_avatar/forum.needle.tools/krizzl0r/32/4262_2.png) [@krizzl0r](https://forum.needle.tools/u/krizzl0r)\
**Post date:** [May 8, 2025, 11:44am UTC](https://forum.needle.tools/t/editorsync-issues/2522/1 "2025-05-08T11:44:42Z")

</div>

First, in reply to [the closed original thread](https://forum.needle.tools/t/editorsync-not-working-for-default-editor-inspector/2345):  
EditorSync now only works for components using the VisualElement way? 🤔  
I think you just have to reenable the old path in EditorModificationListener.cs L176.

Apart from the issue above:

- There’s often trouble when turning the feature on/off (soft restart does not always work and I could not successfully walk a colleague through the process of enabling it even though I have some experience with it by now)
- I hope I don’t make things up but: The sync thing seems to keep a cache which reapplies previous changes when reloading? There were occurences where I could not get a change in the saved/exported scene through to the browser seemingly because it was overridden by a previously synced change. (This is why I have some experience in turning it off).
- Playing around with volume configurations does not reliably work, e.g. enabling/disabling effects.

I can imagine the sync stuff is not high on your priority list, it’s still a beta feature. And save-and-reload works great in most cases.  
_But_ for our designers (and not only them) it’d be of great to have it working better again. As a developer I might see why specific components or properties don’t sync but for others it can be very off-putting 😕

---

<div class="post-metadata">

**Author:** ![needle-assistant](https://forum.needle.tools/user_avatar/forum.needle.tools/needle-assistant/32/3415_2.png) [@needle-assistant](https://forum.needle.tools/u/needle-assistant)\
**Post date:** [May 8, 2025, 11:44am UTC](https://forum.needle.tools/t/editorsync-issues/2522/2 "2025-05-08T11:44:44Z")

</div>

Thank you for the detailed feedback, Krizzl0r! Here’s a step-by-step breakdown and suggestions for each point:

* * *

**1. VisualElement Path Only?**  
Your observation is accurate — EditorSync currently prioritizes UI implemented with Unity’s VisualElement system.

- **Pseudocode Plan:**
  - Inspect `EditorModificationListener.cs` at L176.
  - Check if conditional excludes IMGUI-based inspectors.
  - Temporarily re-enable the old IMGUI path for broader sync support.

* * *

**2. Issues Turning Feature On/Off**

- **Pseudocode Plan:**
  - Log status changes when toggling EditorSync.
  - Ensure proper disposal/re-initialization on enable/disable.
  - Add feedback in Unity UI on Sync status.
  - Document step-by-step for enabling/disabling (especially headless or remote scenarios).

* * *

**3. Stale Cache or Change Reapplication**

- **Pseudocode Plan:**
  - Identify where EditorSync caches previous states.
  - On scene reload, clear or update sync cache.
  - On new export/save, prioritize file-based state over cached state.

* * *

**4. Volume Configuration/Component Sync**

- **Pseudocode Plan:**
  - Check if custom components and ScriptableObjects are serialized and monitored for changes.
  - Ensure Volume’s effect stack changes are treated as property modifications and not missed by sync watcher.

* * *

**General Suggestion**

- For designers, improved UI feedback (sync status, errors, suggestions) can help.
- Document clear troubleshooting steps for enabling sync.
- Consider a “Flush/Clear Sync Cache” button.

* * *

### Code Snippet to Re-enable IMGUI Path (EditorModificationListener.cs Example)

```csharp
// C#
// At EditorModificationListener.cs Line 176
if (/* condition excludes IMGUI path */) {
    // Re-enable IMGUI inspection sync
    ListenForIMGUIInspectorChanges();
}

```

**Note:** The real condition and method name may differ; review existing code to adapt.

* * *

**Tips for Further Questions:**

- Provide Unity version and exact Needle Engine version.
- Share logs when toggling EditorSync.
- Note if the project or inspector uses custom inspectors or non-default patterns.

For more details: [EditorSync docs](https://engine.needle.tools/docs/editor/editor_sync.html)  
If you can share logs or more specifics, I can propose more concrete fixes or troubleshooting steps!

Let me know if you want guidance on step-by-step debugging, or on making custom inspectors EditorSync-ready.

_1 replies left_ - **[Get a PRO license](https://needle.tools/pricing)** for more AI replies.  
_thread\_pWnXEjPFMoqhEsAuoNm01bAo_  
_**Reply to this post directly if you need further help (bottom right button)**_

---

<div class="post-metadata">

**Author:** ![krizzl0r](https://forum.needle.tools/user_avatar/forum.needle.tools/krizzl0r/32/4262_2.png) [@krizzl0r](https://forum.needle.tools/u/krizzl0r)\
**Post date:** [May 8, 2025, 12:34pm UTC](https://forum.needle.tools/t/editorsync-issues/2522/3 "2025-05-08T12:34:43Z")

</div>

Just remembered another specific issue:

- Enum handling. Enum value changes get sent as strings but should possibly be ints/numbers?

---

<div class="post-metadata">

**Author:** ![krizzl0r](https://forum.needle.tools/user_avatar/forum.needle.tools/krizzl0r/32/4262_2.png) [@krizzl0r](https://forum.needle.tools/u/krizzl0r)\
**Post date:** [October 27, 2025, 8:59am UTC](https://forum.needle.tools/t/editorsync-issues/2522/4 "2025-10-27T08:59:04Z")

</div>

Bumping. Sync needs some love 💔

---

<div class="post-metadata">

**Author:** ![krizzl0r](https://forum.needle.tools/user_avatar/forum.needle.tools/krizzl0r/32/4262_2.png) [@krizzl0r](https://forum.needle.tools/u/krizzl0r)\
**Post date:** [March 4, 2026, 9:54am UTC](https://forum.needle.tools/t/editorsync-issues/2522/5 "2026-03-04T09:54:08Z")

</div>

Still no reply. Shameless bump.

---

<div class="post-metadata">

**Author:** ![Marcel\_Wiessler1](https://forum.needle.tools/user_avatar/forum.needle.tools/marcel_wiessler1/32/21_2.png) [@Marcel\_Wiessler1](https://forum.needle.tools/u/Marcel_Wiessler1)\
**Post date:** [March 4, 2026, 11:05am UTC](https://forum.needle.tools/t/editorsync-issues/2522/6 "2026-03-04T11:05:16Z")

</div>

Hi @krizzl0r sorry for the delay. We will look at it. I will keep you posted here.

---

<div class="post-metadata">

**Author:** ![Marcel\_Wiessler1](https://forum.needle.tools/user_avatar/forum.needle.tools/marcel_wiessler1/32/21_2.png) [@Marcel\_Wiessler1](https://forum.needle.tools/u/Marcel_Wiessler1)\
**Post date:** [March 4, 2026, 1:19pm UTC](https://forum.needle.tools/t/editorsync-issues/2522/7 "2026-03-04T13:19:46Z")

</div>

- Regarding soft restart: Which Editor version were you using if you remember?
- Regarding the cache: When you use EditorSync the changed state is stored and reapplied on reload, yes. You can change the query parameter `editorId` (in your URL) to get a clean state.
- Regarding strings/numbers enums: I just tried it here and they’re sent as numbers

---

<div class="post-metadata">

**Author:** ![krizzl0r](https://forum.needle.tools/user_avatar/forum.needle.tools/krizzl0r/32/4262_2.png) [@krizzl0r](https://forum.needle.tools/u/krizzl0r)\
**Post date:** [March 11, 2026, 10:41am UTC](https://forum.needle.tools/t/editorsync-issues/2522/8 "2026-03-11T10:41:00Z")

</div>

Hi @Marcel_Wiessler1, sorry for my late reply. Looking at the 4.16.0 release notes it looks like you found some things to tackle after all, great! 🙂 Will try and report back when I get the chance to try it out.

---

<div class="post-metadata">

**Author:** ![Marcel\_Wiessler1](https://forum.needle.tools/user_avatar/forum.needle.tools/marcel_wiessler1/32/21_2.png) [@Marcel\_Wiessler1](https://forum.needle.tools/u/Marcel_Wiessler1)\
**Post date:** [March 11, 2026, 11:05am UTC](https://forum.needle.tools/t/editorsync-issues/2522/9 "2026-03-11T11:05:10Z")

</div>

Hi yes please report back 🙂 sorry it took so long, it got burried unfortunately