Creating Issues in Vrex

Contents

    Issues in Vrex are digital snapshots of the 3D model that capture a specific view, selected objects, and annotations.

    While issues are often used to document problems or required changes, they can also be used as contextual notes to capture discussions, decisions, or observations directly in the model.

    Who Can Create Issues

    To create issues in Vrex, you must be a member of a Vrex Project. Guests cannot create or view issues.

    Common Use Cases for Issues

    Issues in Vrex can be used to:

    • Document design clashes or constructability challenges
    • Track required design changes
    • Capture discussions and design decisions
    • Add notes while reviewing or navigating the model
    • Highlight areas that require follow-up or future review
    • Track questions, tasks, or observations tied to specific model locations

    How to Create Issues

    Watch the video below for a quick overview, or follow the written steps to learn how to create issues in Vrex

    Video Walkthrough:

    How to Create Issues in Vrex

    Written Steps:

    Open a Project
    Launch the Vrex desktop application and open the project where you want to create an issue
    Navigate to the location of the Issue
    Using the navigation tools, navigate to the location you wish to create an issue of.
    Optional: Prepare your View by selecting related objects and adjusting model visibility as needed
    Use:
    – The object tools (hide and select) and clipping tool to set visibility.
    – The draw tool for markups
    – The measure tool to add measurements
    Click on Create Issue
    You’ll find the create issue function in the bottom right tab
    Select Issue Storage Location/Data Source
    The selected issue location determines where it is available, who can access the issue and how it can be exported.
    Issues can be stored in one of the following locations:

    Vrex
    Best for shared project issues managed in Vrex
    – Issues are stored directly in Vrex
    – Available to all members of the project
    – Can be viewed and exported through the Vrex web application at www.vrex.no, depending on role and permissions

    Third-party integrations
    Best for issues managed in external systems
    – Issues are stored in connected platforms such as BIMcollab, Aconex, Newforma Konekt, and other supported integrations
    – Issues are visible in the Vrex Viewer to users who are members of both the Vrex project and the connected third-party project
    – Access and permissions are controlled by the third-party integration

    Local BCF folder
    Best for private or personal issues
    – Issues are private to the user who created them
    – Available in the local BCF folder for export
    Create a Viewpoint
    Left-click in the 3D model at the relevant location to create a viewpoint. This ensures the issue is clearly connected to the correct context.

    A viewpoint is a saved, specific 3D camera position and state (visibility, sectioning, zoom) that visually captures a design conflict, question, or task. It acts as a “snapshot” within a BCF (BIM Collaboration Format) file, allowing team members to immediately jump to the exact location of an issue in their own software.
    Add Issue Details
    Enter the relevant information, such as title, description, status, priority, assignee etc.
    Save the Issue
    Click the save button to save the issue

    FAQs

    Who can see the issues I create?

    Visibility depends on where the issue is stored. Issues stored in Vrex are shared with the project, while local BCF issues are private to the creator.

    What information is saved in an issue?

    An issue saves viewpoints (specific 3D camera position and visibility state), annotations and measurement, and associated issue information such as title, description, comments etc.

    Can I change where an issue is stored after creating it?

    No. The storage location is set when the issue is created. To change it, you must create a new issue.

    What happens if I store an issue in the Local BCF folder?

    The issue is saved locally, is private to you, and can be exported from your local BCF folder.

    Was this article helpful?