- User Since
- Mar 1 2010, 6:51 AM (642 w, 6 d)
Wed, Jun 15
Wed, Jun 8
Fri, Jun 3
just testing here
i pick the file export stl (scale 1000) and it works fine in prusa slicer no issues.
Reimported the stl and seems to be fine (that cut its viewport clip)
Fri, May 27
I have the blender defaults color management and notice the same behaviuor with the test file provided in the comments(following the steps).
With the blender default i can reproduce the problem, its using the Color management options instead of saving linear. This may or not be a big issue but something to consider, however we also notice a second big (huge) issue that could be related to this, saving exr files using the console can no longer be opened with Krita, it returns an error
(QString::arg: Argument missing: Loading canceled. Error:)
nor can be opened in djview imagin 2.0.6
Apr 25 2022
Apr 22 2022
Apr 3 2022
Apr 1 2022
Mar 10 2022
Feb 17 2022
Feb 3 2022
i can't reproduce the problem using the sphere file in the comments, however im under linux ubuntu 20
Jan 2 2022
Dec 26 2021
a third open question i may add is,
what its going to happen with the clipping option and the chance that the modifier has to detect the symmetry plane and not create faces when extruding along it? maybe a selection output to filter this and to be able to connected to a delete it?
Dec 8 2021
Nov 30 2021
@Julian Eisel (Severin) I just found out a consistent way to trigger the bug, cursor movement.
1 Open blender
2 start moving the mouse cursor
3 While moving the mouse cursor press shift+f1 twice
Nov 26 2021
@Pratik Borhade (PratikPB2123) i just tested the release candidate and it crashes consistently with the instructions in the last message
Nov 17 2021
@Pratik Borhade (PratikPB2123) im testing it under ubuntu, ill try to test it under windows later, maybe random or may be the OS, im not sure i wasn't able to pinpoint the secuence to trigger the bug, but the undo was a variable in all crashes
Nov 16 2021
sorry @pratik cirkleinc (pratik) Borhade (PratikPB2123) i tag you by mistake and im not sure how unsuscribe you from this task
hi @Pratik Borhade (PratikPB2123) i admit getting to it crashing was harder this time than yesterdays, in this case i have to play a bit more disconnecting uvs from the grid texture and switching uvs in the data click back and forward, basically all i did in the video but it was quite random hope there is a pattern in the logs
Oct 4 2021
Sep 25 2021
Aug 20 2021
@Nahuel Belich (belich): should we hunt this down further or is working with the dedicated nodes sufficient?
@Philipp Oeser (lichtwerk) i just test 2.93.3 and works the same as in the original report, in edit mode, the attribute fill changes the material in the viewport for the geometry generated in the node group the expected behavior, however doesn't work in object mode, since its a LTS version its probably something to at least look twice. If the mesh its generated outside the node network attribute fill works perfect, for geometry generated in node doesn't work as expected.
3.0 today does the same but 3.0 its under heavy development there are other nodes so i don't consider so important to lose time there, the issue its the lts, if this would be 2.92 i would say that its not that important but in 2.93 the behaviour its not consistent from a user point of view its like if its only being evaluated in edit mode and skipping something in object mode
May 20 2021
tested todays new material node, works perfect in 3.0 alpha
May 19 2021
i just tested hash: 33fecc9b7f6 and the geometry injected using object info works as it should, however the geometry generated inside the node networks still fails in rendering the assigned material slot.
Material index 1 should be red.
May 5 2021
just test it with todays 3.0 build, still happening the same, works in edit mode but not in object mode, even more, it renders properly if i press f12 while the objects are in edit mode.
version: 3.0.0 Alpha, branch: master, commit date: 2021-05-04 15:30, hash: 87ee8ddfe36a, type: Release
build date: 2021-05-04, 18:18:57
Apr 25 2021
is it by design or limitation for the area light to turn into a circle in the glossy rays ?
Apr 24 2021
Apr 20 2021
did you try file>defaults>load factorysettings?, just to be sure that its not a add on or something else outside blender creating the issue, also you could try the latest 2.93 beta (builder.blender.org) just to see if the problem persists in more modern versions
Apr 17 2021
Apr 12 2021
Mar 30 2021
Mar 21 2021
Mar 19 2021
Mar 17 2021
Feb 25 2021
@Sebastian Parborg (zeddb)
This is becoming a bit weirder than my artist brain can understand, first the tests.
Feb 24 2021
@Sebastian Parborg (zeddb) ill try tonight and let you know
Feb 23 2021
Feb 1 2021
Dec 23 2020
Dec 22 2020
Nov 21 2020
hi @Demeter Dzadik (Mets)
Im talking about objetct constraints not bone constraints, objects can have an armature constraint, i guess it was introduce in 2.83,
This operator copies the constraint properly from object to object .
The problem its with the add on, this option copies the armature constraint (on the object, object level) but ignores its configuration
As far as i see this is the only constraint with this problem but i need to test more, didn't test every constraint maybe others has issues too
Nov 20 2020
Nov 12 2020
Nov 9 2020
Nov 4 2020
Sep 27 2020
Sep 26 2020
Sep 16 2020
Sep 6 2020
Jul 15 2020
Jun 25 2020
Jun 12 2020
Jun 6 2020
Jun 4 2020
hi, is there any news with this patch? it would be really handy to have a solution for the custom normal's issue during merging.
May 26 2020
May 6 2020
yes it doesn't make any sense to use those values, i found by accident that i can put those values, when i try to reproduce it i though it was an issue with selecting the four sliders at the same time and changing all the values at once but i was able to input the zeros one by one with no warning or the software canceling the input.
I made the report simply because it looked really weird but im not sure if it was an interface bug or just a WIP.
May 5 2020
Apr 29 2020
Apr 16 2020
Apr 14 2020
Apr 9 2020
Mar 31 2020
Mar 23 2020
Mar 20 2020
Mar 16 2020
Mar 9 2020
Feb 10 2020
I just fund out, im used to work with the origin of the object at 0,0,0 so to modifie the place and shape of the domain I use edit mode, it seems that mantaflow likes the origin in the center of the domain.
Not sure at this point if this is a bug or intended but its really weird and didn't see any entry/note about this in the manual besides this
Feb 4 2020
Jan 29 2020
Jan 18 2020
Dec 10 2019
Can confirm, that particular color theme its not being saved (HASH: 1a8642937dde )
Dec 2 2019
can confirm, the viewport clip its not clipping selection or tools like polybuild, however poly build doesn't care if xray its on or off.
I was about to do the report but i was busy, thanks.
Nov 28 2019
Marcin Twarowski, yes you are right its fixed, i didn't realize that much time had past since the last time i update my build.
Sorry guys my bad
Nov 20 2019
that only origin its the same that we have in 2.79 try adding a few more objects and try rotate and scale them whit that turn on and off.
Nov 17 2019
tested the last chair with a 2.82 win 7 nvidia 1070
Doesn't crash. . .
However it moves really slow in my machine(i have an nvidia 1070 and it moves slow) looking the file and there are some crazy shader groups, that makes my gpu ask for mercy.
This node group its inside the material "Cedar Wood" its connected to the color of the shader.