Search
-
Re: which engine to use
C++ will replace Uscript, this is new. Instead of using Uscript as language you use C++. The C++ API is for integrating the Unreal engine with the rest of your game. This API has been there all the time and it's not a new feature. But it is not for scripting. It is mainly for integration. Unless you're a coder with the… -
Re: which engine to use
I agree on the Kismet side, Kismet is just invariably messy and should only be used as level-specific scripting. Somewhere a kitten combusts every time someone makes non-level-specific script using Kismet. -
Re: which engine to use
At what point will Uscript and Kismet not be enough? UI? Networking? Edit: Also, if Kismet is so messy, isn't that something to worry about in UDK4 with them merging Uscript into Kismet? -
Re: which engine to use
If you want to do anything large scale that isn't covered by the existing native code, such as complete procedural generation of geometry. (AFAIK, there's no way at all to create polygon batches from UScript short of using DLLBind to open a separate 3D context, lol!) UI is a doddle in UScript, multiple ways of doing it,… -
Re: which engine to use
yes but udk4 will offer c++ api to replace uscript. -
Re: which engine to use
i didn't say that, i said that would be replacing uscript in referring to Bigjohn's comment i quoted. -
Re: which engine to use
Part of a two-man team developing a game here, and it's been going great. Kismet and UScript are enough for us. -
Re: which engine to use
I don't understand. I thought they're putting all the functionality from Uscript into Kismet, aren't they? So then what's the API for? -
Re: which engine to use
UDK is good for prototyping ideas, but if you plan on keeping everything in UScript and Kismet for a large scale game (which is what many people do) then you're going to have a bad-time without direct access to source code. CE, I have no idea honestly...get in contact with CT I guess? Unity is the way to go honestly, it's…
9 results