Code center > Bugs and fixes

Let's make a stable platform

<< < (10/26) > >>

Greven:

--- Quote ---It's the developer's curse. Only people who can't fix bugs can ever find them
--- End quote ---

It is so funny.... AS I have said before! The seed function! Show us the seed value in the in the main window. Then we can report the seed value only and you Num, can find the bug really quick!

Numsgil:
You aren't the only one. ;)

I'm thinking of implementing some sort of auto-bug reprot that zips the save file of the crash, along with settings, etc. and sends it to my email automatically.

Greven:
Well it seems to awful much work compared to my simple idea! The seed value, will replicate the excact same simulation, and have the same error, believe me, even on different computers.

Testlund:
CRASH:

Run-time error 6: overflow.

CODE:

rob(n).mem(refvelscalar) = Sqr(rob(n).mem(refvelup) ^ 2 + rob(n).mem(refveldx) ^ 2) ' how fast is this robot moving compared to me?

HOVERING INFO:

Hovering over first 'rob' as well as '.mem' displays 'rob(n).mem(refvelscalar) = 30509.

Hovering over all '(n)' variables in the code displays 'n= 176'.

Hovering over '(refvelscalar)' displays 'refvelscalar = 695'.

Hovering over next '(rob' as well as next '.mem' displays 'rob(n).mem(refvelup) = -21948'.

Hovering over '(refvelup)' displays 'refvelup = 699'.

Hovering over next 'rob as well as '.mem' displays 'rob(n)refveldx) = -30578'.

Hovering over '(refveldx)' displays 'refveldx = 697'.

Do I make any sence? Is this what you need?

Numsgil:

--- Quote ---Well it seems to awful much work compared to my simple idea! The seed value, will replicate the excact same simulation, and have the same error, believe me, even on different computers.
--- End quote ---
It's already implemented!

Or didn't you know that?  It's just no one actually reprots it when they tell a bug.

Navigation

[0] Message Index

[#] Next page

[*] Previous page