Objects added in 'Local view' don't get assigned to any layer #50133

New Issue

Ray Mairlot · 2016-11-28T18:01:05+01:00

Ray Mairlot commented

2016-11-28 18:01:05 +01:00

System Information
Windows 10 64-bit, Nvidia gtx 570 (render), Nvidia gt 610 (display)

Blender Version
Broken: 841f3e4 (Latest Windows 64-bit build)
Worked: -

Short description of error

I have a specific file that when adding new objects in Local view the new objects do not have any layers assigned (as observed in the Object> Relations panel under Layers). The objects do get layers assigned upon exiting Local view.

I can't replicate this error with other files and it doesn't happen if I re-renter Local view after exiting it.

The file isn't mine (but I have permission to upload it) so I don't know the steps that were taken to create the scenario where this does happen, so I know this bug report may only be of limited use, but I thought I would report it anyway.

The problem came up on http:blender.stackexchange.com/questions/67940/cycles-render-result-doesnt-match-render-view when a user noticed that their renders (from withinLocal view*) did not show all the objects that were visible in the viewport. The fix was to manually assign layers to the object or exit and re-enter*Local view//.

Exact steps for others to reproduce the error

Open the file local view no layers bug.blend
Add a new object, e.g. Shift+A> Mesh> Plane
See that under Object> Relations> Layers the object isn't assigned a layer.
Exit and re-renter Local view to see that new objects now get layers correctly assigned

**System Information** Windows 10 64-bit, Nvidia gtx 570 (render), Nvidia gt 610 (display) **Blender Version** Broken: 841f3e4 (Latest Windows 64-bit build) Worked: - **Short description of error** I have a specific file that when adding new objects in *Local view* the new objects do not have any layers assigned (as observed in the *Object> Relations* panel under *Layers*). The objects *do* get layers assigned upon exiting *Local view*. I can't replicate this error with other files and it doesn't happen if I re-renter *Local view* after exiting it. The file isn't mine (but I have permission to upload it) so I don't know the steps that were taken to create the scenario where this does happen, so I know this bug report may only be of limited use, but I thought I would report it anyway. The problem came up on http:*blender.stackexchange.com/questions/67940/cycles-render-result-doesnt-match-render-view when a user noticed that their renders (from within*Local view*) did not show all the objects that were visible in the viewport. The fix was to manually assign layers to the object or exit and re-enter*Local view//. **Exact steps for others to reproduce the error** - Open the file [local view no layers bug.blend](https://archive.blender.org/developer/F407179/local_view_no_layers_bug.blend) - Add a new object, e.g. *Shift+A> Mesh> Plane* - See that under *Object> Relations> Layers* the object isn't assigned a layer. - Exit and re-renter *Local view* to see that new objects now get layers correctly assigned

Ray Mairlot commented

2016-11-28 18:01:05 +01:00

Changed status to: 'Open'

Ray Mairlot commented

2016-11-28 18:01:05 +01:00

Added subscriber: @RayMairlot

Anthony Edlin commented

2016-11-29 01:25:37 +01:00

Added subscriber: @AnthonyEdlin

Anthony Edlin commented

2016-11-29 01:25:37 +01:00

Yeah it is strange, the v3d->layact is binary 1000000000000000000000000 which has local view flag but no active layer set, so new object is only on local view. Switching almost anything and layact becomes normal. Can't really do much unless we can reproduce what makes it get screwed up.