I have been using OCCT for several years now. I started with version 6.5. In that version I discovered that I could not simultaneously evaluate a NURBS surface from different threads without encountering errors. With help from the OCCT team and this forum I learned that there were caching data structures used by the evaluation code that were incorrectly shared by each thread. The solution I came up with was to duplicate all the surfaces for each thread so that I didn't need to mutex the evaluation operations.
I just saw that OCCT 6.5.3 has been released and I saw bug 22550 in the release notes. This sounds very promising and that it might fix the issues I had encountered in the past. But I am not sure if it addresses everything.
Could someone give me more info about this fix, and whether it is now possible to safely evaluate a NURBS surface from multiple threads?
ps. I am very supportive of the improvements I have seen for OCCT in the recent past. Having multiple forums should make it easier to browse for different categories of posts. Having the git repository should help get patches and build issues resolved more quickly. I hope we can all find ways to help with improving OCCT.