I have noticed that local variables I have been placing on triggers have been disappearing in the toolset. I will place the variables on the trigger, then when I go back later and look, the variables are gone. Some of them are still there, but some are gone.
One possible bug:
I have made about 5 trigger blueprints and they all have the same tag (different ResRef, though). Could this be the cause? Has anyone else encountered this. This is very frustrating since I have a lot of variables on a lot of triggers and I don't know the extent of this problem.
Local variables disappearing from triggers in toolset
Débuté par
M. Rieder
, févr. 19 2011 04:10
#1
Posté 19 février 2011 - 04:10
#2
Posté 19 février 2011 - 04:19
I found one possible cause. I had forgotten to change the script that the trigger was calling to the new script that called for the extra variables. I guess the toolset must have deleted the ones that weren't needed by the old script. That would explain why some remained and some were removed.
Has anyone else ever had this happen?
Has anyone else ever had this happen?
#3
Posté 19 février 2011 - 04:22
I also went back and made sure all the tags, ResRefs and the other thing that i always forget were unique.
#4
Posté 19 février 2011 - 04:26
Well, it looks like the variables are sticking this time.
If anyone else has this problem, my advice would be to make sure the right scripts are being called by the triggers and make sure the tags, ResRef and ResouceName are different.
If anyone else has this problem, my advice would be to make sure the right scripts are being called by the triggers and make sure the tags, ResRef and ResouceName are different.
#5
Posté 20 février 2011 - 02:46
Its doing it again. I looked more closely and it seems that the only variables that get dropped are ones that have a value of zero or nothing. This is okay, sort of, because it doesn't hurt gameplay but all my trigger blueprints are borked and I have to manually enter in all the variables. Very inconvenient and time consuming.
Maybe if someone has time, you could try making a custom trigger blueprint, putting some variables on it, saving it then shutting down the toolset and re-opening to see if it happens to you too?
Thanks for any help.
Maybe if someone has time, you could try making a custom trigger blueprint, putting some variables on it, saving it then shutting down the toolset and re-opening to see if it happens to you too?
Thanks for any help.
Modifié par M. Rieder, 20 février 2011 - 02:47 .
#6
Posté 20 février 2011 - 03:30
Results of the Trigger Challenge
I opened my hobby-mod (a simple affair) and created a module trigger from scratch. Assigned "var1" as an Integer with value=0. Close toolset, Open: var1 w/ 0 still there.
Created campaign trigger from scratch, assigned "var2" as an Integer with value=0. Same result. still there ..
Placed down module trigger "var1" and campaign trigger "var2", both with value=0. Closed toolset, re-Open, both there with the empty variables on each Blueprint, likewise on the placed triggers.
sry. :|
I opened my hobby-mod (a simple affair) and created a module trigger from scratch. Assigned "var1" as an Integer with value=0. Close toolset, Open: var1 w/ 0 still there.
Created campaign trigger from scratch, assigned "var2" as an Integer with value=0. Same result. still there ..
Placed down module trigger "var1" and campaign trigger "var2", both with value=0. Closed toolset, re-Open, both there with the empty variables on each Blueprint, likewise on the placed triggers.
sry. :|
#7
Posté 20 février 2011 - 04:42
Thanks for the help. At least it isn't a bug with the whole system, so I should be able to fix it. So that's good news.





Retour en haut






