Jump to content
AutoDesSys Forums

3dworks

Members
  • Content count

    418
  • Joined

  • Last visited

  • Days Won

    13

3dworks last won the day on July 11

3dworks had the most liked content!

About 3dworks

  • Rank
    Advanced Member

Contact Methods

  • Website URL
    http://www.3dworks.com
  • Skype
    mgroeteke

Profile Information

  • Gender
    Male
  • Location
    Berlin, Germany
  • Interests
    architectural photography, architecture

Recent Profile Visitors

362 profile views
  1. could not edit my previous post, but here it is: you still need to add 180 degrees to the camera's and lights "B" values manually in the coordinate manager, once the scene is imported into cinema. found no other way to fix this, but at least it will work consistently.
  2. interesting topic! i would like to confirm it is working with cinema 4d R20 and FZ 8.6.x at export you need to set options as per screensot. import in c4d per standard settings and units set to meter (in my case). there is an issue with UV mapped textures, but i am using this only for cameras. for objects, the LWO format is reliable, but you will need to open in LW modeler and resave the file once before importing into cinema for not getting any issues.
  3. 3dworks

    export vrscene?

    nevermind, found it by myself, it was only available in the vray toolbar, not in the file menu...
  4. 3dworks

    export vrscene?

    is it possible to export a vrscene from formz? i don't find any export option in my setup...
  5. 3dworks

    Group for "Views"

    +1
  6. 3dworks

    Components and Symbols

    unfortunately, this is still an area where FZ needs to get stable and reliable again compared to old version 6.7.x... i am using FZ mainly because of this feature and try avoid issues when handling components with following tips: * always just use embedded library. most handling of external libraries got me into troubles. * after copy and paste of components from one to another scene, save scene, quit FZ and reload before editing further. * don't ever nest components (this was possible in old version 6) - hope this will come back as reliable feature in version 9? * after updating components or committing a series of changes, save file under a new version, quit FZ and reload scene. many times this fixes unexplainable issues. * try to be very careful when using layers within components. if you delete components which use an inactive layer weird things can happen. in this case, better go back to backup and retsart operations. * did i say to backup as much as you can? use the save incremental file function to do so, and do it specifically before and after creating a new component. hope that helps markus
  7. 3dworks

    please improve the underlay tool!

    unfortunately, using billboards is only an option in certain cases but no a good workaround in most cases, imo. also a simple plane with texture can work, but has same problems. what we really need is a precise and interactive tool...
  8. 3dworks

    rotate and scale while move

    hi marcelo, i was talking about an *interactive* placement tool, not repeat last transformation or fixed macros... thanks anyway.
  9. it has been said many times: please improve the way we can place underlays. this is SO important if you need to model based on scanned drawings or any photo reference. the current system is so cumbersome. open the reference plane parameters box, set up parameters, close the box to see if underlay is matching. rinse and repeat for the next 15 minutes. a simple 'screen update' button already would help a lot and reduce time to a minute. better than that, scale, size, move and rotate handles could make this tool really helpful and reduce setup time down to maybe 20 seconds. i just remember the good old times when pylon's plugin did this job in seconds... currently working again on a project where i have to setup dozens of underlays. it is just frustrating!
  10. 3dworks

    display components as boxes - crash

    hi rob, i guess it's not because i never had any issue using my nvidia on that mac. also this would mean that i would have issues when in wireframe mode generally in FZ, which is not the case. display is very fast and responsive even with extremely high polygon count in this mode, it just happens with this special components function. this cards are officially supported by nvidia on macos with current drivers, which get updated with every new security update. i'm regularly using lightwave, cinema 4d (both with octane renderer), after effects, photoshop, etc... not any issues! yes, i'm still on macos 10.13.6, because 10.14 has no nvidia drivers yet. slowly all 3d apps will migrate to metal anyway, but it will take some time.
  11. Interesting topic and discussion! What is the best way to save an object for Revit actually, and what are the best export options from Revit for importing into formZ? Is there a best workflow in your experience? I am in the progress of working with a company which uses Revit but needs modeling support from time to time for more complex designs. I am on Macs, and have no Revit exerience anyway, so no chance to test it inhouse. Any advice would be helpful. And a question to our formZ developers: will the IFC format be supported in V9? Cheers Markus
  12. would it be hard to implement a fast postioning mode which uses mouse wheel for rotationa nd mouse wheel + modifier keys for scaling a picked object while moving? after positioning, rotating and scaling the object it would be release with a click, as per the simple move command. this would be extremely helpful when having to reposition and rotate hundreds of objects by hand! or is there a script or any key shortcut options to setup this mode? cheers markus
  13. anyone having the same issue? if i switch component display to 'box' as soon as i try to select components, formz crashes. very unhappy with this, because i am editing a scene with a massive amount of components and see no way how to speed up display. working in wireframe mode already. i e-mailed the crash report to support but got no answer yet. max os 10.13.6, latest nvidia drivers, nvidia 980ti card
  14. 3dworks

    FormZ to C4D Workflows

    i've recently switched over to C4D and LWO seems the best solution so far for me if you are coming from a lightwave based workflow. just as an additional tip when using LWO: for some reason, latest versions of FZ for some reason don't export a 'clean' LWO format which is directly accepted by C4D. the workaround is to use LW modeler 2015 or earlier (2018 /19 LWO format will not be accepted by C4D at this point), open the exported LWO and just resave the file. then import this copy into C4D, using the "split selections" option to keep proper layer naming and material assignments easier. works like a charm. the problems i've found when importing FZ into C4D R20 with the other solutions presented here are: with OBJ is that you cannot keep layers as in your FZ scene. unfortunately, riptide pro is not yet available for R20, so maybe this plugin can solve this issue when importing an OBJ generated by FZ. DAE seems not to work at all, i only get an endless objects list with all items named 'node', also all materials are set to a shiny chrome ball. 3DS seems not to work at all, there seems to be a fundamental precision / scale issue DWG works well (C4D R20 imports this natively) but all object / layer names will be lost. FBX has huge issues (no correct layer / object names)... there seems unfortunately still no viable / reliable way to bring lights and camera into C4D from FZ. i thought DAE would be the solution, but it seems to have rudimentary implementation and honestly i don't know if it's C4D fault.
  15. 3dworks

    Forum Functionality is broken

    i also noticed now that wen logging in with my credentials for a short time, the site is marked as 'not secure'... this makes my alarm bells ring... can you explain this behavior? i will not login anymore as a user until i'll be sure that my passwords are not intercepted by some obscure site.
×