- User Since
- May 11 2011, 3:29 AM (483 w, 1 d)
I got this bug on the latest beta build, I know its marked as resolved but it just happened again, if I can reproduce it I will, but it seems to happen at random for now.
Sat, Aug 8
Yes that looks exactly like the problem I had, tho the issue seem to go away if just tell Blender to revert to factory settings, then I save that scene as my startup scene, I dont save the preferences after that tho as I still want my settings to remain as they were, all I did was to replace the startup with scene that is more compatible with that version of Blender, after doing that so far I had never encountered this issue again, I think the problem is due to having a startup scene that was created with a different version of Blender, say you created your startup with 2.83 and then updated to 2.83.4 that seems to screw the loading of files for some reason.
Hello, thank you for explaining this as well, for around 3 months I was puzzled as to why while I had deactivated the hotkeys on the Collection Manager I would still have my collections deactivated and activated by them, I would rather have all this type of behavior merged into one single system to avoid confusion to the user, the addon works very well so far :) but I dont like to use hotkeys to access my collections, I mainly use the addon to move objects from one collection to another, but for some people using hotkeys might be very useful, so by no means I'm of the idea to remove that option, I just thought it would be better to sort of merge this whole set of behaviors into one single system. I also understand you are not directly involved in the legacy systems of Blender, but since your addon is related to the same functionality as those Multiref systems I thought this would be a good thing to mention.
Thank you for the explanation :) form my own user experience the fact the collection manager has an option that fully disable the QCD system while Blender still has some part of the functionality regardless if the addon is active seems like an unnecessary redundancy, I get this hotkeys were there as part of the legacy systems of Blender, but if the add-on is mean to controls the QCD and it now shipping as part Blender then having those hotkeys by default seems necessary, and can cause confusion to the user, this is just my opinion tho, if the hotkeys stay where they are I can just deactivate them like you mentioned, still the way I see it they could be removed entirely and just use the addon as the main controller for that kind of behavior. Unless this hotkeys offers something in terms of functionality that the Collection Manager does not... but it does not seem like that, maybe Im wrong tho, cheers!
Fri, Aug 7
Ah! I found the problem, this was driving me nuts for while, there are some hot keys that are not related to the manager, that serve the purpose of hiding the QCD layers, and they are by default in the Key binds even of if the addon is not active, maybe those hotkeys should be controlled by the addon instead of just being there by deafult? go into the key binds and search for "hide" you will find this lists of hotkeys called: "Hide Collection", the operator coding string is: "object.hide_view_set" "Collection index 1" 2, 3, 4..etc... there's one for each of the number keys of the keyboard, after I disable all of them I no longer made the QCD layers visible or invisible anymore even of the addon was off, or the option for the hotkeys was ticked off.
I think I have found a bug, I will make an official report later but I wanted to inform you of this as soon as possible as its a rather strange problem, the QCD hotkeys are still active even if the addon is turned completely off in the addon manager, this is to say in 2.90 and 2.91 current builds if I click any of the numbers of my key board the layers assigned to the QCD will turn off and on, even if the addon is turned off, also while its turned on I tried to un tick the Hotkey option, I looked into the hot keys in the preferences and it indeed creates or deletes the hotkeys, however even if the hotkeys are deleted by un ticking the option in the addon, if I happen to click any of the numbers of my keyboard the layers will become invisible, its like the hotkey system is embedded into Blender some how, which is really frustrating as I dont really use the hotkey system so I rather have it off, but now if I accidentally hit any of the number keys my layers go away without me wishing to do so.
Fri, Jul 24
I was just wondering what the status for this problem is, I cant use 2.90 for some texture painting I need do for work atm so I'm really interested on a solution for this.
Wed, Jul 22
Sat, Jul 18
I have loaded the factory settings then saved a new startup file, then tried to open a file and that seems to have cleared the issue... some how the first file blender opens i.e. the default startup changes something that can corrupt the next file you try to open after you load Blender, If I can reproduce this error I will send the steps to do so.
And each time I try to open the file the strange exploding looks a bit different just the OP described.
I think I have gotten this error, at times I open a file at this happens, the thing is, this is a file I saved yesterday and opened and closed it several times after it was saved, however just now it decided to do this,
Tested on the latest 2.90 build that was made today, my video card is a gtx1080 my OS is Windows10.
Fri, Jul 17
Yep this is the same problem I have to a T, I hope a fix is found soon :)
Thu, Jul 16
Ok I got the simplified file working, here's the google drive link:
I think I got a simplified file that shows the problem,
and it does not have to do with bump maps because I disconnected all but a principled
shader an image texture and an output node and the problem is there, I'm organizing my files
and recording the steps now.
Thank you for the reply :)
I think I able to track the problem in terms of when the change happened that created it a bit more,
must have happened between the 2 of July and the 15 of July, I just downloaded this build, loaded my file and this strange brush problem is present in the build.
Jul 10 2020
I wanted to make a reply that was not quoting someone but I could not find an option to do it that is why Im quoting you, apologies for this, Im not a coder, just a Blender user that is interested on having the Voxel Mesher working, the reason for this post is just to share a screenshot of the last version I have of the Voxel Mesher, this version that was built on 2.83 and works really well from an end user perspective, and for example the text Im carving into the cube, that kind of Boolean can only be done reliably with the Voxel Modifier, even Zbrush has trouble with that kind of carving at times, not the Voxel Mesher tho, that modifier can work wonders even in its current state, Thank you so much for creating it :)
Jul 2 2020
Aug 28 2017
Hi, The problem is gone, :) thanks a lot, however in today's build the addon "loop tools" is not working.
Aug 25 2017
I know the guidelines, however in this case Im not sure what you need me to do, the video I attached shows very clearly what I did, which is try to use the functions of the F2 addon, by trying to create a quad from a vertex by clicking the key "F"
Aug 23 2017
Jul 19 2017
Any chance this might change in the near future so we can bake textures with alphas in Cycles?, this would be super useful for artist doing game textures, I know you can use Render Internal, but Cycles materials have a lot of options internal does not have, the only think it does not has, is the ability to bake alphas.
Jun 23 2017
I think I can confirm this bug on my machine, I have a Geforce Gtx760 and in 2.78c I'm getting random crashes like the ones described here,
Loop cut then crash, Ctrl+z then crash, delete face or vertex then crash, as the creator of this bug ticket said, all the crashes happened in edit mode.
Mar 11 2014
Thanks for fixing it! It was a real pain working with this bug, really thanks so much for fixing it.
Hi I was able to isolate the bug, now do this steps exactly as i wrote then
(i made sure I wrote the correct hot keys this time sorry about that)
this is one hard to nail bug, if you do anything else besides
the steps I wrote the bug hides and it appears as if you can duplicate
meshes with no problems, its a really sneaky problem this one.
Hi one thing on all the text above each time I write ctrl+d i mean to write shift+d you probably already figure that out but still
my brain got confused while writing.