I know we are all excited about 2018.1, but even though it’s out of beta, it feels as if it is still in Beta form.
I can’t compile for windows when using IL2CPP, but i can when i switch it to back to mono.
I have issues with lightmaps, with unity telling me that i have overlapping UVs for lightmaps and should enable generate lightmap UVs, even though that option is enabled. And i still get artifacts with the lightmaps.
Also when generating the maps, the cpu just stays at 10-20% for hours and seems to go nowhere after making some progress.
I went in the packages manager to download Cinemachine, and the moment it’s imported in the editor i get a bunch of compile errors with the cinemachine scripts. I ended up just deleting it till i actually need it, and hope that there will be a patch out for it.
It means you should increase the pack margin and you probably had that “problem” in 2017 too, it’s just that 2018 now has a way of telling you. It’s a feature 
The lightmaps were fine in 2017 though
And didn’t just halt calculating.
And the thing that tells me to enable, is enabled already.
It just stays like that, unfinished.

@screenname_taken
Can you describe the error that occurs when you build with IL2CPP? We might be able to correct the problem.
That looks like you have visible backfaces and it’s rejecting texels. Try creating new lightmap parameters and setting backface tolerance down to 0.
Or set your materials to double sided global illumination.
@AcidArrow That wall is only single sided with the visible faces looking inside the room. Setting it to 0 made those areas that looked wrong to be all black.
@JoshPeterson It gave 5 errors, that il2cpp.exe did not run properly, but i just heard back from Unity QA, and they said that i may need some stuff for VS installed, so i’m messing with it now to see what i’ll manage.
I didn’t see anywhere though a notice about needing some things installed for il2cpp for windows to work. EDIT: after installing C++ stuff with VS installer, it compiled. Perhaps in the future the editor should have a warning like it has for the JDK and NDK?