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

Raytracer crash with a blocker #3

Open
dingzeyuli opened this issue May 2, 2017 · 6 comments
Open

Raytracer crash with a blocker #3

dingzeyuli opened this issue May 2, 2017 · 6 comments
Labels

Comments

@dingzeyuli
Copy link

Hi, when I try to do the auralization in a scene like this, the raytracer keeps crashing. The only new element in this scene is the center blocker. I tried to increase the reflection order, it seems to help a little bit, but overall the IMS module still crashes when I move the source around the blocker.

Usually the plugin can be fixed by simply stopping and starting the raytracing module and the on-the-fly aurualization. Do you guys know what might cause this problem? Any possible loophole in the raytracer in the case of multiple bounces? Thank you!

image

ims_2017-05-02-153952_pixels.crash.txt

blocker.blend.zip

@PyrApple
Copy link
Member

PyrApple commented May 2, 2017

Indeed, and a hard one (most likely related to multithread based on the logs). searching...

@dingzeyuli
Copy link
Author

dingzeyuli commented May 3, 2017

Thanks for the feedback! When I move the source or listener slowly, the raytracer crashes much less frequently. I guess if the previous multi-threaded raytracing has not completed, new movement happens and triggers a new round of rays. This might have led to the crashing.

Besides the geometry built-in to blender, can I import custom shapes? I made a mesh with OpenSCAD and it seems the raytracer is not behaving correctly. Is there any requirement for the input mesh? mesh quality? topology limit?

office.stl.zip

image

@dingzeyuli
Copy link
Author

dingzeyuli commented May 3, 2017

@PyrApple:
After some trials, I realize the raytracer handles quad meshes much better than tri meshes. At least, no more penetration happens after I switch to quad mesh.

Yet, in the case of the a door and a hallway, the engine still fails. It either computes a wrong acoustic decay or crashes again like in the triangle mesh cases. I was wondering if you have some already-verified complex scene that I can play with? Something more complex than the square room? Thank you very much.

@PyrApple
Copy link
Member

PyrApple commented May 3, 2017

Quad vs Tri mesh, you're definitely right there. No official complex model that I can share for the moment, yet would be pleased to handle one of yours that highlights a bug in acoustic decay estimation. Would you mind opening a new thread on that and keep this one for the blocker issue?

@dingzeyuli
Copy link
Author

@PyrApple Okay! I will upload my slightly more complex model in a new thread.

Since you have worked on this acoustic simulator for a while, are you aware of other similar project or software that has similar functionalities? Thanks a lot!

@PyrApple PyrApple added the bug label May 8, 2017
@PyrApple
Copy link
Member

Non-exhaustive listing of auralization / spatialization software: EVERTims page on my personal website.

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

No branches or pull requests

2 participants