CS4 projects not always compatible with CS6?

I had some issues with CS4 templates that did not work the same in CS6. I updated the items and included CS6 versions too. But it should not happen since CS6 is backwards compatible…
Did this happen to anyone else here?
In two cases it was the Cycore fx that had differences. CC particle world needs to convert to old settings (the floor settings did not work in the same way. Also in CS4 floor settings were in options menu, but in Cs6 are under physics menu). In another project I got some different results (between CS4 & CS6) in CC sphere… and in another one, footages where not following when sliding the time of a collapsed transformation! CS4 & SC5 worked great! That was really strange, possibly a bug!
This is somehow inconvenient, specially because I don’t have CS6 yet, and I have to check my files in associates’ computers…
So guys, did you have any problems with your CS4 templates in CS6 so far?

• CC particle
• Shadow/Highlight
• Curves (sometimes)
• CC cell patern

Think about it, They had to rebuild whole effect to improve it, or fix the bugs. So in CS6 those effects are rebuild or changed in a better way. So sometimes the old good CS4 effect is not the same as renewed CS6.

Some Expressions which created in CS4 doesn’t work in CS6

The same here. Problems with CC particle world, and motion tile.

Give as much detail as possible.

If the bug is in a Cycore (CC) effect, be sure to report the bug to Cycore, too.

Same here. If you have some particles bouncing, CC Particle World needs to be manually converted with the newer version of After Effects, so I had to mention that in my help file. Also, as I noticed, some Distort effects have some weird bugs in CS6. Had to update one of my files because of that…

that’s really important, to know… it would be good for individual projects that don’t appear the same, to have a note from authors on your project description page, so we know to load in cs4 if that’s needed, for properly using the project. good catch

graphic4444 said
that’s really important, to know… it would be good for individual projects that don’t appear the same, to have a note from authors on your project description page, so we know to load in cs4 if that’s needed, for properly using the project. good catch

More to the point, authors should actually open and check their old projects in CS6, before updating the description! It’s wrong to just assume that After Effects forwards compatibility works.

For instance, many of the standard material properties have changed their index number from CS5.5 to CS6 to accomodate the new ray-tracing. This is one reason why expressions may no longer work. Also, the fact that all frames in a comp are read in and checked for caching means that an expression that doesn’t compile for all frames of a comp will fail in CS6, where it would have been okay in CS5. This is particularly common for references to activeCamera, where the camera layer doesn’t extend the full length of the comp.

Checking goes for any version description… it only takes a couple of minutes to open a project up and do a low-res preview. That’s all it takes to check it.

good point Felt, and thx for specific examples… I would strongly suggest to envato that you make it a requirement that authors check compatibility of their files in CS6, and either fix incompatible ones, or submit requests to update the description to not include cs6 if CS4/5 projects don’t work properly in it. otherwise customers aren’t getting what they paid for, and you’ll likely see refunds or tons of service request emails, like “i bought it and the render doesn’t look like the video preview” complaints and the like.

envato, can you guys make that a requirement of authors, to check full cs6 compatibility for those files that state it? or, whatever makes sense, to help