For an empty or basic map, “slow” is less fps than my monitor’s Hz(120), and “too slow” is half that. ~90 is an acceptable medium for me, and of course I expect heavy lag with a dense map, but the overall performance/responsiveness of UDK is significantly better.
Cool, thanks. That gets me up to 90-110fps in an empty map with all ppfx off, but UDK is a solid 120fps(capped at 120 :/). I disabled performance monitoring, too.
I’m adamant about not wasting extra time & money with external tools, to model relatively incomplex shapes(BSP) that could be done in-Editor(and are in some other editors).
Yes, it’s definitely a loss in performance, and some loss of BSP functionality, but it’s still under development(I think/hope!). I see UE4 as a huge change/facelift, that wasn’t exactly for the better, although I’ve heard good things about Blueprint and such. Change means you have to get used to/learn the new things, but in case change has also dropped the Editor’s responsiveness I miss from UDK. Even with the Engine Scalability thing set to lowest, it’s not fast enough for me, so yes, UE4 is of no use/interest to me in it’s current form.
[QUOTE=Jason Forrester;101192]
I get your qualms, but I think UE is still UE basically.
Its neither a step forward or backward because BSP brush work is considered obsolete.
Do I agree?
Actually, no. I think BSP brush work is still a good alternative.
But, UE is leaning towards the more accepted use of Static Meshes.
I think static meshes have been the fad since UE2, and still are, of course, but we have lost BSP functionality, and that’s what gets me. Thankfully Epic agrees, and Geometry 2.0 is on the way…or should be.
Great! Thanks!