Jump to content
AutoDesSys Forums


  • Content count

  • Joined

  • Last visited

  • Days Won


3dworks last won the day on July 11

3dworks had the most liked content!

About 3dworks

  • Rank
    Advanced Member

Contact Methods

  • Website URL
  • Skype

Profile Information

  • Gender
  • Location
    Berlin, Germany
  • Interests

Recent Profile Visitors

246 profile views
  1. 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.
  2. 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!
  3. 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.
  4. 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
  5. 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
  6. 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
  7. 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.
  8. 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.
  9. 3dworks

    Forum Functionality is broken

    also, the user tab is not working at all anymore. any plans to fix this?
  10. 3dworks

    form•Z 8.6.3 Update Released

    i can confirm as well the stability. a few strange things still happen with components, and when deleting objects related to opengl, but very few crashes until now!
  11. 3dworks

    From Foem Z to Unreal engine

    i guess FZ with a direct export option to unreal engine would attract many new customers. i'm also very interested into this connection, but currently using other 3d packages on mac for this purpose seem to be more promising. maybe FZ can add this in the upcoming V9?
  12. thanks setz, but this will only work (VRML2 format only) with C4D but not with Lightwave, which does support this format only in modeler for exporting object data.
  13. I am currently struggeling when i try to export camera (and to a minor level light information) from my FZ scene via DAE or FBX to other programs like C4D or Lightwave. The exported FBX files have all cameras set at to position 0,0,0. Unfortunately, the DAE export module lost the ability to export cameras when FZ jumped from version 7 to 8.x... So one workaround is to save the scene in V7 format and then export from FZ V7 as DAE. But please could you reintroduce camera and light exports in DAE for V 8.x or - if you consider collada DAE as a dead end - at least fix FBX and make it a reliable exporter for geometry, hierarchies, textures, surface definitions, cameras and lights? The interchange between 3d platforms nowadays is more vital than ever to keep FZ part of production pipelines. Removing features out of existing export modules is the wrong way to go. Keeping updated and bug fixed import and export modules is the best way to convince old and potentially new users to integrate FZ within their pipeline.
  14. With the new version of Lightwave 3D, a new format of LWO is used which is not loaded by current FZ versions. LW2018 can save in the LWO2 format as an option and natively read LWO2, but it makes file handling more complex. I wonder if it would be possible to implement import and export for this format? See here for SDK: https://www.lightwave3d.com/lightwave_sdk/ thank you markus
  15. 3dworks

    open / add project broken in last build?

    thanks for testing! i found out in the meantime: it was related to a specific project file. i sent this file to tech support - hopefully they can fix this issue.