Problem context This topic was extracted from OCCT Mantis issue 24324 to involve wider audience into the discussion. Enabling anti-aliasing with help of V3d_View::SetAntialiasingOn() call for a scene containing shaded polygons often results in problems illustrated by the snapshot below: Archived ima
As mentioned on the OCCT visualization tools project page , there is on-going development around implementation of stereoscopic rendering in OCCT 3D viewer. We are proud to share some intermediate results with the community. As of today, the following basic capabilities have been implemented: Graphi
Although we discussed the below items with Sergey (san), let me repeat them here as reminders: 1. Optimizing memory footprint/performance for displaying assemblies by *reusing* visual representations of instances (not recomputing them). Example: 100,000 instances of the same cylinder should rather b
Dear OCCT developers, as some might have seen, I've been testing the Voxel Package as a tool for material removal. Although it is not industry-ready at the moment (at least in my opinion) it looks very promising (!) and I will surely continue working with it and hope to be able to commit some improv
Possible optimization I tried to change the transform of the underling Graphic3d_CStructure However changing the rendering transform over the InteractiveContext has some unnecessary overhead. Best option would be to use a cheap value class (gp_Trsf) in the call, but: --- AIS_InteractiveContext.SetLo
A nice article about an increasing role of realistic 3D visualization has been published recently by PTC: Rendering: It’s the Real Thing . This reaffirms the point of view of the OCCT visualization development team: nowadays, realistic 3D visualization becomes more and more demanded on the market.