And here it is, sir:
Have both new and old UI systems implemented?
Remove the old UI system and keep the new one only?
Thanks for your efforts. I bet everyone will be looking forward to seeing the rest of the series.
Gameplay Programmer / Technical Artist
Projects: Medieval Zombie Demo - zBioBlow - 2013: Infected Wars
UDK Version: Feb-2013
OS: Windows 7 Ultimate 64-bit - Service Pack 1
Intel Core i7 960 3.2 GHz 8MB L3 Cache LGA 1366 130W Quad Core CPU
12 GB DDR3 Mushkin PC3-12800 998959 (6 x 2048MB) 6-9-7-24 1.65V Blackline
ASUS Sabertooth X58 LGA 1366 Intel X58 SATA 6Gb/s USB 3.0 ATX Intel Motherboard
EVGA GTX 580 1.5 GB GDDR5 - Driver Version: 296.10
I said it from my own experience. Yes it can be done in that way, but it;s very time consuming, inefficient and just break all possible rules for good make application.
Maybe it's hard work, but it just proves one thing: I'm ready to put the time in what I want in order for it to work.
I think it's cool YOU can program, well I can't so I search solutions in order to get what I want and UIScene combined with Kismet just did that for me.
I'm not searching for an easy solution, I just want something that works for me, which is why I was happy with UIScene. I could make things work without having to code a single line.
wait, what's the advantage to removing features
I think we can both agree that what matters more is HOW you code rather than what language or system you use, spagetti complex can happen either way.
The only truth I recognize from what you say is that it maybe less efficient (slower) than direct coding but then so are any script languages when compared to compiler languages and compiler languages when compared to machine languages so in most cases unless you are building a massive undertaking (The kind that can give the CPU a hard time breathing) I would think that is negliable.
I would leave in UIscene as long as it doesn't conflict with anything but I do like Scaleform and Actionscript because its much more powerful.
Last edited by ORi; 05-31-2010 at 05:06 AM.
gegebel, I think you are confusing Kismet and UIScene. Kismet is one thing, UIScene is something else.
I think he meant he made his UIscenes do stuff (or appear) using kismet.
Also you can't just reuse code like in OOP. Yotinu have to duplicated your solutionm over and over it's not opitnal for high dependable solutions (like games ;p).
Of course. But kismet is not generating any visible code for user. You can make some complex operations withing it but you can't reuse them later in other project. Because they are connected stricctly to map. As I said hard to update and maintainm what if will find bug ? Or want a new feature or some old feaure are removed and have been using them ?I think we can both agree that what matters more is HOW you code rather than what language or system you use, spagetti complex can happen either way.
Then you dont see any truth, because I said nothing about perfomance. I talk about project maintaing. Which is much harder with tools like kismet and flow graph. These tools were made for simple map scripting not for game making.The only truth I recognize from what you say is that it maybe less efficient (slower) than direct coding but then so are any script languages when compared to compiler languages and compiler languages when compared to machine languages so in most cases unless you are building a massive undertaking (The kind that can give the CPU a hard time breathing) I
m because I didn't would think that is negliable.
Also I didn't test this but I find it unlikely that they wont allow to transfer kismet networks from one project to the other or save custom made node groups for later use and if it is the case im pretty sure that lack of functionality can be easily amended in later releases of UDK...
also you might want to read your post after you post them because you invented a few new words which im not familiar with.
Last edited by ORi; 05-31-2010 at 01:22 PM.
Can't you make archetypes from Kismet and reuse it that way? Or simply cut and paste.. or have a master map that streams in your levels, and contain the kismet in the master map.. you can also export kismet to code iirc, so... plenty of ways to reuse it.
Am new to UDK and unrealscripting, am trying to create UI scenes but wht i know is it has removed from udk. so how can i create ui scenes without Flash and Scale form am using unreal scripting, and canvas. By using canvas i hav created health bars and images but i dont hav idea about how to create menus and buttons.
pls anyone can help me....
Thanks in advance..
A two year old thread might not be the best place to look.
Want to collaborate? Want to chat UDK? Message me on Skype, Craig Delancy. Check out my UDK Youtube channel: http://www.youtube.com/user/xblBlack...ew=0&flow=grid