|
|
Post by TinSoldier on Mar 4, 2023 7:20:31 GMT
My fault,,,, yes.... rads fault for not reporting it YES
Oh man..... wasted more than 4 hours on a 3drad script error.
I was making a PCar output register = to a EventOnInput Object....
instead of it's output register....
I wanna slap myself...
But the thing is, 3drads error system is broken, it's "possible" that 3drad mite give an "input out of range" error, at least i would hope it would.. would have been a few minutes error if it did ............
|
|
|
|
Post by indiedev on Mar 5, 2023 14:03:27 GMT
was a free engine from that era obliged to do so? it's well known that EOI gives 0 to 1 range [edit: -1 to 1 for joysticks but it converts 0/-1 to 0/1] , so any conversion to anything else is the user's responsibility. to find the range you need to convert to you can link said output to a text object using default keyboard controls, if was not listed in help files as many are.
whenever something does not work i always link various stuff to text object for debugging to see what is going on, that's the closest you'll get to a 3drad 'error system' apart from basic script syntax errors.
|
|
|
|
Post by TinSoldier on Mar 7, 2023 2:04:08 GMT
3drad was given for free to owners of the original 3drad v 5.*, it was my understanding it was a paid program to new people.. not literally free, it became free near the end of fernandos support.
That said.... i really wish more errors were fixed before he left, like the error system... because it never worked fully, who knows what errors it would/could have reported.
|
|
