Tsar Hoikas wrote:Blender has some support for translation and has exposed... something... about it in the python API. I'm not sure how it all works, though. It's possible that it would only work for the C-level code. If it is usable from the Python end, I wouldn't be surprised if there is zero documentation for how to do so. Most of what I learn about the Blender Python API comes from quite literally reading the blender source code. Ugh.
Tsar Hoikas wrote:Most of what I learn about the Blender Python API comes from quite literally reading the blender source code. Ugh.
Sirius wrote:Wot ! Some SDL, armature and networking typeIDs got mixed up with the envmap itself!
Sirius wrote:Also, may I suggest keeping the texture space to None instead of direct ? I don't know the difference, but it seems to be the default in Cyan's PRPs from what I've seen
Sirius wrote:If the envmap isn't specified it might be a good idea to automatically create one with a high yon setting, so it reflects the sky correctly...
Tsar Hoikas wrote:and the garbage values appear to be overrunning into another section of the DLL's memory, returning strings from the type map's enumeration. Yikes. We're really lucky that kind of crap doesn't crash PRPShop instead...
Tsar Hoikas wrote:RGB8888 is by definition in direct color space. Unless you'd rather use the greyscale color space?
Tsar Hoikas wrote:Perhaps. I am more curious to know what's wrong with the default environment map that the engine makes. If the issue is that the effect visibility set is not present, then there is probably little that can be done automatically from Korman.
Dulcamara, here is my current Blender file. I hope it helps you fix the swim regions. Like I said when exporting the water visual is still buggy and white, so this will have to wait until the issue in Korman is patched.
Users browsing this forum: No registered users and 2 guests