Jump to content

herbieherb

Member
  • Content Count

    163
  • Joined

  • Last visited

Everything posted by herbieherb

  1. herbieherb

    ExportImageFile does nothing

    I am trying to make a script that exports an image object to a specified file path. Everything works well but vs.ExportImageFile(hImage, path) does nothing. Here is the script: ________________________________________________________ #Get selected bitmaps crit_ = '(((SEL=TRUE) & (T=BITMAP)))' out_list = [] def Add_Handle(obj): out_list.append(obj) vs.ForEachObject(Add_Handle,crit_) #GetFirstImage hImage = out_list[0] #Choose path fileName = vs.PutFile('Choose path:', 'image.bmp') #Exort Image to path vs.ExportImageFile(hImage, fileName) vs.Close(fileName) ________________________________________________________ And an example file: export image.vwx
  2. Im trying to modify the node, so the marionette is also able to scale the symbols. The new node works fine as long as i don't use it with symbols that contain image-props. When i use them the texture is not scaled. As a workaround i can duplicate the marionette object. As soon as i delete this duplicate all the textures are scaled correctly in the original marionette object. It's like they redraw when i delete the duplicate. I also had this issue with image props within scaled symbols in a converted file from vw2018. I suspect that something with the display of image probs in scaled symbols is not yet correct. Here is a sample file of the marionette object: fill area with scaled symbols.vwx I also tried to implement the workaround into the marionette-node. When i use this script on a symbol with an image-prop inside it reproduces the issue. hSym = vs.GetObject('test') vs.SetObjectVariableInt(hSym, 101, 2) vs.SetObjectVariableReal(hSym, 102, 10) When you add these two lines. It works correctly. hSym = vs.GetObject('test') vs.SetObjectVariableInt(hSym, 101, 2) vs.SetObjectVariableReal(hSym, 102, 10) hDel=vs.HDuplicate(hSym,0,0) vs.DelObject(hDel) Unfortunately these two lines don't solve the problem inside the marionette-object. Any help is very welcome.
  3. herbieherb

    Image export of viewport with finished render

    I made big changes to the script. It now exports any number of images and rendered viewports in a single command. You can find it at the bottom of this thread.
  4. herbieherb

    ExportImageFile does nothing

    Here is a new version of the script: New features: exports All selected viewports and images at once gives unnamed images a name within Vectorworks which is also used as filename appends a version number to every exported object enhanced error messages when invalid objects are selected selects invalid and not exported objects after execution export images 1.0 v2018.vwx export images 1.0 v2019.vwx
  5. herbieherb

    set shadow by class

    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.
  6. herbieherb

    set shadow by class

    Here is the python-script i made. It works just like the 'Make All Attributes By Class' - Button in the Attributes Palette. It's meant to add as a menu commant to allow to use it with a hotkey. #v1.3 #by Herbieherb 2019 #enhanced by MRoth def SetClassAttributes(h): vs.SetFillColorByClass(h) vs.SetLSByClass(h) vs.SetLWByClass(h) vs.SetMarkerByClass(h) vs.SetOpacityByClass(h) vs.SetPenColorByClass(h) vs.SetTextStyleByClass(h) vs.SetFPatByClass(h) vs.SetDropShadowByCls(h, True) vs.SetSelect(h) objs = [] def Count_Objs(h): objs.append(h) vs.ForEachObjectInLayer( Count_Objs, 2, 0, 2 ) if len(objs) == 0: vs.FPatByClass() vs.FillColorByClass() vs.LSByClass() vs.LWByClass() vs.MarkerByClass() vs.OpacityByClass() vs.PenColorByClass() h = vs.FActLayer() vs.SetSelect(h) vs.SetDSelect(h) else: vs.ForEachObjectInLayer( SetClassAttributes, 2, 0, 2 )
  7. herbieherb

    set shadow by class

    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?
  8. herbieherb

    Return In Message()

    Got it, thx a lot.
  9. herbieherb

    Return In Message()

    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.
  10. herbieherb

    What mouse do you recommend?

    How long do you use your mouse? I I've only had mine about six months. It still looks like new, no scratches, no corrosion. Maybe they really got that under control.
  11. herbieherb

    What mouse do you recommend?

    This is my SpaceMouse settings. Feels quite natural. I couldn't work without it anymore.
  12. herbieherb

    Worth getting a dual processor motherboard?

    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.
  13. herbieherb

    Mac Pro release date Fall 2019

    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.
  14. herbieherb

    How to draft a 3D swimming pool

    Here is how i woul'd model a pool like this:
  15. herbieherb

    ExportImageFile does nothing

    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.
  16. herbieherb

    ExportImageFile does nothing

    Still had a bug this one fixes it hopefully: ūüėĀ export image v2019.vwx export image v2018.vwx
  17. herbieherb

    ExportImageFile does nothing

    Fixed it: export image v2019.vwx export image v2018.vwx
  18. herbieherb

    ExportImageFile does nothing

    Found the issue. Selected objects from other layers interfere with the script somehow. I'll try to fix it.
  19. herbieherb

    Image export of viewport with finished render

    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.
  20. herbieherb

    ExportImageFile does nothing

    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
  21. herbieherb

    Image export of viewport with finished render

    You have to copy and ungroup the viewport first.
  22. herbieherb

    Image export of viewport with finished render

    Here is a little script that might help.
  23. herbieherb

    WWDC 2019 - Mac Pro Hopes

    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.
  24. herbieherb

    Worth getting a dual processor motherboard?

    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).
  25. herbieherb

    Worth getting a dual processor motherboard?

    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.

 

7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114

 

© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

√ó