- User Since
- Nov 7 2018, 7:19 PM (126 w, 5 d)
Jan 22 2021
That makes sense. As long as it's not "Save as Render" with the current tooltip it's way better. I think "Standard" might not be the best choice for the name and it would make more sense to just call it Display Device Transform directly if it is, but what do I know. Even if it is a bit confussing and named "Standard" at least it makes a whole lot more sense than what it is right now.
Sounds better. Of course "Standard view transform" is just as meaningless, if the standard is not defined. This is another big issue. What is standard? Why not specify the standard just there? Is it sRGB IEC61966-2.1? Or is it any other standard? Why hide it?..
Well, I would gladly do that, but I am afraid it seems I have no way of knowing what it does exactly like most users without deep understanding how Blender's code works and ability to program in C. I am guessing it disables color transforms set in Color Management settings and outputs raw values, is this what it does? In that case why not call it "Disable color transforms" ? Or if it applies other transforms, why not say "Apply x color transforms" where x is those color transforms...
Nov 9 2019
3ds format is still widely used for sharing models online. Many furniture manufacturers use it for example and it may be very helpful and convenient to have native support for it for those of us doing arch viz. It is very sad to see it dismissed with such a short discussion.
Sep 10 2019
Any news on this? Any chance of it being fixed for 2.81?
Aug 20 2019
I can't wait till this is fixed as well. That makes work really inconvenient.
Mar 21 2019
I added a gif showing the problem to the original report. Blender is out of the box, factory settings loaded, drivers are now updated to the newest ones. Problem is definitely there.
It works in 2.79 as it should. I don't see how this can be considered not to be a bug. Camera clipping itself should be considered a bug. There are no cases where one would need to clip a camera they are viewing things from with itself. If the safe areas and passepartout is visible, the camera border should remain visible as well.
Drivers are up to date(well, now they are anyway... version 419.35). I can reproduce this on two different PCs as well both with same GPU, with today's build as well as builds from few days back.
Nov 8 2018
I would mainly consider this to be a bug because the label of the operator in the search menu says 'move on normals' and then the actual functionality does not match this. Since vertices and edges could be moved on their original normals I think it would be reasonable to expect this. The other problem here is that there is no easy way to extrude edges and then move them on the original normals because of the way the normals are calculated as you pointed out. I think this would be a good reason for the operator to work according to it's label. I am no programmer but since the 'Extrude only Vertices' operator leaves the normals as originals and it is then possible to grab and move them on the original normals even though they are recalculated immediately after the operation starts, I assumed that it should not be something impossible.