Is there actual proof of this being a bad engine or is it just a meme?

Is there actual proof of this being a bad engine or is it just a meme?

I mean, any game can be bad on any engine.

Proof of a good UE4 game: youtube.com/watch?v=ns4ExY4JcSo

Covered in filters an ugly lighting and particle effects, Epic made an engine for people who want to hide free premade assets behind some sprinkles.

Its a good engine but it suffers from the same problem Unity does. There are a ton of shitty developers who just make asset flips.

All games that made with UE4 works like shit on my pc. Even the fuckin Snake Pass.

It's a great engine. The problem is that it has a ton of terrible amateur devs who use it to import god awful assets into with oversaturated lighting plastered over them.

Works fine on my machine :)

>Is there actual proof of this being a bad engine
Literally nobody that matters says this. Developers love it and there are a tonne of games made with it coming it.

The only ones saying this are either retards who fall for the meme ( who doesn't even know what "filters and particle effects" are), or assmad Unity shills that are angry their mobile game engine isn't gonna be used by fucking anyone for desktop or consoles soon.

>blueprints
Get the fuck out

Your PC seems to be the problem then, works fine on mine.

Its a professionally used engine, theres absolutely nothing wrong with it.

If you've got to choose between Unity thats used for meme games like Sanicball, The Fantastic Game or Slenderman or something that has been used professionally for years and is now the main engine for Square Enix as they make Kingdom Hearts 3 and the FF7 remake, what would you choose? What professional developer is making a game in Unity?

So why don't you use C++?

It is a good engine, but suffers from devs not understanding utilization methods. I prefer Unity, mostly because I work with c# quite a bit, so it suits me fine. Most of the problem people have with Unity/Unreal games isn't the engine, but rather the lack of optimization devs don't take time for.

>blueprints

He's a Unitybabby who can only script in C#, user.

DUDE INHERITANCE LMAO

DUDE EVEN THE SIMPLEST LINE IN C++ HAS TO BE 120 CHARACTERS LONG LMAO

DUDE BLUEPRINT INTEGRATION FUCKING EVERYTHING UP LMAO

DUDE FUCK DOCUMENTATION LMAO

You're discouraged from using it and the documentation is trash. Epic wants to force their blueprints-meme hard. Might as well use Rpg Maker if you want to drag and drop shit around like a shitty 3d artist.

almost forgot

DUDE FUCK PERFORMANCE LMAO

DUDE CONSTANT FALSE ERRORS REPORTED BY THE MSVS PLUGIN LMAO

DUDE CASTING LMAO

all these "modern" engines are aids

If you use any premade assets in your UE4 game then you are a bad dev, no way around it.

It's accessible. Thus it gets used to make garbage games like ARK.

>inb4 non-dev neets talking shit about devving stuff

>Engine has a shitload of EZbake options so comprehensive literal retards and kikes have slapped together a game and sold big bucks.
>Sup Forums still isn't making their own games

>You're discouraged from using it
You're just expected to know how to use it and not be some third worlder looking to make an asset flip for early access. I came in as a C++ programmer and it was really fast to get into it, just use VA (or Intellisense if you feel masochistic) for the stuff you can't find (or check the fucking code if you don't know what a function does).

>b-but I don't know C++
Then go learn it, why did you think UE4 was a C++ course?

its a great engine but its too much engine. unfortunately far to much work, time, and energy goes into using the engine than making the game.

>UCLASS(hidecategories=(Object,LOD, Physics, Collision), editinlinenew, meta=(BlueprintSpawnableComponent), ClassGroup=Rendering)
>class CUSTOMMESHCOMPONENT_API UCustomMeshComponent : public UMeshComponent

indeed, what sort of noob wouldn't be able to find that this is the correct way to write this particular device by poking around intellisense?

by the way, ue2 had good C++ documentation that was concise and understandable. of course it was a shit engine with a horrible design but oh well.

why not ue4?

The first one is listed plainly in the docs if you just look for UCLASS, UPROPERTY, etc. The second one is in the docs too, but you can just use the add class to project from Unreal and it will do it for you (and if you know C++ you know it's class : parent class anyway).

Sorry you couldn't make your early access survival asset flip, Pedro.

>not pajeet

when will your niggers stop talking about shit you dont understand

Lets be real an informed person is as rarity.

CUSTOMMESHCOMPONENT_API, just beautiful

there's nothing clear about the blueprint essay that must introduce every uclass

what a piece of shit

Every engine is garbage. If you're making a game using a game engine you're doing it wrong. I mean just look at *insert shitty game* and how it looks and plays like garbage. Now, if they had programmed it in Assembly it would look amazing and have actual good gameplay mechanics.

wtf that strawman really made me a unity and unreal fan

>inferior to much superior Japanese engine folded 9000 times

It's only weabs who hate it.

>What professional developer is making a game in Unity?
Blizzard.

The main reason big devs don't use Unity is that it's more expensive for them than UE4 is though.

The way people like talk about game engines makes it really easy to make retarded parodies of the things that they post.

every ue4 game i've played has ran great and looked nice.