Tutorial / reference guide for RogCAD_for_Windows |
CONTENTS Take a few seconds to read the introduction and eight minutes to watch the four short introductory videos. What you read in this document will be more easily assimilated if you've seen it put into practice. Introduction to RogCAD for Windows Introductory Videos -------------------------------------------- PART ONE Introduction to data entry INTERFACE buttons and menus COMPREHENSIVE DATA ENTRY data file format wireframe autoplane repeating cubics single plane buttons SJK transformations At this point you can create useful wireframe models. -------------------------------------------- PART TWO DISPLAYING YOUR MODEL Auto-surfacing Screen capture and screen set macro files macro-g macro-a PALETTES At this point you can achieve simple surfaced models. -------------------------------------------- PART THREE CURVES At this point you can model curved surfaces. -------------------------------------------- PART FOUR repeating cubics along curved paths -------------------------------------------- PART FIVE facades, grids, plan views, going inside |
instruction document date 01/31/2023 https://rogcad.com |
|
|
|
|
|
The data-entry samples and images in the right-hand panel follow the same chronology as what you are reading in the left-hand panel. ----------------------------------------------- Keep all the files in the folders they came in except where instructed otherwise, and do not delete any folders. Your work with RogCAD will involve just two folders -- "empties" and "datah". Within the datah folder, you'll want to create subfolders named as you see fit for storing data files for projects that are not current, otherwise you'll end up with a lot of unrelated data files in your working folder (the "datah" folder). Leave all the files in the "empties" folder intact. Copy files from that folder as needed, and place them into the datah folder with a new name suitable for your project. (The data folder in RogCAD for Windows is named "datah" to distinguish it from the "data" folder used in RogCAD for DOS.) There are five types of data files used in RogCAD, and four of them come in x, y and z versions: s-.txt ax-.txt x8-.txt cx-.txt mx-.txt ay-.txt y8-.txt cy-.txt my-.txt az-.txt z8-.txt cz-.txt mz-.txt Numerical data is entered into those text files as "standard" points : s + cubics cubic elements : ax,ay,az strings of cubics : x8,y8,z8 curves : cx,cy,cz combination of : mx,my,mz standard/cubics/curves Each data file into which you've entered data is called a "group", and you name them as you see fit. When running RogCAD you can display any or all of those groups on screen. Whichever group you've most recently called for display is the "active" group. Projects are typically best broken into groups such as: s-mainshell.txt ax-eastwindows.txt ax-northwindows.txt s-roof.txt s-frontporch.txt x8-porchrails.txt cz-sidewalk.txt Three other important text files that are kept in the datah folder are: START.TXT GROUPNAMES.TXT S-0.TXT In START.TXT, you can edit: default view default color palette default background color for CLS fast-change views You must enter the names of your data files into GROUPNAMES.TXT or else RogCAD will not recognize them. S-0.TXT is an x-y orientation pair of lines. RogCAD will not run if that file is removed from the datah folder. ---------------------------------------------- Autocubes: See right-hand panel beginning here --> Depending on which type of data file you are using, autocube point numbers begin at one of the following: 1 1001 2001 3001 4001 5001 6001 7001 A cube has eight points, therefore autocubes have point numbers in accordance with the following pattern: 4001 to 4008 4011 to 4018 4021 to 4028 etc Points xxx9 and xx10 are not used. A cube has six sides, therefore autocubes have plane numbers in accordance with the following pattern: 4001 to 4006 4011 to 4016 4021 to 4026 etc Planes xxx7, xxx8, xxx9 and xx10 are not used. ------------------------------------------------- This author typically separates exterior modeling from interior modeling, and therefore does not typically model see-through window openings, which are illustrated immediately to the right. In fact, for strictly exterior modeling, exterior walls are often just given zero thickness by virtue of using a single autocube to define the shell of the structure. To achieve see-through window openings, one needs to define wall sections as illustrated further down. And that actually goes quickly, as many of the values are simply repeated. We'll pick up on that again after looking at the two autocube diagrams below and to the right. ------------------------------------------------- ----> See the autocube diagram in the right-hand panel for the point and plane numbering scheme for autocubes. As you build your model, you'll probably want to make reference sketches on which to label points and planes of your model. It almost always comes in handy. ------------------------------------------------ The image immediately to the right is a repeat of the incorrect method of creating window openings. It would not work with the auto-surfacing routine because the walls would get auto-surfaced over the window openings. Rather, the walls need to be defined in segments, thereby creating window openings. In that case, no autocubes are used for the window openings themselves -- those openings exist simply as "absence of wall". ------------------------------------------------ To the right is the model with those wall segments defined, leaving voids which are regarded as window openings. The groups displayed here are: s-simplehouse-3.txt s-simpleroof-front.txt s-simpleroof-back.txt ------------------------------------------------ It's important to break your project into groups so that the auto-surfacing routine will work properly on a project-wide scope. (The RogCAD algorithm for determining overlapping planes is not as sophisticated as what is found in the most expensive software. However, it's beneficial to have your project broken in groups for other reasons as well, so it's mostly a moot point.) To the right we see the group named "s-simplefloor.txt" auto-surfaced. ------------------------------------------------ Now, to the right we see the group named "s-simplehouse-3.txt" auto-surfaced. ------------------------------------------------ Finally, to the right we see the group named "s-simpleroof-front" auto-surfaced. Note that the lines representing shingles are part of the auto-surfacing routine. The spacing information for those lines was entered into the AUTOFRAMING section of st-simpleroof-front.txt. ------------------------------------------------ Go ahead and run rogcad[version].exe Click on the "group" button, then select various groups for display. It will be the most illustrative if you select them from top to bottom, clearing the screen after you've selected all the groups of a cluster. Click the CLS (clear screen) button to clear the screen at any time. Make sure to experiment with the view-change buttons: M (magnification) V and H (vertical and horizontal shift) P/F XYZ (perspective and focus) --------------------------------------------- Refer to the sample project videos higher on this page to see some button-clicking in action. --------------------------------------------- Below are still images that explain all the buttons and menu items. Below that, we'll round out part one of these instructions by looking at data-entry more thoroughly. |
Extremely simple house: See s-simplehouse-1.txt STANDARD: point numbers 1 0,0,0 followed by their 2 0,0,8 x y z values 3 0,30,0 4 0,30,8 5 20,30,0 6 20,30,8 7 20,0,0 8 20,0,8 9 10,0,12 10 10,30,12 999 999,999,999 end of data read Use spaces or commas to separate numerical information. Connect the points defined above, or else RogCAD won't recognize the points: LINEG1: 1,2 3,4 5,6 7,8 1,3 3,5 5,7 7,1 2,4 4,6 6,8 8,2 8,9 9,2 6,10 10,4 9,10 999,999 Below, fewer standard points are defined, while autocubes are used to define an inner and outer shell and to create simple window openings. However, THIS IS NOT THE CORRECT METHOD for creating window openings, and is included as a simple first example of using autocubes. The correct method for creating window openings is in the example that follows beneath this one. -------------------------------------------------- See s-simplehouse-2.txt STANDARD: 1 10 1 12 2 10 29 12 3 10 0 12.5 4 10 30 12.5 999 999,999,999 LINEG1: 1,2 3,4 1,4002 1,4008 2,4004 2,4006 3,4012 3,4018 4,4014 4,4016 999,999 NOTE that we can connect standard points to autocube points, and we can define planes in the same manner. start rotation index point min xyz max xyz and base color ----- ------- ------- -------------- AUTOCUBE400: 4001 1,1,0 19,29,8 0,5 4011 0,0,0 20,30,8 0,5 4021 8,0,3 12,1,7 0,5 4031 0,4,3 1,8,7 0,5 4041 0,13,3 1,17,7 0,5 4051 0,22,3 1,26,7 0,5 4061 8,29,3 12,30,7 0,5 4071 19,4,3 20,8,7 0,5 4081 19,13,0 20,17,7 0,5 4091 19,22,3 20,26,7 0,5 999 999,999,999 999,999,999 0,0 Rotation indexes and base colors have been left at the default value for now. Again, this is NOT the manner in which autocubes are typically combined to build architectural structures. It's for simple illustration. Typically, you'll want to define autocubes in a manner that will facilitate successful sorting of planes for auto-surfacing (automatic plane coloring). That's covered in the example beneath this autocube diagram: incorrect window openings: correct window openings: -------------------------------------------------- |
|
|
COMPREHENSIVE DATA ENTRY - excluding curves ---------------------------------------------------------------------- RELATIONSHIP BETWEEN RUN-TIME AND DATA-ENTRY: While RogCAD is running, you can edit a data file, re-save it, and then recall that particular data group. You might want to toggle the Show button to Hide to prevent wireframe lines displaying. This does not apply to START.TXT or to GROUPNAMES.TXT. Any editing in those files does not take effect until RogCAD is re-started. ---------------------------------------------------------------------- NOTES ABOUT DATA FILES FORMATTING: There must be no line spaces in data files or in START.TXT within a defined section, since the data is read directly by the program. Sections are plainly evidenced by a header in upper case lettering followed by a colon and a set of 999s at the bottom of the section (which tells the program to stop reading from that section). Do not change the 999s or 0,0s at the end of the data reads. The program looks for those specific values. Even sections without data must not contain line spaces between the header and the 999s. (Line spaces are allowed in GROUPNAMES.TXT since that file is associated with a list box accessible at run time.) The top of an s-.txt data file: LIGHTDARK Edit lighting direction preferences. WIRECOLORS Edit colors for wireframe line groups. STANDARD Edit data for standard points. LINES Edit data for point-pair lines. AUTOPLANE Edit data for planes. AUTOCUBES Edit data for autocubes. AUTOFRAMING Edit data for framing lines. TRANSFORM Edit singles, resize, rotate, translate, wrap. We already looked at: STANDARD points LINES AUTOCUBES (single autocubes - not string of autocubes) earlier in this document. -------------------------------------------------------------- Data editing in the text files: Auto-surfacing editing: Edit lighting-direction preferences by choosing the lightest and darkest sides for the planes of your data group. Refer to the autocube diagram earlier in this document. Lighting-direction applies to all planes, not just those planes that are associated with autocubes. The autocube diagram serves as the guide all the same. Only three sides of any rectangular element are visible for a given perspective. The RogCAD auto-surfacer subtracts 1 from the base color of the side you specify as lightest, adds 1 to the base color of the side you specify as darkest, and leaves the third face color unchanged. Assign a base color to your planes based on how you've set up your color palette. Base color assignment is seen further down on this page. Here we see side 6 designated as the lightest side and side 3 designated as the darkest side. Refer to the autocube diagram higher in this document. ---------- LIGHTDARK: 6,3 ---------- Wireframe colors: You can break your standard points into five wireframe line groups, with each line group assigned a different color. Here is what the wireframe color assignment looks like in s-.txt. The first color is the background color for the data-file. ------------------------------------------------------------------ Wireframe line colors: LG1 LG2 LG3 LG4 LG5 cubics cubics cubics WIRECOLORS: 255 254 3 3 3 3 3 3 3 ------------------------------------------------------------------ It's sometimes useful to add dummy points or planes to a data base in the course of editing. Just add data that won't affect the displayed output. This could mean just repeating data, or defining points without defining point-pair lines to go with them. This technique will save you from having to re-number points or planes. |
|
Autoplanes Enter points for planes in a pattern consistent with framing lines and crosshatch lines. Plane, t1,b1,t2,b2, direction,color --------------------------------------- AUTOPLANE: 1 14,16,28,32 6,13 2 29,32,30,33 6,13 3 20,18,27,25 6,13 4 27,25,22,24 6,13 5 2,4,10,12 6,13 6 6,8,10,12 6,13 7 4037,45,14,48 3,2 8 16,22,15,21 2,2 999 999,999,999,999 0,0 --------------------------------------- The direction value refers to which direction the plane is facing, in accordance with the auto-cube diagram. If you subject a plane to rotation using the transformation routines, then you will need to allow for that. The color value is the base color, which is the middle color of the three colors you choose for the plane. Here is why we use the t1 b1 t2 b2 method. The auto-surfacer will insert perspectively correct lines onto the planes entered into AUTOFRAMING1 and AUTOFRAMING2. The two routines insert lines perpendicular to each other. It's too difficult to ascertain which of the two routines to use for a given plane, so just experiment. If one is wrong - the other is right! Plane, number of framing lines ------------- AUTOFRAMING1: 6 24 1 5 2 16 14 5 999,999 ------------- ------------- AUTOFRAMING2: 4013 24 4012 24 4103 12 999,999 ------------- Triangular shapes can be treated just like four- sided shapes when it comes to defining planes, cross hatching or using framing lines. You simply repeat one of the vertices. It's as if one side of a four sided polygon had length zero. The three images in the right-hand panel illustrate framing lines: Roof shingles, bricks, and a stick cabin. |
|
Repeating cubics along an axis: Here are examples of autocubes repeated along the x axis from an x8-.txt data file. As with single autocubes, we specify minimum xyz values and maximum xyz values. The spacing dictates just that - how to space those repeating autocubes. The units of measure are the same as used for xyz values. First we see autocube block 200, meaning points begin at 2001. End cube 208 has points 2081 to 2088. Eight cubics will be drawn, spaced out along the x axis every 18 inches. Below that we see block 300, with points beginning at 3001. Seven cubics will be drawn, spaced out along the x axis every 18 inches. We say "cubics" even though in this particular case, those cubics are completely flat, two-dimensional, since we used 0 for both the minimum and maximum value for z. These flat cubics are 9" x 9" floor tiles, with a white and black checker-board pattern. By using additional blocks, we quickly tile an entire room: See the image of the kitchen near the top of this document. The final two values are rotation index and base color. If you do not subject this data to a rotation by way of using the transformation routines, then 0 is the correct value. 90 degree => rotation index of 1 180 degree => rotation index of 2 270 degree => rotation index of 3 Other degrees => whatever works best: 0, 1, 2 or 3. The rotation index and base color work in conjunction with the autosurfacing routine. x y z x y z spacing end plane rot,col ------------------------------------------------------------------------- (201 - 299) AUTOCUBE200: 0 9 0 9 18 0 18 208 0,1 (301 - 399) AUTOCUBE300: 9 9 0 18 18 0 18 307 0,1 ------------------------------------------------------------------------- Cubics repeated along an axis, then mitered and beveled with transformations: |
|
J plane pl1 pl2 menu buttons Keep in mind that these routines, as well as the SJK (string of planes) routine, are simply an alternative, or a possible addition to, the auto-surfacing routine. Also, keep in mind that these routines, if utilized, are typically part of your macro-g and/or macro-a file. During your design phase, it's useful to test your design using the menu buttons that correspond to these routines. To incorporate these routines, as well as SJK (strings) discussed next, for planes other than autocube planes, you must define your planes in accordance with the t1 b1 t2 b2 methodology, as explained in the autoplane and autoframing sections above. You'll be prompted for a plane number and a color number. Dense cross hatching occurs, coloring the plane. J plane uses 8000 parallel lines. pl1 uses 2000 parallel lines. pl2 uses 500 parallel lines. See SJK / String of planes up and to the right. |
STRING BUTTON ON MENU (SJK routine in macro-g and macro-a) You'll be prompted for: a starting plane, an ending plane, the increment "1" colors every plane from starting plane to ending plane, "2" colors every other plane, "3" colors every third plane, etc. a starting color, a color increment. If you select a color increment of zero, then every plane in the string will be the same color. Plane increments and color increments can have a positive or negative value. The SJK (sting of planes) routine is geared for repeated cubics (autocubes) created in x8, y8 and z8 data files, and for creating either gradient lighting or flat lighting on curved surfaces. Repeatable cubic elements include: fence rails, posts, spindles, window elements, construction framing members, bricks, cement block walls, etc. You make use of the increment feature in SJK to skip over planes in a patterned fashion, using alternating colors as you do so. You can reasonably simulate stone work with a a little experimentation. <--- Use an increment of 10 or -10 to color a string of planes associated with autocubes. Thus, for example, you can quickly paint autocube planes 433, 443, 453 ... 623, which are all facing the same direction; typically using the same color for each. |
TRANSFORMATIONS Transformation snippets are stored at the bottom of the data fles. Here is a sampling of transformation snippets being used. They are from three projects, so the three groups of snippets are not related to each other. You can see from the final group of snippets that we conduct transformation on top of transformation on top of transformation to our heart's desire. You can skew a string of cubics, such as for creating mitered framing members. Step 10 will transform points of successive cubics: first, last, tranx, trany, tranz TRAN STEP10TRANSLATE: 2002 3102 0 2.24 -.415 2003 3103 0 2.24 -.415 999,999 999,999,999 -------------------------------- ---------------------------- Skewing single cubics: Point number, New value TRAN XTRANSFORMATIONS: 2006 4.3 2008 6.7 2026 4.3 2028 6.7 999,999 ---------------------------- ----------------------------------------- first, last, zangle, tranx, trany, tranz TRAN ZROTATETRANSLATE: 1 358 270 -7 -13 0 999,999 999 999,999,999 ----------------------------------------- ----------------------------------------- first, last, zangle, tranx, trany, tranz TRAN ZROTATETRANSLATE: 1 38 90 23.89 41.2 8 201 238 0 .125 62.72 8 401 438 90 .417 45.49 8 999,999 999 999,999,999 ----------------------------------------- -------------------------------- first, last, multX, multY, multZ TRAN RESIZE: 1 7998 .75 .75 .75 999,999 999,999,999 -------------------------------- -------------------------------- first, last, tranx, trany, tranz TRAN TRANSLATE: 1 7998 .5 0 0 999,999 999,999,999 -------------------------------- ---------------------------------------- first, last, yangle, tranx, trany, tranz TRAN YROTATETRANSLATE: 1 7998 -90 0 0 0 999,999 999 999,999,999 ---------------------------------------- ---------------------------------------- first, last, xangle, tranx, trany, tranz TRAN XROTATETRANSLATE: 1 7998 -90 0 0 0 999,999 999 999,999,999 ---------------------------------------- ---------------- End pasting here. TRAN STOP The images in the right-hand panel are examples of skewing, rotations and translations. They are not related to the values in the snippets above. |
Creating mitered framing members by skewing cubics with STEP10TRANSLATE snippet: |
|
|
|
|
|