Pokémon Model Ripping Project

[gdkchan]

That is sooo awesome! Thanks for your hard work! Hopefully I can use GLSL shaders in 3dsmax (I heard vray support rendering them)

Thank you. I don't think that GLSL is widely supported through, mainly because it's tied to OpenGL, and I think that most engines supports both DirectX and OpenGL, so they use something else that supports both and compiles as needed.

At this point I kind of regret working on this, since it probably won't find much use, but anyway since I already started this, I just decided to make the changes also work on Sun/Moon models, where some had the same problems affecting the Koffing model. One example is Cosmog:

[spoiler]

[/spoiler]

Same problem Koffing had. Point sprites being treated as triangles.

[spoiler="Some maybe boring talk about how I implemented what you see on the gif below"]
The first thing I did was search for the shaders on Sun/Moon files. This was easy, they are located inside the same PC model file of the Pokémon model (so, each Pokémon also have theirs shaders inside). They are not using he SHBIN format like OR/AS shaders however, instead it stores a buffer with commands to the GPU, and the shader code is inside one of those commands. Loading the shader was not very complicated actually, and I managed to make it work more or less. The main problem is the ID of the uniform registers, their mapping is totally different from OR/AS, so to make it totally work I would need to implement two maps on the renderer, one for OR/AS (which also applies to most BCH models since OR/AS shaders are based on the default BCH shader), and one for Sun/Moon, and choose the correct one as appropriate. I really didn't wanted to go this way, so I just used OR/AS shaders instead.

Also, another annoying thing. Sun/Moon uses -1 (0xff) value for unused bones. Shader will try to access value on the bone transform matrix array at this position, and this is an illegal memory access since the array is not this big. On my GPU, this makes the model randomly disappear, so I had to add checks on the shader to prevent this sort of thing from happening, and I think that it made the shader a bit slower.

So, luckely, Sun/Moon models uses (mostly...) the same shader names that OR/AS uses, and the shaders are also pretty much the same, so just loading OR/AS shaders actually works!
[/spoiler]

[spoiler="Cosmog fixed (gif)"]
http://i.imgur.com/AS8gYoM.gifv
[/spoiler]

So here a few things I discovered with this:

- Sun/Moon shaders are mostly the same compared to OR/AS ones, main change is shader uniform ids, some code related to matrix transform, and when the point sprite size is calculated, it multiplies the color by 3 (!), and OR/AS doesn't have such multiplication.
- Shader have a uniform called "PressDir" that controls the direction of the projected shadow. This direction is stored inside the model file, on OR/AS as a uniform command and meta data, on Sun/Moon directly inside the material section.
- The name of the shader used to project shadow is called "PressShadow". The shader used for billboarded effects like Cosmog stars and Koffing smoke is "PokeFire", and the one for projected shadows is called "PokeFireShadow". The "normal" shader for Pokémon is called "PokePack" on OR/AS, and just "Poke" on Sun/Moon.
- Like on OR/AS, the low res Pokémon model is ALSO used on the projected shadow. I also suspect that the projected shadow model is using the stencil buffer to render the entire model as a single plain color, but I didn't made any analysis on this yet.

It's probably worth noting that the above fix only works when using the original shaders from Pokémon OR/AS, because the default shader supplied with SPICA isn't capable of rendering those effects.