• bryce

  almost 2 years ago

  doesnt install to blender 3.0 and beyond

• adnan

  almost 2 years ago

  needs updating to work in new blender versions

• Jorge Bori

  about 2 years ago

  Awesome Add-on

• Alex Miller

  about 2 years ago

  Orientation currently isn't working in Blender 3.3 (and hoping it is my user error), and I am hoping that the community can help. Thanks to Diego who has found a decent solution to solve most of the issues so far and I am hoping someone can help me figure out why orientation isn't being copied over to Blender.

• Kevin Watkins

  about 2 years ago

  I can confirm that if you make Diego's fixes listed in the review below from summer '22 - modifications that take less than 1 minute to make - AE2Blend_2_8.py will work as amended going from AE v18.4.1 Build 4 to Blender v3.3.0 2022-09-07. Well, I should say it worked for me the first and only time I've used it so far to "Create Camera" and then "Create Plane". There are certainly enough quirks you need to be aware of, but there are a lot of tutorials out there for that. It does what it says it does - using AE tools for camera solves will make it worth the money.

  Tip of the cap to Diego for not only figuring it out, but circling back to share with the rest of us.

• shbuh

  about 2 years ago

  i can confirm its broken in blender 3.3

• Diego

  over 2 years ago

  Went through the script and it seems most of the issues people are having are from AE writing tiny values in scientific notation. If you really need this to work, here you go.

  When applying a keyframe, the script checks if its a digit. Values close to 0 can look like this (2.98088e-16) and fail the check since it contains an e.
  Checks look similar to this
  if keyFrameData[wordNum + 2].replace('.','').replace('-','').isdigit():
  so the . and - aren't the issue since we're removing them before checking if the value is a digit.

  Adding .replace('E','') somewhere before isdigit() will fix this, but it has to be done throughout the whole script. It has to be a capital E because in the beginning of the script all e's were capitalized so floating point values can work in blender.

  That might be enough to fix it, but I was also having issues with this.

  # PASTE AE KEYFRAME DATA TO ALL SELECTED OBJECTS

  def pasteKeyframesAE(self):
  if checkClipboard(self):
  for target in bpy.context.view_layer.objects:
  if target.select == 1:
  applyTransformData(target)
  
  This might have worked on older versions of blender but it doesn't work for me for some reason. Changed it to this and errors went away.
  # PASTE AE KEYFRAME DATA TO ALL SELECTED OBJECTS

  def pasteKeyframesAE(self):
  if checkClipboard(self):
  for target in bpy.context.selected_objects:
  applyTransformData(target)

  I'm only going to write these snippets since that's all that is needed to get it running consistently and there doesn't seem to be an alternative script. I also messaged these changes to the creator back in march but they have not responded.

• jangseungjin

  over 2 years ago

  hi I’ve updated After effect to 2022 version
  is it still able to be used for the New version ?
  or could you update for that

• frederik Frost

  over 2 years ago

  Great plugin, but how do I use the point cloud function? There is nothing about in the documentation.

• Bad Monk

  almost 3 years ago

  Great add on. Use camera tracker in AE then simply copy and paste into Blender! Works awesome! Just remember to move key frames across to start at frame 1 otherwise the track will be off and not work correctly.

• Displaying ratings 21-30 of 58 in total

Purchase this item to leave a review!