It's fixed.
Something along the way must have been fixed, it don't crash at that point any more.
closed.

Hi Yash, welcome to Blender.
Unfortunately this is not a forum for questions. It is for bugs and bug tracking.
A good place to post your question is over at BlenderArtists.org
For Python more specifically the python forum at BlenderArtists:
https://blenderartists.org/forum/forumdisplay.php?11-Python-Support

@venomgfx Is this yours Pablo?

You can write 16 colon 9 hit okay.
Or as below 400 colon 24 > hit okay.

In D2988#70751, @Inês Almeida (brita_) wrote:

Submitted 87607254d6d

@Joel Godin (FloridaJo) maybe you have a problem in your setup? Can you see any other changes that you make? Drop by IRC #blendercoders if you need help setting up or getting patches with arcanist!

Okay, call me a noob, but I made the changes, built and I don't see that action on macOs.
Screenshots from Xcode :

I can't reproduce here on macOS.
Zoom in, zoom out, fullscreen, perspective, ortho, '.'
Constraint axis is always there for me.

If you are in Local view instead of Global, it will not be there.

Okay, yes, if you add landscape from the menu as opposed to the button on the 'create' tab this happens.
Should be a warning or contextually removed from menu in edit mode.

Have you tried the latest build bot version?

You have to read instructions usually in order to know how to use something.
Read this page: https://github.com/s-leger/archipack/wiki/Setup#download-and-setup-default-material-library
You will see this:

Please read how to report a bug. Title is not a desription.

I have 10.13 also, but no error shows up.
I used 12.20 build

Sorry, maybe somebody else wants to, but I'm not going to download half a Gig file.

Hello Rafal,
Probably a language barrier here. Are you saying you create a subsurfed object in 2.78, and when you open it in 2.79 it is not working?
If so, I did just that. Placed a UV sphere in 2.78, hit control 2 to add subsurf level 2, and then save that file. I opened it in 2.79 and it is working the same, in other words it is subsurfed.
If you can explain the issue you are experiencing a little more that would be good.

Actually it works when manually sliding the Factor slide, but when the Factor is slid within the timeline with keyframes, it does not.
In other words:
Diffuse and Transparent through Mix -> View Material with ViewPort Alpha set to Alpha Blend
Sliding factor shows changes in viewport,
Sliding factor via keyframes does not show changes in viewport.

I can't verify that here.
2.79 Master and 2.79 buildbot render a ball for me.

Try a later version from build bot. Bugs have recently been squashed on these.

ah, must have been fixed recently. 12-13 build does not do that here.

It downloaded for me okay.

@Joey Bennett (Joey_Blendhead) Joey, I started reducing this bug, but it's a massive node layout, can you do that? Delete things until you get to the minimum node setup where that still is outputting black?

Change this node from Multiply to Mix.
See if that fixes it for you. Everything else besides Mix, makes it black.
In the meantime, I'll see if I can recreate with a simpler set up.

Didn't crash on my machine (osx)

Please separate these bugs. Only one bug per report :)

Yep, built this in macOS and works there too.
Thanks

I didn't see it go spastic like that, but it does make huge jumps on my machine.

Not seeing that here on macOS.
Works on 11-30 and just now on 12-05 builds

Not seeing that here on macOS on either 2.79 release or latest buildbot.

Sounds like your numpad is not enabled.
This is the action that happens when you press the numbers across the top.
It enables layers.

Please read how to properly report bugs.
This is not enough information to go on.
You can read how to properly report here: https://wiki.blender.org/index.php/Dev:Doc/Process/Bug_Reports

Not seeing that here on macOS, blender version 11-30

The comment about trying all the mice laying around can throw one off.

@Brecht Van Lommel (brecht) similar to bevel bug

@Brecht Van Lommel (brecht) Interesting the Inset has the same bug.
I was waiting to see if the correction would fix that too, but Dec 1 build still have the issue with inset.
I will submit a new bug report for that.

My 10.13.1 works.
Can you download the latest 2.79 from build bot and use factory settings to see how that works for you?

Just dummy objects. That's what I thought you meant by "alternatively, delete hidden objects. "

Played at about 5 fps,
then deleted Dummy Hair and Dummy Clothing, no difference in playback.
That was with 2.79

Didn't see that here on OSX.
Try my file I just opened yours and saved it again with no changes.
It may be that the file was corrupted.

Have you tried reverting to factory settings (don't worry, it won't save that way unless you tell it to)
and disable any addons you enabled?

Yes, that fixed it.
Thanks

oh, okay, thanks.

