N64 Glide Plugin

thanks, maybe i will in the next release.

is there anyway dave could fix a certain problem with his plug-in? it has to do with lighting and how accurate it is (e.g marios big face in the beginning)

I noticed that too. Mario has a hint of red on his face, this does not happen in Jabo's plugin(or UltraHLE).

I'm not an expert on lighting math, so I'm having a little trouble figuring out what's wrong with my lighting calculations. Can someone download the sources and check the lighting code in 3dmath.cpp calclights() to see if it's correct? light_vector[l] is the direction towards the light, and v->vec is the normal. I think that the problem is that I need a min() or max() somewhere, but I'm not sure where. (see starfox intro to find real problem, something goes negative and it dies as you move the 64 to the left of the characters)

Dave we have a problem:
when you use the plugin, the plugin searches for the INI and if it can't find it, it creates a new one. the problem is that the INI must be the same name as the DLL and if someone want's to change Glide64.dll to something else the INI will not work anymore.

i'm sorry for posting these things here but due to time differences it's really hard for me to talk to you on IRC.


anyway, when using RSP: interpreter on some games Glide64 gives this error (but keeps working well) :

well, that's not Glide64 giving that error, Project64 may be doing it because of an invalid memory access in Glide64 though.

Also, RSP interpreter when I''ve tried it also had problems, make sure that the problem you're giving me does not occur with all plugins.

Anyway, about the Glide64.ini name, I meant for it to be like that. Would you rather me _REQUIRE_ that the name be Glide64.ini, because I can do that too. I did it so that you might be able to have different settings for different games. (of course I will still need to add an INI title to the plugin string for that)

Regarding the ini:

I'd keep it the same, because usually people wont need to rename the dll anyway, and having the ability to have different settings could be usefull... Maybe an option in the plugin itself to name the ini or select a different may be of use, i dunno

Originally posted by Ogy
i'm sorry for posting these things here but due to time differences it's really hard for me to talk to you on IRC.


anyway, when using RSP: interpreter on some games Glide64 gives this error (but keeps working well) :

and because i'm a total idiot with no real input....

that color scheme is horrible!


krhydaddy

Originally posted by Dave2001
I'm not an expert on lighting math, so I'm having a little trouble figuring out what's wrong with my lighting calculations. Can someone download the sources and check the lighting code in 3dmath.cpp calclights() to see if it's correct? light_vector[l] is the direction towards the light, and v->vec is the normal. I think that the problem is that I need a min() or max() somewhere, but I'm not sure where. (see starfox intro to find real problem, something goes negative and it dies as you move the 64 to the left of the characters)

I think I found the mistake.

in rsp_uc00_movemem change:

rdp.light[i].dir_x = (float)(((BYTE*)gfx.RDRAM)[(a+8)^3]) / 255.0f;
rdp.light[i].dir_y = (float)(((BYTE*)gfx.RDRAM)[(a+9)^3]) / 255.0f;
rdp.light[i].dir_z = (float)(((BYTE*)gfx.RDRAM)[(a+10)^3]) / 255.0f;

to:

rdp.light[i].dir_x = (float)(((signed BYTE*)gfx.RDRAM)[(a+8)^3]) / 127.0f;
rdp.light[i].dir_y = (float)(((signed BYTE*)gfx.RDRAM)[(a+9)^3]) / 127.0f;
rdp.light[i].dir_z = (float)(((signed BYTE*)gfx.RDRAM)[(a+10)^3]) / 127.0f;

the light directions are signed byte values ranging from -127 to 127. This is the same mistake I made when I started doing the lighting.

Cya L8r,
Icepir8

Originally posted by Dave2001
well, that's not Glide64 giving that error, Project64 may be doing it because of an invalid memory access in Glide64 though.

Also, RSP interpreter when I''ve tried it also had problems, make sure that the problem you're giving me does not occur with all plugins.

Anyway, about the Glide64.ini name, I meant for it to be like that. Would you rather me _REQUIRE_ that the name be Glide64.ini, because I can do that too. I did it so that you might be able to have different settings for different games. (of course I will still need to add an INI title to the plugin string for that)

firstly, about the error: i'm sorry it was my mistake... it is caused by PJ64.
secondly, about the name:i believe people will change the name as a result of wanting (like me)to have 2 or more versions of Glide64, but i didn't understand your meaning "have different settings for different games" could you or someone please elaborate.

that color scheme is horrible!

what? it's the default color scheme for win98!

Ah, beautiful! Thanks Icepir8! Such a simple error... I remember having an error like this somewhere else too earlier on.

Like my layered fog? I CANNOT get it to interpolate right!!! I've tried EVERYTHING. I was considering switching to fog coords instead of a fog table, but I can't get anything to show up when I add the fogcoord parameter. Any ideas why the fog might layer like this instead of interpolating?

(yes, I know the colors are wrong, and it's the wrong distance, these were all test values)

... and after a gazillion years of working on it, the flames FINALLY work.

wo great job man