Kismet UI solution

[WinterT]

I'm just now getting into Kismet, like just started learning up on it today so no real knowledge base. With that said this UI solution looks bloody awesome. I'm curious to know though would this completely wipe out the need for scaleform? I don't know the limits of either system yet so I'm curious. If this is a simpler route and has equivalent abilities I see no reason to even start reviewing scaleform unless its a necessary evil.

[XilenceX]

"For the new Kismet to work, it has to be allowed to do its thing by the gametype. Included in the UnrealScript is a gametype, if you want to use this in your level/game you must set your level/game to use this gametype, or alternatively merge the relevant code into your own gametype."

Could someone please explain how to "alternatively merge the relevant code into your own gametype" ?

Yeah it would be awesome if someone could explain the necessary steps to do that (e.g. which code goes into which file&line...). I would much prefer to use SimpleExtHUD over any other solution but there would have to be a way to make it work in the clean November UDK installation. ^^

[threearabawys]

Can anybody tell me how I can merge this code with my previously created classes?

[threearabawys]

I get this error message when I try to build...

UDK\Development\Src\SimpleExtHUD\Classes\SimpleExt HUDPlayerController.uc(70) : Error, Redefinition of 'event ClientStopCameraAnim' differs from ori
ginal; different number of parameters

Any Ideas?

[XilenceX]

I get this error message when I try to build...
Any Ideas?

Heh that's the easy part... there is some thread about it as well. You just have to delete that block of code about CameraAnim in the .UC files. However the script is full of references that require UT code! So if you are using your own gametype instead of the old UT code you are going to have a bad time. ^^
Deleting the 3 .UC files with UT in their name removes most of the errors. However then there is still the cursor file with lots of UT references but if you delete that one as well the HUD works again... obviously without the mouse courser functionality. ;(

[threearabawys]

Thanks XilenceX
But I just ended up going into that file and commenting out the problem line and it worked fine... for now hopefully it'll keep working and I won't need whichever piece of code I disabled lol

Happy New Year.

[Deewad]

Fantastic, Thanks!

[onij]

To get this HUD system working again with NO ERRORS and without deleting any lines that could innevitably cause more issues:
Delete/Replace or comment out this line, line 70:

Comment out/Delete this:
reliable client event ClientStopCameraAnim(CameraAnim AnimToStop)

REPLACE WITH THIS:
reliable client event ClientStopCameraAnim(CameraAnim AnimToStop, optional bool bImmediate)

Then for me to get this to fully work I had to do a full recompile on my scripts using Unreal Frontend.
Also note that any features that involve the mouse will not work if "Emulate Mobile Features" is turned on above your UDK viewport because the mouse won't work (by this code) in a mobile game.

[Kuda]

Thank you onij!

[nonder]

I use my own framework for these things (menu, hud...) but it is accesible only in codes. I am using it in all my projects but I am planning (and partly developing - I need to finish my primary project now) create new kismet UI framework with things like text boxes, buttons, radio buttons, checkboxes, scenes, cursors, sliders, images, bars, templates, effects and so on (really many things and for skilled people there will be nice interface to make anything what they want because every aspect and value will be accesible inside editor). I am designing it to be absolutly easy so creating things like menu or hud will take only a few minutes. I will make documentation and many video tutorials too. I will give you more info when It will be nearly finished. I want people to say when somebody asks how to make gui that there are three ways: coding(canvas), my framework, scaleform.

[G-Rath]

Hey I have a question - In the code for RenderObject, there are all the outputs for mouse, such as mouse over, left mouse press etc. Now the textboxes and TextMat both extend from RenderObject, but only TextMat has the mouse outputs... is that a bug, or is there a reason behind that? I want to use text boxes (aligned textbox to be exact) for my menu, but right now it would mean I have to create a invisible texture to detect the mouse input...

Is there a way to fix / (re)enable this for the Render align string / textbox nodes?