Jump to content
AutoDesSys Forums


  • Content count

  • Joined

  • Last visited

  • Days Won


Everything posted by 3dworks

  1. I'm currently trying to work on a complex project with the latest available 9.1 version but very unhappy with how many bugs when dealing with components make FZ simply hang. I reported only a few, as not all steps are reproducible and every bug report takes time. Mostly i found issues when making a copy of a component a new unique component. for example assigning a new layer to this one makes hang FZ. Also just trying to rename a component after certain steps makes FZ hang. I'm getting about one hang every 10 minutes now, so I guess i will - once more - switch back to FZ 8.5.x, which is really frustrating, as I will also need to switch machine. Anyone else having these issues?
  2. You should first of all respect rules of conduct here.
  3. Yes, crossing fingers. I've given up on 9.2 as well this morning after trying to handle my current project. Components geometry simply disappears when trying to edit with "open component" command from the components palette. Some components material assignments get scrambled over time as well. After trying to edit components sometimes layer visibility settings are unfunctional until restart and reload of the scene. Too much stuff going on and as ZTEK reported very well, in an illogical way, so reporting is extremely difficult, because mostly there are no reproducible steps to make the bugs happen. So, switching back once again to version 8.5.6 which for me remains the most stable version ever. Some bugs there as well, but at least i know how avoid them.As long as I can keep my MacOS High Sierra Mac running with it, it remains a backup solution but working. Fortunately, FZ has the ability to save to older versions!
  4. Thanks for getting back! I see now that I sent my licensing issue email to sales@formz.com on October 9 , maybe because i thought licensing is part of their work. I never got a reply, but probably this is not your department, then... Also, I did receive all your answers on the Vray server issues, but after telling you in the previous email that I did a reinstall of the server - and sending logs and screenshots - you recommended me to do a clean re-install. Not really helpful in this case... This issue is still unresolved, but I do not need to use Vray at this time.
  5. No airing here, and I didn't get any answer from FZ support for all my last e-mails, be it just crash reporting or direct support questions. FZ Support used to be one of the best services of any software I ever used, but nowadays unfortunately it is not anymore. After the sad departure of Paul Helm a few years ago, everything changed to the worse. One example: a few weeks ago I was even in a very bad situation when I couldn't use FZ on my new laptop beacuse of licensing issues. I really needed to work on my trip, but couldn't because support didn't answer my email. Also, for what are forums here if not for sharing experience and asking questions which maybe support couldn't easily answer from a technical point of view? Why getting polemical over this? Aren't we all in the same boat using this software which is working so well on one side and at the same time has so many bigger or smaller quirks on the other? I will now try the fresh new 9.2, hopefully something got better. Unfortunaltely, the "changes" document reports ...no changes.
  6. Is there any tutorial about how to import the datasmith file and assets into unreal? I don't get this done without getting deeper into the matter. At least, it's not working drag and drop, LOL. Twinmotion seems to work well so far!
  7. 3dworks

    Imager V9 not working?

    I read in older forum posts that Imager had some quirks which needed to be addressed. Il the latest V9 incarnation it seems not to work at all. if I load a scene and set image type to shaded work for all images, then try to render, I'm getting "The following entries in the imager set have a rendering type for which no exporter is loaded and printing is turned off. These entries will not be rendered. Select OK to proceed." I don't get any solution out of this dialog, also i cannot find exporter settings anywhere. What to do?
  8. 3dworks

    Imager V9 not working?

    I could fix this by not using default prefs but loading my existing FZ modeler prefs in Imager preferences. Honestly i don't understand what this does exactly, but suddenly i could render everything...
  9. 3dworks

    Imager V9 not working?

    BTW in FZ 9 I'm also generally missing image options in the dialog when exporting rendered images, for some reason they have been removed - in V8.6 we still had them.
  10. 3dworks

    Apple Silicon M1

    same question here!
  11. I'm always using FZ for all the architectural modeling in my projects. The modeling and polygonal editing features in C4D are extremely useful however, once the model was imported into the scene and setup for rendering. I wish there was a better data connection between FZ and C4D but actually it works quite well going the route via VRML or Sketchup format. Before switching to C4D, I used Lightwave for many years, and FZ supported that format directly. However, LW became less and less well supported on the Mac side, and C4D, while expensive, has so many useful and straightforward features that make my work much easier now. LWCAD, a complete parametric and NURBS capable modeling plugin formerly just available for LW is now availeble and actively developed for C4D, so maybe in future this could be used inside the package as an alternative modelling tool.
  12. Apart of Redshift, Otoys Octane is also available for Metal users and running extremely well. As I pushed my hardware also forward to use Big Sur and Metal with AMD graphics cards, I guess Vray without such an option will not be a likely upgrade for me on FZ right now. Running happily C4D with Octane on Macs here.
  13. wakening up this discussion again, and now we have already FZ version 9.1. is IFC file support something on the list for future versions? i'm regularly getting projects where this kind of exchange could be really useful.
  14. As I recently upgraded one of my Macpro's to use MacOS 11.2.3 (with help of Opencore and a Radeon RX580 card), I was wondering if there are any known issues with the legacy FormZ version 8.6.5 when working with this system? I'm unhappy with 9.x and still consider this version the best and most stable version I ever used. Any feedback would be extremely helpful. Cheers Markus
  15. thanks for confirming my findings.
  16. i found out a problem with components, they are definitely not working because of a display issue (AMD radeon RX580 8G card here). i guess i will have to use 9.1 at this point...
  17. Here until now it seems to work well, but i could not test all features yet. What was your problem?
  18. 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.
  19. 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
  20. 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.
  21. 3dworks

    Export as 3DM file

  22. 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
  23. ...is this going to be fixed? this doesn't really inspire confidence to the user. cheers markus
  24. 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.
  25. 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.