6:16 i think it is possible to process b-rep model as an SDF and then render it using a raymarching technique. not very popular approach, but the point is we _can_ render our model directly, without converting it to polymesh.
Happy to see some material on OCCT, its hard to find outside the official docs. Will you go more in details on AIS (objects selection) and OCAF ? I'm planning to use python bindings of OCCT to create an app and I'm wondering if It will be easier to use OCAF or rewrite things in Python directly, so any more infos would be nice :)
Yes, we'll go deeper with OpenCascade modules, although it's quite a long process to describe everything in detail. For example, the official OCAF training takes 2 working days, and I'm not sure it would be exactly right to devote several lessons solely to OCAF, especially, in the early days of this channel. At the same time, maybe it's more valuable to uncover OCAF than modelling because OCAF is so poorly documented that literally any extra bit of information will be new ;)
@@QuaoarWorkshop Great, yeah I sure think learning more about the less undocumented modules is good, but at the end I'm sure any topic you decide to talk about will be great news so thank you :)
Nope. It contains only this BVH package. Equipped with that, you might want to develop your own collision detector. Good reading here is the book "Real-Time Collision Detection" by Christer Ericson.
What is minimum size of application using occ? Release application (exe + libraries + additional necessary files needed to run occ) . How many MB can it take?
That would strongly depend on the set of libraries you use from OpenCascade. Given that the libs are linked dynamically, you can sum up their sizes to obtain the final figure. All the modules are fine-grained, e.g., if you're not using fillets, you do not need to include TKFillet library in your distributive (unless you link against a lib that has it as its own dependency, of course). For lesson 4 (visualization, ruclips.net/video/PXkv7fmURnI/видео.html), the following libraries would be in the distribution: freetype.dll Lesson_04.exe TKBRep.dll TKernel.dll TKG2d.dll TKG3d.dll TKGeomAlgo.dll TKGeomBase.dll TKHLR.dll TKMath.dll TKMesh.dll TKOpenGl.dll TKPrim.dll TKService.dll TKShHealing.dll TKTopAlgo.dll TKV3d.dll In total, it is ~22MiB.
List of lessons (done and planned): analysissitus.org/forum/index.php?threads%2Flist-of-lessons.3%2F
I could not push the like button faster on this . thanks.
A very rare presentation thank you
Very interesting and clear overview of OCC modules ! Thanks 🙏
Thanks, @Alexis! Glad to have you following :D
Thanks....very helpful...
6:16 i think it is possible to process b-rep model as an SDF and then render it using a raymarching technique. not very popular approach, but the point is we _can_ render our model directly, without converting it to polymesh.
I think that's what nTopology does for their SDF-based models. It's very interesting indeed.
Happy to see some material on OCCT, its hard to find outside the official docs.
Will you go more in details on AIS (objects selection) and OCAF ? I'm planning to use python bindings of OCCT to create an app and I'm wondering if It will be easier to use OCAF or rewrite things in Python directly, so any more infos would be nice :)
Yes, we'll go deeper with OpenCascade modules, although it's quite a long process to describe everything in detail. For example, the official OCAF training takes 2 working days, and I'm not sure it would be exactly right to devote several lessons solely to OCAF, especially, in the early days of this channel. At the same time, maybe it's more valuable to uncover OCAF than modelling because OCAF is so poorly documented that literally any extra bit of information will be new ;)
@@QuaoarWorkshop Great, yeah I sure think learning more about the less undocumented modules is good, but at the end I'm sure any topic you decide to talk about will be great news so thank you :)
You mentioned fast collision detection. Does open cascade have implementation of collision detection algorithm? GJK algorithm?
Nope. It contains only this BVH package. Equipped with that, you might want to develop your own collision detector. Good reading here is the book "Real-Time Collision Detection" by Christer Ericson.
What is minimum size of application using occ? Release application (exe + libraries + additional necessary files needed to run occ) . How many MB can it take?
That would strongly depend on the set of libraries you use from OpenCascade. Given that the libs are linked dynamically, you can sum up their sizes to obtain the final figure. All the modules are fine-grained, e.g., if you're not using fillets, you do not need to include TKFillet library in your distributive (unless you link against a lib that has it as its own dependency, of course). For lesson 4 (visualization, ruclips.net/video/PXkv7fmURnI/видео.html), the following libraries would be in the distribution:
freetype.dll
Lesson_04.exe
TKBRep.dll
TKernel.dll
TKG2d.dll
TKG3d.dll
TKGeomAlgo.dll
TKGeomBase.dll
TKHLR.dll
TKMath.dll
TKMesh.dll
TKOpenGl.dll
TKPrim.dll
TKService.dll
TKShHealing.dll
TKTopAlgo.dll
TKV3d.dll
In total, it is ~22MiB.
@@QuaoarWorkshopgreat. thanks.