- User Since
- Jul 26 2010, 5:29 PM (477 w, 2 d)
Jun 27 2019
Maybe there's a better fix but I just commented out the right mouse case, you can no longer cancel the yellow line placing part but it doesn't cancel instantly. You can still cancel the slide part with the right mouse button.
I tested this more and found out that
- There is a tweak action by default (grab) on right click and it works.
- Actually everything other than loop cut works on right mouse.
So right click can only be used for cancel and nothing else? That seems like a waste of a button then.
As far as I know there are no tweak actions in Blender by default, so yes, it's a custom keymap.
Jun 18 2019
May 22 2019
That's true. But why are you able to right click in the Undo History then when it doesn't do anything useful? It gives the impression that you can do what is listed (change hotkeys and so on) when you can't. You can't right click in Operator Search (though that would be useful), so shouldn't it be disabled in Undo History as well?
May 20 2019
Nov 20 2018
Sep 21 2018
Couldn't you just check if there is a local armature with the same name? That would make more sense to me than just throwing a bunch of letters onto names even when no local armatures with the same name exist.
Sep 6 2018
Left click select does feel better when using pen tablets (personally). Also not sure what "Using Alt-LMB for view manipulation also didn’t work with this option." means, it works for me, maybe not by default but at least after changing keys.
Aug 11 2018
- The workflow in the documentation is probably meant to help new users by not having them believe you can "create holes" or something with shape keys, where such an operation (deleting vertices in a shape key) will actually also affect the basis shape key (as in the whole mesh).
Aug 6 2018
Jun 23 2018
Jun 20 2018
Jun 19 2018
Mar 11 2018
Mar 1 2018
I don't see why something like that should be an addon instead of a core feature in User Preference - Editing or somewhere.
On Windows it's super broken. You can only copy paste text into text objects. When pressing spacebar after typing a bunch of characters instead of activating IME you actually input spaces into the text field which isn't how Japanese IME on Windows works. When you type the first character it's not input at all, the rest of the characters are input as if you're typing in English. Kanji conversion doesn't work at all.
Feb 28 2018
It helps the Blender-UE4 pipeline so it helps users of Blender using it in combination with UE4. In this case it was FBX related and maybe hard to fix in Blender, so it was fixed in the UE4 side instead. If you're curious it's the "armature creates an extra bone in UE4" problem, I'm pretty sure that has been reported before. Maybe not a bug per definition if it's working as intended, but it caused problems in UE4 because you could not share rigs between characters, had to animate root motion in object mode and so on. For me as long as it works smoothly it's not too important where issues are fixed.
In an asset pipeline you want things to work, how they work under the hood is not that important to the end user. I don't believe other software put dots in names, most allow duplicate names and you have to actually fix that before exporting so in this sense Blender is better, but there's no way to change the dot delimiter to something else in Blender currently which causes this problem.
Feb 27 2018
Nope, this is a pretty low priority UE4 bug probably (compared to crashes and so on) and right now Epic is preparing for GDC so there's little happening on the engine side.
Feb 26 2018
What you could do is copy the right plane and remove the shapekeys, select the sphere, shift click your new plane, then at keyframe 30 do Join as Shapes (found on the black triangle button under the add/remove shapekeys buttons), then at 60 do the same thing. After that animate the new shape keys so you get a smooth curve.
Feb 25 2018
Changing the scene unit scale using the presets doesn't create an undo step so you will revert to the previous value when changing the cylinder radius (which is basically an undo and then a new operator with the new radius value). You can get around this by typing the value manually, so just changing to metric and typing 0.01. You can also save a startup scene with those settings using Save Startup File.
Feb 23 2018
I can confirm this. It doesn't work in the text editor or python console either.
Feb 19 2018
Thanks for the commit.
Feb 18 2018
- Fix whitespace.
- Less ugly version.
Feb 15 2018
Definitely looks like something weird is up. I also noticed that it seems to work with Accumulate enabled.
Feb 14 2018
You've got a bunch of objects using mesh data Cube which doesn't have any vertices, the operator uses the vertices to find out where it should align (or something like that) so it fails when there are no vertices. If you isolate the objects that actually are the cubes (using mesh data Cube.001) it works fine. Did you mean to have empty mesh objects instead of using for example Empties?
This is caused by rB702bc5ba26d5ff2a4da9e92cabb2fa34ed3f2312. Anyway instead of duplicating the bones you can use Armature - Symmetrize instead, that way you get the right names (and don't need to duplicate and scale the bones).
Feb 8 2018
A plane doesn't have width (well, volume) so I don't see how it could be used to separate things. You can see that it is cutting the mesh though, and if you apply the boolean you can see that you end up with new vertices where the plane was. So basically you made a fancier version of loop cut. 😛 If it's supposed to actually split the mesh in half then it could be a bug but it's still nothing like the Carve result you got.
Feb 7 2018
Maybe some matroska (.mkv) weirdness? https://matroska.org/technical/specs/notes.html
The video playback is only fine because by default Blender sets the scene fps to the video fps. If you disable use video fps when adding the file (down left) you get an extremely slow video.
Feb 6 2018
I reported the bug for now, it should be very clear what's wrong. I will update with their response later (if any).
The issues tracker is only for "accepted" bugs and was not used in earlier versions (it didn't exist back then). Here are a few answerhub reports:
It was reported a bunch of times but not fixed yet. You're right though, I checked the code and there's even a comment saying "// find the Fbx mesh node that the Unreal Mesh matches according to name". So there's no check for converted file names.
It kind of is like throwing water on a campfire but I agree. Apart from a Collections icon which is needed, what's wrong with plus signs or minus signs like everywhere else in Blender? (vertex groups, UV maps, whatever)
The way you phrased this is more of a support thing. Anyway you've probably enabled Manipulate Center Points next to the pivot point picker.
After checking in UE4 only these characters seem accepted in names: a-z, A-Z, 0-9, -, _, ´, ¨, §, ¤, +. I'm not sure if these are actually accepted or if it's another bug (maybe breaks in cooking) but at least can strip the non working characters. Checking for name collision between objects could also be done too although I think this would be pretty rare that you've got one object called Cube.001 and another called Cube_001 for example.
Feb 5 2018
- Fix mistake in tspace argument.
My hack (don't tell mont) wasn't meant to be reliable really, just a quick fix to a strange problem.
Feb 4 2018
- Remove whitespace.
- Change name to "Only...", add active vertex color layer to export.
By default it uses units as a measurement so in Blender default scale island_margin 0.0 means 0m and island_margin 1 means 1m. You mentioned UE4 so I'm assuming you're using a scene scale of 0.01 for skeletal mesh compatibility.
Feb 3 2018
Added function that replaces enumerate(), by default mimics enumerate but when export_active_uvmap is true it returns the active uv layer index and active uv map instead. Keeps the code the same which looks nicer.
- Remove more whitespace.
- Remove whitespace.
Update. Hopefully nothing went wrong...
- Remove no longer used IntProperty import.
- Remove code duplication by adding uv_enumerate function that either
- Remove unneccesary comment.
Can't you just click Generate Data Layers to make sure all of the vertex groups are there?
Feb 2 2018
It is a bit weird because there's a Check Existing flag in the operator with the description "Check and warn on overwriting files" but it doesn't actually do anything which seems like a bug. It's set to True by default but set to False it should disable the warning popup that is hard coded right now it seems like. Then when this is fixed similar props could be added to the Delete operator and any other operators that do this.
Jan 31 2018
Not really related to the task itself but the spreadsheet is in the recycle bin so it will be removed if left there, you might want to move it out if you don't want it deleted.
Jan 29 2018
Smooth Stroke does sound like something you do after a stroke, maybe it should have been called Stroke Smoothing (or Lazy Mouse as above).
Jan 28 2018
Yes, it seems like the best approach is to fix all of the files (external libraries?) that actually give warnings with UTF-8 forced for everything. That process has started already too.
Jan 27 2018
I did see that gaia in IRC mentioned a lot of warnings when compiling in vs2013 "<gaia> hi. when building with vs2013 i currently get about 1400 warnings all saying "cl : Command line warning D9002: ignoring unknown option '/utf-8'"", I have only built blender with 2015 myself. Is this a 2015 feature or should it work on 2013 too?
Jan 26 2018
That being said if there's a better solution (like fixing the thing that causes the warnings in the first place) I have no problems with that, just ignore this patch. I just want Blender to build really.
Changed behavior to export the active (selected) UV map as per Campbell's suggestion.
You can just change the key for loop select if you want alt+left click view rotate. Since Blender shouldn't randomly change keys for you it's up to you to solve any conflicts.
Jan 25 2018
Every vertex group having every vertex is because the cube is tiny and there are only 8 vertices. Plus all bones have Deform enabled, if you disable Deform no automatic weights will be applied for that bone. Also the bones are pointing up instead of out from the sides, the weights are using some kind of raycast so having them point a certain direction makes them more accurate. If you increase the subdivisions you should see that not all vertices end up weighted to all bones. Try it on a mesh like Suzanne instead and you will see that it works as intended.
Jan 20 2018
If it works fine in 2.8 it's definitely not high priority. An easy workaround is to just add vertex color layers to everything because this bug only affects meshes that don't have vertex color layers.
As a temporary workaround you can change line 127 and forward in import_fbx.py (see the path of the error) to this:
Jan 19 2018
If it's not a problem I would like to see these included:
rBfdd3d969a621 - fixes long standing bug that caused problems when confirming operations with enter when using a pen tablet and the pen is not touching the tablet input area.
rB235f578a0d21 - improvement to loop cut so you can type numbers using the keyboard and still move the loops around with the mouse.
Jan 18 2018
Looks like this for me:
Jan 17 2018
Jan 16 2018
- Restore whitespace before break statement.
- Temporary fix for UV map index range errors with multiple objects.
- Add space so it looks like the rest of the code.
- ... in all files.
- Put the new stuff on a new line so it's more obvious that it's new.
- Remove uneccessary newline.
- Fix for wrong version.