Closed GoogleCodeExporter closed 9 years ago
11/02/09 18:30:01 changed by abauer
To add to this:
- Matrices are needed for the current frame of course.
- B) can be used as a workaround for A).
If B) is easier to implement than A) we could for now go this route and do A)
later.
11/02/09 18:34:27 changed by ckulla
Option B might already be working since we recently implemented the textureinfo
call.
11/03/09 10:26:29 changed by abauer
Any documentation already anywhere on how to use textureinfo in OSL to extract
the camera world_to_screen and
world_to_camera matrices?
If so, then I could start playing around with it.
Searching for 'textureinfo' (on SPI main page) does not return anything OSL
related...
And 'gettextureinfo' seems to support matrices only for shadow maps...
tnx
11/03/09 11:17:38 changed by lg
(A) is a combination of matrix routines that I'm already working on, and
getattribute() which we haven't done yet but is
coming up soon (and will need a little support from the Arnold side, too).
I think (B) is already working and is part of gettextureinfo(). It ought to
work fine for any texture file that has these matrices
embedded. I'll fix the docs if it implies that it only works for shadow maps.
Original comment by rene.lim...@gmail.com
on 11 Jan 2010 at 6:32
[deleted comment]
[deleted comment]
[deleted comment]
Original comment by rene.lim...@gmail.com
on 23 Feb 2010 at 6:34
I believe this is all implemented now.
Original comment by larrygr...@gmail.com
on 23 Feb 2011 at 11:09
Original issue reported on code.google.com by
rene.lim...@gmail.com
on 11 Jan 2010 at 6:31