This Jira was created from CrashReports submitted by the public due to the high number of occurrences. Descriptions from users are provided below. Error message: Assertion failed: (Index >= 0) & ( ...
After building geometry with multiple box brushes stacked on top of one another, the selection no longer isolates a single brush but acts like all of the brushes are combined. This issue can be res ...
When editing multiple Blocking Volumes in geometry mode, only one Blocking Volume will properly update it's collision. This seems to just be an update issue. Moving or editing any BSP will cause t ...
This issue was reported by internal UT developers. When selecting the surface of a brush that share flush surfaces with other brushes, all surfaces are selected. This seems to only occur after sel ...
When a new BSP is created, modifications are made to the level's default brush. These changes affect how volumes are placed, with different BSPs causing different behavior in volume placement. ...
When converting a BSP to a Static Mesh, the object receives no collision even after changing the settings in the details panel of the newly created static mesh. ...
When adding a bsp Geometry object into the world the edges flicker. The effect can sometimes be seen better if you change the tessellation of an object that has it. Observed on border edges of a sel ...
Editing bsp within folder in world outliner will unhide bsps within a subfolder Regression (No) issue (does) occur in 4.10.4 ...
BSPs will be built with light/shadow extrapolated even if they are placed in a hidden sub_level of the project at the time of building. Also Tested in 4.10.4, 4.11 Preview 6 and Dev-Editor-CL-28772 ...
BSP brushes cannot be selected through other BSP brushes that are set to hidden through the world outliner. Other assets such as static meshes are unaffected by this or do not cause the same error t ...