Skip to content

Invalid field with v0.7 #23

Open
Open

Description

@tmetais

Hi,

We have updated OpenPGL to version 0.7. Overall, the update went smoothly, but I encountered an issue with the new version on a specific scene that was not present before.
After updating the Field with a batch of samples, the field becomes invalid, even though the sampleStorage itself is valid.

This scene contains some samples that are very far from the origin.
If I clamp the sample positions within [-100000, 100000], the field remains valid after the update.
However, what surprises me is that if I do not clamp the positions but instead call SetSceneBounds with [-100000, 100000], it does not fix the issue.

cheers,
Thomas

Activity

  1. changed the title [-]Invalid field with v7.0.7[/-] [+]Invalid field with v0.7[/+] on Mar 14, 2025
  2. sherholz-intel commented on May 19, 2025

    @sherholz-intel
    Contributor

    @tmetais thanks for reporting the issue.
    I looked into it and found the problem, which was related to the integer arithmetic used when building the spatial structure for extreme large scenes.

    Here is a fix for the problem, could you test it before we merge it into the devel branch?
    /fix/empty-invalid-regions-on-first-fit

    Cheers,

    Sebastian

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions