Jump to content
AutoDesSys Forums


  • Content count

  • Joined

  • Last visited

  • Days Won


Everything posted by 3dworks

  1. I'm rendering with Octane for a few years right now and very happy with it. Workflow currently is to export into Cinema 4D where i setup scenes and render via the plugin. A direct connection would be cool, of course. Rhino has it, btw.
  2. Pixar's USD exchange format seems to establish as a new standard nowadays in many 3D apps. The latest C4D version for example will support it. Render engines like Octane are starting to support it. Can we expect FZ to incorporate it soon? Maybe this format could solve once for a while all exchange problems between FZ and other apps, if well implemented. I'm still missing an export / import module in FZ which handles geometry, surfaces, textures, cameras and lights alltogether in a decent way. https://graphics.pixar.com/usd/docs/index.html
  3. 3dworks

    USD as file exchange module

    i agree on your points as well, BIM support would be crucial for the future of FZ. the great strength of USD is that lots of platforms are adopting it right now and we need one reliable way to transfer geometry, materials (or at least coulors), layers, cameras and lights from FZ to other platforms. no current format is doing this well, especially if you consider camera settings. one format which could do it would be FBX, but it is reduced to geometry only in FZ. DAE collada as well. i also found the exported data missing correct material settings. these are long term and reported issues with the exporter plugins. it seems to me the only format currently updated with each version was and is DWG. in my workflow, i am modeling geometry and assign all materials + layers in FZ, then export the scene, import it into C4D where i do the setup and then render with the octane plugin render engine. the problem is: i cannot transfer my FZ scene as it is to C4D, just the geoemetry + materials + layers and only by exporting to LWO first, then importing this format into C4D. all other exchange formats are not working as well, because they are missing layers, materials or even don't export geometry as well.
  4. 3dworks

    Export as 3DM file

  5. Could we get an additional option to trigger a backup copy manually via a hotkey? This would be extremely useful as the time or number of operations triggering sometimes can produce lots of unnecessary action / backup copies. Also, the incremental save via LAB extension will alter the file name, which is not always what we want. Thank you for consideration markus
  6. ...is this going to be fixed? this doesn't really inspire confidence to the user. cheers markus
  7. 3dworks

    DWG import is still without layouts!

    I forgot to add, that workflow wise it could be also a big improvement if we could just import vector PDF data into FZ, provided we get an import dialog which gives us options to set a scale and maybe some filters for the imported geometry.
  8. I am not happy with the DWG import in FZ V9. Why is there no option to import DWG files as they where intended to see, with their proper layout / viewports settings? I thought this would be improved when departing from V8 but still it's not there in V9. If I import any DWG into your competitor modeling app Rhino, it will be shown as intended by the author, with proper layout, exactly as the reference PDF's which show the plan as it is intended to be seen. The problem is that FZ always imports ALL data on one "sheet" without any layout. In general drafters use large areas of these sheets for setting up the drawing or designing variants. These are all imported by FZ, which makes it sometimes impossible to guess what part is relevant for the final design. The only refenrence in this case is to get PDF'a for all plans from the architects as references and then cleaan up manually the FZ imported DWG's to finally get the intended reference / underlay in FZ. This is just too time consuming! I remember in an older version of FZ once there was an option to choose layouts when importing DWG's but I forget which version that was. Other apps like Rhino show that it is possible, so please add this feature again to the DWG import module - it's a big workflow stopper here right now.
  9. 3dworks

    Align2 v.9

    chris, thank you for generosity and for sharing this, will try it when V9 becomes more stable and my working version...
  10. 3dworks

    V-Ray for FZ update?

    any updates on this?
  11. 3dworks

    formZ v9.0.3 Now available

    After seeing that you added a minor feature to the underlay function, which is always good, the question raises again: can we expect any real improvement to the workflow of this tool? This was one of my many unfulfilled expectations for V9, a well working underlay management... The best thing we ever got was the Pylon plugin years ago, but with the discontinuation of it, we never got an alternative to number typing. Right in these days I am again struggeling with lots of image underlays which need to be aligned. Just frustrating. What I would expect from a professional application is at least that level of functionality: place, scale and rotate with the mose the underly until it is matching, so we can match any imported image in less than a few seconds. Honestly, the current way to type in data by trial and error is something which i would accept 30 years ago. Sorry for being so harsh, it's just that I still had hopes for FZ9 and expected also other important improvements which I/we requested over years. Not sure if it was even worth the upgrade price at this point. I'm still working with 8.5 because of stability issues on my system. Also, I agree with some other remarks here in the forums. I'm not reporting bugs much more for a longer time already because I have the impression reports are not followed up well since Paul's sad departure.
  12. when i export my scene as SKP 2017 and reopen this in sktechup make 2017 edition, all cameras are missing in the imported scene. same happens if i import this SKP directly into C4D R20. is this a bug or a missing feature? if it is a missing feature, please add this functionality ASAP, because it's the only way to get cameras out of FZ to other 3D apps currently. FBX or 3DS are not working properly, DAE export from FZ does not support cameras (or even materials) and WRL is nowadays obsolete and not supported by anyother 3D apps we are using here.
  13. what is the best way to get a terrain model from point cloud data? i have both a coordinates list in CSV format and a DWG with all the measured points as crossed lines in their real space position. i am already searching around for some time but could not get any viable solution for this. i remember FZ had a plugin handling point clouds in the past - but this seems to be discontinued? cheers markus
  14. 3dworks

    from point cloud to terrain?

    a native / plugin solution for FZ would be best imo. something which would be integrated to the existing terrain tool would be my greatest wish and allow for smooth workflow. most third party options are limited, for example not available on macos or quite expensive (like the c4d plugin)...
  15. 3dworks

    from point cloud to terrain?

    maybe something like this old tool for sketchup a plugin which is called topshaper.
  16. 3dworks

    from point cloud to terrain?

    will there be a tool / plugin for cloud modeling / terrain forming from point clouds in FZ9? this kind of situation is recurrent and most time it is a lot of work to do it by hand.
  17. 3dworks

    export vrscene?

    is it possible to export a vrscene from formz? i don't find any export option in my setup...
  18. 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.
  19. 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.
  20. 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.
  21. 3dworks

    export vrscene?

    nevermind, found it by myself, it was only available in the vray toolbar, not in the file menu...
  22. 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
  23. 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!