Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ERR: Probe interpolation failed #174

Open
ddmrc opened this issue May 19, 2023 · 8 comments
Open

ERR: Probe interpolation failed #174

ddmrc opened this issue May 19, 2023 · 8 comments
Labels
Unreal Issues related to Unreal Engine integration

Comments

@ddmrc
Copy link

ddmrc commented May 19, 2023

Hello!

Platform: Windows, UE 5.1 (Standalone).

So I have baked the data, assigned it and even had it working once but all of the sudden this started to happen.

When I debug status it does show up the .ace asset and even the amount of probes. When I debug voxel or probes nothings shows up.

I also have done this for a smaller map and it works perfectly (this one currently holds around 1700 probes). Any ideas where can I start poking around to figure out how to fix this?

Thanks!

bugAcoustics

@MikeChemi
Copy link
Member

Because nothing shows up when you have voxels or probes visualization enabled, I'm wondering if you have a transform issue. Is your AcousticsSpace transform set to the origin?

The best way to debug this is to turn on the probe debug display and run around your scene until you find them.

@ddmrc
Copy link
Author

ddmrc commented May 19, 2023

With the debug (pre-bake) everything shows up. I am actually thinking that the .ace file may be corrupted? I'm doing it locally and it takes 13 hours on my computer so maybe something weird is happening? Because even when I import a smaller map bake data into this one it reads it properly.

@MikeChemi
Copy link
Member

Certainly possible, but because it tells you the amount of probes in the ACE file, I'm suspecting that's not the problem.

Any errors in the output log?

@ddmrc
Copy link
Author

ddmrc commented May 19, 2023

Nothing in the output, it just shoots the message in the image when I load the bake done for the bigger map. If you know of any other tests I can do that would be super helpful!

@MikeChemi MikeChemi added the Unreal Issues related to Unreal Engine integration label May 19, 2023
@MikeChemi
Copy link
Member

We really need to find where those probes/voxels are. On your acoustics space, if you turn on both Draw Probes and Draw Voxels, and set your voxel draw distance to something very large (like 100000), then run around while playing your scene, do you find probes or voxels anywhere? Or are they just completely missing?

@ddmrc
Copy link
Author

ddmrc commented May 19, 2023

Nothing, I even put the draw distance to 9999999.0.

That said I am taking a big fps hit when drawing, so they must be rendered somwhere I think. Also looked under the map but nothing. Maybe as you suggested they are offseted. Very weird, this has happened consistently when doing the same big data bake.

@esdete2
Copy link

esdete2 commented May 21, 2023

Because nothing shows up when you have voxels or probes visualization enabled, I'm wondering if you have a transform issue. Is your AcousticsSpace transform set to the origin?

Have you checked this? I had the same problem and for me the AcousticsSpace was offset. Simply set the Location values to 0.

@ddmrc
Copy link
Author

ddmrc commented May 21, 2023

I just did a test and did make sure that it was in Zero vector and it works! I actually do not know why my brain completely skipped that part of the message.

I do not remember if it was offseted before but reimported a new AcouticsSpace and set the absolute location to 0 and it seemed to fix it.

Still have to do some tests on the latest main version to see if it will work, as I am testing on a different branch but it seems like a solid fix.

Thank you so much!!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Unreal Issues related to Unreal Engine integration
Projects
None yet
Development

No branches or pull requests

3 participants