Bumping this. Testing in 5.4.4 in the VR template and created a new level. Having the crashing happen when I drag the water into the scene unless I turn off ‘Instance Stereo’ (for VR) and ‘Forwards Shading’ in the project settings.
I did see in another forum that someone was using r.water.waterinfo.rendermethod 2 to prevent the crashing but would prevent the water from rendering at all in editor or would make the water go all spikey when switching to another rendermethod (0 or 1) after the waters been placed.
I could get things working seemingly fine as soon as those as those two settings off but having instance stereo off is a bit of an issue for me as I may need it on for other reasons in the near future.
Has anyone done a bug report for this one? It is probably an engine bug that should be put forward to them if not already.
Just tested the VR template in 5.4.4 yesterday and can replicate the issue instantly. I’m current on Windows 10. My Laptop is Intel i7 11th gen, RTX 3080, 32GB RAM. Can recreate the crash in another project also which is where we initially found the issue.
Hey there @Kaputtea7475! Welcome back to the community! Thanks for the update, I can verify the issue is still occurring. It seems to be related to the way the water shader is rendered that is failing to be reproduced between the two viewports.
It doesn’t crash if I run the editor as DX11, but the water also won’t render under DX11. And if I save the level and reload the editor in DX12 mode, it will crash on load.