Share your excitement for Unreal Engine 5 with free wallpapers, GIFs, and more!

[Legend286]

@AntiGravity

Lets see what happens 18 months to 2 years from now. But the answer is more likely to be positive than negative imo… After all, this isn’t 2014 and UDK-Kismet vs UE4-Blueprints etc.

1. Magic-Nodes-Scripting may be available. If so we may get a text form of BP.

2. We know Epic were already working on a text form of BP anyway for both file saves and file auditing / differencing.

3. We know Epic plans to add scripting. Will there be a BP to Script converter? You can bet on it…

So there’s three options right there. Plus Epic have already said to keep working in UE4 and migrate over. What’s the point just migrating the art assets, when they’re the aspect that most devs will likely want to upscale to take advantage of the new rendering system.

Also Epic would risk alienating the very audience they want to keep - the enterprise crowd. Was it c++ that won them over? Hardly! It will be the C++ crowd that will have the most work facing them. But its also likely Epic are factoring this all in now. Hence changes like this or this ahead of time.

Overall, breaking Blueprints is a definite no no… Think about it, they’re the easiest to keep intact anyway versus C++. Anyone whose been upgrading the same projects since early 4.x has already seen just how resilient Blueprints are…

[USER=“434”][/USER] Any thoughts?

Hopefully we get c# scripting along with Blueprints and C++