Search options (Page 14 of 60)

Yes you are right it's "onChar"
(EDITED on top)

yes right now a better mechanism is needed to feed the character events,
the trunk version of Maratis doesn't really support unicode like the new experimental branch.

I'll think about something, maybe committing the unicode fix in the trunk.

You can animate the texture UV offset.
Look at this link : http://forum.maratis3d.com/viewtopic.php?id=98

For mac it's the same system,
you just have to go inside the MaratisPlayer.app packet :

create a bash with something like :
MaratisPlayer.app/Contents/MacOS/MaratisPLayer "" 1024 768 1

yes sorry, you are right, because MGame::draw(); call a clear.

the first method is not necessarily slow as you can either deactivate the x-ray objects in the main scene when they are in x-ray, or have the x-ray objects only in the secondary scene from the beginning (if they are always seen in x-ray).

Other solution is to add an option in MMaterial to ignore depth-test so the object won't be affected by the z-buffer,
but your material should use an additive blending mode to avoid self intersection issues (additive blending can be render in any order).

do you mean the general painter's algorithm ? (was used for real time software 3d before the z buffer technique)

or do you just want to do a special effect ?

in Maratis the rendering order is managed by MRenderer (here fixedRenderer or standardRenderer),
in the standardRenderer it happen globally like that :

- get the list of objects visible in the camera view
- render all non-transparent sub-meshs from near to far in depth-test only (early Z test) and build occlusion culling
- render occlusion-culled non-transparent sub-meshs in random order
- render transparent sub-meshs in far to near order

It's a bit different in the iOS renderer for example (no early z test because iphone and iPad 3d card uses tiled rendering).

To sort objects you can use MCore's "sortFloatList(int indexList[], float floatList[], int start, int end)"

But all depends on what you want to achieve.

Good animation tutorial, it's the basics of animation any 3d animator need to master,
you can transmit a lot of the character feeling and energy with the body, thanks, keep going.

it's interesting, I don't know how far it can go but the video is impressive.

for the ones interested, the research paper is here : http://cg.cs.tsinghua.edu.cn/papers/SIG … 3sweep.pdf

so maybe your entity bounding box is not up to date :
*entity->getBoundingBox() = *mesh->getBoundingBox();

Hi,

sorry for the late reply, I was working in another town for a week,
it will be valuable to add a simple to use post-processing system to the trunk.

At first it could follow the logic of the camera layer and add two functions to activate/deactivate a post-process shader in lua.
Later we could add something in the editor, but probably only after we move the editor to MGui-v2 (from the experimental branch).

1 : add an "MFXRef * m_FXRef;" to MOCamera to handle the post-processing shaders
there is already "MTextureRef * m_renderColorTexture;" and "MTextureRef * m_renderDepthTexture;" to handle the render to texture.

2 : add the effect rendering to the default MGame::draw

3 : add two lua functions to enable and disable a camera effect. For exemple :

Camera = getObject("Camera")
enableCameraPostProcess(Camera, "shaders/myPostShader.frag")
disableCameraPostProcess(Camera)

4 : in a second time, we also need to add custom variables to the camera to send uniform variables to the shader (to control blur size, focus etc). I'll think about something generic that can create dynamic MVariable.

I think AxisYPoint or P and Q might be wrong,
they all need to be in the same coordinate, meaning global or local.

so, or you make AxisYPoint global, or you make Q and P local.

you can look at the code of the look-at behavior : https://maratis.googlecode.com/svn/trun … LookAt.cpp