SnapTool for R2023?

ferdinand

it works fine here:

Which exact version are you using? What is your console output? These are just some 2024.0.0 SDK binaries I had flying around anyway and I could recompile things, but we should first make sure that there is not something simple going wrong on your side.

Have you made sure to remove the binaries from the 2023 SDK from your plugin path?

Cheers,
Ferdinand

moebius

I have the 2023.1
I set the search path.
in the plugin folger are just plugins, no SDK stuff (or do you refere to the sdk.zip in the C:/.../maxon folder?
I tried it with all other plugins removed.
nothing in the console

ferdinand

Hey @moebius,

You cannot use 2023.1 to load the 2024.0 SDK, the SDK is not downwards compatible, but I assume that was a typo and you meant 2024.1. I meant that you should avoid having both the SDK_2023 and SDK_2024 binaries in your plugin folder, i.e., both the binaries I uploaded here in November 2022 and the ones from a few days ago.

Cheers,
Ferdinand

moebius

2024.1: typo... sry!
there is no SDK in the plugins folder.

it's not possible to redo the SnapTool as standalone Plugin/Tool? It's such an good helper, and work way better than the build in snap function. Ill do a yt comparison at some time

thanks anyway for your help!

ferdinand

Hey @moebius,

we cannot provide a plugin from the SDK as a separate download. In fact, we usually do not provide any binaries for the SDK at all. I will recompile the SDK next week and upload it here. That is all I can do for you, in case there is something fishy with this binary going on.

Cheers,
Ferdinand

moebius

ok thanks and have a nice weekend

ferdinand

Hey @moebius,

Please excuse for the delay, things are a bit hectic here at the moment. I have recompiled the SDK for 2024.0.0 in release mode (the link from above is a debug build I think, I then just grabbed what I had on disk anyway).

2024.0.0 SDK Binaries (WIN).zip

Cheers,
Ferdinand

moebius

You are my hero!
sorry I also was not here often. But this litte tool works now again!

moebius

Hi Ferdinand
Here we go again. It does not work anymore in R2025. Would you be so kind and update it? Or talk to Dave he should put it in C4D asap

Thanks a lot!!!

ferdinand

Hey, moebius, sure I can update this, but it will probably only happen next week, as I currently still busy with the SDK.

moebius

thanks! I'll come back in a feew weeks

ferdinand

Hey,

Here is a 2025.0.0 SDK build. Just as for the previous builds, this is Windows only, and also not code signed. Maybe we can find a bit permanent solution in the future, as the C++ SDK also contains a quite useful tool for Python developers (the Active Object plugin).

~~Cinema_4D_CPP_SDK_2025_0_0.zip~~

Cheers,
Ferdinand

moebius

Hi Ferdinand!

Thanks a lot!
unfortunately it does not show up in the extentions.
but, hell jey, a permanent solution would be great. An overhaul of the snap tool in C4D!

m_adam

Hi just to let you know that Ferdinand is in vacation, he will look into your topic once you are back.
Cheers,
Maxime.

moebius

nice comunity

ceen

Implementation of that tool would be nice indeed!

moebius

@ceen Does it work for you in R2025?
This Tool and TransformTool would be so great! Here an overview of this old plugin

ferdinand

Hey @moebius,

So, for me and for Maxime this just loads fine. I suspect you are hotlinking the wrong folder. Just unpack the zip into a folder and then hotlink that folder. E.g., MyUser\Downloads\cinema_4d_cpp_sdk_2025_0_0. When it is still not working, the only thing I could think of is that you are operating on some company device where the the admin really went buck wild with WDAC (Windows Defender Application Control) and disallowed the loading of any unsigned DLLs. Because I did not sign these DLLs.

But that is very unlikely I would say. It is more likely that you are linking the wrong folder.

Cheers,
Ferdinand

moebius

Hi!
no, does not work.
sorry for asking: did you compile it in "debug mode", not "release mode"? This was the issue with the compile a couple years ago

ferdinand

A debug build should load as much as a release build (the latter is just a quite bit faster). I quite frankly do not remember if if put this to release before I compiled, as in my daily work I usually compile debug builds. I will recompile it one more time tomorrow.

I still think you are not correctly linking the folder. Can you show us what you do?

Cheers,
Ferdinand