Closed nyue closed 2 years ago
@BruceCherniak
Works like a charm. Thank you.
I have rebuild with the latest OSPRay studio with OSPRay 2.8.0 and all the dependencies.
Confirming that the call to frame->frameProgress() and the comparison is essential in getting it to work.
Cheers
Thank you for verifying. I don't know what the ultimate fix will look like, but this tells us a whole lot and allows you to try some things out. Cool. That one was really keeping up and night. :-)
Cheers.
Hi Nicholas, I have merged a fix for this issue into the gitlab devel branch (https://github.com/ospray/ospray_studio/commit/6bd05fbbbad4c215de9de454490731e129f017d5). When you get chance, would you mind trying the latest devel branch on a couple of the system that failed for you previously? The nano cluster would be especially interesting to test on.
I have verified it across several VM installs that exhibited the problem, as well as making sure it doesn't introduce artifacts in other situations.
I have now built the branch the old Intel chip I have, it is working just fine. Thank you.
The Jetson Nano cluster is misbehaving so it might take a couple more days for me to get you an answer. I am also interested to see how the fixes works out on ARM CPU
Hmmm. Bummer. Recall that the fix is only on the devel branch at this point. You did remember to git checkout devel
? The git clone will default to the master branch.
Ha! In my haste I did not checkout devel branch.
Rebuilt everything on the devel
branch. All is well.
So on my Jetson Nano ARM64 running Ubuntu 18.04
I have loaded all the demo scenes with no problem, with the known caveat of there being no denoiser (will follow up in a different conversation) as this tests is not on an Intel CPU.
Cheers
I have been able to build ospray_studio
In the menu, there was option to load some sample scenes but nothing happens.
Do I need to install other packages or set some CMake settings in order for the samples scenes to show up ?
Cheers