| 03-20-2006, 07:02 AM | #1 |
Limitation of WE I'm looking at it.. I'm somewhat led to believe there is a maximum number of Functions calls you can have say when a "Unit begins casting an abillity.." I found problems when you go over 64 of them any new triggers of that type dont work.. Is this my imagination. I'm 100% sure the trigger is right. but the trigger simply doesnt happen? |
| 03-20-2006, 07:09 AM | #2 |
You mean, a limited number of triggers that will run on the same event? I haven't experienced that yet, and I have many triggers like that in my arena... not sure if there's 64 of them, though. In any event, this sort of limitation seems unlikely, it is possible you have some other error in your code. |
| 03-20-2006, 04:18 PM | #4 |
Why would you have 64 of them? Isn't it more efficient to put them into one trigger? |
| 03-21-2006, 08:14 AM | #5 |
Well the triggers were added in over time. Originaly there was only 75 triggers.. so I didnt really care. now I am going over 350 so I need to compress them. There is definately a bug with it.. and now I need to reduce this amount further.. I found that doing multiple units at once causes even more weird bug to happen. for example if you select 10 units and use an abilty. A trigger that detects another abilty being triggered went off.. I was going wtf.... U basically need BTW I think the number is 256. |
| 03-21-2006, 08:22 AM | #6 |
Couldn't you consolidate these by using liberal numbers of branches? |
| 03-26-2006, 02:05 AM | #7 |
256 is a reliable number, if anybody hasent noticed already, computers and code go off instances of 2, (2,4,8,16,32,64,128,256,512) windows 32, 128mb memory, burn speeds etc... What im trying to say it computers normally use these kind of numbers, so 256 sounds good :D |
| 03-30-2006, 05:20 AM | #8 |
There are many limits. There is a thread execution size (time) limit that you have to be wary about. |
