R10.5 Animation - what changed?

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 25/10/2007 at 14:34, xxxxxxxx wrote:

User Information:
Cinema 4D Version:   R10.5 
Platform:   Windows  ; Mac  ;  Mac OSX  ; 
Language(s) :     C++  ;

---------
Hmmm.

R10.111 - adding animation works flawlessly.

R10.506 - adding animation works flawlessly to crash C4D instantly.

Considering that I'm about to have a hundred or so really pissed off users with R10.5 and a broken plugin, could you please provide information on WHAT changed, pretty please?

And how about releasing the SDK Documentation BEFORE releasing the software so that we plugin developers can be prepared instead of looking like asses when these things occur? I was hoping not to be required to make another version set of builds. Time to drop R8.2 and R8.5 support as this would make something like 16 builds (R8.2 W/M, R8.5 W/M, R9.1 W/M/64, R9.5 M/UB, R9.6 W, R10.0 W/UB/64, R10.5 W/UB/64).

Thanks,

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 26/10/2007 at 00:14, xxxxxxxx wrote:

What kind of animation crashes?

As for the 10.5 SDK, there will be soon an update to the docu.

I am sorry to hear that you are angry but delays are unfortunatly anavoidable with a free SDK support.

cheers,
Matthias

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 26/10/2007 at 00:32, xxxxxxxx wrote:

What I've found is that R10.506 64-bit animation works (MacOS may work, but I still need to install the R10.5 demo there). It seems that R10.506 32-bit does not like the VS6.0 R10 plugin in some areas.

But I can't get a working VS2005 (Pro) 32-bit build for R10.506 (or R10). The libs are built (including zlib and libpng) and the project builds without errors. But Cinema 4D R10.506 32-bit crashes on startup every time. This will be the first time that I'm using VS2005 for 32-bit builds. I've checked settings exhaustively with those for cinema4dsdk. It could be the zlib and libpng 32-bit static libraries in VS2005 aren't kosher - but it will be difficult to 'comment them out' as major parts of the plugin depend on them. And the 64-bit static libraries work. (?)

There seems to be a lot of back-and-forth on what is working and what isn't with the R10 plugin in R10.5. Win32 animation crashes are definite. Tools seem to be non-functional with HNs involved. It's a bit difficult to do a thorough shakedown of a plugin this complex with each new release (21 plugins working in concert - and growing).

To answer your first question - any hint of animation results in Cinema 4D R10.5 disappearing. This occurs on both Windows 32-bit and Windows 64-bit with the 32-bit version of Cinema 4D R10.5. If it's a problem with using VS6.0 and R10 api, the current situation with VS2005 isn't going to make it easy to resolve.

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 26/10/2007 at 01:03, xxxxxxxx wrote:

VS6.0 could be a problem since MAXON dropped VS6.0 completly since Cinema R10 I think. I have no possibilty to check against VS6.0 so you have to figure this out yourself, sorry.

Here are the new IDs for the special tracks.

CTpla   PLA track
CTsound Sound track
CTmorph Morph track
CTp2p   P2P track
CTtime Time track

There is a new parameter in CTrack::GetCurve().

CCurve* GetCurve(CCurveType type = CC_CURVE,Bool bCreate = TRUE)

If bCreate is TRUE a cureve will be created if there is no curve avaible.

Otherwise there are not many changes to the API for accessing the timeline and they will be in the next docu update.

cheers,
Matthias

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 26/10/2007 at 02:16, xxxxxxxx wrote:

Any tips on how to ensure a working 32-bit plugin with VS2005? I've been fiddling with settings and overchecking everything in the build to find anything - and still C4D crashes immediately when starting with this build. Whatever is crashing is crashing before the plugin(s) are even launched - so no calls to zlib or libpng at that point!

The BugReport just mentions an Access_Violation but the thread has no information on what caused the crash - usually you get the plugin, module, or Cinema4D.exe - nothing like that. It is definitely the plugin - but it crashes so early that it isn't documented?

This appears to be a low-low-level problem (compiler/linker crap that makes C4D go bye). Where do I begin when the current information is "It crashes"? The chief suspects are the static libs - I'd hate to rely on debugging to find out pretty much what is already known esp. considering that the application is only loading. Now you see why I stuck with VS6.0 for as absolutely long as possible - it WORKS! It may be crap, but it works.

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 27/10/2007 at 20:43, xxxxxxxx wrote:

Here's what I found out:

Building the cinema4dsdk Win32 release version under Windows XP Pro x64 using VS2005 (w/64-bit support available) resulted in an api library of a different size than the same one built under Windows XP Pro using the same VS2005 version wo/64-bit support available. And the latter worked using a new vcproj instead of reusing the 64-bit one (with a new Win32 target added) despite the configuration settings.

Don't know why, but isolating the Win32 from the x64 builds made a difference. (???) I have at least 8 builds in VS6.0, so there is some curve to learn...

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 19/04/2008 at 12:18, xxxxxxxx wrote:

The new parameter in
CCurve* GetCurve(CCurveType type = CC_CURVE,Bool bCreate = TRUE)
makes things very difficult. A version, compiled unter R10.5 crashes at this call when running in 10.x and vice versa! So I have to introduce new plugin versions for 10.5 just for this f***ing minor change! Isn't it possible to extend functions without loosing compatibility to the previous c4d version???

Is it possible to make a wrap so that it can run in both c4d versions?

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 21/04/2008 at 01:30, xxxxxxxx wrote:

Sorry Cinema plugins are only upwards not downwards compatible. I am afraid you have to compile for each Cinema version. Maybe Robert can chime in, he supports a wide range of Cinema versions with his InterPoser plugin.

cheers,
Matthias

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 21/04/2008 at 03:11, xxxxxxxx wrote:

Hey Robert,
You may have already checked... and I'm not sure if VC2005 is set up like VC2008 is, but in VC2008, there is no compiler option for the "/vmg /vms" compiler flags... I had to add them in the extra/additional options field.
I literally spent 4-5 hours chasing wild geese around before finding the problem.

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 21/04/2008 at 04:14, xxxxxxxx wrote:

Hi Matthias,

if it were upwards compatible, the problem would not have occured. The R10-compiled plugin crashes when running under R10.5 at the mentioned call!