The Code Quest is a 3-month long project to wrap up the development of the first public beta release of Blender 2.8.
It runs from April 9th to June 30th, 2018 in Amsterdam at the Blender Institute.
To learn more visit: https://www.blender.org/2-8/quest .
Some silly comments...
It makes me of QBlocker :
After you've modified your object, will these gizmos disappear or will they show up on every object once the tool is enabled? I feel like this'd be better for modifiying other shapes fast.
In addition to these gizmos, we could offer a toggle here to switch into Walk Mode more easily:
The original design doc here has some issues I'd like to improve upon:
Personally I prefer simply Walk Navigation (where you can also fly with TAB) which is in Blender.
@Adam Preisler (Alphisto) This doesn’t add any extra affordance to switch cameras. This is about the ability to more easily manipulate the camera when inside the camera view, which is currently not so easy by default.
Since there is a discussion now and a hopeful horizon I would like to add that since we're talking about cameras it would be great to have Exposure & Contrast controls.
@Arbaz Arif (AcidRain0) Appreciate the support for this, but please don't do that - this is not a forum. Hopefully this could be added for 2.83 if there is time. We'll see.
Bump
This is a great addition. Please consider making it accessible from Sculpt Mode as well. Thanks!
Any plan to release custom editors as presented in "Editor Addons" ? That would be very useful for Addon developers.
@PawelP (Zuorion): Averaging is not the same as comparing. Anyway, this is more depending on implementation rather than a purely design issue.
@William Reynish (billreynish) hmm, in editmode, transform pannel is already being calculated in realtime for milions of vertices
@William Reynish (billreynish) Looking at the space from the user POV (vs performance) - Do users want to have animation, driven, keyframed control for every property? If so, then they need the ability to control every property. To have control they can interpret with minimal error they need to understand the state of controls. One of the states of properties is multi-select - thus they need an experience that lets them understand any property that can be driven/animated when there is a multi-selection.
@Karl Mochel (kalmdown) Of course, that is obvious. The difficulty of that is one of performance. Blender then has to compare many values to see if they differ or not. But, many other apps seem to do this with no issues, so it must be technically possible for us to do.
A few additional thoughts...
New to Blender but designed VR IDEs and 3D MRA packages.
I just fired up my old and trusty Softimage 2015 because it had a very nice multi-select behaviour: If you select 2 or more objects with different attributes, it displayed an empty value for everything that wasn't set to the same value in all objects. If you now typed in a new value it set it to the same for all objects. BUT: if you entered something like "2+" it added 2 to all of the selected objects' property values. Very very nice. You could even enter expressions to e.g. randomize a value per object.
Unity allows that, and it shows "--" when the values are different. It is quite handy to be honest.
The initial bugreport is still valid, as the behavior of the operator is still broken.
@Jack Doe (mrPizza344) 2.79 will be available forever, don't worries. The BGE as it is won't come back to 2.80 though.
I want y'all to re-add the game engine. I love that feature, and i have to use 2.79 because you are not willing to update it.
I very much like this proposal.
Could it be possible to add a pivot to each image, to be able to scale from it?
I've found a workaround for making Dynamic Weight Painting visible in Blender 2.8 in Eevee and Cycles (Look Dev and Rendered):
Unwrap your object and scale the UV-map so that all UV-vertices are at (0,0). Now add an UV-Warp-Modifier to your object and use two Empties added at (0,0,0) and (1,1,0) as helper objects for the Modifier.
The dynamic weight paint map "dp_weight" determines the influence of the UV-Warp-Modifier. From the UV-Map-node, we separate the x or y value, put it into a color ramp with blue at the left, green in the middle and red at the right.
Plug the color ramp into your shader node and the weights become visible: See in attached files:
With a plane: