Jump to content

DomC

Member
  • Posts

    609
  • Joined

  • Last visited

Everything posted by DomC

  1. hi @raouls For me it works, when the option is ON. For you it works when this option is off. What i observed is the following: 1. I have the main Window on the external screen, second screen is internal display of mac book 2. Vectorworks is startet on the external screen 3. If The Vectorworks border nearer than 3 cm on the screen border where the internal display is arranged i have epic lags for different actions. Also other Things seems to get slow (Finder) 4. If i drag the VW Window away from the border it is getting fast as expected 5. If i turn ON (Screens uses different spaces) it also works as expected and i can work with a miximized Vectorworks Window So i am little puzzled. I i update my OS, it looks like, that i have to switch OFF the Option again.
  2. Hi @raouls I wonder, it that option on your spaces settings (print screen german version above) was on or off?
  3. Hello I got a new MacBook Pro m3 end last year. I have sonoma 14.3. After setup my new system i had a short time of very big frustration because the performance was not as i excpected. Slow and epic lags (4 seconds or more and juddery).Also other things worked laggy like text editor or Filemaker. But there i am not so sensible. I think those was lags maybe another user could would take as "normal" and ignore it but i compared to my 2018 intel mac it was slower. On the internal Monitor everything was fast very fast and smooth. Also with a new user (which is often the workflow to test if it is something related to settings of the system) I found the option "screens uses different spaces" (which is translated from my german version. Do not know, if this is the exact name of the option in english too) which was turned off. After switching it on (which does make not difference for me to work) it is the best performance i ever dreamed of and very stable. Maybe can you look at that option @Dagny? I fellow just updated his intel Mac on 14.5 and have issues. The other fellows with a Apple silicon not issues after updating on 14.5 So personally i will stay on 14.3 till i can take the risk of something do not work anymore.
  4. Took a quick look I think, it is not the Marionette Network or the code inside the Marionette that produces the crash from my sight. It is the PIO which crashes by handling it in the script. I can see a crash by duplicate and move with alt-key and by edit the script. No crash with a Version, that not contains the PIO you insert in the script. That indicates, that the PIO you use inside script is crashing. Also not crash in 2024 (but maybe still an issue). Some Points that i saw: 1. Insert PIO then delete after The strategy is, to insert a PIO which has the same size as the segment of a polygon. If a Bool is 0 then delete the PIO. So you insert the PIO, set Bool to 0 and then after insertion delete PIO. Also i see, that the text you insert is not deleted in that case what would result in async text and PIO. Better would be not insert Bool is 0. Also then you have to filter the rest of the network also. 2. Writing to the record "Korpusmöbel - Objektinfo" Which is a read-only record in my opinion. Or minimum will be overwritten by the PIO itself. Maybe it works but still something risky. 3. Crash No idea what exactly produces a crash. Definitely no crash without PIO if i deactivate the symbol node. Also no crash, running the network not as a PIO Node just as a Network. The used cabined PIO may not be designed to exist inside Marionettes or other PIOs. That's maybe the source of the crashes. However i would 2024 give a try and skip 2023. Because there i can see no crash.
  5. The Script was made, screenplane planar objects was still a standard. it would still work with grouped screenplane objects. It seems, that the dup-container node puts screenplane planar objects on the 2D representation of the PlugIn. And grouped layerplane planar objects were putted on the 3D component of the plugIn. If we switch on top view we can see the groupes. Thanks for sharing that issue.
  6. Hello Which Version you would need? Regards Dominique
  7. It seems to be possible also by deleting with the selection state. So far it seems to be the best option. vs.DeleteObjs()
  8. vs.DoMenuTextByName('Clear',0) OK, this would delete the Original PIO. But i am not feeling good by using a DoMenuText in this situation.
  9. Hello I have a PIO with Button-Widgets. One of them should convert the PIO in another PIO and back. Is it possible to delete the PIO with the Button at all? elif theButton == cButton6: if replace_object(): vs.DSelectAll() vs.SetSelect(GlobalValues.pio_handle) vs.AlertInform('Press delete after action to delete original object', '','') #This would work so far vs.DelObject(GlobalValues.pio_handle) #This wont work (and if it would work i think it may result in a crash?)
  10. Should still work in 2024 (tested on mac 2024 Sonoma) 1. Select Excel File (I use Version 1.0.4 from xlsx) By clicking the Button of the Pick File Node. But if this was wrong it would throw an error message. Maybe to prevent path issues copy on desktop 2. Sheet Name input. This should match to the sheet name in the excel file. But if this was wrong it would also work by taking the first sheet name. 3. Check "Confuguration Dialog" Anyway, if input of the xls import was wrong it would throw also an error. If just nothing happens, the creation of space maybe fails. The reason maybe could be there is no area value or the area value was not returnet on output. column1 is imported without area not space. Also click the debug method to see, how many areas are outputed. It is normal we have more field values and values than areas. Because the field and values repeat because to match the set Record Field Node. If we have 3 columns it return double fields as area outputs. If we have 5 columns it returns 4 times more fields than area outputs etc.
  11. This are the options: 1. Saving/having an external (excel) list and make it fits to the input list of the Marionette. In Excel we can use formulas to have a list and a second sheet whitch grabs the list just for the needed columns. Then import the external list directly into the worksheet inside of Vectorworks. 2. If you are using interiorcad, you can configure a cutting list export, which fits to the needs and then follow step one 3. There is an internal list you could define with interiorcad which writes directly to a worksheet 4. Copy/paste can be tricky, because pasting in a worksheet may fail because you had to activate exactly the range of the pasted list first, which is hard. So import is the better option. 5. At least it could be an option to make (small) adaptions to the script so that it reads the needed columns automatically of any list. Or even directly for external file more even directly from part out of the drawing without doing any export/ import steps. I think the simplest way is to export to excel, then delete the unwanted columns and import into the Worksheet with the worksheet menu. That brings me to the idea to maybe make an example which directly reads one of the standard cutting list formats of interiorcad.
  12. I think the column "Drehbar" was never implemented (In fact it had no impact if i write there 0 or 1 it just took the checkbox "Rotation erlauben" which was a global option for all materials). I improved the Script with Version 1.0.4 and now it reads the column as soon as i checked the checkbox "Rotation erlauben". This setting will take care of the column "Drehbar" (Rotateable)
  13. Hi Did not looked into your code details because i keep that theme for a time from my brane. I think the general we can take an objects entity matrix and set that entity matrix to another object. With Set- and get Entity Matrix. This is not really hard. What was always the point is, that having some points in 3D which defines a plane transferring to an entity matrix wen need for the SetEntityMatrix Script command. What i have so far in that direction: 1. A way to have 3 points and gets an VW entity matrix of 3 points. Somehow my code os spreaded over a bigger code so i do now know if exactly that works in your example. code and functions i needed there code snippeds. I would say the code here took me several hours of figuring out that easy looking code. But i think at the end it maybe needs just a few lines if it was optimated. Also the vs.Vec2Ang() solves a lot. It would be hard to find out in which quadrant the plane is oriented and the direction of the points etc.. Like i told, not looked yet into your code. This snipped worked here for getting rotation matrix from 3 points. Not sure, if it works in all directions and for vertical planes in every situation. I always thought there must be a general solution for that. And there is but on the other side we must fit it to the vw SetEntity matrix also the plane matrix are different from the rotation matrix. 2. Getting a centroid and a plane. With that we can project points on that plane (not a vw plane, a plane defined by the normal matrix of the custom getPlane Node in that example). Here: At one point everything is turning into hard work. But we still have fun 🙂
  14. Version 1.0.0

    22 downloads

    Often what is missing to make usable Elements of this geometry is the fact, that faces need to be planar to make buildable elements. Also it need to be planar to make extrudes and other solids out of it. The Two nodes "get Planes" and "ProjectPoints" are a step in this direction. This example do nearly the same the existing Surface Array already can do. Except it directly gets geometry from a subdivision object. Anyway this has to be seen as a first step trying to model hulls with planar AND closed shapes. Which looks like a very hard task.
  15. OK For some reason (my dumbness?) i convert the column "TeileName" into a number, which fails and put out an error. You can do to correct: 1. Without new version or edit the script insert a number here in Column C instead a text. 2. Or edit the script (quite easy) as following: a. Edit the PIO object b. Double click the wrapper DrawParts c. Edit Formula to c+'\\rPos. '+str(a)+'.'+str(b) instead of c+'\\rPos. '+str(a)+'.'+str(int(b)) OK, maybe a little bit complicated. I post your corrected file and a new Version 1.0.3 Thanks for reporting the issue. Werkteil Optimierung Kopie_b.vwx
  16. Initially the issue is, that putting geometry into the profile group it is centered to the mid point (Even if you move profile before you create path it does not matter, it will be centered independent from its coordinates, thats why we have to move AFTER creation of path extrude). I am not sure anymore, why i used that locus point to get offset of the profile group(if you know the offset of the reference point to the middle of the profile you do now use locus point you can just move the profile by a known value). Reseting path extrude after moving the profile inside, is definitely still necessary in my opinion.
  17. Hello Sorry kinda occupied at the moment. The vs.ResetObject(x) will do reset at the end of a script i guess. So when it it duplicated it duplicates the unreseted state of the object and converting to mesh deletets the path position which is not reseted. What you can do, is a "hard reset" by using vs.SetObjectVariableBoolean(x, 1167, True) instead of vs.ResetObject(x) As far as i notice by changing the reset node it would keep the mesh in position. Hope that works for you
  18. Hi maybe you can Link or Post your file or pm me
  19. The Message says that it tries to add a float to a string ('100mm' + 10, 'hello' + 100) etc. Maybe the type of value in the sheet is not the same like in the sheet that works? Also I think it could related to a VW update. I provided a 2023 1.0.2 to fix that issue. Uploaded a New Version, which uses "vs.ValidNumStr()" for Every cell. So if A cell contains no valid number, Vectorworks tries to convert to a number. Do you use that fresh version or an older one?
  20. Agreed, class organization is still a crucial aspect, often posing challenges for users. Not all offices and projects require the same workflows. In the realm of Big Projects, the class structure may deviate from the standard, evolving over several years, and copying from old drawings might not be a significant concern. On the whole, it appears to be the right approach to employ a management tool that seamlessly connects various elements. This functionality seems to be already present in Vectorworks and is working quite effectively but always open for future improvements. We have the Ebenen/Klassen-Manager tool and/or the class/layer mapping feature. These tools allow users to define class mappings and save/load them for use in different projects. While mapping classes during object pasting might be functional, it does not align perfectly with the broader workflow requirements addressed by the aforementioned features, such as inserting resources and importing geometry. Try thinking one step forward i can imagine, that something like a overall document style (Not just for classes, mybe also central saved values as project data etc. - i think styles are really a great working concept) could be worth thinking about in this direction. However: Admittedly, I have not insight to "smart paste" feature in action, so my assumptions may be incorrect. It appears that this command executes a standard "paste" action initially, followed by a dialog that enables the user to modify the class of the pasted elements within a selected class, while also offering the option to delete newly created classes if undesired. Due to potential reliance on legacy commands or an inaccessible included file, the functionality may no longer be operational. Generally, scripts can be normally easily adapted for new versions, even when some functions are outdated. But the script does not seems to be available anymore? I use a similar script for records, i invested some time to fit to the class requirements. The script saves the substitution dictionary on disk, a feature seemingly unsupported by the old function. This script appears to encompass approximately 30% of the original "smart paste" pascal-script and its associated included file. It suggests that a fundamental element may be missing or that the dialog code in my example is more concise due to the dynamic creation of the object without the use of dialog builder components. The Dialog of my script: ''' DomC 26.12.2023 Disclaimer: This script comes with no warranty or official support services (excluding the Community Forum). Use at your own risk. It is recommended to test with a copy of your original documents. Known Issues: - Some content within symbols or PIOs may lead to unexpected results. - Pasted resources, including colors, symbols, line types, dimension standards, etc., are not translated; only classes are affected. - The script performs an all-encompassing paste action, resulting in a change to the pastes, still selected elements after pasting. - Pasting inside annotations, Symbols, PIO Graphic Containers etc. may result in unexpected results. - If a bug occours no pasted objects should be missed. Just maybe in wrong classes or maybe unwanted classes are deleted at the worst case. - This script is proof of concept and not matured by testing in real environment The script manages settings using a JSON file (smart_paste_settings.json). It provides functions to read and write a dictionary of class translations from and to the JSON file. Class Management: It defines functions to get a list of existing class names in the document and find the difference between two lists of classes. After a Paste operation (vs.DoMenuTextByName('Paste', 0)), it identifies new classes. Dialog Interface: If the debug_dialog flag is set to True, a predefined list of new classes is used for testing the dialog. The script creates a dialog that allows the user to interactively manage class translations. The dialog includes options to paste all into the active class, view classes present in the dictionary, substitute classes in the dictionary but not in the drawing, and handle new classes not yet in the dictionary. Dialog Functionality: The dialog provides an organized interface with columns for the original class name, the last translated class, and a dropdown menu for selecting a new class. It includes color-coding for clarity (blue for in the dictionary, green for in the drawing but not in the dictionary, red for not in the dictionary). Users can save their settings using a checkbox. Undo Mechanism: If the dialog is canceled, the script performs an Undo operation (vs.DoMenuTextByName('Undo', 0)). Post-Dialog Processing: After the dialog, if saving settings is enabled, it updates the JSON file with the new class translations. It handles the class translations for pasted objects, updating their classes according to the user's selections. It identifies classes to delete based on the difference between new classes and those in the class dictionary. Overall, the script provides a user-friendly interface for managing class translations, making it easier to handle classes in a Vectorworks document. ''' import vs import os import json # Set the folder and file paths for the settings settings_folder = os.path.join(vs.GetFolderPath(-15), 'smart_paste') settings_file = os.path.join(settings_folder, 'smart_paste_settings.json') # Set debug mode (True for debugging, False otherwise) debug_dialog = False # Get the active class name active_class_name = vs.ActiveClass() # Function to read settings from a JSON file def read_settings(settings_folder, settings_file): # Create the settings folder if it doesn't exist if not os.path.isfile(settings_folder): os.makedirs(settings_folder, exist_ok=True) try: # Read the class dictionary from the settings file with open(settings_file, 'r', encoding='utf-8') as file: class_dictionary = json.load(file) except: # If an error occurs during reading, set an empty dictionary class_dictionary = {} return class_dictionary # Function to write settings to a JSON file def write_settings(settings_folder, settings_file, class_dictionary): # Create the settings folder if it doesn't exist if not os.path.isfile(settings_folder): os.makedirs(settings_folder, exist_ok=True) try: with open(settings_file, 'w', encoding='utf-8') as file: file.write(json.dumps(class_dictionary, ensure_ascii=False, indent=2)) except: # If an error occurs during writing, display an alert dialog vs.AlrtDialog('Error writing setting File') # Function to get all class names in the document def get_class_names(): out_classes = [] num_class = vs.ClassNum() for i in range(1, num_class + 1): cname = vs.ClassList(i) out_classes.append(cname) return out_classes # Function to find the difference between two lists of classes def class_diff(old_list, new_list): return [c_new for c_new in new_list if c_new not in old_list] # Read existing translation from the settings file class_dictionary = read_settings(settings_folder, settings_file) # Get existing class names in the document existing_classes = get_class_names() # Perform a Paste operation vs.DoMenuTextByName('Paste', 0) # Get existing class names after pasting actual_classes = get_class_names() # Get new classes after pasting by finding the difference new_classes = class_diff(existing_classes, actual_classes) # class list for testing dialog if debug_dialog: new_classes = [ "Lorem ipsum", "Unknown Class1", "Dolor sit am", "Consectetur", "Adipiscing", "ClassNotInDictionary", "Elit", "Sed do eiusm", "Unknown Class2", "Tempor", "Incididunt ut", "Labore et", "Dolore magna", "Aliqua", "Ut enim ad", "Minim veniam", "Quis nostrud", "Exercitation", "Ullamco", "Laboris", "Duis aute", "Reprehenderit", "Voluptate", "Velit esse", "Cillum", "Excepteur sint", "Proident", "Culpa qui", "Aenean commodo", "Massa quis", "Enim justo", "Rhoncus ut", "Integer", "Tincidunt", "Cras dapibus", "Vivamus", "Elementum", "Aenean vulpu", "Aliquam lorem", "Phasellus", "Fermentum", "Viverra quis" ] items_left = [] items_middle = [] items_right = [] translate_list = [] saved_settings = {} def dialog_settings(): # Control IDs kOK = 1 kCancel = 2 # UIAskForStringsToReplace def CreateDialog(): # Alignment constants # Create the main dialog layout dialog = vs.CreateLayout( 'Class Substitute', False, 'OK', 'Cancel', True) # Create controls and set their positions vs.CreatePushButton(dialog, 5, 'Paste all in active class.') vs.SetFirstLayoutItem(dialog, 5) vs.CreateStaticText(dialog, 6, 'new_class present in dictionary', 30) vs.SetStaticTextColorN(dialog, 6, 0) vs.SetBelowItem(dialog, 5, 6, 0, 1) vs.CreateStaticText(dialog, 7, 'substitute class in dictionary but not in drawing', 40) vs.SetStaticTextColorN(dialog, 7, 4) vs.SetRightItem(dialog, 6, 7, 0, 0) vs.CreateStaticText(dialog, 8, 'new class not yet in dictionary', 30) vs.SetStaticTextColorN(dialog, 8, 2) vs.SetRightItem(dialog, 7, 8, 0, 0) vs.CreateStaticText(dialog, 9, 'Existing class manually attached', 30) vs.SetStaticTextColorN(dialog, 9, 3) vs.SetRightItem(dialog, 8, 9, 0, 0) # Script Scope Variable initialization max_lines = 20 num_groups = int(len(new_classes) / max_lines + 1) kgroup_list = [] start_id = item_id = 12 class_counter = 0 kgroup_list = [] for i in range(num_groups): # Create a group for each set of classes item_counter = 1 group_name = 'List ' + str(i) vs.CreateGroupBox(dialog, item_id, group_name, False) kgroup_list.append(item_id) last_item = item_id item_id += 1 for c_index in range(class_counter, len(new_classes)): c_new = new_classes[c_index] if class_counter >= max_lines * (i + 1): break # Check if the class is in the dictionary and set text styles accordingly in_dict = False in_dict_butnot_drawing = False if c_new in class_dictionary: in_dict = True last_choice = class_dictionary[c_new] if last_choice not in existing_classes: in_dict_butnot_drawing = True text_style = 2 # 2blue, 3green, 4red, 0black if in_dict: text_style = 0 if in_dict_butnot_drawing: text_style = 4 else: class_dictionary.update({c_new: active_class_name}) text_style = 2 last_choice = class_dictionary[c_new] # Create static texts for class names and last choices vs.CreateStaticText(dialog, item_id, c_new, 65) vs.SetStaticTextColorN(dialog, item_id, text_style) if item_id == kgroup_list[-1] + 1: vs.SetFirstGroupItem(dialog, kgroup_list[-1], item_id) else: vs.SetBelowItem(dialog, last_item - 2, item_id, 0, 1) last_item = item_id item_id += 1 vs.CreateStaticText(dialog, item_id, last_choice, 65) vs.SetStaticTextColorN(dialog, item_id, text_style) vs.SetRightItem(dialog, last_item, item_id, 0, 0) last_item = item_id item_id += 1 vs.CreateClassPullDownMenu(dialog, item_id, 25) vs.SetStaticTextColorN(dialog, item_id, text_style) vs.SetRightItem(dialog, last_item, item_id, 0, 0) last_item = item_id item_id += 1 item_counter += 3 class_counter += 1 item_counter += 1 # Create a tab control for better organization vs.CreateTabControl(dialog, 10) vs.SetBelowItem(dialog, 6, 10, 0, 5) for id in kgroup_list: vs.CreateTabPane(dialog, 10, id) # Create a checkbox for saving settings last_item = item_id item_id += 1 vs.CreateCheckBox(dialog, item_id, 'Save Settings') saved_settings['id_save'] = item_id vs.SetBelowItem(dialog, 10, item_id, 0, 2) return dialog # Dialog handler function for dialog interactions def DialogHandler(item, data): if item == 12255: # Enter Dialog pass if item == 5: # Update middle column with the active class name for all classes for id_middle in items_middle: vs.SetItemText(dialog, id_middle, active_class_name) vs.SetStaticTextColorN(dialog, id_middle, 3) class_dictionary[vs.GetItemText( dialog, id_middle - 1)] = active_class_name if item in items_right: # Update the right column with the selected class name item_text = vs.GetItemText(dialog, item) vs.SetItemText(dialog, item - 1, item_text) vs.SetStaticTextColorN(dialog, item - 1, 3) if item_text not in existing_classes: vs.SetStaticTextColorN(dialog, item - 1, 4) class_dictionary[vs.GetItemText(dialog, item - 2)] = item_text if item == kOK: # Save settings if the checkbox is selected saved_settings['save'] = vs.GetBooleanItem( dialog, saved_settings['id_save']) # Store translation information in a list for id_left, id_middle, id_right in zip(items_left, items_middle, items_right): c_old = vs.GetItemText(dialog, id_left) c_new = vs.GetItemText(dialog, id_middle) c_last = vs.GetItemText(dialog, id_right) translate_list.append([c_old, c_new, c_last]) return kOK # Initialize variables and run the dialog result = False dialog = CreateDialog() if vs.RunLayoutDialogN(dialog, DialogHandler, True) == kOK: result = True return result result = True if len(new_classes) > 0: result = dialog_settings() if result: # Check if saving settings is enabled if saved_settings['save']: # Write updated settings to the settings file write_settings(settings_folder, settings_file, class_dictionary) # Initialize a list to store pasted objects pasted_objs = [] # Function to add handles to the list def add_handle(h): pasted_objs.append(h) # Get the active layer and its name lh = vs.ActLayer() ln = vs.GetLName(lh) # Define criteria for selecting objects based on the active layer name c = "(INSYMBOL & INOBJECT & NOTINDLVP & NOTINREFDLVP & ((L='ldummy') & (SEL=TRUE)))" c = c.replace('ldummy', ln) # Use ForEachObject to collect handles of selected objects vs.ForEachObject(add_handle, c) # Loop through the pasted objects and update their classes for obj in pasted_objs: old_class = vs.GetClass(obj) new_class = class_dictionary.get(old_class, 'None') vs.SetClass(obj, new_class) # Identify classes to delete classes_to_delete = [] for class_n in new_classes: if class_n not in class_dictionary.values(): classes_to_delete.append(class_n) # Delete identified classes for class_name in classes_to_delete: vs.DelClass(class_name) if not result: vs.DoMenuTextByName('Undo', 0) For testing purposes this Marionette can be helpful to train the dictionary. Not really tested in real-application. @matteoluigi you see potential to take over the existing script? Test Classes.vwx
  21. Update: After Working a little more in this environment and Drawing some Modells. I see a little better the lag in user-interaction. Not slow but the little lag, that would let us loos a game or missing the string of a guitar. I short: Nothing for Vectorworks Artists ... Also i see, that some (loved) tools (Ähnliches Aktivieren) and menu commands (Edit Workspace works but not Exit and save) wont work. And I am sure, some further issues i will see. Menu looks strange, seperators looks like empty lines in menu commands. Issues see with - Tool Ähnliches Aktivieren - Callout Tool - Auto Dimension - Elevation Benchmark - Measure Angle - Grid Axis - Eye Dropper - Parallel Tool Just too many tools do not work it looks ... Promising at the first look, the second look is disapointing but still better, than i thought but for me no alternative to a native Windows System. 😢
  22. I think there is no difference between VMWare or Native ARM System. Vectorworks run in "compatibility - Mode" on ARM Windows. except in VMWare or parallels it is just slower. From my sight, VMWare seems to play in one league higher than parallels. Emulating Software somehow does hurt my hart but if i really look at my Solution: 1. Money was spent on a very nice and powerfull M3 max (How i love that machine ...) 2. Running the Emulation thing is a sacrilege but in fact: I can run A Windows system with an startet Vectorworks in 20 Seconds! by just pausing the Virtual machine and saving the state: 3. Speed and lags are comparable to a Medium Windows System which is 3 Years old. Still i need much less power to work on that system 4. Additionally the hope, that update of Windows and native ARM Software will even improve the situation If i look at the facts in that moment i will not buy a new pc for some time and i think i will practice this "sacrilege" workflow.
  23. Hi Marcel Thank you very much for responce. So far my experience, that it was able to install VW with an alternative Windows Image (Win 11 ARM). After starting VW Mentioned, that some vlb was not able to load. (Cinerender) After That VW works quiet smooth and fix in 2D, but in 3D nothing visible. Like you mentioned. Also no wireframe model. After Deactivated the Parallels Display driver, the 3D Shaded view is visible but it is very slow. Also a bigger modell crash. Next Test with VM Ware Fusion. Test-Version. I only have two CPU cores. I hope this is because of free Test Version. After Installing Windows 11 with the same iso image i was able to install VW. With VM Ware Fusion it was able to install something like VMWare Tools. This installing Drivers also Display Drivers. After Restart i have a Graphic Adapter Named VMWare SVGA. Then I start VW. It Installation and startup of VW is slower than on parallels. But on Parallels I had 12 CPU Cores and on VWMare Fusion . Only two. After Shut Down the virtual Machine i can set up more cores It seems to be good enough for testing, Support but not for really working or offering as a Training Computer for Customers. Additionally Cinema 4D do not run at all. But Shades View is OK. VWM Ware VW 2024 M3.mp4 Edit: After giving the virtual Machine more than 4GB RAM, it works better 🙂 But Still generating the 3D Takes more time and the double emulation (Mac Silikon > Windows ARM > Win 11 ARM > Winx86 VW) seems to be incompatible to the VW Render-System.
  24. Hi I try to install a Windows Version on Parallels on my m3 for special Support- and Training cases. After all i found out, Parallels 19 needs a Windows 11 ARM Version. And on a Windows ARM Version, the Installer of Vectorworks 2024 will not start. Somebody have experience with that constellation? Thanks
  25. "C:\\Temp\\Output.csv" would work also I would strongly recommend, always create path strings with the path module. So it is as proof as it can be and this works also cross-platform: import os path = os.path.join('C:', 'Temp', 'Output.csv') # or even more propper path = os.path.join('C', os.sep, 'Temp', 'Output.csv')
×
×
  • Create New...