Don't get me wrong, I'm not just looking at this from an AI-focused perspective. The fact that they are heading in this direction is what's frustrating. On the other hand, I can see that they are completely changing the framework. But do they really have to get rid of visual scripting? And yes, Blueprints might have a text equivalent, but we already know what that looks like. It's highly unlikely they'll work with LLMs. Overall, I'm not against the Verse language, nor am I against them changing the framework, but they seem way too focused on the AI side of things
Yine C++ kısmına girilmiyor ama metin tabanlı olması görsele göre daha zor olacaktır. Fakat biraz Scene Graph incelendiğinde aslında daha büyük bi değişiklik var. Unity vari ECS yapısına geçiyolar. Yüksek ihtimalle motor entegreli AI aboneliği açacaklar falan filan. Visual graph olarak da tool olacağını düşünüyorum verse o kadar karmaşık bi dil değil aslında ama bakalım
@GurlekAlparslan@UnrealEngine Amaç AI ekosistemi ama mevcut framework komple değişiyor işin özünde. Daha çok ECS altyapısına dönüyorlar. Fakat bunu yapmak için illa visual graph kaldırmak zorunda değiller ama onu da AI için zorunlu kılacaklar.
@kiaran_ritchie@MikeGemi1 It’s not that 'everyone can code' now; it’s that everyone can use AI. The real reason Blueprints are being deprecated is to force everyone into an AI-native ecosystem. They need to just admit that.
This isn't just about replacing Blueprints; you're changing the entire framework. You’re going to do the same thing you did with Lumen, where you didn't just make static lighting obsolete—you broke it and stopped supporting it. You are going to force people into this. Developers are being pushed into this new ecosystem