forums.ps2dev.org

[Ghoti]

Hi folks,

I have this error in psplink:

[hlide]

please output the assembly code at this point.

by the way could you try to avoid "double" ? using it will compute in a software mode (double are emulated through integer computation), which is probably not what you want.

[Ghoti]

Hi, well I did not cast anything before this, hoped it was the problem. If i don't use the casts it still works fine for theother values.
the sqrt command needs doubles so is there a better way to avoid the software mode ? (if i don't cast will that do the trick , like i did before trying to cast?)

I can't output the assembly code at this point because I never got the debugger to work.

any ideas ?
_________________
My PSP games:

Boxy II: http://www.ghoti.nl/boxyii.php
Elementals: http://www.ghoti.nl/Elementals.php

[hlide]

void Vector3D::Normalize(ScePspFVector3& vec1){
float lenght = (float)sqrt((double)(vec1.x * vec1.x + vec1.y * vec1.y + vec1.z * vec1.z));
vec1.x /= lenght;
vec1.y /= lenght;
vec1.z /= lenght;
};

[Ghoti]

k well I'm not into asm at all so i replaced my function for yours(I thought I should do that i guess)

and I get also errors with the FPU only now in compiler time:
/cygdrive/c/DOCUME~1/Reinier/LOCALS~1/Temp/ccERFXrw.s: Assembler messages:
/cygdrive/c/DOCUME~1/Reinier/LOCALS~1/Temp/ccERFXrw.s:328: Error: Improper VFPU register prefix 's'
/cygdrive/c/DOCUME~1/Reinier/LOCALS~1/Temp/ccERFXrw.s:328: Error: Improper VFPU register number (003)
/cygdrive/c/DOCUME~1/Reinier/LOCALS~1/Temp/ccERFXrw.s:328: Error: illegal operands `vmul.t'

maybe I should not have done that but I could not find a difference with the other code. hope this helps a bit :s
_________________
My PSP games:

Boxy II: http://www.ghoti.nl/boxyii.php
Elementals: http://www.ghoti.nl/Elementals.php

[hlide]

fsqrt ?

[hlide]

[hlide]

[hlide]

[Ghoti]

i have a lot to learn still :s

what include file do i need for the fsqrt ? can't find it and also through google not.
Will that fix the crash also ?
_________________
My PSP games:

Boxy II: http://www.ghoti.nl/boxyii.php
Elementals: http://www.ghoti.nl/Elementals.php

[crazyc]

[hlide]

math.h ?

well the float version of math functions must be preceded with f

so sqrt(double) -> fsqrt(float)

http://nixdoc.net/man-pages/IRIX/man3/sqrt.3.html

if not defined :

[Ghoti]

k it crashes at the first calculation:
float x2 = vec1.x * vec1.x;
doesn't make sense :s

and it does that with those values, because the first time i use it it works without a crash
_________________
My PSP games:

Boxy II: http://www.ghoti.nl/boxyii.php
Elementals: http://www.ghoti.nl/Elementals.php

[Jim]

C99 says it's a suffix, not a prefix.

[hlide]

[Ghoti]

Hi well, I have a toolclass for this with a lot of functions, writing to file, displaying debug info etc. but one function is to loop the debug info, so when you reach that function it goes into a loop, or well it should go into a loop. I have create the loop in front of thevariables and after the variables and before it does its work perfectly fine but right after the first line of code it crashes :(

EDIT:
if I do this:
sprintf(s, "x= %f y= %f z= %f", vec1.x, vec1.y, vec1.z);
it shows that but as soon as I change it into vec1.x*vec1.x in stead of just vec1.x then it crashes :s
vec1.x = 0.00000f , so since when can't i multiply somthing by zero, i though that you cannot divide by zero but multiply also ?
_________________
My PSP games:

Boxy II: http://www.ghoti.nl/boxyii.php
Elementals: http://www.ghoti.nl/Elementals.php

[Jim]

Of course you can multiply by zero, but is it really 0, or just 0 to 5 decimal places? Can you try using %g instead of %f?

If this "Status - 0x20008613" is your FPSCR, then that is showing a divide by zero exception.
<edit>I'm pretty sure it is, can you post the code with the "don't divide by zero" check in it that you are using?

Jim
_________________
http://www.dbfinteractive.com

[TyRaNiD]

Status is actually the MIPS SR reg, you should be able to dump the actual FPU status reg with the 'exprfpu' command. Of course the character codes after the FPU exception actually indicate what has happend. In this case they are I which is inexact operation, U which is underflow and V which is invalid operation. Basically you have a normalisation issue with one of your floats being too small and the fpu blows up :) Best way around this is normally to just disable fpu exceptions.

[Jim]

Aha! Thanks, I should have spotted that :)

Jim
_________________
http://www.dbfinteractive.com