The blue NumLock LED on the pad is so bright that it is clearly visible even through the thick photo paper. I printed them on matt photo paper - the kind you get in stationery stores - and then "laminated" (before cutting) with Scotch Magic Tape. I'm also guessing they are far better quality than the cheap pad I bought.Ī couple of other things: The icons were traced from the new v.20 toolbox using Inkscape. These are a lot more expensive, but the key definitions are stored onboard so you don't need software like HID-Macro or USB Overdrive to interpret the strokes. Now, if this works as well as I expect it to, maybe I'll think of something more advanced like those programmable control pads from Genovation or the keypads and sticks from X-Keys.
Overall, the process was easy - in fact the most time-consuming part was deciding which tools to include and how to group them. Essentially, I've managed to get most of my heavily-used tools in here.
The NumLock toggle allows me to give some of the keys dual function. Some can already be seen on the ARCHICAD YouTube channel and I'm likely to click F5 multiple times a day to refresh the browser page and find out if any new videos have been uploaded! We don't want another Lightworks scenario.Īs always, there are bound to be a number of small incremental improvements which will emerge as we go along. This may not be big news but it is desirable for the built-in renderer to evolve alongside the external engine, otherwise we risk stagnation-which is akin to running backwards in our field.
So far, clash detection within ARCHICAD has (to the best of my knowledge) only been possible with elements from MEP Tools.
This is pure BIM and will probably get a big thumbs up from larger practices. I'm guessing here that the criteria sets will be defined much like we do for graphic overrides. Clash detection is something that users always needed to do in an external program but this ability has now been built into the core program.