Dupligroup made out of a linked file object do not render on network. #40166

Closed
opened 2014-05-12 19:41:15 +02:00 by Yegor · 9 comments

System Information
CentOS 6, Nvidia Titan

Blender Version
Broken: 2.70 19e627c and 2.70a official
Worked: (optional)

Short description of error
Dupligroup made out of a linked file object do not render on network (cycles).

Exact steps for others to reproduce the error
Make and Object1. Link an Object2 from a file. Make a group out of Object2. For Object1 in object->duplication->group select that group with the Object2.
Object2 won't appear on render. Renders fine on a local machine.

**System Information** CentOS 6, Nvidia Titan **Blender Version** Broken: 2.70 19e627c and 2.70a official Worked: (optional) **Short description of error** Dupligroup made out of a linked file object do not render on network (cycles). **Exact steps for others to reproduce the error** Make and Object1. Link an Object2 from a file. Make a group out of Object2. For Object1 in object->duplication->group select that group with the Object2. Object2 won't appear on render. Renders fine on a local machine.
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @YegorSmirnov

Added subscriber: @YegorSmirnov

Added subscriber: @Sergey

Added subscriber: @Sergey

Please always attach .blend files which demonstrates the issue. For now i only have one clue: objects were linked with absolute path, so opening file from another computer wouldn't work unless you store files on exactly the same location.

But it's also unclear, are you using some sort of network render or just open files with blender on another machine?

Please always attach .blend files which demonstrates the issue. For now i only have one clue: objects were linked with absolute path, so opening file from another computer wouldn't work unless you store files on exactly the same location. But it's also unclear, are you using some sort of network render or just open files with blender on another machine?
Author

Sorry for that. Here they are. Two files, one of them is the reference for another (network_render_test.blend is the main one). And i'm rendering using "network render" with Cycles (render farm - to clarify), not just on the other machine on network. The linkage is relative.
network_render_reference_test.blend
network_render_test.blend

Sorry for that. Here they are. Two files, one of them is the reference for another (network_render_test.blend is the main one). And i'm rendering using "network render" with Cycles (render farm - to clarify), not just on the other machine on network. The linkage is relative. [network_render_reference_test.blend](https://archive.blender.org/developer/F88795/network_render_reference_test.blend) [network_render_test.blend](https://archive.blender.org/developer/F88796/network_render_test.blend)
Author

Please, confirm the bug. It's quite crucial for complex simulation projects with object instancing using.

Please, confirm the bug. It's quite crucial for complex simulation projects with object instancing using.

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Sergey Sharybin self-assigned this 2014-05-20 14:03:15 +02:00

Network render addon is currently missing a maintainer, and for my knowledge it never dealed with the libraries.

What you can do is to pack libraries into .blend file before sending to the render (you'll find it in the space-bar menu).

For until we've got network render addon maintainer would consider this is a TODO. Can't update official list in wiki atm because of maintaince there, but as soon as maintaince is done will update the list.

Network render addon is currently missing a maintainer, and for my knowledge it never dealed with the libraries. What you can do is to pack libraries into .blend file before sending to the render (you'll find it in the space-bar menu). For until we've got network render addon maintainer would consider this is a TODO. Can't update official list in wiki atm because of maintaince there, but as soon as maintaince is done will update the list.
Author

Packing libraries did the trick! Thanks a lot!

Packing libraries did the trick! Thanks a lot!
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#40166
No description provided.