Skip to content

bug: packing files is immensely unclear #7

@Rokonuxa

Description

@Rokonuxa

Bug Report

engon version:

1.6.1

Current behavior:

Several methods of packing, localizing, extracting or changing appended assets are simply nonresponsive.
Others SEEM to work, but leave me with completely empty objects without any data, full of errors and just generally do not work.

Expected behavior:

When I click "make local", the thing on which I clicked that, gets turned local. As described by tooltips, documentations and so on.

Steps to reproduce:

Use the outliner options, which usually would make linked data local to the current file and observe as it does not do that.

Other information:

If this is needed in some way, for whatever reason, including an engon-specific way to do it anyways, like with a sidebar menu for example, would be ideal.
If engon assets are not intended to be made local at all, a good alternative would be a clear method of re-linking assets when a file has been transferred to another machine. For example, my second PC, made specifically for rendering, that is in the next room about 5 meters away from where I am typing this.
As I am not a company, both machines are mine, I have the relevant assets on both machines.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions