Jump to content

herbieherb

Member
  • Posts

    284
  • Joined

  • Last visited

Everything posted by herbieherb

  1. Thank you very much, I didn't know that there are any additional commands that are not in the function reference. SetDropShadowByCls worked fine. What surprised me a bit is that a command to set the default shadow in the attributes palette to class attributes is missing. Even if you press the button 'Assign class styles' in the attributes palette, the shadow is not set according to class. Was this forgotten when the shadow option was added?
  2. Any news on this? Im also trying to write multiple lines of text into the same message box. None of the above worked for me.
  3. I'm trying to make a script, that sets all attribtues by class, but i can't find a way to set the shadow settings by class.
  4. The Threadripper 2990wx actually is the best you coul'd get for cpu rendering with cinema4d/vectorworks. The only systems that beat it are very expensive dual and more prozessor xeon machines. But for the price of these systems you coul'd also get yourself several threadripper machines that you use together with cinema 4d pro. So nothing beats the threadripper in cpu rendering atm.
  5. It's exactly like you say. It's damn good hardware and except the basic version at a very good price. But unfortunately an incredible waste of money to use for Vectorworks.
  6. Here is how i woul'd model a pool like this:
  7. Yes, that should be possible, but it requires some work. I will take a look at it on occasion. Until then you could integrate the script as a menu command into your VW-UI. Then just shortcut it to use the script faster.
  8. Still had a bug this one fixes it hopefully: 😁 export image v2019.vwx export image v2018.vwx
  9. Fixed it: export image v2019.vwx export image v2018.vwx
  10. Found the issue. Selected objects from other layers interfere with the script somehow. I'll try to fix it.
  11. I have extended the script so that rendered viewports can now also be saved directly as images. It also saves the images with the object name as filename now. You'll find the new scripts at the above mentioned thread in the script section.
  12. I have extended the script so that rendered viewports can now also be saved directly as images. The script now takes the name of the object as prefix of the file name. Here is the current script: export image v2018.vwx export image v2019.vwx
  13. You have to copy and ungroup the viewport first.
  14. For Vectorworks and CPU rendering the MacPro is totally overequipped. ECC-Ram doesn't do anything in Vectorworks. More than a single graphics card doesn't help either. Without needing ECC-Ram, you can also do without the expensive Xeon processors. A threadripper provides the same performance for much less money. Unfortunately the same motherboard is built into all MacPro. In the basic version this is hopelessly overpriced, because it is made for hardware up to 50'000$. So in the basic version simply too much performance remains unused. We Vectorworks users also have some special requirements. Who doesn't render, is well served with a gaming PC with Profi SSD, and who renders needs Gaming RAM/GPU and Profi CPU/SSD. Neither of these is served with the new Mac Pro, despite its modular design.
  15. Here is the cinebench of a 64-core dual xeon computer. It gets a score of 5626. But one xeon processor costs as much as my hole threadripper computer. The 32-core Threadripper gets nearly the same score (5677).
  16. I don't think it's worth it. If the performance of the 32-core threadripper isn't enough for you yet, you'd probably still be cheaper with a second threadripper computer than with a dual processor xeon board. With Cinema4D you have the possibility to combine the computing power of both computers. You may also want to wait until autumn. AMD has just officially announced that the Threadrippers will get a 7nm update. Rumor has it that there will be up to 64 cores.
  17. The Cinebench OpenGL results depend more on CPU single core speed than on the GPU. It's because the test doesn't stress modern GPUs at all so the bottleneck is always the CPU no matter how strong your GPU is. It just shows the performance with small models. Much more important than the Cinebench GPU score is that the model fits into the VRAM of the graphics card and that it is quickly loaded into it. That's why many users prefer the more expensive gamer graphics cards for Vectorworks. They have more VRAM and more cores than consumer graphics cards and still have faster clocked VRAM and faster clocked cores than professional cad graphics cards.
  18. Threadripper 2990WX OC all cores @ 3.7GHz
  19. You're right. In single-core tasks the Xeon is superior to the Threadripper. Unfortunately this doesn't make much difference for the performance in Vectorworks in practice. Except that you get a bit more performance out of OpenGL, you don't notice much in your daily work. With the vast majority of other single-core tasks you don't notice any difference, because the bottleneck is not the single-core speed of the processor. Anyway, that doesn't justify betting on the nearly $1000 more expensive processor. Especially because we are talking about a rendering workstation and here the threadripper can score again with its multicore performance. The iMac-Pro as a rendering workstation is simply too expensive for the performance it delivers in Vectorworks. I'd definitely wait to see what the next (hopefully modular) MacPro will bring.
  20. Here is a script that exports images directly and lossless. Take the script at the bottom of the thread. The pictures get a date stamp automatically. With it you can easily create a chronology of renderings. However, you have to ungroup a copy of the viewport to get an image before running the script. export image file
  21. Luke from the german forum added a name generator to the script. So the filenames automatically get a date stamp and a overwrite should not happen anymore. export image.vwx
  22. You pay a lot for things that bring absolutely no benefits for vectorworks. 10gb ethernet will not make your project-sharing any faster. The bottleneck is the single core cpu score. The slowed down xeons are performing really bad for single-core tasks and with multicore tasks the threadripper kills it anyhow. ECC ram does not bring any more stability to vectorworks. The graphics-card has a lot of cores but it's slow clocked. A gaming-card woul'd suit way better for vectorworks. All in all, a fully featured iMac Pro only delivers a small amount of the power of a threadripper into vectorworks, but costs many times as much. I would only recommend it if you need the parts for other software. Vectorworks will perform very well on it. But the iMac Pro just isn't worth the money for Vectorworks alone.
  23. The iMac Pro isn't worth the money for vectorworks. Get yourself a threadripper rendermachine instead. Or at least wait until apple brings out its new MacPro.
×
×
  • Create New...