@Joshua Leung (aligorith)
Can you take a look at this Joshua?

Have you tried a recent version from BuildBot?
There used to be an issue, I think it's been fixed in a later build.

True.
If you set IOR to 1.0, it turns black.

@Sergey Sharybin (sergey) wrong Rob, try @rob (blenderpedia)

I see that too.
Don't know enough about nodes to know if its a bug or not.

On 11 - 8 and 11 - 12 build on 27" Mac, and works fine here.

In 3D view, 'N' brings up the properties panel.
It is under the heading 'view'.

Not seeing any vid.

Happens here on OSX as well.
crash report attached.

@LazyDodo (LazyDodo) I guess the Blender docs are wrong then. I doesn't say 'only on OSX and Linux'.

Not sure if connected issue, but 'inset' also has a weird glitch where a second 'inset' insets to the same proportion as the first.
One small move of the mouse and it jumps back to normal size (just less than original face size).
Will wait for developer to see if issues are connected before generating bug report for this as well.

Also OSX here, but have never seen that.

Not seeing that here.
Can you upload your crash report?

True.

Because you have 'Lock Object' to plane.
Click the x to remove the constraint.

Also, upon opening, the vertex 'X' position is .00078. If you manually change it to something like .00079 and above or .00076 and below, it works normally.

If I pack external data, it no longer crashes.
You have to import, then export > crash.
If you import, pack, export, > no crash.

Happens here on OSX as well. Oct 24 build.
crash log here:

This has already been reported here: T53145

Yes. Same here on OSX 10-26 build.

Same here on OSX. oct 26th build

This is about as 'incomplete' as they come.
Please read https://wiki.blender.org/index.php/Dev:Doc/Process/Bug_Reports

@Campbell Barton (campbellbarton) I'm guessing this is either yours or Brechts?

Probably when denoting USD should be a decimal, but on the other hand, different countries us the comma instead of the decimal.:
https://www.quora.com/Which-countries-other-than-Germany-use-a-comma-in-place-of-the-decimal-point

Have you tried 2.79?

@venomgfx Pablo I think this is your area?

@rob (blenderpedia) Okay, gotcha.

@Brecht Van Lommel (brecht) I'm not sure he did the OpenMP test as you described.
The video showed him changing threads in the UI as opposed to a command line command. Is that the same?
Rob, can you verify that you ran this in command line?

I see the same thing, and I'm drawing with a mouse.
I tried several setting changes in smoothness and iterations.
First pic is Blender second is another animating program that draws vector graphics.
I don't know though if Blender was programmed to draw grease pencil in vector or not though.

It doesn't look like it's the CPU.
You may want to see if it is a GPU bottleneck.
GPUview is the tool for that, a description of it is here;
https://graphics.stanford.edu/~mdfisher/GPUView.html

Hello Rob.
Can you go to this page and follow the instructions for installing the Microsoft Process Explorer
to better show the threads running during that process?

Sounds like it's reading it as a QWERTY keyboard.
If it was a bug for German keyboards I'm sure we would have heard about it by now.
Have you tried another computer or another keyboard on that computer?

@Bastien Montagne (mont29) Then why when manually changing the seed does the hair change position?

True. Rendered image out also does not change.
#frame in seed does change seed, but does not change hair location.
Seems to work for emitter particles.
Similar to T50331 deps graph issue? @Sergey Sharybin (sergey)

I loaded Houdini Apprentice, did as you said and although it didn't crash, it does have some artifacts in the display (see image)
(exported from OSX version)

No crash here on OSX.

Couldn't crash here on OSX.

Sorry, not enough to go on here.
Please read about creating a proper bug report :
https://wiki.blender.org/index.php/Dev:Doc/Process/Bug_Reports

In T52840#461281, @Carlo Andreacchio (candreacchio) wrote:

@Joel Godin (FloridaJo) are you using the new depsgraph and a nightly build? it probably needs to be newer than the 14th of september.

Yes, but it's been like that for eons. Possible because in 2D 'Y' is up, and 3D (blender and others not to mention CNC) Z is up.
Anyway, to change it now would break all files back to 2.46.
Not a bug, sorry.

Not seeing that here on OSX. Feather feathers, and V - A adds handles. Not sure if correctly but I see handles.

.obj files do not contain material information.
More info here: https://gamedev.stackexchange.com/questions/21303/how-can-i-include-vertex-color-information-in-obj-files/66270#66270

When I import the svg to QCad, it shows up as 13.5 mm .
My guess after reading some forums is that CorelDraw does not export with the same dimensional units as blender imports with io_curve_svg.