forked from bartvdbraak/blender
ee7a2ccb22
The funny thing is: I only spotted this bug in March of this year. Almost one year after the original release. I think I don't parent objects to the camera often. In terms of code I think that I can even think in a more elegant solution. I don't really need to rotate the camera, but simply to calculate its Modelview Matrix. """ m_rasterizer->SetViewMatrix(viewmat, cam->NodeGetWorldOrientation(), cam->NodeGetWorldPosition(), 1.0); cam->SetModelviewMatrix(viewmat); """ The reason why I originally was rotating the camera was to make sure the frustum calculation was using the right camera frustum. For the frustum it takes the camera modelviewmatrix so the rotation really shouldn't be necessary. Leaving as it's for the time being. * Note: the bug was never officially reported |
||
|---|---|---|
| .. | ||
| BlenderRoutines | ||
| Converter | ||
| Expressions | ||
| GameLogic | ||
| GamePlayer | ||
| Ketsji | ||
| Network | ||
| Physics | ||
| PyDoc | ||
| Rasterizer | ||
| SceneGraph | ||
| VideoTexture | ||
| CMakeLists.txt | ||
| Makefile | ||
| SConscript | ||