koobas.hobune.stream
Hack and Slash tutorial Stack Overflow problem
Hello, I have followed the Hack and Slash tutorials by BurgZergArcade successfully up to number 30 (Or half way through it at least). At 4:34 on the video, when i try to save the vitals, unity says that I have a StackOverflowException. I am pretty sure from Google searches that this means I have an infinite loop of some kind, but I can't find where it is in my code and I can't find anyone else who has had the same problem. I am quite new to using CSharp in Unity and I was hoping that the tutorials would help me to improve, so it would be a great hep to me if someone could help me out. This is my code for saving the vitals:
for(int cnt = 0; cnt < Enum.GetValues(typeof(VitalName)).Length; cnt++) {
PlayerPrefs.SetInt(((VitalName)cnt).ToString() + " - Base Value", pcClass.GetVital(cnt).BaseValue);
PlayerPrefs.SetInt(((VitalName)cnt).ToString() + " - Exp To Level", pcClass.GetVital(cnt).ExpToLevel);
PlayerPrefs.SetInt(((VitalName)cnt).ToString() + " - Cur Value", pcClass.GetVital(cnt).CurValue);
}
Thanks,
Dan205
This piece of code can't cause a stackoverflow. Maybe your GetVital function is causing it. Are you even sure that this is causing it? Have you tried to comment out this part?
Infinite loops just freeze your application. The most common reason for a stack overflow is an end recursion. In other words a function is calling itself without a reasonable break-condition. This can be directly or indirectly.
// direct:
void Foo()
{
Foo();
}
// indirect:
void Foo()
{
Bar();
}
void Bar()
{
Foo();
}
Each function call will push the return address on the stack and create the local stack frame for the function. When the function exits this is cleaned up, but you never leave the function so the stack grow until you run out of stack memory.
Thank you! You're right. I commented each of the 3 playprefs out and found that the last one was the problem. I then looked at the original script (As you said, the GetVital() function) and found that in actual fact all it was was a capitalisation error. Silly me!
