-
Hi, we created and configured a UnityConvertersConfig instance to not use specific custom converters when deserializing JSONs. This appears to work wonderfully in windowed mode, but when we try to run the same code in a headless editor ("-batchmode"), our converters appear to be added to the global converter list and they get run for every field that we try to deserialize. Is there something we need to do to make the editor load the ScriptableObject while in headless mode? EDIT: I forgot to point out that this behavior is inconsistent cross machines. It works fine on my laptop but is broken (as described above) on our build machine (running Jenkins) |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
Hello @jchowdown! Thanks for reporting this, I've not heard about any use cases for headless editor yet, so I've sadly not considered it yet. During initialization, it tries to load the Unity resource asset by the name The only conclusion I can make is that your Jenkins build may have the Are you also using the Either case, I'll do some manual testing to try and reproduce this. I've opened an issue of this over at applejag/Newtonsoft.Json-for-Unity.Converters#61 |
Beta Was this translation helpful? Give feedback.
-
I was unable to reproduce this issue, sadly. But let's move this discussion over to the issue applejag/Newtonsoft.Json-for-Unity.Converters#61 as this is a new issue that I don't have an answer for (yet), so a GitHub Issue is better suited than a GitHub Discussion. |
Beta Was this translation helpful? Give feedback.
I was unable to reproduce this issue, sadly. But let's move this discussion over to the issue applejag/Newtonsoft.Json-for-Unity.Converters#61 as this is a new issue that I don't have an answer for (yet), so a GitHub Issue is better suited than a GitHub Discussion.