The "Hollow" BSP ability breaks my geometry

anonymous_user_4976221d · October 16, 2014, 4:20pm

Trying to develop a series of rings, I create cylinders with the “Hollow” geometry setting checked. The below images are the results:

More importantly, any other BSP that intersects these rings get corrupted with faces missing and even after deleting the rings, the BSP remains corrupted. After turning “Hollow” off and rebuilding geometry, my engine crashed.

anonymous_user_4976221d · October 16, 2014, 4:23pm

Another strange bug: After restarting the editor, Unreal asked if I wanted to restore the unsaved level. I hit “Yes” but got an error message that Unreal couldn’t load it. What it did load, was the level minus all the bugs.

Jonathan_Dorman_1 · October 17, 2014, 9:56pm

I’m not seeing this behavior when creating Hollow geometry in 4.4.3 or 4.5. To be clear, these are the steps I’m taking:

Drop two additive cylinders from the BSP menu into the level.
Select both cylinders.
Click the ‘hollow’ checkbox in the Details panel.

Are you doing something different?

anonymous_user_4976221d · October 17, 2014, 11:53pm

It’s not the hollowing, but unhollowing that causes issues.

Add two additive cylinders from BSP menu into the level
Select both cylinders
Click hollow
Build Geometry
Click unhollow
Build Geometry

Jonathan_Dorman_1 · October 21, 2014, 6:16pm

I’m still having no luck reproducing this issue (tried in 4.4.3, 4.5) by following your steps precisely.

What version of the editor are you using?

anonymous_user_4976221d · October 21, 2014, 7:21pm

Version 4.4.3

Jonathan_Dorman_1 · October 21, 2014, 8:01pm

Do you have any other ideas about what might be causing the problem? I’ve tried following your steps in 4.4.3, with Update BSP Automatically on, and then with it off, and neither caused anything out of the ordinary.

anonymous_user_4976221d · October 21, 2014, 8:05pm

I’ve been following the same steps to repeat my issue. Maybe there is a hardware difference where my computer can’t process the geometry?

Jonathan_Dorman_1 · October 21, 2014, 8:17pm

That’s possible. Do you find this same thing happens in a new project?

If you wouldn’t mind, send me your dxdiag, as well.

anonymous_user_4976221d · October 21, 2014, 8:27pm

I can’t get the issue to duplicate consistently in new projects. How do I upload the Unreal dxdiag?

Jonathan_Dorman_1 · October 21, 2014, 8:50pm

The dxdiag is a windows utility, not something related to Unreal. On Windows 7, you can just type ‘dxdiag’ in the Start menu and run it, then Save All Information.

Jonathan_Dorman_1 · November 4, 2014, 6:57pm

Are you still having trouble with this, Liforce?

anonymous_user_4976221d · November 4, 2014, 7:03pm

I can no longer duplicate the issue.

Jonathan_Dorman_1 · November 4, 2014, 7:11pm

Since the issue is not reappearing, I’m marking this question as Resolved. Let me know if the issue reappears and we’ll investigate it further.

Thanks,

Jonathan