Dear all, we are observing some strange behavior when trying to run lidar sensors from the Chrono::Sensor module on PCs with Ampere GPU (compute capability 8.6).
Our setup is as follows - Chrono 7.0.0 - OptiX 7.2.0 - CUDA 11.6.2 - USE_CUDA_NVRTC=OFF - CUDA_ARCH_NAME = Auto Everything is running fine on Pascal or Turing GPUs and we see the lidar point cloud data that we would expect. However, when a colleague of mine is building and running the same code on his PC with Ampere GPU, the model as such is running OK, but we get "flashing" lidar point cloud data. More precisely, the correct point cloud data is returned at discrete time points, but most of the time the sensor seems to be returning blank data (i.e., zero intensity returns everywhere). We get the same behavior when using CUDA NVRTC. Is this a known issue or has anyone observed something similar? Might this problem be solved by upgrading to Chrono 8.0 and/or a more recent OptiX or CUDA release? To my understanding, the above toolset should be compatible with Ampere 8.6 architecture and the observed behavior appears to be really strange :/ Any help is highly appreciated! Thanks, Christian *Christian Feller* *Lead Simulation Engineer * Danfoss Power Solutions GmbH & Co. OHG Virtual Solutions & Verification DPS R&D / Software -- You received this message because you are subscribed to the Google Groups "ProjectChrono" group. To unsubscribe from this group and stop receiving emails from it, send an email to projectchrono+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/projectchrono/f94aafc7-5409-4d8a-aa50-018697f255b6n%40googlegroups.com.
