[STL Export "Very High" isn't good enough]

Have you ever exported an STL and are disappointed that you can see the facets in a curved surface.  That is because the Very High setting only creates 158 segments in a in cylinder per face.  This causes you to see those facets in your print if your cylinder is large.  Using a vectorscript you are able to export at higher resolutions than the menu command.  Below are STL files of the same cylinder. The first one is exported at Very High using the menu command and the second one exported using the "Export STL UI Quality" script with and input of 1500 in the attached file.  Note that the more complicated the model you may have to reduce the resolution of the export as some of the parts may not export.   

100 = Very High like the menu command

UI allows the user to enter a value

Scripts are provide without warranty and user to use at their own risk.  

The file must be saved before running the script.  The STL file will be created at the same location as the file and will be named with the active layer name. 

 

 

 

 

STL Export Ultra High Resolution.vwx

[Mesh Conversion and Facet generation density]

I figured out that I can increase the number of facets in an STL export using the ExportSTL command. Per the command the percent of tessellation resolution should be a Real number between 0 and 100 but you can increase that number above 100 to increase the tenssellation.  

 

FUNCTION   ExportSTL ( filePath:DYNARRAY[] of CHAR;  exportBinary:BOOLEAN;  percentTess:REAL;  exportObjectsOptions:INTEGER) :BOOLEAN ;

 

percentTess = tessellation resolution -- from 0 to 100     0 -- low,     100 --high

 

[Lock setting for veiwport Cache]

On 12/29/2022 at 11:28 AM, Pat Stanford said:

As a works around what about using the Render Bitmap tool on those VPs to generate an image that would then not need updating?

Great suggestion, but not quite what I am lookin for, I wish that tool had a hidden line render option.

[Script to class Sheet Layer objects]

4 minutes ago, Jiajing said:

Circling back to it, I am having hard to find those INDEXes from Appendix, for instance, not sure 1166 means in GetObjectVariableString, is there a doc with full list of index. 

Find it here

https://developer.vectorworks.net/index.php/VS:Function_Reference_Appendix_F

or the root

https://developer.vectorworks.net/index.php/VS:Function_Reference_Appendix

[Lock setting for veiwport Cache]

I wish there was a way to permanently lock in the viewport cache of a viewport.  Many times we have interior elevations that once they are created and edited they will not change and if they do we are aware that we are editing them.   The issue is that it takes a long time to regenerate all of the interor elevation viewports which are not changing. Sometimes the link is broken and we have to recreate it.  It would be great if there were a switch to permanently lock the viewport cache even after a crash so that the viewports have no need to update unless the lock is swiched off. 

 

[New Clothes Rod Tool]

Love it! Thanks!

 

["lck' Lock file naming]

Nevermind, I was informed Synology does have an answer. 

["lck' Lock file naming]

Please remove the period from the beginning of the lock file name.  This period causes the file not to sync with synology cloud stations and theirfore we are unable to determine if a remote user has a file open. 

[Script to Select doors or windows of a matching style]

I edited it to also select unstyled versions.  I also added Spaces, Comm Devices, and Receptacles

 

PROCEDURE SelectMatch;
VAR
h : HANDLE;
piotypeis, layernameis, stylenameis : STRING;

PROCEDURE GetStyleName(h :HANDLE);
BEGIN
	stylenameis := GetPluginStyle(h);
	piotypeis := GetObjectVariableString(h, 1166);
	
END;

BEGIN
layernameis := GetLName(ActLayer);
ForEachObject (GetStyleName,(NOTINDLVP & NOTINREFDLVP & ((L=layernameis) & (SEL=TRUE) & ((PON='Door') | (PON='Window') | (PON='Space') | (PON='Comm Device') | (PON='Receptacle')))));
SelectObj((((PON=piotypeis) & (PST=stylenameis) & (L=layernameis))));
END;

Run(SelectMatch);

 

[Script to Select doors or windows of a matching style]

PROCEDURE SelectMatch;
VAR
h : HANDLE;
layernameis, stylenameis : STRING;

PROCEDURE GetStyleName(h :HANDLE);
BEGIN
	stylenameis := GetPluginStyle(h);
END;

BEGIN
layernameis := GetLName(ActLayer);
ForEachObject (GetStyleName,(((L=layernameis) & (SEL=TRUE) & ((PON='Door') | (PON='Window')))));
if stylenameis <> '' THEN SelectObj((((V) & (PST=stylenameis))));
END;

Run(SelectMatch);

 

To use select one door or window and run script.

[Drawing coodination switch not working during script]

I wrote a script to renumber viewports but I get a warning that the number has been used before.  If Drawing coordination is turned off they no warning is displayed.  So I tried to turn it off in the script and turn it back on at the end but it still gives the warning.  Test file attached. 

 

{Script Name: VP Label (Consecutive)

This script will renumber drawing labels contained within VP annotations in order picked by mouse. 

David Hamer, 2022 revision 11/7/2022}


PROCEDURE NumberVPConsecutive;

VAR	
   numberStr : STRING;
   h,h2, anno, h1 : HANDLE;
   pX,pY : REAL;
   doorNumber,dummyVar,vpNumber : INTEGER;
   zoomis:LONGINT;
   DCPref:BOOLEAN;

PROCEDURE SetVPNumber;
BEGIN
GetPt(pX,pY);
  	if GetTypeN(h) = 122 THEN BEGIN {if h is a viewport}
		anno := GetVPGroup(h, 2); {creates group from annotations of selected viewport}
		h1 := FInGroup(anno); {selects the first object in the anno group}
		while h1 <> NIL DO BEGIN { steps through every object in the viewport selected by the click}
			if GetObjectVariableString(h1, 1166) = 'Drawing Label' THEN BEGIN {if veiwport object is a drawing label}
				SetRField(h1,'Drawing Label2','Drawing',numberStr); {VW 2021 Version sets the drawing label to the current active number in sequence}
				vpNumber := Str2Num(numberStr); { convert number string to number.}
				numberStr := Num2Str(0, vpNumber + 1); {subtract number from sequence then convert number to string.}
				ResetObject(h1);
			END;
			h1 := NextObj(h1); {get next object in viewport\}
		END;
		ResetObject(h);
	END;
END;

BEGIN
DCPref := GetPref(544);{get status of drawing coordination}
SetPref(544,FALSE);{turn off drawing coordination}
ReDrawAll;
{•••• Ask for starting number ••••}
numberStr := StrDialog('Enter and INTEGER to start numbering:','1');
Message('Click in empty space to end numbering');
SetVPNumber;
  {•••• Repeat process until there is NO object at the clicked location ••••}
  WHILE GetPickObjectInfo(pX,pY,h,h2,dummyVar) DO BEGIN
    SetVPNumber;
  END;
ClrMessage;
{ReDrawAll;}
SetPref(544,DCPref);{set drawing coordination to original state}
zoomis:=GetZoom;
SetZoom(101);
Setzoom(zoomis);
END;

RUN(NumberVPConsecutive);

 

vp renumber.vwx

[vs.GetPt()]

This is how it works:

import vs;

def DoIt(h1):
	vs.AlrtDialog( "we're in", h1 )

def PickPointCallback(pt):
	vs.ForEachObjectAtPoint(DoIt, 0, 0, pt[0], pt[1], 5)

vs.AlrtDialog( "show let you pick a point, and then show a dialog with the object's handle" )
vs.GetPt( PickPointCallback )

 

You need to add your function to the (PickPointCallback) definition part of the script to evaluate pt[0] and pt[1]

[Vectorscript command to report the scale of a viewport]

13 hours ago, Pat Stanford said:

Scale:=GetObjectVariableReal(VPHandle, 1003);

 

Where 1:Scale is the scale of the viewport.

Thanks!!

[Vectorscript command to report the scale of a viewport]

Does anyone know a vectorscript command to report the scale of a viewport?

[Trying to filp the source polyline in an extrude but my scipt does not work.]

Funny thing is both scripts work if the interal shape is a polyline but it does not work if it is a Polygon.  See attached file.

 

Flip Extrude Profile.vwx

[Trying to filp the source polyline in an extrude but my scipt does not work.]

Thanks, I just came to same conculsion after I got this script to work minus the refreshing issue. 

 

 

def FlipIt(h):
	h1= vs.FIn3D(h)
	if vs.GetTypeN(h1)==24:
		h2 =vs.FIn3D(h1)
		if vs.GetTypeN(h2) == 21:
			if vs.Random() >= .5:
				vs.Mirror(h2,False, (0,0), (5,0))
	vs.ResetObject(h1)
	vs.ResetObject(h)
			
vs.ForEachObjectInLayer(FlipIt,2,2,0)

 

[Trying to filp the source polyline in an extrude but my scipt does not work.]

Tried this but no luck

 

def FlipIt(h):
	if vs.GetTypeN(h) == 21:
		if vs.Random() >= .5:
			vs.Mirror(h,True, (0,0), (5,0))

			
def ResetIt(h):
	vs.ResetObject(h)
	
vs.ForEachObjectInLayer(FlipIt,2,2,0)
vs.ForEachObjectInLayer(ResetIt,2,0,0)

 

[Trying to filp the source polyline in an extrude but my scipt does not work.]

Trying to filp the source polyline in an extrude but my scipt does not work.

Any ideas!

 

def FlipIt(h):
	if vs.GetTypeN(h) == 21:
		if vs.Random() >= .5:
			vs.SetSelect(h) 
			vs.FlipVer() # doesn't flip the poly,  but if I replace this command with vs.HDuplicate(h) it will duplicate it

			
def ResetIt(h):
	vs.ResetObject(h)
	
vs.ForEachObjectInLayer(FlipIt,2,2,0)
vs.ForEachObjectInLayer(ResetIt,2,0,0)

 

[Fix the New combined Straight and Curved Wall Tool]

Ok fine that Vectorworks combined the curved wall tool with the straight wall tool.  That being said why did you make the option to switch from straight to curved the first option instead of the last option.  Now everytime I use the wall tool I have to relearn the U,I,O,P,[,]  shortcuts.  The option should have been added to the end of the tool options not the begining. 

 

PLEASE move it to the end of the options.  Besides most rarely draw curved walls so why would it be the first option?

[Slow performance on i9 10 core processor]

Also noticed that when Vectorworks 2022 starts it switches to "Below Normal" Priorty meaning other programs have higher priorty than Vectorworks when running. 

[Slow performance on i9 10 core processor]

Why when I update section viewports am I only using one cpu instead of multithreading.  I thought everything was moved to 64bit multithread.  It takes way to long to update. 

If it is using more than one core it doesn't appear to be in the resource manager. 

[Editing Space boundry]

Is it possible to edit both the Net and the Gross boundry of a space without affecting the other?

[Help connecting trusses]

Can anyone help me to connect these trusses in the possition they are in. 

 

File attached

 

truss.vwx

[Open solid DTM]

Thanks, I never remember that this is an issue.

[Open solid DTM]

I created the attached DTM from 3D contours but when I view it as a rendered solid it only shows the bottom faces and appears empty. 

Open solid DTM.vwx