devkitPro

Hi, Well i think you're on the wrong way.. Devkits architecture slightly differs from retail versions, moreover homebrew SDK is *not* supporting hw dev units *only* retail units. I don't know precisely the tidbits but outdated/unsupported official tools from N. were generating incompatible elf ...

well, as far as the media engine can execute mips code in //, has got its own 2-4Mb ram and of course a full bag of limitations in its use.. Can't we consider it as a second cpu ? http://lukasz.dk/mirror/forums.ps2dev.org/viewtopic0be6.html?t=2652&postdays=0&postorder=asc&start=0 You have already ...

Ok, i haven't got any psp around to open it myself but from wikipedia -> http://en.wikipedia.org/wiki/PlayStation_Portable#Hardware_2 (notice: two 333 MHz MIPS32 R4000-based CPUs ) The Main CPU is allegrex while second CPU is supposed to be called the Media engine/block. So i was wandering, if there ...

Hello,

What is the recommended method to make a proper use of both 333Mhz Cpus? if it is possible..

Ok,

Finally i found the problem which was somewhere else into my code (as usual ? ^^)
So it works as expected and i'm really glad now
8 hw lights are far enough when you can make many combinations of them.

Hello :) Ofcourse it's possible to set the lights new for each mesh you render in a scene Ok then, just to avoid the confusion from my first post. i understand the hw limit of the 8 lights and yes , i'd like to reuse/redefine multiple settings (as GXLightObj settings) over these 8 hw lights (that's ...

Hello,

certainly a silly question but..

Any chance to get rid of 'the really' only 8 lights settings?
it would be really nice if we could reset lightObjects parameters and encapsulate more than 8 settings.
(well, more or less the way it works with opengl)

Hi,

do we need to explicitly call CAST_Init(); during initialisation ?

thx

Hello, Tested guxxx implementations using 23/06/09 SVN version. It seems all fine from my side ^^ Would be nice to get guQuatSlerp implemented aswell. The MtxInvXPose optimised assembly version would also be neat for lighting (normals, envmap and so on) Let us know when full optimised versions will ...

Hello, Ok both versions are giving similar results. here are right ordered Mtx versions: for quatMtx: const f32 diag = guMtxRowCol(m,0,0) + guMtxRowCol(m,1,1) + guMtxRowCol(m,2,2) + 1; if(diag>0.0f) { const f32 scale = sqrtf(diag)*2.0f; quat->x = (guMtxRowCol(m,2,1) - guMtxRowCol(m,1,2))/scale; quat ...