The 'up' vector IS already normalized by SUp's API - when you use 'vector.normalize' on it it is unchanged.
BUT, I have got to the bottom of this - it's my error
I convert the XYZ values from SUp's inches into meters in the code, so that the camera details of a point3d like 'pos' are in the right units for Octane. I had inadvertently also included that conversion for the XYZ values of the 'up' vector - but it's NOT a point3d - it is already a normalized vector - this made the 'up' vector's XYZ values much smaller than they should be !
I have now fixed all of that 'up' code and it'll be posted shortly as
beta.u.
That update will also include some code changes to try and circumvent this js error you are still getting - I discovered what I think is doing it - some browsers don't like a child process to try and change its parent before it's all fully loaded - in the case of the sliders' js it looks at the value in the associated text-box and updates the slider OR gets the value of the slider and updates the text-box - so they are always in step. However, to get the dialogs to format properly a text-box and its slider are inside separate table sections. If one tries to modify the other on the page's load your js/browser settings throw an error message as a child is modifying its parent [mine has never given an error though ???]. So now the new approach is that one only updates the other
if their values differ - and on first load they should be the same anyway. Please try it and feedback on this - if this fix doesn't work then at least I think I have the cause that must have another solution somewhere... It could also be associated with the way SUp 'populates' a web-dialog - let's see how this fix works...
Another minor change is that the main dialog now closes/deactivates tidily when you cancel it with the X button top-right [previously it had closed the dialog but it had left the Octane Render 'tool' shown as activate in the File menu]...
