Hi Yves, If you just double-clicked the executable and found the prompt closed shortly after launching, then you should instead use a Windows-based command line terminal to run them (Powershell?). This will allow you to see the output/error message.
Remember you'll typically have to supply a JSON file as an input argument, something like "*.\demo_GPU_repose.exe demo_GPU_repose.json*". You should try that from a terminal. That's the only suggestion I can infer from your description. Thank you, Ruochun On Thursday, June 9, 2022 at 4:17:23 AM UTC-5 [email protected] wrote: > Sorry for the multiple messages, but I figured it might be good for you to > have access to my build logs. Here is the one with Debug, knowing that I > get the same results and output with the Release one. > > Thanks, > Yves > > On Thursday, June 9, 2022 at 8:57:43 AM UTC+3 Yves Eric Maxime Robert > wrote: > >> Thank you for your answer. >> >> I have been trying to use WSL for days, but it never worked. So I >> proceeded to a clean installation with Windows, following the instructions >> of the website, using the same software (SourceTree, CMake, VS2022). I >> installed CUDA as well. >> >> Here is a zipped folder containing all the advanced CMake information. >> >> Thank you for your help, >> Yves >> >> On Thursday, June 9, 2022 at 5:54:06 AM UTC+3 Ruochun Zhang wrote: >> >>> Hi Yves, >>> >>> Most likely the environment is the problem and it can be the tricky one. >>> You are running on Windows, not WSL, right? Also, maybe you should show >>> your "Advanced" options so we have an idea about how your CUDA >>> environment/paths are set. >>> >>> Thank you, >>> Ruochun >>> >>> On Wednesday, June 8, 2022 at 12:33:01 PM UTC-5 [email protected] >>> wrote: >>> >>>> Hello, >>>> >>>> Sorry about that, I must have unchecked the box when taking the >>>> screenshot. >>>> The compilation has been done with the GPU module, which is why I have >>>> access to the GPU demos. >>>> >>>> Do you have an idea of why it does not work? >>>> >>>> Thank you, >>>> Yves >>>> >>>> On Wednesday, June 8, 2022 at 7:13:52 PM UTC+3 Ruochun Zhang wrote: >>>> >>>>> Hi Yves, >>>>> >>>>> You should enable Chrono::GPU module. It's the GPU-based physics >>>>> module and right now it is Chrono's dedicated granular simulator, those >>>>> demos need that. >>>>> >>>>> Thank you, >>>>> Ruochun >>>>> >>>>> On Wednesday, June 8, 2022 at 9:09:03 AM UTC-5 [email protected] >>>>> wrote: >>>>> >>>>>> Hello everybody, >>>>>> >>>>>> I am new to Chrono, but would want to run a simulation which should >>>>>> be very close to what the repose demo found in Chrono::GPU, to the >>>>>> exception that I need some recent additions to the code, so I have to >>>>>> use >>>>>> the feature/GPU branch. So everything that follows is with that branch. >>>>>> >>>>>> I already compiled Chrono following the tutorial for Windows in the >>>>>> past and could run several demos. But having now access to a NVIDIA GPU, >>>>>> I >>>>>> installed CUDA and additional dependencies, and followed the >>>>>> instructions >>>>>> again. I saw that OpenGL was important to have to be able to run this >>>>>> repose demo, so I also compiled it. Here is how my CMake window looks: >>>>>> [image: cmake.png] >>>>>> It got built well on VS2022, with all succeeded and 1 skipped. >>>>>> >>>>>> With that, I can run all demos with their executables (IRR, >>>>>> Postprocess, ...), except for the GPU ones. The ball drop one shows a >>>>>> terminal with values and outputs files, and that's the only one. The >>>>>> rest >>>>>> just crashes with no output as soon as I click on the executable. >>>>>> >>>>>> My guess was that I do not have the granular module enabled, and from >>>>>> the documentation I need that. However, I cannot find it, and cannot >>>>>> find >>>>>> how to install it. >>>>>> >>>>>> Could you please help me figure that out? >>>>>> >>>>>> Thank you, >>>>>> Yves >>>>>> >>>>> -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/projectchrono/a81c752a-6eab-4c26-8015-069957cd5a82n%40googlegroups.com.
