Germano, please see the .blend files, scripts are included and test scene is setup with extra instructions.
Ah, you're right. We use mediawiki template for the link which adds T (which i always forget). Fixed now!
Looking at the description its a simple out of ram issue.
Some things can get quite out of hand when it comes to ram use.
This issue slipped into 2.78b but it is fixed in current git. Will be ported to 2.78c which is planned tomorrow.
Sounds good! I think there's a typo in the link on the TODO page (TT instead of T).
Those are fully internal guts
Er... Can something that is clearly accessible to the user (Ctrl+Alt+Z) be considered "fully internal"? The basic logic behind proposals like these is that if users are able to see and/or manipulate some part of the program's state, it's reasonable to expect that it should be accessible to the scripts too.
Ok closing then.
I don't think such changes should be done for 2.79 instead of 2.80. Especially stuff like changing shortcuts and design guidelines. From a user POV these may not be trivial.
Also, when changing guidelines we should make sure there's wide agreement and then do it once and for all (more or less). We must not change any guidelines, just to change them again after a few releases.
Mathutils.BVHTree does not take into account the matrix when creating a bvhtree. It is as if bvhtree were using the local coordinates of the object.
That's why in raycasts or nearest, the ray or point need to be transformed with the inverse matrix.
For overlap you need to create the BVHTree with the object coordinates already transformed.
It is not practical to analyze possible errors in scripts that do not come with blender, you need to be more specific with the problem.
You can ask questions in the blenderartists.org forum to make sure it is a bug.
I just compiled the latest version and the fix is working perfectly! :)
Nice ! I dont see anything that raise concern. I will need this when I do edit mode overlay. Hopefully I'll be able to extend it to my needs.
hi, it could be too much to implement this now, might be a better 2.8 target? we still have not updated the contrib addons to the first panel location as option changes, if we want to do this, it needs to be all or none.
I do agree with the change. i think also we could look at adding the base code into addons_utils.py so it's accessible by all addons & not on a per addon base.
I am not convinced at all we should expose such things. Those are fully internal guts and exposing them must not be done as-is. I'm also not convinced with the reasoning you gave. There are following issues:
Much appreciated! I'll review closer later today.
Yes it can, there is no bug here, this is user assistance task and should not be handled vie this tracker. User forums like blenderartists.org or blender.stackexchange.com should be used for that matter.
There is no bug at all here, you are confusing to completely different things:
- Properties define using bpy.props are “real” RNA properties, they behave like built-in native properties of RNA structures. It changes the definition of the class itself, since it’s available in all its instances.
- Properties defined/accessed with the 'dict' interface are IDProperties (a.k.a. Custom Properties), only usable with some limited type of data (IDs mostly, plus a few other ones like Bone). It only affects an instance of the RNA class, others won't have it.
Can see two cases here. First one is the bevel not being orthogonal in the first case. This is caused by the bevel object rotated according to the curve twist, which is currently set to Minimal Twist. Using Z-Up with some manual control over the bottom CV will fix this issue.
My example was an extreme edge case to illustrate a more subtle problem. I think the issue here is that, regardless of the intended behavior, the curve bevel feature has created an expectation (a mathematical axiom) in the mind of the average user. The axiom is that a cross section normal to the curve at any point should be identical to the bevel object in shape and size. 2D curves always follow this axiom, but 3D curves only follow it part of the time. The way it is now, the tool cannot be used to create certain common shapes, like handrails, etc. See the attached .blend file for an example. If we don't want to break the existing functionality, maybe we should add an option to address this use case, like a checkbox on 3D curves called "Consistent Width" or something. Thoughts?
Can Blender run on Intel HD Graphic 5500? I plan to learn Blender now but very confuse about which notebook should I buy?
Could you delete my account as well, and wipe all personal data?
Well the purpose of Proxy textures is to do a small check for weak hardware. This was never intended to be a full OOM handling. This was designed for 3D textures and I ported it to other type. But it's sure that a video memory manager would be very handy if not vital. Ton already suggested we worked on one but there is no plan for now.
I just tried with 2.78-9992e6a169 AMD driver 15.20.3 (I cat seem to upgrade to 15.302 (ubuntu15.10))
Crashed right away.mirco_test.crash.txt
Ok will do... -.-
Sorry, this is not the right place for end user support, please seek user support on user forums like blenderartists.org or blender.stackexchange.com.
The tabs should be ok now ( my method of submitting the diff by copy/paste created the error).
Then how can I subdivide the face? :) Please help.
I also see a issue when a mesh has UV and bevel applied the UV seam is added to the bevel. This results in weird UV mapping when its rendered. When i play with segments i get different outcomes. This same thing is for edge crease, bevel weight and sharp edges. All of these items get applied to the new created segemnts of the bevel resulting in weird and unwanted behavior.