Wierdly behaving 3D objects / Meshes about fluidx3d

[ikozyris]

I have the same problem on an Intel Iris Xe iGPU. The examples worked, so I tried a custom STL file, which had similar issues. Then found this issue and can reproduce the exact same weird rendering. There are no problems when run on CPU.
I suspect either a driver issue or the iGPU doesn't have enough memory.

[ikozyris]

This is the output of lspci on Linux 6.8.0-1009-oem Ubuntu 24.04 and i7-1370P:

0000:00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-P [Iris Xe Graphics] (rev 04)
	Subsystem: Dell Raptor Lake-P [Iris Xe Graphics]
	Kernel driver in use: i915
	Kernel modules: i915, xe

And glxinfo:

name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel (0x8086)
    Device: Mesa Intel(R) Graphics (RPL-P) (0xa7a0)
    Version: 24.0.9
    Accelerated: yes
    Video memory: 31704MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) Graphics (RPL-P)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 24.0.9-0ubuntu0.1
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 24.0.9-0ubuntu0.1
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 24.0.9-0ubuntu0.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

intel-opencl-icd is version 23.43.27642.40-1ubuntu3
In its package description it mentions support for up to Alder Lake (12th gen), while I'm on Raptor Lake (13). I installed the latest drivers from intel repositories. Now the package is 24.22.29735.27-914~22.04 and the isssue persists (the noble package is for jammy?).

[gitcnd]

Loads OK for me - you probably need a larger simulation? Try 14000u instead of 4000u

I ran it like this from WSL:-

/mnt/c/Windows/System32/WindowsPowerShell/v1.0/powershell.exe start "cmd.exe '/c mode con: lines=80 & bin\FluidX3D.exe -f ..\..\cat.stl -r 16000 --SUBGRID --rotz 90 --rotx 180 --roty 180 --try -0.9 -y 1 -z 0.5 -x 0.3 -c 0.15 --aoa 0.0 --slomo 200.0 --fps 60 --SRT --UPDATE_FIELDS --GRAPHICS --EQUILIBRIUM_BOUNDARIES --FP16S --D3Q15 & pause'"

using my branch from here: https://github.com/gitcnd/FluidX3D/tree/inline_things

What are the "some quick calculations on the characteristics" you're trying to work out?

For context - I'm the author of the free Fusion360 "Airfoil Tools" add-in - which might also be able to help.

[ProjectPhysX]

Hi @MGRAFF2006,

I'm sorry that the first thing you see is something not working. Let's get to the bottom of it. Thanks for already providing the reproducer! I need some more information: What hardware are you running this on? Maybe it is an issue with the particular drivers.

Running this exact reproducer on my system (tested on 3 OpenCL devices: Arc A750, UHD 630 and i7-8700K), the setup looks fine and I can't observe the artifacting. The mesh looks also fine.

To place the model in the center, use this:

	Mesh* cat = read_stl(get_exe_path()+"../stl/cat.stl");
	cat->rotate(float3x3(float3(0, 0, 1), radians(-90.0f))); // rotate -90 degrees around z-axis
	const float scale = 0.8f*fmin(fmin(lbm_N.x/cat->get_bounding_box_size().x, lbm_N.y/cat->get_bounding_box_size().y), lbm_N.z/cat->get_bounding_box_size().z); // scale parts
	cat->scale(scale);
	const float3 offset = lbm.center()-cat->get_bounding_box_center();
	cat->translate(offset);
	cat->set_center(cat->get_bounding_box_center()); // set center of meshes to their bounding box center
	lbm.voxelize_mesh_on_device(cat);

Kind regards,
Moritz

[ProjectPhysX]

Hi @MGRAFF2006,

is this issue resolved for you?

Kind regards,
Moritz

[ProjectPhysX]

@MGRAFF2006 @ikozyris which exact iGPU from which CPU, and what driver version is it? Does it still show the artifacts with the latest Intel iGPU driver?