vapid steppe
@mossy beacon I'm assuming this is for you, but 1.3.9 had this fix mentioned
compile error when having mismatched using statements in one partial system that's different than another
However either I'm misunderstanding what this fix was for or unfortunately this doesn't seem to have fixed it the problem, as it still happens when you have a partial systems split over multiple files
if i remove the unused usings it breaks as above
just been working around it by disabling the suggestions
mossy beacon
I think there was a problem landing the dll changes, if you remember how to update the sourcegen DLLs you can try regenerating them and seeing if it works, otherwise it might have to wait until next update 😅
vapid steppe
let me give it a test
after rebuilding i get less errors but there are still some remaining
mossy beacon
Huh, how does the generated files look?
vapid steppe
like it's missing stuff
first one missing unsafe
second one missing using BovineLabs.Core.Jobs;
vapid steppe
Side note
using Unity.Entities;
using Unity.Jobs;
#if BL_CORE_EXTENSIONS
using BovineLabs.Core.Groups;
#else
using Unity.Scenes;
#endif
#if BL_CORE_EXTENSIONS
[WorldSystemFilter(Worlds.ServerLocal)]
[UpdateInGroup(typeof(AfterSceneSystemGroup))]
#else
[WorldSystemFilter(WorldSystemFilterFlags.ServerSimulation | WorldSystemFilterFlags.LocalSimulation)]
[UpdateInGroup(typeof(InitializationSystemGroup))]
[UpdateAfter(typeof(SceneSystemGroup))]
#endif
public unsafe partial struct SaveSystem : ISystem```
conditional usings break source gen
```cs
using Unity.Jobs;
#if BL_CORE_EXTENSIONS
using BovineLabs.Core.Groups;partial struct SaveSystem {
[global::System.Runtime.CompilerServices.CompilerGenerated]
partial struct GetAllOpenSubScenesJob : global::Unity.Entities.IJobChunk```Mind giving a repro case for the unsafe/partial stuff? -> haven't been able to repro locally 😄