Hi Dan, Hi Jason, thank you both for your answers and support. We are of course aware that our setup is a bit behind current development. But as we have built up our vehicle modeling toolchain with dependencies on Chrono 7.0 base classes, upgrading to develop would probably be some work. Before starting that endeavor, it would be cool to have some feedback such as
- a user/developer who can confirm that OptiX sensors work just fine with the above or a similar setup (--> we should look for errors on our end that are independent of Chrono or OptiX release) - a user/developer experiences or has experienced the same and has a potential fix (--> we can stop looking for stuff that we are doing wrong) - a user/developer who points us to a compatibility issue with Ampere GPUs and the above setup that we are not aware of (--> we can stop looking for other errors and go for newer releases) That being said, I will take a stab at upgrading our toolchain to Chrono develop and newer CUDA + OptiX. Thank you, Christian On Wednesday, November 15, 2023 at 9:56:53 PM UTC+1 JASON Z wrote: > Please consider upgrading Chrono to either the 8.0 Release or the main > branch of the chrono repo. > > There have been updates since 7.0.0, and we recently upgraded the Optix to > 7.7.0 in the main repo. > > It will be difficult for us to debug on issues happening on previous > versions. > > On Wednesday, November 15, 2023 at 8:58:26 AM UTC-6 Christian Feller wrote: > >> 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/f891e87b-3633-485d-90fe-3115cc9a219bn%40googlegroups.com.
