2008-10-18 02:45 AM
2009-02-27 08:05 PM
b_lutz wrote:Good to hear from you, and i must say this interaction from both GS and Maxon is very encouraging. Thanks for asking for our input.
..I am following this thread since some time now and there is much important information for me in it. As Gergely already pointed out, the way data is exchanged between ArchiCAD and CINEMA 4D si exchanged changed. Those changes brought some problems, but also gives us much more possibilities in the future.
b_lutz wrote:So as i mentioned before our clients (currently all architects) are using both ArchiCAD (v10-12) and Cinema4D (R10-R11). These offices are generally focused on smaller scale residential, commercial and educational projects although there are a few larger projects in the mix (largest being a high-rise project). Competitions are common as well.
..what kind of work you are doing and what kind of projects you are working on.
b_lutz wrote:Most of the offices using C4D are using it both for Visualization (the Exchange Plugin) and Modelling (the old 'Maxonform' plugin).
To help me understanding your problems better, could you please give me a quick overview on your workflow ..
b_lutz wrote:Mostly stills, animations not very often (may change, just a training issue we are working on). The VRayforC4D render engine is also used by some and renders usually go through post in Photoshop.
Are you mostly doing still or animations also? Are you using any other software after rendering in CINEMA 4D?
b_lutz wrote:In general the existing Exchange Plugin works really well for Viz purposes - there could be some improvements the others who directly use this every day may be able to contribute, i will give it some thought and get back.
What is the biggest problem with the exchange between ArchiCAD 12 and CINEMA 4D?
b_lutz wrote:As i said, they are all architects
How often does a project get updated and what kind of data is getting changed?
2009-02-27 09:03 PM
Macbook Pro M1 Max 64GB ram, OS X 10.XX latest
another Moderator
2009-02-27 11:02 PM
b_lutz wrote:
could you please give me a quick overview on your workflow
b_lutz wrote:
and some information on what kind of work you are doing and what kind of projects you are working on.
b_lutz wrote:
Are you mostly doing still or animations also?
b_lutz wrote:
Are you using any other software after rendering in CINEMA 4D?
b_lutz wrote:
What is the biggest problem with the exchange between ArchiCAD 12 and CINEMA 4D?
b_lutz wrote:
How often does a project get updated and what kind of data is getting changed?
2009-02-28 10:59 PM
Wokka wrote:A real bi-direction exchange (or Hotlink) that retained some intelligence would be great - understand there will be some things that just cannot be translated between the two though.
This is just an idea for discussion. In ArchiCad we create viewsets for our documents that basically take a snapshot of the project with particular layers, pens, materials etc. Integration into Archicad via saving a view of the model could then basically 'hotlink' our file to C4D. Save ArchiCad and run an 'update ArchiCad model' in C4D would be real integration. I think this would be good generally for projects but there could be issues with saving different versions, teamwork etc. Just a thought.....
2009-03-01 11:08 AM
owen wrote:Good in theory but I always use C4D for importing better cars, trees, people etc so the render in C4D would really just be an update of the C4D file. Which lighting rig would it use?, etc would be an issue if you just send it to C4D.
Being able to define bi-directional links between AC and C4D cameras could even open the door for accessing Cinema functions directly within ArchiCAD, such as 'Render Camera in Cinema4D' ..
2009-03-01 04:48 PM
Wokka wrote:We do pretty much the same (adding entourage, etc in C4D) and you said basically what i am suggesting - trigger a render in the linked application - although I am not proposing to be able to alter C4D render settings from within AC, you would have to switch to C4D to do that. But if say a camera is linked you could trigger a C4D render of the linked camera using the linked files current render settings. But maybe it is not really that useful afterall - it would just automate the 'Update C4D with AC Model' and 'Render Active Camera' processes.
Good in theory but I always use C4D for importing better cars, trees, people etc so the render in C4D would really just be an update of the C4D file. Which lighting rig would it use?, etc would be an issue if you just send it to C4D.
If you were to follow that thinking, you'd really be saying instead of render with lightworks, render with AR, render with Maxwell , render with Vray etc.
Wokka wrote:I probably did not explain myself clearly enough. I actually think Graphisoft should focus on providing better links to other rendering programs than providing a better built-in render engine and put more into the core 'BIM' tools. I can understand the market logic of doing the latter though - many people do not have access to or want to buy a separate render engine (look at what Revit has available). The above camera-linking function is just one idea for better linking of the two, beyond a simple linking of the model. It would somewhat simplify things for basic rendering tasks that are just beyond what the internal render engine can do. It seems like Maxon+GS are looking for these sort of opportunities - who knows what the new 'Melange' API will allow. But i agree entirely that if it slows development on their respective applications core functions then it should be given a low priority.
I've always believed Archicad should an architectural documenting, BIM tool first and a renderer second. Sure lightworks etc should be improved and developed, but not at the expense of the real job ArchiCad does. We all know it has a lot of unresolved issues with new tools that don't quiet work properly and haven't been fixed for several releases (ie SEO's, libraries, curved roofs etc). Let Graphisoft work on ArchiCad, Maxon work on C4D and just maintain a good link between the two.
Wokka wrote:Yes very different functions and I am also very aware of its problems! Objects created in C4D are often so large as to be unusable in AC - if they do anything more on the 'Maxonform' side of things this really needs to be the highest priority. Maybe there is some way Cinema can be leveraged to enhance AC tools, but the result needs to be way more flexible and intelligent than the current 'Maxonform' output (bloated GDL objects). e.g a wall transformed in C4D should remain a wall back in AC, not a dumb GDL object. However I have hopes that Graphisoft will be improving their own modelling engine and tools, includi....
The current plugin (NOT exchange plugin but 'Maxonform') for me is completely separate software and it's only use is creating distorted objects not easily generated in ArchiCad. Unfortunatley they are completely bloated and generally unusable in mainstream documentation (unless you like to hack GDL) but OK in the design process. Maybe new API's like 'objective', cadimage, etc might fill this role better eventually?
2009-03-02 12:57 AM
2009-03-02 10:02 AM
SunnyBris wrote:I had completely overlooked this .. no idea why as it is THE major hassle with imported AC geometry using the existing plugin. Please do something to fix it, it screws up any volume effects.
...we use Vray for C4D predominantly but have to reverse the normals on the glass material polygons after every translation for the vray material properties to work properly. Is this something that can be fixed or even for the material and cinema to keep the reversed properties when it gets re-translated?
Another wish is for an option for the materials to be ordered by name and not just poly count on import.
2009-03-02 11:02 AM
2009-03-02 04:32 PM