Ridley5 opened this issue on Jul 26, 2010 · 1724 posts
bagginsbill posted Thu, 26 August 2010 at 4:42 PM
On this focal length business, check what is being written into dataOut.bbml. If it is the right value, then go look at the camexport.py file.
adp rewrote my code to use his parameters, and I think there is a mistake there:
print >> file, 'Camera "%s"' % camtype
print >> file, ' "float fov" [%s]' % fov
if gp.get("overrideFocalLength", "false") != "false" :
print >> file, ' "float focaldistance" [%s]' % gp.get("focaldistance", gp.get("focallength", 50))
Notice that it doesn't override the fov - instead it writes a focaldistance into the lux file. That isn't the field of view. So with his exporter you probably can't get the correct field of view by overriding.
Also he changed the code I had in there to set up the LookAt configuration line. I have no idea what is going on.
I know my exporter produces 100% accurate camera position.
I just have a little more packaging to do and it will be ready.
I'm putting everything in a runtime structure so you have nothing to install, nothing to configure. Just unzip and go.
Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)