Search results

I don't see any problem in this code. Just a naive question, do you run your application in Release mode?

Hi @Rubiofm7, It's quite tricky to hint you about a way to go until we can see a code dedicating to implication of trsf to robot's joints and updating the scene afterwards. Is it possible to provide the community with this piece of code and models you import? Otherwise, it's unlikely anyone can...

I guess you're looking for asiVisu_ShapeRobustSource.h/cpp class. https://gitlab.com/ssv/AnalysisSitus/-/blob/master/src/asiVisu/sources/asiVisu_ShapeRobustSource.h?ref_type=heads Since ASitus uses VTK as a rendering engine, its tesselator isn't that is used in Occt.

The Z-depth fighting is a well-known problem. All this 3D-rendering stuff is beyond my knowledge a bit, but from what I know OCCT's rendering engine provides something to mitigate visual artifacts and does some offset magic behind the scene if asked properly. Given that you might want to...

Hi Alex, could you please elaborate on why do you might need this Transfer_TransientProcess?

Hi! Can you share the data which we might use to reproduce the issue?

Hi! Is my understanding correct that you're looking for a sort of visualization tricks to improve the text's redability?

Hi, unfortunately, not. This software aims for CAD models inspection, and so it deals nothing with FEA meshes.

Below is another sample code where OcctFramebufferObject is an item to render on and OcctViewer is a class wrapping OCCT rendering capabilities (initializes window, context, view(s), etc.)

The sample you rely on initializes the OCCT viewer by giving it the id of the main window what means the OCCT viewer uses the canvas of the main window for rendering, and changing the size of the host item (OcctViewer item) has an impact on the camera view. Approaching FBO will allow you to...

Please, point out what version of Qt\Qml you use as it makes a big difference since Qt 6.

Hello kndpeng, Could you please elaborate more on the issue you face as I'm not sure I got it. Providing a piece of code could help as well.

stoneszone, I haven't been able still to reproduce the issue at my PC, but can it be so that there are different OCCT versions at your OCCT? Such a problem can occur when there is a mix between dlls used during the compilation and running after.

VTK is evolving project, and so its API can vary from version to version, what means that the projects relying on this library should be properly updated to use API coming with upgraded VTK. If ASitus's compilation is broken with vtk9.2, it means that ASitus should be updated according to the...

You can follow both ways - install OCCT or compile it on your own. What way to go depends on the use-case. After OCCT is compiled - there are dlls and libs - you can move on to compilation of any project depending on OCCT including ASitus. Since you have dls, libs and includes of whatever...

Please, share ASitus configuration.

You are free to compile ASitus against OCCT version you need, for that CMAKE proposes the corresponding variable(s) pointing (3RDPARTY_OCCT_DIR) to the OCCT artifacts such as bins, libs and includes. It's normal practice to patch/customize OCCT and then use it for other projects backed on top of...

What if you run asiExe.exe in Debug mode? Switch to installation folder (.../bind) and double click on asiExe.exe.

I suspect there might be a mix of debug and release libraries in your configuration of ASitus. Double-check the paths to 3rd-party dependencies of ASitus which set up for Debug mode.

If I were you, I would turn on the debugger and examined the code step by step to getting out what exactly the problematic place is. Have you tried to run your application in Debug mode?