Illegal Property Modifitcation: VK_WaterBody_Ocean

My team members had this problem before on our V1 project until we had to start all over again because the file was broken with non-stop errors. So this is our version 2 of the project.

After syncing the project from the last session from a team member of ours, I noticed our water body is broken. No water collision. Not even functioning properly and is causing illegal property modification error.

The image with the clearer ocean is what it looked like before the update for the beginning of Chapter 5 happened and the other is what it looks like now. I feel there is something I’m missing or doing wrong.
It needs to be the clear ocean when the other one has been causing errors before.

Can someone please explain how I can fix this easily without replacing anything?



Thank you for your report! Can you please re-post using the “New Issue” option on the Issues and Bug Reporting forums? Posts with this feature are connected directly into our development team so we can quickly get to them!
For more information, such as how to get the reference ID, please check out the article here: Using the Creative and UEFN Bug Reporting Form

The Illegal property modification can usually be ignored, it always pops up after any change but shouldn’t reappear until ocean is modified again.

The Waterzone defines the area of close up ocean action for the player and should be larger than your playable area, where is yours at.
There are also Collisions Extent settings in the Ocean component, check they are as big as the waterzone.

The clearer ocean bit is usually for distance fx, but I see your clear ocean has foamy edges at the sand so it must be within the waterzone and has tiny waves,
Maybe your Wave settings have reset to default ??

I tried deleting it and replacing it with ‘Ocean’ and it keeps having the same issues even though we didn’t touch the ocean settings. Are you on Discord? It would be easier for me to message on there than here since it doesn’t ping if there’s a notification.

I very much doubt it is a bug in UEFN and it’s impossible for me to look for an error code. Simply sharing image/video proof with an explanation would have been helpful for me to send on the report.