- User Since
- Oct 19 2018, 2:15 PM (47 w, 5 d)
Mar 22 2019
Thanks big time, Campbell. That was fast.
*I can comfirm it as working as expected*
on our Win10 system.
Mar 17 2019
THIS is the following Report to Bugreport T57305, where I found out, that this function should alsready work inside of Blender. It just seams to be defective.
Mar 16 2019
Thanks, Campbell for your answer.
I have tried similar in Blender 2.79 without any success.
Now I have tried this as exact as I could, I also watched Tutorials for Autokeyframe in 2.80 - but it looks like it does not work for recording a Camera via NDOF.
It doesn't write any keyframe, via NDOF.
I pressed the record button in Lock Cam to View - switched to Camera, being in the Animation timeline.
I pressed play, moved the Camera with the 3D Mouse (NDOF). No Keyframe is being written.
I switched back to 3d view and moved the camera by marking and moving it by pressing "G" on the Keyboard. It recorded that movement as Keyframes in the timeline as expected.
NDOF is not being transfered into Keyframes this way.
Mar 13 2019
Comfirmend: working in Win10 64bit, as expected. Thanks a lot Campbell :)
Feb 5 2019
Yay. Thanks, Campbell. But please tell me that this will be fixed in April this year. Production needs to start.
Jan 10 2019
Dec 27 2018
Any News on this?
Is there another way to at least snap the camera to the current view or get the coordinates of the current view to put into the camera x,y,z fields + rotation somehow?
Dec 21 2018
This is the link as promised.
As you can see in this video, there is a little more movement of the 3D mouse, very erratic. It increases even more, when continuously pressing space bar. But nonetheless, it's unusable. After additionally installing the software from 3D connection for space navigator, the little movement that was present (as seen in the video), is completely killed of. Only here and there there is some movement of about one pixel to all directions but mostly none at all. It is behaving just like it did before installing Windows completely a new, with a virgin installation of blender 2.80
After installing a new Windows 10 Pro, the 3D Mouse behaves generally the same as before. I now have installed Win10, Firefox then Blender (just downloaded a few minutes ago) and tested. Not even the 3D Mousedriver from 3D Connection itself has been installed. Only what windows does on it's own.
I'll put a film on youtube about it soon.
Dec 12 2018
Here's a link to a video, showing the error happening.
And it's even more strange, that in version 2.79 of blender 64-bit, there is no error and the camera is moving correctly. On the same system.
Thanks, for looking into this. I really hope it can be solved, as this is very much breaking our pipeline, or at least slowing it down significantly.
Dec 11 2018
I had tested on my earlier machine.
I had it in Windows 7/64bit as well, in the same manner as in Windows 10 now.
First: I just found this post, which seams to be related to mine, I just don't know how to add it here: T59199