Strange Render artifacts on Safari Mobile only

Throwing this out here in case it might be an implementation specific thing, but on Mobile Safari only I am getting very strange volume render artifacts, as if it is reading the array data in the wrong order. Also reproducible on the Xcode iOS simulator.

A brief summary of my architecture: I am creating a vtkImageData object with preallocated Float32Array and manually inserting DICOM pixel data into each slice of the scalar array, then displaying in 3 parallel camera vtkRenderWindows, each with their own vtkVolume object (for individual window leveling), but each volume inherits the same imageData object. This works fine in all scenarios save for Mobile Safari.

Since many vtk.js API examples run fine on the iPad, is this just an issue with something I’m doing somehow? Any tips on where to look?

vtk.js version: 12.1.3, but have tried the latest v13 as well, with no difference in behavior.

iOS Safari:

Literally Any Other computer browser:

[mix3d]

It was user error after all. My company’s Dicom loader apparently grabs a jpeg on mobile devices, I wasn’t aware of that behavior. I might try to make the volume work with jpeg data, but forcing it to get the right file is making it work again.

Your recap DID help me pinpoint the problem though!

Closing the issue.

[jourdain]

Glad it help…