How many constraints
Emrys
Member Posts: 38
The advise is often given that constraints use lots of processor power and you should use as few as possible.
Is there a target number one should keep in mind?
I know it probably is not possible to give an actual number. But how about a guide line estimate?
Is there a target number one should keep in mind?
I know it probably is not possible to give an actual number. But how about a guide line estimate?
Comments
I have one project where it has about 5 constrains going on at all times and it doesn't seem to be bad but you really do need to get a scene to where you like it, add your constrains and then deploy it to the device. Then look for ways to optimize; such as changing constrains to a Change Attribute using a timer where possible. So if an attribute only needs updated every 'x' number of seconds, use that method rather than a constrain which fires every cycle.
I currently have several actors constrained to one invisible actor that carries most of the behaviors, motion limitations, and collisions. So I was getting a little worried about how many is too many.
Anyways, definitely look to optimize once you get a good representation of your 'level' by getting it on the handheld and play around with it. There is never a better way to see what works and what doesn't. Look at all of your objects that have constrains and look to see if you can't change them up using a different method and definitely look to see if you can limit the constrains to one or two objects and then do periodic references to those objects for updates; either through the use of a timer or a rule (for example, on collision).
Good luck!