GameLoft game engine

Lamenting the loss of beast?

 

Now you're undoing expensive therapy for some readers, I'm sure

 

You misunderstood. I didn't want to say what Natural Motion did can only be done with source access I was just saying that we see more studios using modified engine that's all

 

At moment no one from Natural Motion stated that they've migrate to unity 5 don't exaggerate things dude. a
At least at Unite 16 Liam Murphy stated they were trying to port the game to unity 5 and I've downloaded the apk just for testing purpose and I can easily see they continue using unity 4.x

 

You don't need someone to outright state something to make the suggestion that they'll be able to achieve far more with the next major release of a game engine. It's just common sense that having access to better tools would naturally lead to better results.

If someone makes the statement that they're trying to port the game I would naturally make the assumption that it has yet to be made available to the public. Naturally the older releases that were originally made for 4.x will still be on 4.x.

 

What the hell are you on about? I half-jokingly commented that these guys can do wonders with a really old Unity version. Exaggeration is funnier than getting pissed at random forum members.

 

You said:

I am simply asking for evidence of Natural Motion using a modified Unity 4. The GDC paper I linked does not talk about a modified Unity 4. Are you talking about a different one?

I am assuming that by "modified Unity 4" you mean a version of Unity 4 with a modified source.

Creating your own shaders and adding a bunch of editor scripts != modified Unity 4 in my book.

 

That's probably not likely. As unity provides more acess to things like scriptable render pipeline, the need for source becomes less important. Also, having access to the source is very, very expensive, and a huge effort to maintain.

 

In anyone's book.

 

Alas, I've seen/heard a heck of a lot of people talking about stuff like "making an engine based on Unity" when what they really mean, possibly without realising it, is "writing scripts for Unity just as it's intended to be used".

In my book, if you're making a non-trivial project and you're not making, extending or modifying tools to suit your project specifics then you're missing out on important efficiencies.

 

Honestly, get with the times. Everyone knows that not doing an asset flip means hardcore engine based on Unity.

 

We are getting closer for sure. I believe it has brought developers closer together - which is beneficial for all of us - and the industry as a whole.

 

You're right, I should have qualified it. 'In anyone who actually has a clue's book.'

 

Lol i'm not getting pissed at anyone here we are discussing

 

You can clearly read in the PDF "CSR was built in a variant of Unity 4" maybe I misunderstood what they're trying to say by that...I'm sorry, my bad

 

Ex-Gameloft employee said: "There are rare instances when third party game engines are used, such as in preproduction phase, when a basic prototype is needed to be presented to HQ. If the prototype passes, the game gets to be developed with the internal engine." Source

Asphalt 9: Legends uses Jet Engine which apparently uses SFML for graphics and Bullet for physics.

 

That cool to hear from ex-employee. But SFML is still experimental on Android and iOS it's still not officially supported

 

idk, i scrolled thru asphalt streetstorm racing credits and saw it mentioned sfml

 

For Asphalt 9, they are using custom-built Jet Engine.

 

Asphalt 9: Legends uses Bullet Engine and Jet Engine for physics.

 

When Bioware switched over from using Unreal to using Frostbyte, it was a massive shift for the company, and caused a huge disruption of their development process. And that decision wasn't made internally, it was a mandate handed down by the publisher that they had recently been acquired by. In the end, it did a huge amount of damage and caused an enormous amount of extra work.

Switching technology stacks, especially mid-project, is a massive undertaking for any developer. The bigger the developer, the more time and cost it will take to switch gears. Switching engines is a massive decision, and needs to be considered very carefully. No one makes such a decision lightly, or at least no one should.

Personally, I'm more interested in expanding or altering existing engines than I am in switching them. An engine you are already experienced at using is usually much easier than one that you have to learn fresh. You can throw around all the features you want, but an established pipeline usually trumps shiny new playthings.