millenliam

I'm currently trying to optimise a rather big patch of mine, and I've read in many places that removing all unneeded UI objects is a must.

However is a [message] object classes as a UI object?

message-object-is-it-classed-as-a-ui-object

I would remove everything that blinks, writes or draws and isn't needed. for me the most obvious culprits are: bang/button, toggle, number boxes and message objects. The message object is to display data or for user choices. So if your message box is constantly updating its text, there is probably a better way of doing it...

right - as soon as the message which is displayed changes, the problem given applies.

in most situations list/pack/pak can replace it.

Using either [zl reg] or [trigger] instead can pretty much eliminate most of the instances of [message] in your patch I would imagine.

[int], [float], [trigger], [prepend] and [pak] are my go to objects for optimizing/reducing ui objects.

ya exactly changed as an UI object..
==================non voice projects


[message] object - is it classed as a UI object?