- User Since
- Jan 11 2010, 1:49 PM (401 w, 3 d)
Aug 13 2017
Fully convinced :)
Ah, indeed. Thanks Aleksandr. I guess the new way is the fix for the old behaviour, right?
Aug 11 2017
Um, this addon is included in Blender 2.79 RC1 :)
Jul 19 2017
Not here, unfortunately. Still the same behaviour with a fresh downloaded buildbot build, sorry.
Jul 5 2017
Jun 29 2017
Jun 28 2017
Indeed. No 404 anymore. I forgot to check this in the newest version. But the link now leads to https://docs.blender.org/manual/en/dev/editors/3dview/object/index.html#bpy-ops-object . And the manual entry is at http://docs.blender.org/manual/ja/dev/editors/3dview/object/properties/duplication/duplifaces.html
Jun 27 2017
Feb 23 2017
Yes, that fixed the problem. Many thanks :)
Feb 21 2017
Ah, so i am glad that i asked again. Thanks for confirming :)
Feb 20 2017
Feb 13 2017
Icon only buttons would need the tool name too.
Jan 9 2017
Hm. To drag it down to its minimum size is just the worst case to show the problem most clearly. This "minor" glitch causes me now to drag the title bar around every time i change the size of the Blender window. And it's enough to drag it just a few pixels around to make it visibly open up.
Jan 5 2017
Nov 17 2016
Oct 31 2016
Oct 21 2016
Nevermind. Now i get what you mean. They come up when i can have access to it. Available for example appears in the list when i already have a keying set.
I can without problem assign those keyingsets in the dropdown box in the timeline. So it's wrong there too?
Oct 20 2016
Jul 13 2016
Thanks for the info :)
Jul 7 2016
Thanks a bunch :)
Apr 19 2016
Apr 12 2016
Not permanently. Just during import. Once done the cursor turns back to normal.
too fast at the send button ... and at my laptop, which is another Win 7 system. Means it is reproduceable at an independant system. It also happens with every obj file that i have tested. That was my first thought, that something is wrong with the obj file. But tested with several other files, and always same result.
Yes. For 2.77 it was the factory settings.
Mar 2 2016
Feb 21 2016
Feb 10 2016
Dec 23 2015
In case it helps a bit, the file where this message gets triggered is the wm_windows.c file , Line 784 in the static int ghost_event_proc class.
Too fast at the send button ...
Ah, indeed. That was most probably the "randomness" i have experienced. Thanks for the hint. Just curious, why are there two edit boxes at all? Looks a bit like double functionality :)
Dec 22 2015
Dec 14 2015
Thanks Julian :)
Dec 3 2015
Okay, seems that i have catched with the show/hide dot files the one button of the row that has this behaviour ^^
Dec 1 2015
Well, most users will most probably not even know this feature exists in UV Editor. It has no menu entry ^^
Thanks Sergey :)
Argh, i wish i could edit images. The other half of the image was not meant to be publically shown :/
Nov 4 2015
Oct 19 2015
Oct 10 2015
Thanks for explanation :)
Oct 9 2015
I did some more investigation. And i think Lukas Stockner was at the right spot here. It seems to be connected with the old to do that you mention here. Most of the by him red marked keys have the wrong key mapping when i try to add a new hotkey. In the search field the keys works correct though.
Oct 8 2015
Different key mapping for different apps? You never stop learning ^^
Hm, there is no event when i change the hotkey. The console only gets flooded with wm_window_make_drawable arguments. Do i miss something else?
@Lukas Mandok (Lukas), i am at Windows 7 here, so i cannot talk about Linux. But it can be that we are at something bigger here.
I have tested this at two independand german Win 7 64 Bit systems when this is of help. My main system. And my laptop, which has Win 7 fresh installed after a disastreous Win 10 update attempt. Same behaviour at both systems.
Sorry for the big picture. I wish you could edit your own reports ...
Oct 2 2015
Jun 26 2015
Yes that makes sense. Thanks for the explanation.
I see. Thanks :)
Jun 23 2015
Nov 12 2014
Thanks for fixing :)
Oct 16 2014
Just thougth i chime in to confirm that 2.71 worked too. Good luck.
Thanks. I see. I'm no C developer, sorry. All i can offer at the moment is Windows plus the haswell cpu. So i can always test if a change has fixed the issue.
Seems to work fine with AVX2 disabled. But i am not sure where Cycle currently renders. CPU or GPU. The render tab just gives me the choice between supported and experimental. Not the choice between CPU and GPU.
Oct 15 2014
Well, i can still confirm and reproduce it, but i guess i don't count ^^
Jul 15 2014
Yes, here it works. But this version crashes very often. So i am kind of trapped here since this new version fixes the crashes.
Thanks juicyfruit. Sounds to me like i cannot really do anything here by myself. I hope the informations are nevertheless useful to catch the baddie :)
Thanks for having a look everybody :)
Jul 14 2014
Thanks sergey :)
Jun 27 2014
Forgot to add the version. Blender 7.61 2014-6-23 - 19:27
May 3 2014
You never stop learning. Thanks :)
Apr 14 2014
Mar 1 2014
Thanks CoDEmanX :)
Feb 27 2014
Huh? Why do you close this task? The bug is still valid and reproduceable. It was just a typoe in my original message that i was unable to fix.
Ah, sorry, wrong hotkey. It's Numpad 0 by default. But i use center view at selection very often, and the camera nearly never, so i have switched the keys here ...
Feb 24 2014
Thanks for having a look at it Campbell.
Feb 21 2014
Thanks for the support CoDEmanX. I would have nothing against a C implementation really. Would make me even happier to have this natively in Blender instead by a plugin :)
Feb 19 2014
Nov 26 2013
I see and accept that this issue will not be fixed.