michaelk

I think modern versions of VW will open .mcd back way before 2000.

Nurbs curves don't extrude and you need more than one nurbs curve to do a loft. But good on 'ya for jumping into nurbs curves! If you create two or more nurbs curves that are like section cuts for the solid you want to create you run the loft tool in the first mode. If you create a nurbs curve that is a path (called a "rail" in VW) and one or more profile nurbs curves you use the second mode If you create 2 nurbs curves to be the outside edge rails and a nurbs curve to be the profile that gets stretched and squished between the rails you use the 3rd mode. Post back if that doesn't make sense :-).

Sorry, that file sets of the piracy alarm and won't open. It's been a long time since one of these has come through. If I'm reading the file header correctly (big if 😁) it looks like it was a very old pirated version. You'll have to go back to whoever supplied that drawing and see if they can help.

Not sure I understand exactly which behavior you are trying to get. If you want to draw a line 2400mm long do you usually 1) Select the line tool, Click to set the start point, hit type 2400 using the numeric keys, move the mouse to get the angle and click or Enter to set the angle and complete the line OR b) Select the line tool, click to set the start point, TAB bring up the data bar and type 2400, TAB to change to the Angle field, enter a value, etc. Then click or ENTER to finish the line OR iii) Double click the line tool (or type 22 on the numbers above the letters) to get the Create Object:Line dialgog box and enter the location length and angle of the desired line.

There is a preference that might be what you're looking for. Click on the gear in the top right and see what your setting is for the data bar.

Attributes palette. Look at the bottom of the palette. There is a button for a marker on the beginning and end of the line. They are probably both selected. If you make sure nothing is selected and turn those buttons off, that will be the default for all objects you draw after that.

uitvoering v12 v2013 (2) v2020-dwg.zip

One of the pull downs (Color, Reflectivity, Transparency, Bump) has to be set to Image

The renderworks textures are in the resource manager. To edit the texture: You can right click on texture in the resource manager and choose Edit. In the bottom left you will see a size box and a button called Set by Image…. Click the Set by Image… button. On the image you will see a line with dots on either side. You can move points around and type in a value to set the size of the siding overlap. Then click on Edit Surface Hatch to change the hatch or reposition and / or resize the current hatch. To use just a hatch: Right click on the texture in the resource manager and choose Edit. Under Color change the pulldown from Image to Color. Click on Edit and choose a color. That will leave the hatch but take away the image that makes up the texture.

Hope this helps. Not sure what's going on with these files. They appear to be old educational German language version missing the suffix. I got what I could from them. The conversion to dwg made all the layers the same scale. I think 1:50. 030127_Grundriss_gesamt_v2020-dwg.zip aktuell v2020-dwg.zip

Usually it just needs a reset. Try closing the palette and opening it again. Window > Palettes > _________ When that doesn't work drag the palette out of the dock and put it back.

Who you callin' old and useful!?!? 😁

Instead of filleting walls, use the menu command AEC > Fit Walls to Objects Draw an extruded polyline or something to define the shape you want. Put it in a dummy layer and fit the walls to those objects.

What version of VW?

Are the data you want to put into the user fields unique to a fixture or just that fixture type?

How does one create a Text Style resource with VS?

You must have a different function reference page than me. I don't see that function. This would really explain a lot.

I'm using 2020. Every time I change anything in the definition it adds or subtracts a Y from one or more of the control points. Always the Y. It ping pongs between 1 and 2 Ys. So far it hasn't used 3 Ys! Haven't checked 2019 to see if this is new.

How do you assign an object to a control point?

Joshua Yes, that pict is from the Script Editor. It does NOT match the plug-in manager definition. But I get an unidentified variable error if I don't add the extra Y. I haven't found HLength to give me bad results. I have found that the tangent at a point on a polyline is sometimes very inaccurate if the polyline is an arc and the point is at the end (double click point). That's why I'm adding 1" to the beginning and subtracting 1" from the end. James - stellar idea. I'll give that a try.

Good question. You might try making a template file (.sta) and bringing that over. If you open that file it should have all the document settings.

It's just a setting. Look in Window > Data Bar Options… In the second group you probably want to check "Allow numeric keypad entry for instant data bar activation"

Welcome to the forum. I think this will do what you want: File > Page Setup > Printer Setup… Format for Any Printer Choose A3 if it's there. Use Manage Custom Sizes… to create it if not. Hit OK to get back to the Page Setup… dialog box Make sure Horizontal and Vertical are both 1. Tick show page boundary and show page breaks to confirm that you will get what you want.

OK. I feel like I'm getting closer. Will I figure it out before I slowly go insane? This gets the end of the polyline text in the right place, but the control point is in the wrong place. What am I doing wrong? Procedure Test; VAR SeatNumH, ObjectHandle, tempHandle, ControlGeometry, objectHand, recordHand, wallHand : HANDLE; XCordOffset, YCordOffset, Rx,Ry, ControlLength : REAL; BTest : BOOLEAN; PtAlongPath, TangentAtPoint : VECTOR; Sx,Sy, objectName, CurrentClass : STRING; Pt : POINT; BEGIN CurrentClass := ActiveClass; BTest := GetCustomObjectInfo(objectName, objectHand, recordHand, wallHand); ControlGeometry := GetCustomObjectPath(objectHand); ControlLength := HLength(ControlGeometry); BTest := PointAlongPoly(ControlGeometry,1", PtAlongPath,TangentAtPoint); { MoveTo(pControlPoint01X,pControlPoint01YY);} Rx := pControlPoint01X; Ry := pControlPoint01YY; TextOrigin(Rx,Ry); BeginText; 'BEGIN HERE' EndText; SetTextVerticalAlign(LNewObj,3); SetTextJust(LNewObj,2); SetPenColorByClass(LNewObj); SetFPatByClass(LNewObj); SetFillColorByClass(LNewObj); SetTextStyleByClass(LNewObj); BTest := PointAlongPoly(ControlGeometry,ControlLength - 1", PtAlongPath,TangentAtPoint); {MoveTo(pControlPoint02X+PtAlongPath.x+24,pControlPoint02YY+PtAlongPath.y+24);} Rx := pControlPoint02X + PtAlongPath.x; Ry := pControlPoint02YY + PtAlongPath.y; Sx := Num2StrF(Rx); SetRField(objectHand, 'BeginningAndEnd', 'pControlPoint02X',Sx); Sy := Num2StrF(Ry); SetRField(objectHand, 'BeginningAndEnd', 'pControlPoint02YY',Sy); Message( 'X: ',pControlPoint02X,CHR(13), 'Y: ',pControlPoint02YY); TextOrigin(Rx,Ry); BeginText; 'END HERE' EndText; SetTextVerticalAlign(LNewObj,3); SetTextJust(LNewObj,2); SetPenColorByClass(LNewObj); SetFPatByClass(LNewObj); SetFillColorByClass(LNewObj); SetTextStyleByClass(LNewObj); END; RUN(Test);

Love it when it's late at night and Australia steps up! So I don't write to the control point field. Just TextOrigin??!!?!?!?!?! That sounds so much simpler 😋