View Single Post
  #8   Ban this user!
Old 10-31-2009, 11:20 AM
Grant Nicholson Grant Nicholson is offline
 
Join Date: Apr 2008
Location: Canada
Posts: 44
Grant Nicholson is on a distinguished road
Enroute vector editing

I've been designing vector graphics for 19 years, 17 of it professionally.

Software that is supported by huge numbers of users receives much more development than software with a smaller user base. The field of vector editing is dominated by the field of graphic design, with a few major players such as adobe.

There aren't as many cnc operators as there are people using graphic design products; this means the programs don't have the huge influx of financial and user support that design software does.

I can purchase a vector editing program of supreme quality for $700 (and it probably has millions of users buying it). Enroute pro was around $7500 (Cdn). The vector editing in enroute leaves a whole lot to be desired. I am drawing my artistic renderings in other much better software that was intended for this purpose, and importing it into enroute.

This being said, Enroute has some awesome features for quickly creating relief art. I have been combining 3D modeling from other software with enroute's functions, and it speeds things up tremedously. I wish it were possible to rotate reliefs on the y axis without converting to mesh, but oh well.

The tooling up functions are excellent, and very intuitive. It really doesn't take long to catch on.

mitered corners, be it during extrusion, or offset contours, have some difficulties.

Imported bitmaps are sometimes buggy.

Exported .ai files usually don't work - printing creates a .pdf file though, and the pdf's are just fine, and can be edited elsewhere.

I'm thinking of going through and compiling my observations about how the software functions, as a service to the company and user base. There are many things to note.

I think Enroute is a fine piece of software. I feel like I made the right choice in purchasing it with my router. I'm sure that all router software has inherent weaknesses and states of development (any intense graphics software user knows how common this is) If we want it to continue to improve, we as users should document it's weaknesses and send them on to the company for tweaking, as occurs in many other software developer/user situations.

Any thoughts?
Reply With Quote

 

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361