lgoodkind

Unless I am doing something wrong here creating a paving/class material legend with images doesn't seem to work properly. The hatch images in the attached document only show a background color and not the actual hatch. How are we supposed to create a material legend - as requested by building plan checkers across the united states? Can someone tell us how this is supposed to be done in Vectorworks? I've been using this software for 20 years now and there still isn't any reasonable way, as far as I can tell, to create a hardscape legend. hatches not working in worksheet.vwx

Confusing indeed! I do see the usefulness in the joint pattern options, especially the radial pattern. I don't see any way, as you say, to also apply a hatch under these joint patterns. If it can be done the best option (for us anyway) would be to have the hatch and joint pattern on separate classes to turn them off/on on sheet layers. The most important thing here is that we need control over hardscape hatches so that they may be displayed differently on say an irrigation plan vs. a planting plan. Simply greying out the entire class or layer is not very useful. We used to create separate layers or classes for paving fills and linework. If we are to transition to using hardscape objects then we would need the same functionality to retain readability on construction drawings. Thanks for your response.

It appears that hardscape objects appearance is not to be controlled by classing but by hardscape object definition. What is very confusing to me however is that you also have the ability to set components of a hardscape to have a Material and that material can also have a hatch setting for 2d views. The material appearance settings however seem totally irrelevant as I can't seem to find any way for those to be displayed.

Me too - Another Vectorworks pre-release disaster - again we are the beta testers - not the developers who apparently don't bother to use the software after they 'improve it' for us. My mistake again in upgrading - Better to wait a year to upgrade as I have in the past as it is not worth all the headaches. We are reverting back to 2021 for now. We will upgrade to 2022 and the END of 2022.

Am I missing something? I cannot get either an isolation valve or master valve to show any pressure loss or flow no matter where they are connected. They always display the same error no matter if they are from a catalog or custom. All other components downstream and upstream of them show flow and pressure and are working fine.

I am unable to add custom pipe material to the 'Catalog Item Edit' dialog. I would like to add, for instance, HDPE SIDR 15 pipe type to the list. One can add it to the list but you are unable to change the pipe size to anything other than '0.00' thus it won't work - the program then won't size the pipe on the plan or perform any needed calculations.

Here's a file demonstrating the problem. I hope this can be resolved. We can't really use the irrigation module until it is. Irrigation fail.vwx

I've had the same problem since I started using the irrigation tools years ago. Are we the only ones using this tool? This is one of several problems that have never been fixed. I'm not sure Nemetcheck cares that much.

I'm having a lot of trouble getting access to the data of the Plant Database in worksheet scripts. For instance the following should return the 'Blooms Begin' field data currentObject = vs.WSScript_GetObject() #Record 1 is the handle to the Plant Record, Record 2 is the handle to the plant object associated with the record vRecordHandle = vs.GetRecord(currentObject, 1) vRecordName = vs.GetName(vRecordHandle) bloomRecord = vs.GetRFieldOpt(vRecordHandle, vRecordName, "Blooms Begin") vs.AlrtDialog("Blooms Begin: " + str(bloomRecord)) This returns nothing All of the other database functions work however there does not seem to be any way to obtain the content via va.GetRField(). In the below loop all vFieldValue are blank for vFieldID in range(1, vFieldsNum + 1): vFieldName = vs.GetFldName(vRecordHandle, vFieldID) vFieldType = vs.GetFldType(vRecordHandle, vFieldID) vFieldFlag = vs.GetFldFlag(vRecordHandle, vFieldID) vFieldValue = vs.GetRField(vRecordHandle, vRecordName, str(vFieldName)) vMessage = "Record: " + vRecordName + "\nField : " + str(vFieldID) + "\nFieldName: " + vFieldName + "\nFieldType: " + str(vFieldType) + "\nFieldFlag: " + str(vFieldFlag) + "\nFieldValue: " + vFieldValue + "\n" #vs.AlrtDialog(vMessage)

Pat, Thanks for your reply. I get the desired results with the wildcards, meaning I get a 'true' in the cell when using.. =IF(('Plant Record'.'Blooms Begin'='*spring*'), 'true', 'false') and the data contain Spring and Winter When I use the following - all I get is a blank cell with no error =IF(('Plant Record'.'Blooms Begin'='*spring*'), PLANTIMAGE(2), 'false') I thought I would try and tackle a Python script to fix this but although I'm versed in Python the VS reference is pretty dense. I can't even find a reasonable way to debug within vectorworks to output print() statements to see what anything is doing. plant worksheet.vwx

I'm trying to display a plant database image based on the flowering season using the following =IF(('Plant Record'.'Blooms Begin'='*spring*'), PLANTIMAGE(1), ' ') This is not working. I can test that =PLANTIMAGE(1) works on another column Any ideas anybody?

@jeff prince If you are interested we could use your help modifying a database . lane@lanegoodkind.com

@jeff prince How did you go about modifying the .usr file to add those columns?

I agree completely. The wall tool is not yet there for Landscape and Civil. All landscape walls have footings and cap finishes with different finishes and dimensions than the core material.