Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unclear Blast Authoring extension usage #360

Open
PavelSupenko opened this issue Feb 4, 2025 · 0 comments
Open

Unclear Blast Authoring extension usage #360

PavelSupenko opened this issue Feb 4, 2025 · 0 comments

Comments

@PavelSupenko
Copy link

PavelSupenko commented Feb 4, 2025

Hello, dear Blast developers!
Maybe I am missing something and this message should be on Discussions tab. If yes, sorry for interruption.
I want to integrate authoring functionality into Unity and already made a lot - I've transferred your SDK to the CMake, modified it to work on mobile platforms and MacOS and created a working bridge for the low-level API. And now I started implementing the required C++ part for authoring (as an example I am using your deprecated tool from another repository), but found that mentioned in your documentation tool named ConvexMeshBuilder that is required by the NvBlastExtAuthoringProcessFracture function is just an abstract class with no inheritors:

class ConvexMeshBuilder
{
public:
    virtual void                    release() = 0;
    virtual CollisionHull* buildCollisionGeometry(uint32_t verticesCount, const NvcVec3* vertexData) = 0;
    virtual void releaseCollisionHull(CollisionHull* hull) const = 0;
};

In the NvBlastExtAuthoringProcessFracture function documentation described that this object should be created by non existed function:
collisionBuilder Collision builder created by NvBlastExtAuthoringCreateConvexMeshBuilder

As I see this collision builder is used inside mentioned function with no null checks or something more so I can't skip it or something like that I think.
Unfortunately I see there are no tests for this functionality so only one information source I can use is the deprecated usage example that has PhysX dependency that is not here anymore.

Could you please help me with the correct flow around this functionality? Maybe I am doing something wrong and I don't need it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant