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

Try volume materials instead of custom raymarching #22

Open
JanVogelsang opened this issue Jan 28, 2022 · 3 comments
Open

Try volume materials instead of custom raymarching #22

JanVogelsang opened this issue Jan 28, 2022 · 3 comments

Comments

@JanVogelsang
Copy link
Contributor

https://youtu.be/R2RQm_Bu81I?t=1244

@JanVogelsang
Copy link
Contributor Author

@JanVogelsang JanVogelsang removed their assignment Apr 28, 2022
@JanVogelsang
Copy link
Contributor Author

JanVogelsang commented May 2, 2022

Starting point: The main question is what data the built-in raymarcher expects. The volume data for the custom raymarcher is heavily preprocessed, which makes it unusable for the built-in raymarcher.
Content/Materials/M_TestVolume

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

No branches or pull requests

1 participant