I know this thread is a few months old, but for the benefit of the OP if they’re still interested, or anyone else who hits this from a search as I did…
Your description of the “weird perspective” issue sounds to me as if you’re seeing the expected result of deleting a face from a one-sided mesh (and this is not an Unreal-specific behavior). In game engines as well as 3D content creation tools like Blender, Maya, or 3D Studio, most of the polygons in the mesh will be one-sided, because rendering the hidden inside faces would waste GPU resources. If you remove a face from a cube, you’ll see the other faces from either the inside (where they will, by design, be invisible) or from the outside (as before, since the other faces haven’t been changed by you deleting one). Whether you are looking at each face of the cube from inside or outside depends on the orientation of the cube and camera in your viewport.
In level editing (and again, this is not Unreal-specific), this one-sided rendering is extremely helpful if you want to create a level where the player camera is close to their in-game character’s position so they see a ceiling or roof over their head. But you as the designer don’t want to have to be zoomed in that close for editing. If the ceiling or roof meshes are one-sided, they will render to the game camera from the inside but will be invisible to your viewport camera while editing. You’ll edit the level with an almost omniscient top-down visibility, but your players will have an immersive fully-enclosed experience.
This also applies when editing something like a cottage or house if the interior is a separate mesh from the exterior. The walls will typically be rendered only from the inside, so you can place furniture, lights, and props with ease but your players will still see a fully immersive level from the inside. Likewise the exterior mesh will render only from the outside, to save resources at runtime.
I am new to Unreal myself but experienced in other environments, and I’ll add my +1 to the excellent replies from others. My focus is more programming than design, but I’ve learned enough Blender to be proficient (though not expert) and create medium-complexity models. The BSP Brushes in Unreal are a useful prototyping tool, but coming from Blender or Maya or 3DS these feel very confining. Even as a programmer, knowing some 3D modeling has empowered me in several ways:
- If I need a prototype to test my programs, I don’t need to rely on someone else having time to create it.
- If I have a commercially-produced model with a minor problem, such as some flipped or missing triangles, I can fix it myself quickly.
- Knowing a little about another team member’s job helps me appreciate their work more, and helps me communicate better with them on collaborative projects.
3D modeling tools can be daunting if you approach them in an effort to learn the entire tool, but perhaps try thinking of it another way: Learn to use one of the tools (Blender is free for anyone, and the Autodesk tools have academic editions that are free or inexpensive), but set your initial goal modestly: “I will learn ______ tool just enough to do what I could have done in BSP.”
That level of learning will give you everything you could have done in BSP, but now you have taken the first steps down a longer 3D modeling road that won’t dead-end at that first waypoint. If you never need to go further, you still have the needed capability for your projects, but if you do need to go further, you’ve got plenty of room to gradually increase your skill without switching tools.
Learning Blender or the other 3D modeling tools deep enough to create cinematic renders is a major undertaking. Learning these tools deep enough to create a window frame or a traffic cone is, however, quite an approachable task.
Hope this helps!