- User Since
- Mar 27 2007, 4:55 AM (651 w, 6 d)
Aug 24 2018
Thanks for the feedback. I'll keep descriptions more concise in the future, and will be sure to always include a .blend.
Jul 16 2017
@Nutti (Nutti) @Alexander Milovsky (hp9000)
Nice proposal. I hope Alexander Milovsky will agree to having the Sure UVW Map add-on included in 2.79! It's a great add-on and I've found it really helpful when doing archiviz work.
Jul 3 2017
I too can confirm that placing Blender.app directly in /Applications solved the issue with a duplicate icon appearing in the dock. One solution besides creating a .dmg installer could be to have Blender.app placed alongside (instead of within) the folder that contains the licenses and extras (such as Blender Player). That way when users drag it to /Applications it's exactly where it needs to be from the start. Just an idea.
Jun 13 2017
@Lukas Stockner (lukasstockner97) I would be happy to. Where can I find a "debug build"? This is the first time I've heard of this type of build; pardon my ignorance.
Jun 5 2017
Update: I was able to reproduce the same result on another machine with the following specs:
Apr 21 2017
Mar 30 2016
Hey, wanted to let you know that after updating to Python 3.5.1 it's working just fine! Case closed. :-)
@Bastien Montagne, my Python version is 2.6.1 (I guess I should probably update). Btw, it didn't work typing sys.version, but typing python -V in Terminal worked.
Mar 28 2016
Dec 12 2015
Nov 13 2015
Got it - thank you for the explanation! Looking forward to when this becomes possible. :-)
Nov 12 2015
Nov 5 2015
Ha! So it was a fluke that it worked before. Well now we know the correct way to do it, so that's good. Thank you for looking into it and explaining.
Nov 3 2015
Nov 2 2015
Oct 26 2015
Regarding my last comment, I can see now that it is possible to have a mesh with multiple pieces of disconnected geometry, some having a root vert (and therefor skinned) and others not. So even if a root vert is present on some pieces, if a root vert is not present on each piece the object will not be skinned entirely. So if an alert message were to be added it should probably be worded to include this idea.
Oct 23 2015
I see! It's all clear now. Thanks for explaining!
Oct 22 2015
Oct 8 2015
Rock on! Thanks!
Oct 7 2015
Sep 7 2015
@Fabio Arnold (donfabio) Sorry, but posting a .blend won't help for this one. It seems to be a UI issue. Luckily we have some new info on it, and a lead on a resolution!
See this: http://blender.stackexchange.com/questions/38147/os-x-fly-mode-wont-respond-to-mouse-movements/
Aug 21 2015
This is a really elusive problem. Each time I thought I knew what was going on, it turned out to seem to be caused by something else. By the end of the day yesterday the .blend I had initially had the problem in was mysteriously working again, but when I would create a new file the problem would occur in the brand new files.
Aug 20 2015
Wait wait wait... my conclusion was wrong! Everything I posted above about replacing the settings folder fixing it is a lie!
I just ran into this too. Mouselook broke in Camera Fly Mode. It was working and then suddenly a setting got corrupted and it stopped. Relaunching Blender didn't fix it. Only doing a "Load Factory Settings" resolved it. In case it helps here are the Preferences I modified today between the time it was working and the time it stopped working:
Jul 16 2015
Jun 23 2015
Nice work, Julian!
Jun 22 2015
Jun 7 2015
Feb 4 2015
Nov 4 2014
Since it's unclear if anyone intends to fix this any time soon, I'm going to post a workaround I found for the time being.
It takes a bit more time than the Grease Pencil, but it's not too bad, and at least it makes curve re-ordering possible.
Nov 2 2014
I experienced this bug today. Seems it is still a problem in 2.72 (95182d1)
Oct 26 2014
Kévin, thanks for mentioning that.
In my .blend I had the particles being influenced by an image texture, as well as by the particle settings. While these values should not step on each other's toes, it is something worth noting.
FloridaJo, thank you for reducing the .blend to its very basic elements and reporting.
I used your .blend and was able to reproduce the crash on another Mac when resizing the window after rendering.
So now we have seen this occur on three different Macs running three different versions of OS X.
I wonder if any Windows or Linux users will be able to reproduce this.
Oct 25 2014
Oct 13 2014
Sep 17 2014
Sep 4 2014
One thought I had was that it might be helpful if there was some visual feedback given to the user that an event was taking place at the cursor location when the L key is pressed. It would help distinguish a difference between L and Ctrl+L and serve as an indicator that "hey, something is happening near your cursor". So I made a small 48x48px animated .svg that could theoretically appear for a moment at the cursor location when Pick Linked is used. I don't know if .svg is a format that could be incorporated into Blender, but I could just as easily make it an APNG or series of PNGs etc. Since it's an .svg the stroke color and other parameters can be changed by opening it in any text editor. You can see the animation by opening it in a web browser.
Thank you for clarifying that! OK, my mistake.
I was not clear on this for a very long time. I think the reason for it is that selecting a vertex and immediately pressing L will effectively select all the geometry linked to it in most cases... (have the same effect as Ctrl+L) but this is only because that's where your cursor is in most cases. So I got the impression that L selects all the linked vertices of the current selection, but actually that is what Ctrl+L does. It was my misunderstanding. I didn't realize there were two separate operations. Sorry about that! In this case there is no bug, there is only user error.
Jun 20 2014
Jun 12 2014
Never mind, I just realized thanks to nexyon's comment that it is in Strip > Crossfade sounds, and I was able to right click on the menu item and add a shortcut that way. It then showed up in the shortcut mapping list under Sequencer > Sequencer (Global): sequencer.crossfade_sounds I think having the () at the end when I pasted it from console is what caused it not to work for me initially. Problem solved.
Sorry to post in a closed ticket, but could someone please tell me how to assign a keyboard shortcut to the "Crossfade sounds" operator? I noticed from the console it's name is bpy.ops.sequencer.crossfade_sounds() but when I assigned a shortcut to this nothing worked. I can only call it from the spacebar menu. I can't seem to find any other relevant info on the web except for this page, so maybe you guys are the only ones who know, lol. Thanks.
May 22 2014
Thanks for the feedback willi, I just installed the latest build and sure enough, it has been fixed :-)
May 13 2014
Feb 12 2014
Thank you for the prompt fix, sergey! You're awesome!
Feb 9 2014
Jan 20 2014
Thanks mont29 for identifying my report as a duplicate. Sorry I didn't catch it. I did search with similar keywords before submitting, I swear. At least better to get reported twice than never at all though. ;-)
Jan 19 2014
Update: I have found that the same bug occurs when using Blender Internal. It is not specific to Cycles.
This came as a bit of a surprise to me as Blender Internal is not new.
In any case, it appears not to be a problem with the render engine but rather the automation system or the node system.