-
Notifications
You must be signed in to change notification settings - Fork 184
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
Problems with texture transparency and segfault using GPU module/device #588
Comments
Hi Tanner,
Cheers, |
I'm happy to hear that several texture problems have been fixed! Hopefully that bodes well for the issue that I'm facing. I'll have access to that Intel DevCloud machine again in a couple of weeks, so I'll be able to do some more testing then. Once I get access again, what's the best way for me to test the newest versions? Should I plan to build OSPRay and friends myself, or is there a nightly-built artifact that you can share with me? |
Hi again RenderKit team 👋
I'm doing a project using OSPRay for our Intel Center of Excellence program. The core idea is to create a rendering service/web API for visualizing biodiversity and energy efficiency data at a city scale.
We're at the phase of our project now where we have enough data (geometry, textures, etc) that we need to use the OSPRay GPU module/device.
During my testing, I noticed some weird rendering artifacts:
Initial symptom of the problem
Since then, I've tried to create a minimal reproducible example, and I've broken our problem down into a problem with textures. There are two symptoms:
First, on GPU, my texture maps are partly-to-mostly transparent. The amount and location of transparency is related to the texture size. In general, for a texture of size N, the first 1/N is only partially transparent and the remaining texture is varying degrees of mostly transparent.
Second, on GPU, copying the data for a 19x19 texture crashes OSPRay with a segfault inside a memcpy, inside
ospray::Data::copy()
.I did something kind of weird: my script to reproduce this problem is in Python using a ctypes-based wrapper around OSPRay. Everything works perfectly fine using the CPU device, so I don't believe the problem is related to my wrapper.
The source code for the script is in https://github.com/player1537-playground/OSPRay-GPU-Texture-Problem in the
test.py
file.test.py
has a small amount of documentation at the top, but the short form is:SYCL Devices
My oneAPI environment
My shell environment
2a) Inside the script is a
config
variable, you can change it to change which test case to run.2b) If the script is successful, it will create an
image.png
at the root of the repository.cpu1
gpu1
cpu2
gpu2
cpu16
gpu16
cpu19
gpu19
The text was updated successfully, but these errors were encountered: