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

[Unreal][Feature Request]Add a field to specify an LOD to use for creating the phononscene #111

Closed
DavidWLejeune opened this issue Feb 7, 2020 · 3 comments

Comments

@DavidWLejeune
Copy link

In really complex worlds the phononscene file size can get extremely large, which effects load times and potentially performance for real-time reverb.

This can be worked around a bit by just creating a hidden lower-poly scene and putting the phononcomponents on that, but that's not very efficient.

It would be nice if on the PhononGeometry component we could specify LODs from which the phononscene will be generated. This would allow the creation of more optimized phononscenes without dramatically affecting the acoustics of the environment.

@1runeberg
Copy link

Thanks for the feedback @DavidWLejeune !

We're also looking at supporting sublevels which in some cases may help in audio design, potentially not with dynamic geometry.

this request seems reasonable, will have a look for the next release and put an update here.

@kisak-valve - can i be set as the assignee to this issue please. thanks! :)

@funkysandwich
Copy link

I second this. I'm using high-poly modular assets, so simply using 'Add Geometry component to all actors' results in very large file sizes and long export/load times.

It'd be nice to set a min LOD level for static mesh geometry exports under World Settings.
Also, a property on the geometry component to specify a proxy static mesh asset would be great too, to use that mesh instead during the baking/export process.

Copy link

This issue has been automatically marked stale, and will automatically be closed in 30 days if no activity occurs.

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

No branches or pull requests

4 participants