←back to thread

Speeding up Unreal Editor launch by not spawning unused tooltips

(larstofus.com)
205 points samspenc | 2 comments | 03 Sep 25 01:28 UTC | HN request time: 0s | source
Show context
bob1029 ◴[06 Sep 25 08:45 UTC] No.45147656[source]▶
From a purely technical perspective, UE is an absolute monster. It's not even remotely in the same league as Unity, Godot, etc. when it comes to iteration difficulty and tooling.

I struggle with UE over others for any project that doesn't demand an HDRP equivalent and nanometric mesh resolution. Unity isn't exactly a walk in the park either but the iteration speed tends to be much higher if you aren't a AAA wizard with an entire army at your disposal. I've never once had a UE project on my machine that made me feel I was on a happy path.

Godot and Unity are like cheating by comparison. ~Instant play mode and trivial debugging experience makes a huge difference for solo and small teams. Any experienced .NET developer can become productive on a Unity project in <1 day with reasonable mentorship. The best strategy I had for UE was to just use blueprints, but this is really bad at source control and code review time.

replies(9): >>45148077 #>>45148138 #>>45148160 #>>45148564 #>>45149063 #>>45149666 #>>45150591 #>>45151827 #>>45154587 #
Agentlien ◴[06 Sep 25 18:44 UTC] No.45151827[source]▶
I have worked full time for five years with a combination of Unreal and Unity. I've also worked for five years with Frostbite and another five in various custom engines.

I absolutely love both Unreal and Unity. Unreal is amazing from a technical perspective and having worked with a talented team in Unreal the stuff we were able to make were mind-blowing given the resources we had.

Unity is way easier to work with if you aren't focused on high fidelity graphics. In fact, I've never tried any engine that felt as easy to work with as Unity. I would absolutely not call it a monster. Even with a fairly green team you can hit the ground running and get really productive with Unity.

replies(1): >>45152101 #
1. moron4hire ◴[06 Sep 25 19:19 UTC] No.45152101[source]▶
The problem with Unity for green developers is that a lot of the defaults are bad and there isn't a lot of guidance to fixing it unless you just Git Gud at Unity, which is not something I've observed a lot of green developers do. There's a reason why "Unity Asset Store Dump" is a meme and it's largely because of content farm companies churning projects off the backs of perpetually underpaid junior developers (with no seniors around to mentor them). I saw too many of my friends in the local VR scene 10 years ago see absolutely zero economic progress and very little technical progress because of it.

So yeah, Unity is an easy on-ramp. But unfortunately, I think it puts people in a bad market that doesn't serve them well.

replies(1): >>45152297 #
2. Agentlien ◴[06 Sep 25 19:44 UTC] No.45152297[source]▶
I do agree that some of the defaults are quite bad. A great example of this is how even Unity themselves recommend an object workflow very different from what their engine naturally seems to suggest: You really shouldn't use tons of objects with update methods called directly by the engine. You need managers with update functions which iterate over all their subjects. Doing it the intuitive way easily becomes unsustainable and is horrendous for performance.