fixed small issues
In DisableForText() function, GL_ALPHA_TEST is disabled. This causes this issue with my patch when the text is in front of plane: http://www.pasteall.org/pic/93763
Issue is caused by winding & vert of faces used to 'start the loop' (dupliface uses a 'face space' to orient dupliobject, onae axis (the normal) is easy to get, but the two other ones are more or less 'random' chosen, here based on first vert in each face loop. So there is no real bug here, it’s more a matter of TODO to find better ways to define face spaces, but that’s not a tracker topic really. Thanks for the report anyway.
Just set import scale to 100 and everything is OK.
Guys i m really really really sorry that i didn't come back to answer, may be you have guessed that since i didn't come back i didn't have that problem (bug )anymore. So i tested it with latest build my own and buildbot everything went just fine. So thanks for closing it.
I have a fix for this but would prefer to commit it after the release so that there is time to test it properly, since this is quite fragile code with many tweaks over the years.
thanks for the explanation!.
Thanks, committed (https://developer.blender.org/rBTS3824), will try to get this in final 2.76 as well…
I upgraded to Xcode 7 and can now also see the issue in my own builds when using the 10.11 SDK. It seems beginGestureWithEvent and endGestureWithEvent are no longer called. Other seems to have encountered the same issue:
Hi Alex, just checked the file on my machine with your patch. Everything seems to work fine.
I do not see any issue with your file really… this looks like user support to me, not bug report, please ask for help on forums & co (blenderartists.org, http://blender.stackexchange.com/, etc.) before making a report. E.g. if you have your Camera.002 selected together with an airport building, yes, view will zoom out heavily when hitting 'view all' . shortcut…
Please only report one issue per report. I’ll remove the jpeg one from this one, please create a new report for it.
ill rebuild RC3 with 6.4 and upload somewhere to test this today or early tomorrow
There was one change and that on investigating a report on XCode 7 that was upgraded.
@Rainer Blümel (Red-Shirt) Please just attach here the PO file (no need for MO one), I will commit it to DE translation branch.
Sorry, my mistake, what i meant is the blender versions 2.76-rc1 to rc3.
As currently no one is working on the German translation I have downloaded the current Po-File and changed the faulty umlauts. Now it no longer hurts in my eyes.
If someone is interested in the amended Po-File or MO-File please send a message.
Hi, tested your new file with my workstation but no freeze or crash.
Preview render work until the 10 appointed samples .
Ok, that is super. Because i realy would like to see this Function added to Blender.
Then thanks a lot for your fast answers.
Fixed the 'missing xxx pycontext' messages, would not really expect those to cause the crash though.
I cannot confirm this on osx. works ok here. Please drag drop error files to git rather than paste wall of text.
Assigning to @Campbell Barton (campbellbarton)
This file requires around 1.3gig of ram in peak (on 32bit linux system, where memory allocation is a bit better due to less fragmentation) which might be a tight fit for your 32bit system.
I've checked, it works fine in 2.75a and stop work in 2.76 rc1
I'm not sure what do you mean "reliable". scene_update callbacks are called when it's needed to make sure whatever scene is up to date (by applying animation, drivers, re-calculationg constraints and so on). If no scene is involved into render process, then render pipeline surely wouldn't be updating any of the scenes.
I am cloning the 64 lib for building 64 version. It may take a while
Thanks for the report :)
Cool thanks... Still trying to set up my build involvement
There already is a note to that effect here (more or less): http://blender.org/manual/about/markup_style_guide.html#table-of-contents
Never-mind the web version was not updated yet. It is rebuilt now and looks a lot better. You may want to add to the writing style to keep indexes shorter.
@Aaron Carlisle (Blendify) Not sure what you mean..?
Is there any way to removing the links to the options and technical details for the procedural textures?
No need to make your own build to test this.
I'm not building it myself (and won't likely have time to set that up today, but I can test tomorrow), but my xcode version is 7.0.1, if that makes any difference.
Trying with a magic mouse, I can see the issue, it works fine in 2.76RC1 but in 2.76RC2 it's zooming when trying to rotate. In my own build of the latest master and the latest build from builder.blender.org it works fine though, so it definitely seems like it's something in the build environment.
See here for a more in depth explanation of this mechanism:
Please define what you mean by storing "relative transformation". Relative to child and parent?
Here's a .blend with the texture packed cycles_volume_UV_crash.blend
This is a feature, the child object stores the relative transformation at the time of parent and keeps using it, you can use Shift-Ctrl-P instead if you don't want this behavior.
They are not the same as cycles textures (BI and cycles have separate procedural textures), but I see what you mean about going too deep.
And actually these textures AFAIK are the same for cycles so maybe all this information should be moved to a different location
well the procedural texture section there is no need for it too link to the sub-pages for each node. So basically the tree is two in depth for a lot of sections
Could you define what needs to be done? (e.g. what pages should be moved where, or how the section should be re-done?)
I got a crash once when accidentally connecting the point density node to the displacement output
Hi, cant reproduce crash or freeze but texture is not included.
Tested with own .png
I am experiencing the same issue on 2014 macbook pro. Trackpad gestures work fine in 2.75a but not in 2.76 RC3
Please follow our submission template and guidelines and make a complete, valid bug report, with required info, precise description of the issue, precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.
This is just a complete mirage… You have the feeling it’s rendering quicker, because dragging the mouse that way forces tens of updates of the Image space each second, while by default it only refresh once or twice a second during render (which enhances render time, btw, since it consumes less CPU cycles and avoids too much locking between threads too)…
But I Can Send You This:
Windows 7 Ultimate 64-bit
Using AMD a6-6400k
I have not changed a single thing in the file. I have asked other users to tell me if it did the same for them,but they used their own files and it happened to them also.