Not that it much matters, but I'm running AECS3 on Win XP. Anyway, what I'm trying to do is find a way to import 3d files I created in Blender 2.5 into After Effects. I've spent quite some time trying to find a script or something that will work, but without much luck. The scripts I've found are for earlier versions of Blender and may not be compatible with 2.5.
Does anyone know of a script that will either:
One other thing: Why can't AE import .obj files? That's an extremely common (from my experience since I also do some work in DAZ, and have played around with Cinema 4D which is way out of my budget) format for 3d....
* The formats that Blender 2.5 exports are:
After Effects is a composting, motion graphics, and 2-2.5D animation program. As such, you will not be able to import 3D scenes or models (such as .obj files) and be able to work with the scene natively. Instead, you should animate and model, texture and light, and then render (in one or several passes) in your 3D program (in this instance, Blender), and then import the rendered image sequence into After Effects for further animation, compositing or effects work.
If you have Photoshop Extended, you can import the obj into that, save it as a psd file, and then open the psd in AE (make sure it's set to Live). You can then apply transforms on your 3d model (rotate, pan, scale).
To me, it's a bit silly that AE can't open .obj, .fbx or .dae files. They're more expensive, but Fusion and Nuke can.... AE would probably have to be completely rewritten...... Should have done that while converting to x64....
PS, there might be a script for Blender that can export nulls, lights, cameras into AE...
Why can't AE import .obj files? That's an extremely common
Well, if AE was a 3D program I'm sure it would, but as they otehrs said it isn't and you are expecting something from it that it cannot do. It may offer more 3D features in the future, but for the time being that entails the use of the described workarounds or the use of third-party plug-ins.
You know, I'm starting to feel a bit like Peter in Office Space and dealing with TPS reports. I understand that AE is not a 3D program, I really do. I also understand the difference between a 3D program such as Blender or Maya and AE.
(Note: if your feelings get easily hurt, please stop reading here.)
However, the issue of being able to import obj files is the least of my worries, but everyone (except David) seemed to latch onto that and proceeded to pound me over the head with it. My issue was that I couldn't import 3D files I'd created in Blender so I can composite them. You can import files from Maya (a major 3D app) but not Blender, so that's why I'm wondering why you can't import .obj files which are a much more common file type for 3D. It's that simple. Not only is Maya listed in the acceptable files list in the Import dialog, but I've seen 3d files imported into AE in more than one online tutorial. That was ONE sentence out of a much larger post. And NO, I'm not looking to work with those files like I would in a 3D program where I'm doing modeling, changing textures, etc. All I'm looking to do is import a 3D file so I can composite it (sorry I wasn't that specific, but I'd figured people would understand that or at least ASK WHY I wanted to import if they weren't sure). Think about it, if I can do modeling in Blender, WHY would I want to do modeling in AE?
To me, it's amazing that someone with 13 posts to this forum can understand that better than people who have hundreds or thousands of posts. I'm not angry at anyone, just frustrated and aggravated that rather than post something helpful, some people on this forum would rather repeat the same point that addresses a minor issue. I really don't need to be told 5 times that AE is not a full fledged 3D program, as I understood that already and even if I didn't I would have understood that after the first reply addressing that minor question. Again, I'm not looking to hurt anyone's feelings, but try to get people to understand that if an issue is fairly simple, the same (perceived) answer doesn't have to be posted again and again and again. Doing so doesn't help the OP at all.
Sorry that you feel lambasted. That was no one's intention, I'm sure.
The reason that you see a filetype import for Maya is not that it can import Maya geometry directly, but it can read a Maya ascii file (not binary), and use that data to import camera and locator (aka "null") information into a matching composition. No geometry is imported in this process.
David gave you a workaround of being able to tumble, dolly, or track around geometry made in 3D. Still, you may find the results limiting in comparison to working natively in a 3D application.
I think your best route may still be to render out image sequences in one or more passes and then composite in AE.
Can you point to a link to one of the tutorials that you mentioned so we can see exactly how they tutor imported and worked natively with 3D geometry? Zaxwerk's Invigorator is the only third-party plug-in that I'm aware of that has some limited functionality for these means. However, being that it's a third-party plug-in, this is not a feature that ships with After Effects.
Thanks Timeremapper. I know it was no one's intent to do so, but it's just really frustrating to be told the same thing over and over. Anyway, here are some links
If you watch the first tutorial, at around 27 minutes and 25 seconds, you can see that an image (PNG) sequence in 3DSMax was rendered, and then imported into AE. I don't have time right now to watch the second tutorial, but I'll try later unless someone else can get to it first.
At the beginning of the tutorial, a reference for the 3DSMax scene was exported via a custom script from AE, but that's all it was. A reference.
I briefly skimmed through the second tutorial, and you'll be able to see that in the very beginning of the tutorial, Andrew renders out a PNG sequence from 3DSMax. Again, he seems to be rendering image sequences as noted earlier, and compositing them in After Effects. FWIW, David has been posting on the After Effects User forums for years, despite his 13-post count. He's also the resident XSI advocate .
The forum format got switched over a while back, and a number of users got locked out of their old IDs and as such lost their post count.
By definition, OBJ is a geometry-only format (ASCII formatted vertex and polygon lists) from the stone age of computer graphics. Asking for the ability to import it implies just that - you want to animate geometry. A Maya file on the other hand is a scene file that always contains a default camera, a default light and may optionally contain other items/ entities. That does, however, not mean that AE would/ should be able to translate them. It's no different with .blend files, MAX scene files, Collada files etc. - there are scripts that can convert entities that exist in AE and those programs, but neitehr provides a facility for translating geometry because AE simply can't render it in any way without external help. That's al lthere is to it. So ultimately, we fell victim to a misunderstanding because you may not have used the right terminology. That's all there is to it. And don't worry, David is just as much a veteran as some of us. He just prefers not to post that much, hence his low count (or did the black monster swallow his points during the forum transition?) Anyway, no hurt feelings on eitehr side, I hope.
Yes, as others have said, After Effects has many ways of importing 2D image files rendered out of 3D applications, and After Effects has many ways of importing camera data from 3D applications. That's great, because After Effects has internal representations of 2D layers and cameras.
But After Effects can't import 3D objects/models.
The closest that we come to an exception is that After Effects can import a PSD layer that includes a 3D object, and then use the internal Photoshop rendering engine to render that into a 2D image.
Europe, Middle East and Africa