[Bugs] please mod.
Hey guys, we had an official bug thread and everyone seemed to have went crazy thinking every thing that acts funny is a bug without verifying... and that seems to have gotten the thread deleted..
So i thought we can start an un-official one that the sous can help moderate and verify if they have the time to.. but don't post unless you are 100% certain it's a bug that is reproducible in controlled environment.
So i thought we can start an un-official one that the sous can help moderate and verify if they have the time to.. but don't post unless you are 100% certain it's a bug that is reproducible in controlled environment.
Comments
not sure what the problem is, but if you simply make a real type attribute and enter 1111111111, and display text that attribute.. it shows up as 111111016
---------------the following is more of bug i notice consistantly but doesn't have time to verify in controlled environment to single out the issue yet.---------------------------
2nd the copy-paste bug. that seems to happen when heavy copy-paste, is used.
3rd redo-undo, when you redo, the script box moves back to where it was with the value in the box still being the same. (again only happens during certain conditions)
I do this all the time, and I don't have any issues…Do it one rule at a time, and make sure that if there are any custom attributes, you create those before you start copy and pasting, and even then you sometimes have to go through and reset the attribute expression editor to reflect the correct attribute.
If you copy and paste an entire set of rules from an actor, you will have problems, but if you go through a little at a time, it works fine. At least it does for me.
It's been working for me, and I haven't come across the script not running when I do it this way. I do experience the script not running when I try to do it all at once.
And there's always Deep Blue Apps Project Merger, but that's another cost.
We closed the 0.9.6 bug thread because we gathered all the information necessary to get user feedback, spot any new issues, and communicate known issues with the community. As always, your feedback is important to us and helps us shape a better product for the future.
However, the best way to bring bugs to the attention of the GameSalad team is submit them via bugs@gamesalad.com. The more detailed the email- the better. Project information, computer specs, attached project files, etc... will help our team fully investigate these issues. We investigate each reported bug and project sent through that channel.
We will continue to provide general feedback regarding the reported issues on the forums. Again, thank you for your consistent feedback.
Lauren