You should probably report this using official bug report form.
When ist Twinmotion import to Unreal coming?
Most likely this is because GPU lightmass uses raytracing and BSP geometry is not supported by raytracing
As far as I know (from old bsp workflow egnines), brushes should be compiled into final geometry before the start of light baking, maybe GPU lightmass perparation skips it, so there is no final bsp geometry to process? Anyway, I reported this bug to the tracker.
Trying to compile in Unreal Engine 4.26 and having a lot of unresolved externals with classes inheriting from UDeveloperSettings, though its module is āEngineā and thatās already in the dependenciesā¦ any idea of which new dependency is required?
Thereās now a separated module called āDeveloperSettingsā 
preview 7
enabled dx12
gpu LIGHTMASS
ray tracing on
on trying to start project I get crash
Fatal error: [File:/Build/++UE4/Sync/Engine/Source/Runtime/Engine/Private/ShaderCompiler/ShaderCompiler.cpp] [Line: 5232] Failed to compile global shader FStationaryLightShadowTracingRGS . Enable ār.ShaderDevelopmentModeā in ConsoleVariables.ini for retries.
UE4Editor_Engine
UE4Editor_Engine
UE4Editor_Engine
UE4Editor_D3D12RHI
UE4Editor
UE4Editor
UE4Editor
UE4Editor
UE4Editor
ntdll
SAME thing here.
I enabled the r. part , and it did get a little further, froim 46 to 57% but still failed same as your error.
āD3D12RHIā is the Unreal devil, itās everywhere crashing to everyone since a few versions ago.
Happens to Fortnite players too, some times it stops for a while but usually comes back when the engine is loading lazy fonts.
Interesting about when Unreal starts to fully support Vulkan ray tracing & all other features?
Can anyone tell me how to enable occlusion using depth in AR kit on iphone 12?
Turning off Render After DOF on a translucent material (Surface ForwardShading) crashes the editor when saving or clicking āapplyā.
In fact, checking or unchecking any of the boxes on the material node and then saving the material crashes the editor.
Update: Itās another tessellation-related bug. See reply below.
I think I have this bug isolated. World space coordinates plugged into a normal map crash the editor if the material has Render after DOF enabled on a translucent material. If I use regular Texture Coordinates it will compile in preview 7. I already submitted a bug report but I can be much more specific about how to reproduce it so maybe Iāll submit a new one.
Update: It compiles if tessellation is turned off on the material. Just another bug related to the broken tessellation.
I just checked the issues page, no one has submitted any bugs related to preview 7ās tessellation problemsā¦ am I the only one thatās having these problems or are people just not submitting bug reports? Does Epic know this is an issue?
Well, how should i put it: ItĀ“s one thing, writing those bug reports, and another, getting them accepted/registered by the devsā¦ (and a third one, getting those reports/bugs actually solved).
The issues tracker seems to be pretty much useless for the public. Go to the original post and scroll down to all the bug fixes, copy one of the tracker IDās and look it up on the issue tracker. Practically all of them are private.
Literally all you can do is just submit it and hope it gets fixed some day.
Gotcha, I had no clue. I had one bug submitted a few years ago but didnāt know thatās how it was.
Been having some trouble with the water plugin and world comp. Does anyone know why this would be happening:
Specifically, Iām referring to the way the water material seems to just stop rendering at around 153K units in both X and Y (so the image above is showing the top right of its maximum bounds). Not sure if itās something with the way I have my world comp/landscape setup (Iāve had this same problem in multiple attempts at creating a world comp setup) or if itās just a limitation of the water plugin?
It still deforms the landscape as expected. Itās just the water material itself that is getting cut-off. In case it makes a difference, this instance of world comp was setup by importing an externally made tiled landscape. Also, Iām up to date with 4.26 via Github (although this has been happening since it first went live).
While Iām sort of on the subject, Iām also having a problem with the water body landscape weightmap setting. In this example I have just a basic landscape material setup with two layers (Color1/green and Color2/red). I can get it to work just fine with a landscape spline, but it doesnāt seem to show up with any of the water bodies (a river in this case). Am I just not understanding what the āLayer Weightmap Settingsā does on a water body? I assume like the landscape spline it just looks for the landscape layer you provide it, but that isnāt happening here.
Iāve yet to see anyone successfully use landmass or the water system with world composition.
I asked about this in the last livestream and was told essentially that they didnāt know if it would work, and that world composition is on its way out and will be replaced by their new world partitioning system in UE5.
Thanks. Unfortunate but makes sense I suppose if itās being phased out. Guess Iāll put it on the back burner for now and maybe keep messing with it a little bit when I have time.