just testing here
i pick the file export stl (scale 1000) and it works fine in prusa slicer no issues.

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

In T97550#1346156, @Philipp Oeser (lichtwerk) wrote:

That is a duplicate of T70372: Export FBX shape keys are not read back when re-importing on Blender., no?
That is because you cannot apply modifiers with shapekeys, this works if you have the Apply Modifiers option OFF, right?

i can't reproduce the problem using the sphere file in the comments, however im under linux ubuntu 20

In T94574#1281553, @Tomas (Rusculleda) wrote:

I might be wrong but I think that is expected behavior. Collection info node outputs an instance. If you add a realize instances after collection info it works. The same way, if you turned on "as instance" in the object info nodes it would have the same behavior.

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?

@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

@Pratik Borhade (PratikPB2123) i just tested the release candidate and it crashes consistently with the instructions in the last message

@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

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

@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

tested todays new material node, works perfect in 3.0 alpha

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.

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.

is it by design or limitation for the area light to turn into a circle in the glossy rays ?

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

@Sebastian Parborg (zeddb)
This is becoming a bit weirder than my artist brain can understand, first the tests.

@Sebastian Parborg (zeddb) ill try tonight and let you know

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 .

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.

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.

@Sebastian Parborg (zeddb) this is looking a lot better with today's build, could this be fixed by the updates that @Clément Foucault (fclem) did the lasts weeks?

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

Can confirm, that particular color theme its not being saved (HASH: 1a8642937dde )

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.

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

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.
https://docs.blender.org/manual/en/latest/scene_layout/object/editing/transform/control/pivot_point/index.html

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.