- User Since
- Apr 16 2012, 4:32 PM (318 w, 1 d)
Suggestion after talking with @Bastien Montagne (mont29) :
assuming 2 windows at different times, when the user deletes a key on window 1, write the current evaluated transform in that window to the original DNA.
The end result is that the object would stay in place in the window where the user is working. On window 2 it would jump to the same position than on window 1.
Mon, May 21
Sun, May 20
Fixed pointer comparison between evaluated and original camera object
Fixed coding style according to guidelines: should be Object *ob, not Object* ob
Using active object for pose mode after talking with sergey
File I used for testing:
Sat, May 19
I made this quick patch to show if Blender is running with or without COW enabled as I kept getting confused with multiple Blenders while testing.
It has an include for depsgraph, so double check your includes if editing that file.
Mon, May 14
Sun, May 13
Scenario 1: you're both right :) behaviour is the same than for 2.79, nevermind!
Sat, May 12
Removed silly assignment of evaluated camera to v3d->camera. Fixes Ed_view3d_smooth_view.
For viewnumpad_exec, the final result when pressing numpad0 seems to be always correct.
Here is my test file:
Thu, May 10
I can't see the panel for background images and also couldn't quickly figure out how else these are meant to be used now.
Mon, May 7
The following look good to me, marking as done:
Sun, May 6
Sat, May 5
Wed, May 2
Hi @Friedemann Seebass (frisee)
I'm sorry I took this long replying, I have been more away from Blender than I wished to :)
Apr 23 2018
Feb 14 2018
^^ awesome. thanks!
Feb 13 2018
The naming of the options was indeed confusing to me and I wasn't sure if 'WITH_CYCLES_CUDA_BINARIES' meant something else than 'WITH_CUDA'.
Jan 22 2018
Jan 7 2018
Jan 5 2018
Updated, as I noticed the node on the image was actually a 'Texture Image' node instead of 'Image'. Both should work now :)
Apr 17 2017
Oct 31 2016
Confirmed in 2.78a
@Peter B (retep.orib) do you recall having issues with copying the settings from a previous release?
Also, is this version 2.78 or 2.78a? (you can check this and the build's hash in the splash screen)
Oct 16 2016
Oct 4 2016
Aug 21 2016
Jul 6 2016
Apr 20 2016
Apr 19 2016
I have no idea how much work is to setup the new skin, vs stripping down our current version to be compatible with the default skin.
That being said, I am all in favor for css tweaks so that it looks like the other blender websites, as long as it is not too much work.
I am not so worried about styling, but about the functionality of the navigation.