Category Archives: Video

Welcome to the new bosses…

…same as the old Bass.

If you’re hoping the change at the top of Autodesk is going to result in a change to the all-rental business model, abandon that hope now. In this nodding-heavy video, temporary co-CEOs Amar Hanspal (product guy) and Andrew “Baked Beans” Anagnost (marketing guy) confirm it’s full steam ahead. Not unexpected, really.

If either of these guys is selected as CEO (my money’s on Amar), the rental push will continue. Don’t expect to be saved by an incoming CEO, either. The Autodesk board won’t appoint a non-believer.

If you won’t abandon your perpetual licenses, you’ll need to abandon Autodesk.

Video lulz with AutoCAD 360

Thanks to Hans Lammerts on Twitter for pointing out this amusingly cringeworthy AutoCAD 360 YouTube ad:

The guy spilling his coffee and falling over reminds me of the people in those infomercials that can never get the simplest things right:

https://youtu.be/3eMCURWpNAg

OK, so the ad’s bad, but how’s the product? I had a look for myself at the browser version of AutoCAD 360, which is the current name for what has been Visual Tau, Project Butterfly and AutoCAD WS in previous iterations dating back before Autodesk’s acquisition of the Israeli technology in 2009.

It’s a while since I tried it, so I was interested to see the progress that had been made. After all, CAD in the Cloud has been Autodesk’s focus for a long time now, and as this is likely the first product people try out, you’d expect it to be pretty dazzlingly good after all those years of development, right?

Interestingly, it’s still called a Beta, which hardly inspires confidence. Nevertheless, it didn’t misbehave for me, at least to begin with. It didn’t do very much at all for me, though.

On opening a very simple small 2D drawing, the first thing I noticed was the white background. As the drawing contained yellow text, that was no good so I looked for the settings to change the background to black. Couldn’t find any settings. I guess I didn’t really want to read that text anyway.

Nevertheless, I could zoom and pan around OK with tolerable performance. When I tried to select some objects to edit them, nothing happened. I looked around for buttons to press to do things. There was very little to see, and nothing I could find for doing anything much other than redlining over the top of what’s already there.

The second time I tried to open the same drawing, it just hung there, displaying a blue propeller thingy:

I gave up and tried again. This time, things were different! It locked slightly differently:

Now I see why it’s still called Beta.

To be fair, it hasn’t locked like this for me in the past so maybe it’s a one-off. Assuming it’s working, it’s a useful enough viewer. It has some limited markup functionality. That’s it. It’s free, and you get what you pay for.

Calling it AutoCAD 360 is highly dubious. It’s not AutoCAD or anything remotely close to it. It’s not even CAD. It’s a simple online product with capabilities that fall well short of the weakest CAD application back in the bad old days, when people could only dream of something as advanced as the dumb guy’s Nokia in the embarrassing Autodesk 360 ad.

There are also mobile versions of the software for iOS and Android. Haven’t tried them recently, but when I did they were acceptable viewers. Apparently you can pay for versions that actually let you do things. Go for it if you feel confident in Autodesk’s ability to provide a quality product. Me, I’m out.

BricsCAD V17 – the best AutoCAD upgrade in years?

I’ve been evaluating BricsCAD for a few years now, and have been looking at it pretty seriously as a DWG-based LISP-compatible AutoCAD alternative for a year or so. A couple of weeks ago, I flew to Munich for the Bricsys International Conference (at Bricsys’ expense – see the Legal page for disclosure) where I learned quite a few things I had failed to notice during my own evaluation of V17. As you may have noticed, I can be pretty hard-bitten and cynical about what CAD companies have to say about their products, but I came back impressed.

The conference and the product itself are not free of flaws, but I have to say the progress Bricsys has shown in developing the BricsCAD product is really quite astonishing. The rate at which serious, worthwhile-to-customers improvements have been made to BricsCAD over the last few releases is huge. Some of it’s just catching up with existing AutoCAD features, but most of it is going beyond what Autodesk has done. Overall, Bricsys lately has outstripped Autodesk’s efforts in improving its DWG-based flagship CAD product to such a degree that it’s frankly embarrassing for the much larger corporation.

I grabbed Bricsys CEO Erik De Keyser for a brief chat at the end of the conference. I told him that while there were still important areas that need addressing, nevertheless if Autodesk had shipped a new release with a quarter of the improvements that Bricsys managed with V17, it would still have been the best AutoCAD upgrade in fifteen years. Yes, the gap in progress from Autodesk to Bricsys really is that big.

The difference appears to be one of attitude. The Bricsys development team (many were there in Munich to speak to) is focused, motivated and enabled. For Bricsys, BricsCAD really is the flagship product. That’s where all the effort goes; everything goes into the DWG-based product. High-performance 2D drafting, user interface innovation, parametric 3D models, IFC-certified BIM, sheet metal, everything. You would think this would lead to massive bloat, but somehow it doesn’t; the product remains small and fast.

For Autodesk, the emphasis has been elsewhere for some years now. The rate per release of worthwhile AutoCAD improvements, never stellar since the 12-month release cycle was adopted, has been trending downwards since AutoCAD 2010 and has slowed to a trickle. Autodesk is happy to accept the income from AutoCAD customers and use it to develop a hundred trendier products, neglecting the foundation on which the company was built. That’s relying on inertia, and there’s a big question mark over how sustainable that is.

Here’s a 5-minute YouTube marketing video outlining some of the changes. If you have a bit longer, here’s a 37-minute YouTube video of the new features from head of development Hans de Backer. The presentation lacks sparkle (no insult to Hans, but he’s no Lynn Allen) but the substance is there. Note that Hans was demonstrating live to the full conference using a pre-release product, including opening a huge drawing, which surely deserves marks for bravery! As a bonus, you can just about see Owen Wengerd and myself in the bottom left corner.

I’ll be going into more detail on BricsCAD V17 pros and cons later (yes, there are cons), but for now here’s the press release and here’s where you can download the product for evaluation. It’s a straightforward download of a 234 MB MSI file and the install takes just over a minute. That in itself is a breath of fresh air for people who are used to hanging around, waiting for AutoCAD downloads and installs to finish.

Autodesk’s social media consultant spills the beans

Ever wondered why Autodesk is putting so much emphasis on social media these days? Why AutoCAD needs Facebook and Twitter commands? It’s because Autodesk pays social media consultants lots of money to tell them about the importance of social media, and how to be social and media-ish. In this video, one of those consultants explains the process:

Olympic Fencing – Mythbusting the Shin v Heidemann Controversy

This is a departure from the usual subject matter of this blog, but one of the advantages of running my own blog is that I can write what I like on it. This post does have a mention of AutoCAD, but it’s so minor and marginal it’s probably not going to interest many of my usual readers.

Introduction

Now the Olympics are over and a video has been made globally available, I’m going to discuss what happened in the Women’s Epee semi-final between South Korea’s Shin A-Lam and Germany’s Britta Heidemann. The image of Shin sitting disconsolate and alone on the piste, in white on a black background, is one of the iconic images of the London 2012 Olympics. It was replayed at the closing ceremony. Besides making for ‘good’ television, it’s one of the human stories that go to make the Games more than just a vehicle to sell junk food. I’m driven to write about this because I’ve seen a huge amount of complete rubbish written on this subject, mostly by people who have absolutely no idea of the subject about which they are ranting so angrily, but also by some fencers who should know better. I have seen my sport unjustly tainted by inaccurate reporting, demonstrably false accusations, defamatory and untrue statements made against honest fencers and officials, and because this is the Internet, a vast amount of illiterate ranting and ugly racism. This includes both ‘joke’ racist trolling and the real thing, neither of which will be tolerated in comments on this blog. I hope that by delaying this post, most of the morons will have moved on and found something else with which to amuse themselves.

It’s difficult to avoid feeling sorry for Shin in her predicament and outrage at what appears to be a terrible injustice. However, I intend to examine what happened step-by-step and analyse it completely dispassionately, explaining the rules and procedures so they can hopefully be understood by non-fencers. Other than Shin and Heidemann, I will not be using the names of anyone involved, in an attempt to make this as clinical as I can. Where there were failings, I intend to clearly point them out. Equally, where there were not failings, I intend to point that out, too, even if it is contrary to popular belief.

I have no bias to declare here; as a British Australian I didn’t really care who won this bout. I do know and respect a coach who knows and respects Shin’s coach, but I’ve never met or seen anybody directly connected to these events. Fencing is a small world and it wouldn’t surprise me to discover that I am connected to most of the Olympic field via only 2 or 3 degrees of separation.

tl;dr?

This is a very long post. If you can’t be bothered reading it all, feel free to skip to the Mythbusting section. However, I’d appreciate it if you took the time to read all the relevant parts before commenting based on just a subset of my observations.

Background

It’s ironic that an epee bout has been such a controversial event, because it’s generally considered the most straightforward of the three fencing weapons to referee, with the simplest rules. The fencers start in the centre of a 14 metre piste, behind en garde lines 4 m apart.  The whole body is target area, and the first person to hit the other is awarded a point. After a point is scored, both fencers are returned to the en garde lines. If both fencers hit each other within 40 – 50 ms (1/25 to 1/20 of a second), they are both awarded a point and are still returned to the en garde lines.

There is an important and relevant exception to this general double-hit, both-get-a-point-and-return-to-the-middle rule, and that is when the scores are equal and the next hit would win the match. Under such circumstances, a double hit simply stops the bout. The scores do not advance and the fencers are restarted, positioned in basically the same locations they occupied before the hit. What do I mean by this? Well, here are the relevant rules (quoted here as an English translation of the canonical rules, which are in French):

t.17.4. When placed on guard during the bout, the distance between the two competitors must be such that, in the position ‘point in line’, the points of the two blades cannot make contact.

t.17.6. If no hit is awarded they are replaced in the position which they occupied when the bout was interrupted.

t.17.8. The competitors may not be replaced on guard, at their correct distance, in such a way as to place behind the rear line of the piste a fencer who was in front of that line when the bout was halted. If he already had one foot behind the rear line, he remains in that position.

t.17.11. The fencers must come on guard correctly and remain completely still until the command ‘Play!’ is given by the Referee.

t.24. When the order ‘Halt!’ is given ground gained is held until a hit has been given. When competitors are replaced on guard, each fencer should retire an equal distance in order to keep fencing distance.

t.25. However, if the bout has been stopped on account of corps à corps, the fencers are replaced on guard in such a position that the competitor who has sustained the corps à corps is at the place which he previously occupied; this also applies if his opponent has subjected him to a flèche attack, even without corps à corps.

t.27. Should a competitor cross the rear limit of the piste completely — i.e. with both feet — a hit will be scored against him.

To explain some of the fencing jargon here, the position ‘point in line’ is where each fencer stands and holds the sword out with a straight arm pointing horizontally at the other fencer. When fencers are started from any position other than the en garde lines, they should be far enough apart that they are both able to do this without the swords crossing. If a fencer feels that the opponent is too close, it is customary to stand point-in-line, at which the referee will expect the opponent to do likewise while the distance is adjusted accordingly. A corps à corps is when the fencers bump into each other, which isn’t a real issue here. A flèche attack is where one fencer takes a ‘running jump’ past the other. This will become relevant later on.

After the preliminaries are over, the fencers start behind their en garde lines, each 2 m from the centre of the piste. Fencing referees always use French at the top levels, so the Austrian referee (selected by computer randomly from a pool of referees from nations not taking part in the bout) calls to the fencers, “en garde” (get on your guard), “pret?” (are you ready?), and if nobody replies with “non” (no), the fencing starts with the referee’s call of “allez” (go/play/fence). If the referee needs to stop the action, she calls “halt”, pronounced in French with a silent ‘h’ and a short ‘a’. It is unfortunate that the words used to start and stop the bout both begin with an “al” sound, and it’s unfortunate that the word to start the action contains two syllables, but that’s what tradition has given us. It could happen that a referee calls en garde, pret, one or both fencers start early and she calls halt! rather than allez.

In this match, the first fencer to score 15 hits will win, or if nobody gets to 15, whoever scores the most hits within the time available. That time is three periods of three minutes, each separated by a one minute break. If scores are equal at the end, a further period of a maximum of one minute is fenced, at which point there will be a definite winner. There are no draws in fencing. There is no let’s-do-it-all-again option. So let’s have a look at how the bout panned out:

First period

YouTube video link

The bout starts normally enough with en garde, pret, allez and the fencers start moving. Around half a second later, there is a small beep that indicates that the clock has been started. Why doesn’t it start at the beginning of the referee’s “allez”? Because at this level, the referee’s duties are separated from that of the timekeeper. At the level I usually fence, the referee holds a remote control and can time the button press to coincide more closely with the spoken call, but at higher levels the referee is relieved of this burden to better concentrate on the fencing and make clearer hand signals to explain decisions to the audience. The down side to this is that there is always a delay between “al-” where the fencers start and “beep” when the clock starts. The delay varies depending on how well the timekeeper can hear the referee given the background noise, how long it takes them to hear the entire word “allez”, determine it’s not “halt” and press the start button. The reflexes of your average timekeeper are not quite as sharp as your average Olympic fencer, but this isn’t usually a significant problem because it’s the same for everybody and most bouts don’t go down to the last second. Fencers should expect every action to be timed from a point slightly after fencing actually starts, and it happened all the time to varying degrees during the London 2012 event.

Although it’s not obvious on the video, exactly one second after the timekeeper presses the button and about 1.5 seconds after the fencing starts, the clock clicks over from 3:00 to 2:59. For this period, the clock will be counting down using its internal resolution: 2:59.90, 2:59.80…2:59.10…2:59.01 – all of these will be displayed as 3:00. So the bout starts with no movement at all apparent on the clock for well over one full second after fencing actually starts. This will happen at the end too, but much more controversially.

During the first period, Heidemann scores 2 hits, then Shin gets one back to leave the score at 2-1. Towards end of the first period, both fencers back off, the referee calls halt and moves to the first one-minute break period with 6 seconds still to play. This is not actually permitted in the rules, but is generally accepted by convention; neither fencer is particularly interested in attacking and nobody complains about it.

Second period

Video link

No hit is scored for one full minute, which is one of the conditions that triggers a non-combativity rule that is designed to encourage fencers to actually fight each other rather than both waiting for the opponent to move; a real problem in epee. When both fencers back off shortly after, the referee calls halt with 1:52 remaining in the second period and moves on directly to the third period. This is done fully in accordance with the rules, so naturally nobody complains about it.

Third period

Video link

At 2:27 Heidemann attacks and Shin counter-attacks, winning a point to leave them at 2-2. Heidemann starts to get more attacking. At 1:53, double-hit, score 3-3. Fencers return to en garde lines in accordance with the rules. 1:33, another double, 4-4. On restart, Shin steps forward over en garde line as en garde is called, but steps back as referee calls pret. Referee ignores this minor infraction and allows play to continue. At 1:13, another double is scored, 5-5. Heidemann has often adjusted her mask during the bout, and at 0:30 waves to attract the attention of the referee who calls halt. Heidemann brushes hair back from her eyes. Fencers are allowed to do this sort of thing within reason. There is a rule that makes it a yellow card offence to have hair obscuring the target area in foil and sabre, or the fencer’s name in epee, and it’s also an offence if hair has to be adjusted during the bout to prevent this particular target/name obscuration from happening. However, there is no rule preventing a fencer from adjusting their hair to move it out of the way of their eyes so they can fence to the best of their ability.

Edit: a referee of greater experience and ability than myself has suggested that Heidemann could well have been given a yellow card for interrupting the bout without adequate justification.

The last 30 seconds pass without a hit. From 0:13, the referee could have called non-combativity which would have resulted in a final minute being fenced in its entirety, regardless of the score unless a fencer reached 15 hits. The referee has some discretion here, because the rule states the trigger for non-combativity as approximately one minute without a valid hit. Instead, she allows play to continue to the end. If she had called non-combativity, it would have removed one potential source of controversy. In a final minute triggered by non-combativity, double hits advance the score and fencers are returned to the en garde lines each time, meaning there is no grey area about where the fencers are supposed to start. This grey area becomes significant later on.

Edit: the same referee has informed me that the approximately one minute period must be continuous, and that the hair adjustment episode, justified or not, constituted an interruption that made the 1:13 period non-continuous.

However, non-combativity isn’t called this time. Therefore, as the last period finished normally with the scores equal, a sudden-death final minute is fenced, with the first single valid hit winning the bout. Double hits stop the bout but are otherwise ignored. But what happens if there is no single valid hit? Who wins then? Do they keep fencing indefinitely until someone wins? No. In situations like this, one fencer is randomly assigned priority at the start of the minute. It could be done with the toss of a coin but is now usually done electronically. What this means is that if the scores are still level at the end of the final minute, the fencer who was awarded priority is given a hit and wins the bout. In this case, priority was awarded to Shin. This means that if the entire final minute had passed without a valid single hit, Shin would have won the bout on what amounted to an electronic coin-toss. Is this fair? Yes. Those are the rules, all fencers enter the event knowing that that is what will happen, and both fencers had an equal chance of being placed in that situation. It is actually very common for a fencer with priority to lose the bout, and extremely rare for the full minute to be fenced. It’s simply a mechanism for forcing the issue and ensuring that there’s at least one fencer with a must-score attitude.

Final minute

Video link

At 0:24 Heidemann performs a flèche attack when Shin has her back foot on the back line, resulting in a double hit. According to rule t.25, Shin is supposed to stay where she is, but instead Shin walks forward and places herself further up the piste. This “stealing” of ground shouldn’t occur, but it’s not usually considered an infringement worthy of penalty unless the referee points it out and the fencer refuses to place herself as requested. The referee fails to do anything about this particular issue and Heidemann does not object. She places herself at the correct distance away from Shin’s new position. When the bout is restarted Shin’s position is such that she has gained 1.65 m. This gives Shin a significant advantage, because if both of her feet move behind the line, a hit is awarded against her and she will lose the bout. This may seem a minor detail to a non-fencer, but it’s not. Being placed on the back line makes it difficult to use distance to time your counter-attacks, a real problem for an epeeist trying to avoid receiving a single hit.

How do I know the distance Shin gained to within about 50 mm? That’s where AutoCAD comes in. I did screen captures of the video footage, paused at the time the hit was scored and the time fencing resumed. In AutoCAD, I attached the images and was then easily able to compare the distance between the fencers’ feet and the back line with known distances (e.g. the back 2 m of the piste). There are probably better tools for the job, but AutoCAD was handy, familiar, and good enough. My job was made easier by the fact that both fencers chose to position themselves on the far side of the piste, right next to the line, making it easy to measure. Strictly, this is against the rules; fencers should position themselves in the centre of the width of the piste. However, referees frequently allow this to happen unless somebody is practically off the side of the piste or a fencer complains. This kind of leeway in minor matters is often shown by referees, as it was in this case throughout the bout.

Back to the bout; at 0:15 Heidemann flèche attacks again, resulting in another double hit. This time, Shin’s back foot is 0.45 m behind the back line when she is hit. The referee checks the video replay to see if Shin went entirely behind the back line, which she did, but not until after the hit, so it didn’t matter. Despite the referee knowing from the replay exactly where Shin should be placed, she allows Shin to walk up the piste again. Before allowing fencing to start, the referee says “distance, both of you” (in French), because the fencers are slightly too close to each other. At this instruction, Heidemann shuffles back slightly but Shin shuffles forwards he same amount and is allowed to start with her back foot is 0.7 m in front of the line. Thus, she gains another 1.15 m.

At 0:09, same again. Heidemann flèches, double hit, Shin moves from 0.7 m behind to 0.65 m in front of the line, a further gain of 1.35 m.

At 0:05, another Heidemann flèche, another double hit. Shin has been pushed back so far that only the front half of her front foot is on the piste and her back foot is 0.6 m behind. That is, she’s about 0.1 m from going over the line completely and losing the bout. She then moves forward so her back foot is 0.4 m in front of the line, a gain of 1.0 m. Before fencing resumes, the referee calls the fencers to ensure adequate distance. Heidemann starts moving forward before pret is called and Shin complains (rightly) about Heidemann being too close, and she moves back slightly. During this distance reset, Shin gains another 0.2 m, giving her a total of 1.2 m advantage this time round. The distance is still slightly too close when fencing resumes, but the referee allows play to continue. Nobody complains about this.

At 0:04, another Heidemann flèche, another double hit, Shin does the forward walk thing again and moves her back foot from 0.5 m behind to 1.1 m in front, gaining another 1.6 m. The distance at resumption is still slightly too close, but nobody complains.

The magic second begins

Video link

After 3 more seconds, at 0:01 another Heidemann flèche results in another double hit. Shin moves her back foot from 0.7 behind to 0.1 in front in preparation for the last second’s play. The distance between the fencers looks too close, so the referee calls for distance again from both fencers. Following this, Shin moves her back foot to 0.1 m behind the line, giving a net gain of 0.6 m this time.

The distance still looks too close based on how close the swords are to each other, but Heidemann is leaning crouched forward which would make the distance look closer than it really is. If both fencers had stood up and presented a point-in-line position to check that the swords could not touch, they may have been not much closer, if any closer at all, than the distance required by the rules. If you doubt this, try it at home with a weapon. Stand en garde facing a wall, then present point-in-line and shuffle forwards until the tip of the weapon touches the wall. Without moving your feet, bend your arm to return to an en garde position. The tip’s not really that far away from the wall, is it? Lean forward as Heidemann did, and you will find that you can easily touch the wall with your weapon, even with a very bent arm.

At 0:01, Heidemann anticipates the call of allez and starts early, with another double hit as the result. If the timekeeper managed to start the clock at all, there is only a tiny fraction of a second (maybe 0.1 s) between the time starting when the timekeeper presses the button and stopping automatically when Heidemann’s point is depressed. As a result, the time still shows 0:01. As a sabre fencer, I assure you that it is not that unusual for an action to be completed within a second; I’ve seen this sort of thing happen before where a fast fencer and a slow timekeeper are involved. The referee could have given Heidemann a yellow card for starting early. However, this would be fairly harsh; a little leeway is usually allowed for this minor infraction, as it was for Shin in the third period. Had a yellow card been awarded, it would have had no immediate direct effect on the bout, but a subsequent infringement of any type would result in a hit against and thus loss of the bout. It would therefore have made Heidemann very wary of starting early again.

When coming en garde this time, Shin resumes in the correct position and Heidemann attempts to start too close. On Shin’s legitimate objection, the referee calls Heidemann to yield distance. She does, but then regains it and a little more. The referee has to call for distance again, and Heidemann is in danger of receiving a yellow card for failing to obey the referee’s instructions. Despite these calls, fencing is allowed to resume with the fencers too close. Again, the situation isn’t as bad as it looks because of Heidemann’s lean forward making the swords look closer than they would be if performing a stand-up point-in-line distance test, but it’s fair to say that the referee did not adequately enforce the rules at this point. This time, it’s to Heidemann’s advantage, unlike the multiple previous times where it was to Shin’s.

At 0:01 again, there is no early start by Heidemann but again, a double hit occurs with a small fraction of a second between the timekeeper’s button-press and the hit landing, and thus the time is still registering 0:01. Shin complains to her coach (apparently about the time not counting down) and walks up the piste again. Some commentators have stated that the timekeeper didn’t start the clock at all during the course of this hit, but I can clearly hear two beeps for the start and the hit, much less than half a second apart. While play is halted, the referee asks the timekeeper, “Time?”, presumably to check that things are working properly. At this, the timekeeper apparently presses the start button accidentally (or mistakenly believing that the referee wished the time to be run down), resulting in it going down to 0:00. It takes about half a second to do this, in hindsight giving some idea of the time that was remaining. Some of the crowd cheered, thinking the match was over. However, the time can’t count down when there is no fencing happening, so there was obviously a fault. Where there is a timekeeping fault, the rules clearly say the referee must estimate the remaining time and have the time set accordingly:

t.32.1. At the expiry of the regulation fencing time, if the clock is linked to the scoring apparatus (obligatory standard for finals of official FIE competitions), it must set off automatically a loud audible signal, and automatically cut off the scoring apparatus, without cancelling hits registered before the disconnection. The bout stops with the audible signal.

t.32.3. Should there be a failure of the clock or an error by the time-keeper, the Referee must himself estimate how much fencing time is left.

She asks for it to be set to one second, which is what the clock said before the error, and calls the fencers en garde. Given that fencing clocks use a visible resolution of one second, this is the only action the referee could reasonably take. It might be that the clock actually had only a hundredth of a second left on it internally, but there’s no way of anyone knowing. She couldn’t estimate the time at 0:00 because there was clearly some time left on the clock when the error occurred; it said 0:01. While the clock is being set back to 0:01, the Korean coach comes out of his technical area to complain about the point that three actions could not be launched without the clock counting down from 0:01. He’s not allowed to come out of his “box”, or appeal any decision (this is the fencer’s responsibility), or shout at the officials. He could well have received a yellow card for doing any of the above. He is apparently a usually very calm, polite gentleman and he must have understandably felt very strongly about the situation to react in this way.

At this point, it’s important to note that it is traditional in fencing (as in most other sports) for all decisions of the referee to be final, and this is largely still the case today. Some decisions can now be appealed, but options are limited. You can appeal on the referee’s interpretation of the rules, but not on a finding of fact by the referee, except in a limited number of video appeals where that facility is available (as it was here). Also, fencing has only one undo step. You can only appeal the previous hit. If you realise that your weapon hasn’t been working all bout when you are 10-0 down, you can ask for it to be tested and you might get the last hit annulled, but 9-0 down is the best you can hope for. As for the time you spent fencing with a useless weapon before that last hit, forget it. That time is gone, and not subject to appeal or adjustment. This may seem harsh and unfair, but it’s really the only way it could be. Trying to unravel a bout beyond a single hit is just too difficult to codify and apply practically, given all of the possible permutations. Here are the relevant rules:

t.122.1. No appeal can be made against the decision of the Referee regarding a point of fact.

t.122.2. If a fencer infringes this principle, casting doubt on the decision of the Referee on a point of fact during the bout, he will be penalised according to the rules. But if the Referee is ignorant of or misunderstands a definite rule, or applies it in a manner contrary to the Rules, an appeal on this matter may be entertained.

t.122.3. This appeal must be made:
a) in individual events, by the fencer,
b) in team events, by the fencer or the team captain,
it should be made courteously but without formality, and should be made verbally to the Referee immediately and before any decision is made regarding a subsequent hit.

Back to the action. At this stage, the fencers are ready to fence the final second. It may be that the time should really have been 0:00.01 rather than 0:01.00, but the latter is the official time at this point. Shin has done a bit of querying and her coach has made his views known, but the coach is not entitled to officially appeal and Shin not done so. Even if an appeal had been made, it is almost certain to have been rejected. The official time is the official time and is not subject to appeal. The referee’s setting of the clock to her estimate of 0:01 was done exactly according to the rules, and is the best estimate that could be made given the one-second resolution that is displayed and can be set on the timing mechanism. An attempt to set a time of some part of a second might possibly have been made by setting to one second and performing a quick start/stop, but it would have been without precedent and fraught with difficulty. An appeal that queried the setting of the time to 0:01.00 would have been rejected on the basis that it related to a matter of fact as determined by the referee. Such an appeal would have possibly resulted in a yellow card for Shin, not that it would have mattered at this late stage. So nothing up to this point has been appealed, and once there’s another hit, nothing that has happened up to this stage can possibly be appealed, regardless of the circumstances.

The referee insists that a reluctant Shin put on her mask and fence the final second that is now on the clock. The referee again calls for distance specifically from Heidemann, although it is Shin who has moved forward during the commotion, gaining another 0.7 m. Again, the fencers are still allowed to start with a distance that is a bit too close, but not as bad as it looks due to Heidemann’s lean. I estimate that the fencers are perhaps 0.5 m too close. Certainly, the distance that the fencers are allowed to start at is inadequate. Equally certainly, the distance is inadequate not because of Heidemann encroaching ahead of where she should, but primarily because of Shin’s walk up the piste.

Up to this point, Shin’s total gain from walking up the piste after each double hit amounts to over 8 m. The referee has erred in allowing this to happen, thereby handing Shin an enormous advantage. It is extremely likely (although not completely certain) that if the referee had set the fencers correctly each time, Shin would have lost by either being driven off the back of the piste, or found herself unable to use backward motion to make effective counter-attacks. This would have happened a long time before the magic everlasting second became an issue. Alternatively, the referee could have warned Shin the first time she did it, issued a yellow card the second time and a red card the third time, handing Heidemann the bout. This could also have happened long before time became a source of controversy. The last second has understandably attracted a lot of attention, but nobody seems to care about the 6 seconds that weren’t fenced in the first period, the 113 seconds that weren’t fenced in the second period, or the 13 seconds that could have been chopped off the third period for non-combativity, or the fact that doing so would have completely changed the situation regarding distance, because each double hit would have returned the fencers to the en garde lines.

The final hit

Video link

So the fencers are set en garde (too close due to Shin’s advancement and the referee’s failure to disallow it) and with a full second on the clock (which is more than there should have been due to the timekeeper’s error). On allez, Heidemann launches forward, beats Shin’s blade and hits her, with the clock still on 0:01. Let’s examine that last sub-second in detail.

First, the referee starts with the words en garde, pret and allez as usual, with the same short period of time between pret and allez that she had been using on previous occasions. This predictability allowed Heidemann to time her start of movement to coincide with the start of the word allez, which she did perfectly. As she launches herself forward, the referee’s word allez is completed, and the timekeeper reacts pretty quickly and presses the start button. You can hear the beep just before Heidemann beats the blade, about 0.3 s after allez starts and only 0.1 s after allez ends. The hit lands shortly after (about 0.7 s later). If the timekeeper was (as some have suggested) deliberately trying to give Heidemann time to score a hit by delaying the start button, they made a really bad job of it. In this particular instance, the timekeeper reacted as quickly as it is reasonable to expect.

The appeals

By the rules of the sport, Heidemann has now won the bout. Heidemann hit Shin one more time than she was herself hit, and this was done within the time allowed as measured on the official equipment. What would normally happen now is that the referee checks the video replay, orders the fencers to the en garde lines, indicates the winner and observes the fencers saluting each other, the referee and the crowd, before shaking hands and retiring to prepare for the next bout. Instead, what happens is that all Hell breaks loose.

This post is already enormous, so I don’t intend to go over the appeal process or the sit-on-the-piste thing in any detail. I will, however, point out that there was really never any hope for any appeal. Remember, nothing prior to the last hit is subject to appeal. Taking that last hit, there was a second left on the official clock at the start, and Heidemann scored a valid hit within that second and before the buzzer loud signalled the end of the bout and the scoring mechanism was disconnected. You can’t undo the fact of that hit just because you don’t like the result, or because it’s heartbreaking for the defeated athlete. However, here are some relevant rules about the appeal process, if you’re interested:

t.84. By the mere fact of entering a fencing competition, the fencers pledge their honour to observe the Rules and the decisions of the officials, to be respectful towards the referees and judges and scrupulously to obey the orders and injunctions of the Referee.

t.95.1. Whatever juridical authority has taken a decision, this decision may be subject to an appeal to a higher juridical authority, but only to one such appeal.

t.95.2. No decision on a question of fact can be the subject of an appeal.

t.95.3. An appeal against a decision only suspends that decision when it can be judged immediately.

t.95.4. Every appeal must be accompanied by the deposit of a guaranty of US$80, or its equivalent in another currency; this sum may be confiscated for the benefit of the FIE if the appeal is rejected on the grounds that it is ‘frivolous’; this decision will be taken by the juridical authority responsible for hearing the appeal. However, appeals against the decisions of the Referee do not require the deposit of the guaranty mentioned above.

Despite the one-appeal rule above, there were actually two appeals entered. The first was an immediate verbal appeal of the referee’s decision (contrary to the rules again, by the coach rather than the fencer), where a gaggle of officials from several different countries spent some time examining the video evidence and discussing the matter. The Technical Director then informed the referee that her decision was upheld, and she awarded the bout to Heidemann who rushed over to shake Shin’s hand as required by the rules, then left to prepare for her next bout. A second, written appeal was then entered, accepted and discussed for even more time while Shin sat alone in tears. The appeal was eventually dismissed, Shin was informed and escorted from the piste by FIE officials.

Mythbusting

Addressing various specific complaints that I’ve seen, let’s take them one at a time to see what’s true and what’s false.

  • Timekeeping in fencing has a resolution of one second, which can lead to problems such as thisconfirmed. But this has always been the case and it’s the same for all fencers. Problems like this are actually extremely rare; when they occur fencers might feel hard done by, but it’s something we accept and live with. That said, I would not be surprised to see a change to fencing timekeeping at the top level as a result of the publicity from this incident, maybe changing to a resolution of 0.1 seconds in the last 10 seconds of the bout.
  • The referee did not place the fencers correctly, allowing Heidemann to start too close on the last two hitsconfirmed. This was indeed a refereeing error; allez should not have been called while they were that close. But it’s important to note that Shin was largely responsible for this because she advanced up the piste and placed herself in that position. It’s also important to note that at no point did either fencer stand point-in-line prior to fencing to ensure the distance was set correctly.
  • Shin advanced up the piste after each double hit but one, gaining vital ground, allowing her to better counter-attack and stay in the boutconfirmed. According to my calculations, she gained over 8 m in this way.
  • The referee demonstrated anti-Shin bias in her placement of the fencersbusted. While it’s true that the referee erred in allowing the fencers to start too close, Shin had placed herself in that position. She could have held out a point-in-line and/or backed off to the correct position in order to ensure there was adequate distance. The idea of anti-Shin bias by the referee is ridiculous, given that she allowed Shin to illicitly gain over half a piste during the final hits.
  • The timekeeper hit the start button a fraction of a second after allez was called, resulting in Heidemann having more time to score the winning hitconfirmed. But this needs to be placed in context. The timekeeper always hits the start button a short time after allez is called, it’s just the degree that varies. The delay that occurred on the winning hit was consistent with what had been occuring earlier in the bout, and indeed in other bouts in the competition. It is not reasonable to expect a timekeeper to react significantly faster than they did on the winning hit.
  • It’s impossible to score two hits without the clock being seen to count down at least a secondbusted. We’re talking about Olympic fencers here, with fast muscles and faster reflexes. The tip of a fencing weapon is said to be the fastest non-ballistic object in sport. Have a look at some of the Olympic sabre bouts and see how much the clock winds down after a few straight attacks from a full 4 m apart. At a much lower level than this, I’ve seen a 5-hit sabre bout decided in 7 seconds, and that’s with the referee doing the timekeeping and thereby avoiding the delays you tend to get with a separate timekeeper.
  • The timekeeper failed to hit the start button at all during the penultimate hitbusted. It is possible to make out a clear start beep during this action, but it’s only just before the beep for the hit.
  • The timekeeper hit the start button while fencing was halted before the last hit, allowing the clock to move from 0:01 to 0:00. This resulted in the clock being reset to 0:01 and Heidemann having a full second to score the winning hitconfirmed. This was indeed an error, and it had a significant effect on the outcome. But it’s no indication of bias. The timekeeper (who I understand to be a British adult fencing volunteer) is unlikely to have had any desire to see any particular fencer win this bout. Fencers generally have an extremely well-developed sense of fair play, so it’s a highly insulting accusation to make. However, if you assume that there was pro-Heidemann bias, doing this deliberately would have been an extremely risky strategy. Not only was the action extremely exposed, there was a significant risk that the time of 0:00 would have been accepted by the referee as the official time, with Shin being declared the winner.
  • The referee erred in having the time set to 0:01 following this timekeeping errorbusted. The rules are explicit about what to do under these circumstances, and the referee followed them in the only way open to her.
  • Heidemann acted ungraciously in celebrating her victorybusted. Nobody who has watched more than a couple of fencing matches could believe this. It’s always unfortunate for the fencer who doesn’t win, but the nature of the sport is such that each bout always has a winner and a loser. Celebrating an important fencing victory with exhuberance is totally normal. Not celebrating a narrow victory to win a place in the Olympic final would have been totally bizarre.
  • Shin received a yellow card during the boutbusted. I have seen several statements to the effect that Shin already had a yellow card and therefore may have felt reluctant to argue with the referee about Heidemann’s distance. This is false. Shin received a yellow card only at the very end of her long wait on the piste, well after the bout was over. What appears to be confusing some observers is that the video shows a patch of yellow next to Shin’s name that appeared between the third period and the final minute. This was there to indicate that she had priority, not to indicate that she had a yellow card.
  • The clock was reset to 0:01 because Shin committed an infringementbusted. I have seen claims that the FIE claimed in an official statement that the clock was reset from 0:00 to 0:01 because of a yellow card infringement by Shin. This is one of the more bizarre things I’ve seen claimed. First, the video makes clear that there was no infringement at that point (at least, not one noticed or addressed by the referee). Even if there had been an infringement, there is no provision in the rules for adjusting the clock because of any infringement. There is no such thing as a “penalty second” in fencing. It didn’t happen, and couldn’t have happened.
  • The clock displays 0:01 when the time is anything from 0:01.99 to 0:00.01 seconds, so there was practically 2 seconds in which to score the last hitbusted. Watch the videos of this and other Olympic bouts and see what the clock does when it’s moving freely (not interrupted by hits). It doesn’t take 2 seconds to move from 0:01 to 0:00. A period starts at 3:00 and moves to 2:59 one second later, not instantly. Moving from 0:02 to 0:01 takes one second. Moving from 0:01 to 0:00 takes one second, too.
  • The clock gets reset to a whole second every time a hit is scoredbusted. Heidemann has been quoted as stating this, but it’s not correct. Again, watch other videos and see what the clock does. Sometimes the clock ticks down practically instantly after the start beep is heard, while on other occasions it takes nearly a full second, depending on how much of a full second was left internally on the clock. The most obvious proof of this is when the timekeeping error is made before the final hit. You can hear the start beep when the button is pressed and the end beep when the time reaches 0:00, and there is clearly less than a full second between the beeps.
  • The FIE reprehensibly demanded money from the Koreans before the appeal, proving that it is corrupt, biased and evil – busted. Some people got pointlessly very worked up about this. This is all above board; it’s written into the rules (see above) and applies to everybody. An $80 deposit is required along with a written appeal. As with other sports, an appeal deposit is there in the established procedures to discourage frivolous appeals. The sum is insignificant in the scheme of things (my last competition’s entry fee was about triple that), and my understanding is that it is almost always refunded anyway. Move along please, nothing to see here.
  • Shin staged a sit-down protest on the pistebusted. Sit-down protests are not allowed in fencing. Any kind of protest outside the official processes (e.g. throwing your equipment around) is generally considered an offence against sportsmanship and subject to a black card. Even refusing to salute correctly is a black card offence, which means exclusion from the whole competition and a 2 month ban. Shin stayed on the piste because she believed, or was told, that she had to remain on the piste while the post-match appeal was being heard. It is true that both fencers staying on the piste is a requirement during an appeal on the piste. However, from my reading of the rules it does not appear to be a requirement during determination of a written appeal.
  • Shin was rudely manhandled off the piste by security goons – busted. Once Shin was informed of the outcome of the official appeal, she had no place on the piste and was under an obligation to leave when requested. There were further bouts to be fenced, including her own bronze medal bout to be held 10 minutes later. If she didn’t leave at this point, she was in grave danger of receiving a black card and losing the right to fight for a medal at all. It was in everybody’s interests, particularly hers, that this didn’t happen. Rather than waving a black card in her face and calling security, a senior FIE official and his colleague put their arms around her and gently encouraged her reluctant departure. A yellow card was discreetly shown at this point; it’s not clear if this was for her initial reluctance to leave or as an automatic procedural result of the failed appeal. It is unfortunate from the point of appearances that the gentlemen in question are significantly larger than Shin, but other than that it is difficult to think how this could have been handled more gently.
  • The FIE should have just made the fencers re-fence the final minute or even the whole boutbusted. Not only is there no provision for doing this within the rules, it’s also an illogical suggestion. People who are outraged about Shin having to hold on for a possible extra second or so are suggesting that she should do so for another whole minute, or up to ten minutes? How does that make sense?
  • Shin “deserved to win”busted. I’m moving away from a purely objective viewpoint by addressing this point, but to me, the fencer who scores the most hits deserves to win. That would be Heidemann, then. If Shin had survived that final everlasting second, she would have been awarded the bout thanks to random selection rather than scoring the most hits. While Shin was undoubtedly disadvantaged by timekeeping errors, she was only still in the bout at that time because Heidemann had already been significantly disadvantaged by refereeing errors.
  • This is the worst example of timekeeping ever seen in top level fencingbusted. Enjoy this video of the second period of the 2009 Veteran (70+) World Championship Sabre Final. Keep an eye on the clock between hits.

Summary

There were undoubtedly mistakes made in both refereeing and timekeeping in this bout. However, they were relatively minor mistakes compared with those that are made on a regular basis by all fencing referees, myself included. It’s not at all uncommon for a hit to be given the wrong way in foil or sabre. It happens, and we live with it, because mistakes are made in all sports where human judgement is involved. Despite a lot of Internet ranting, there is no real evidence of any anti-Shin bias. When examined objectively, the sum of the incorrect and dubious refereeing actions in this bout show that a significant net benefit was provided to Shin.

Although I cannot aspire to the level of excellence and dedication demonstrated by Olympic fencers, I know from recent personal experience that it’s very unpleasant to lose an important bout. It’s heart-rending to lose that bout by the slimmest of margins. It induces not just anguish, but also anger, when you lose that bout because of what you believe to be refereeing, timekeeping or scoring errors. Been there, done that, bought the T-shirt. So I can very much empathise with Shin A-Lam in her predicament. But was she robbed of an Olympic medal? No, not really. Not when you examine all the facts.

AutoCAD 2013 – Autodesk video tutorial for Help

Autodesk has produced a 2-minute video explaining the features of the new Help system in AutoCAD 2013 that I recently panned. As you might expect, it’s kind of upbeat and chirpy, but the fact that Autodesk feels the need to provide a tutorial on how to use Help says it all, really. Whatever, it may be useful to you, so here it is. It’s hosted on the Autodesk site, unlike many other Autodesk videos (and my own, to be fair), so those of you who have YouTube blocked at work may still be able to watch it.

If you’re having trouble watching the tutorial, don’t panic. I expect Autodesk will soon produce another tutorial explaining how to use the tutorial explaining how to use Help explaining how to use the product to actually do work.

Software as a service is great…

…for some things. The other day, I amused myself by creating a video using a site called Xtranormal. You’ve probably seen 3D cartoon-like videos of people with stilted voices. It’s done by signing up for a free account, choosing a background and some characters, then typing in your script. This is converted, generally fairly successfully, to spoken words. The characters lip-sync to your script, you publish the video and you’re done. If you have a YouTube account, the site will upload the video for you. Video creation service provided on line, video hosting and viewing service provided on line. No problem.

Here it is; this blog’s readership is not the intended audience, so you probably won’t find it particularly amusing.

Could the video creation have been done using a standalone application rather than doing it on line? Absolutely. It may well have been quicker on my PC, but using this SaaS was fine. It performed well enough to be usable. Somebody taking my work isn’t an issue, as I always intended to show it publicly anyway. The worst that can happen is that my email address is abused, but it’s easy to make a throwaway email address.

I think that for this trivial recreational task, SaaS technology was absolutely appropriate. If the site had been unavailable or my Internet connection had been down, it wouldn’t have really mattered. If YouTube goes down for an hour and people can’t view my video, so what? If YouTube closes my account and makes all my videos unavailable, that would be more annoying but still not fatal.

So, full steam ahead for CAD on the Cloud, then? Er, no. It has yet to be shown that the Cloud is the appropriate technology for that particular use. I’m sure it will be, for some specialist niche requirements. But all of it? A complete fully-functional CAD application provided on a SaaS basis as an appropriate use of technology? Not any time soon. Maybe one day, but then again, maybe not. There will have to be real, demonstrated benefits that outweigh the concerns. The CAD Cloud vendors are going to have to go well beyond the “Wow! This is cool!” phase first, and start engaging the CAD community in serious discussion about the genuine concerns that customers have about the technology. Ignoring those concerns won’t make them go away.

Australian Fencing Championship 2011

I have been away in Sydney for a while, attending the Australian Fencing Championships. I fenced in five events with uneven success (I came 52nd out of 70 in the Open Foil, for example), but a few things made me happy. First, I was able to fence for Western Australia in the Team Foil event as captain of the WA ‘B’ team, which put up a decent performance in going down to a strong ACT ‘A’ team. Next, I came 6th in the Veteran Foil; down from last year’s 2nd, but quite respectable given the strength of the field.

The event I was really concentrating on, the one in which I most wanted to do well, was the Veteran Sabre. I fenced pretty well through the pools and direct elimination bouts and got through to the final. There, I faced an opponent who had beaten everybody else that day, and I had trouble maintaining the same level of performance. Who would come through to be crowned national champion for 2011? Watch the video (YouTube, 3:02 long) of the Veteran Men’s Sabre Final to find out:

I’m on the left. If a red light goes on, I’ve hit him. If he hits me, it’s a green light. If both lights go on, we’ve both hit each other within 120 milliseconds and the referee awards the hit based on right-of-way rules. Veteran direct elimination bouts are fought until one fencer scores ten hits. Link to results.

Fencing in Canberra – video

It’s about time I posted about something other than the Cloud, or even CAD.

Every year, there are four national-level fencing competitions in Australia. As they are almost all held on the other side of the continent, I don’t get to compete in them as often as I’d like. However, a couple of months ago I did have the opportunity to compete in the third of these competitions for 2011, held this year in Canberra.

This was very special to me because my mother and sister were in the audience and it was the first time either of them had ever seen me fence. It was also special because my sabre coach, Frank Kocsis, flew out to be with me and his other students. Frank has taken only two years to move me from complete sabre novicehood to being competitive at national level, particularly in the veteran (over-40) events.

This is not an entirely Cloud-free post, because this video of me fencing in the Veteran Men’s Sabre Semi-Final (2:49 long) is hosted on YouTube:

I’m on the right. If a green light goes on, I’ve hit him. If he hits me, it’s a red light. If both lights go on, we’ve both hit each other within 120 milliseconds and the referee awards the hit based on right-of-way rules. Veteran direct elimination bouts (like this semi-final) are fought until one fencer scores ten hits.

If you want to see how the winner of the semi-final did, here is the Final (4:46).

I got into a fight. Caught on video.

Last weekend, I competed for the first time in a national-level fencing competition, the “Be Active” Western Australian International Fencing Tournament (AFF#3). Most people compete in one or two events within a competition, but I thought I would challenge myself and had a go at all six of the individual events available to me. I set myself what I thought were realistic goals for each event. Here is how I did at chasing those goals:

Open Men’s Foil – goal: top 32 – result: 22nd – achieved.
Open Men’s Epee – goal: top 32 – result: 42nd – failed.
Open Men’s Sabre – goal: top 16 – result: 16th – achieved.
Veteran Men’s Foil – goal: top 8 – result: 3rd= – exceeded.
Veteran Men’s Epee – goal: top 8 – result: 6th – achieved.
Veteran Men’s Sabre – goal: top 4 – result: made the final – exceeded.

If you are interested, have 5 minutes to spare, and your access is not blocked at work, you can have a look at me competing in the final of the Veteran Men’s Sabre using this YouTube link. Hopefully, you should find it a pretty entertaining contest, even if you don’t entirely understand what’s going on. If I hit him you will see a red light, if he hits me it’s green, and if both lights go on that means we have both hit each other within 120 milliseconds and the referee decides the point based on right-of-way rules.

I have only been fencing sabre for about a year, so I was very happy to reach the final. That I did so is all down to my sabre coach at my club Excalibur, legendary Hungarian master Frank Kocsis. You can see him briefly on the video as he approaches me during the break to calm me down and get me to focus. I don’t think I’ve ever been that pumped!

AutoCAD for Mac in Beta

Disclaimer: I have absolutely no access to inside information about this Beta. Even if I had, I would not reveal anything that I had learned as a result of such access. This post discusses only information that is already public knowledge.

The native Mac OS X AutoCAD port that Autodesk has been foreshadowing for some time is now in Beta, it seems. The Italian Mac community is getting particularly excited about the leak, but it’s also a popular subject of discussion on at least one English-speaking forum. The Autodesk codename is Sledgehammer, and it’s currently 64-bit only. If this is a subject that interests you, with a bit of sniffing around you can easily find screenshots, a video and you can apparently even download it via torrent if you’re feeling particularly brave/stupid.

If you’re interested in trying it out, it would be much better to apply to join the Beta program. That way, you will stay legal, you won’t download a trojan and you will contribute towards improving the product. Autodesk will probably need such contributions, because the early Beta allegedly runs like “a sewer” with huge performance issues. That should not be a surprise at this stage, but it should give you some idea of how much work Autodesk has ahead of it before it has a product that is fit for human consumption.

Oh, if you do join Autodesk’s Beta program, please be a bit more careful with the software than the guy who thought it would be a cool thing to hand out to his friends.

Edit: Ralph thinks it’s fake. I really don’t think it is, but must acknowledge the possibility that I’m wrong.

Edit 2: More discussion and screenshots at SolidSmack.

Autodesk Knowledge Base – who thought this was a good idea?

This evening, I needed to know exactly which operating systems were supported by all AutoCAD releases from 2004 to 2011 inclusive. I have a pretty good idea, but I needed to confirm that my mental picture is completely correct. So I hopped over to the Autodesk Knowledge Base and entered “system requirements” in the search engine. Only one of the first 50 results was relevant, and that was for AutoCAD 2011. So I clicked on that. Did I get an easily digestible list of system requirements, including a list of exactly which operating systems were supported by AutoCAD 2011? No, I did not.

What I got was this:

AutoCAD 2011 System Requirements Knowledge Base Entry

So I clicked on the pretty picture, hoping to be taken to an easily digestible list of system requirements, including a list of exactly which operating systems were supported. Is that where I was taken? No, it was not.

Instead, I was taken to a 16-minute YouTube video. As I was not being blocked by a business firewall at the time, I could watch a few stuttery, blurry marketing images flash past during the few seconds it stayed on my screen. There’s a technical term for this kind of thing. It begins with w and rhymes with bank.

But I don’t need to tell you how dumb this is. Anybody who is smart enough to read this blog can work that out. But the people at Autodesk who thought this was a great idea? Really, what on earth were they thinking? What were they smoking? Strewth!

Carl Bass on TV

Autodesk big cheese Carl Bass gets a friendly interview on NBC’s Press:Here (amusing name, “press colon here”). It’s kind of funny seeing CAD described by non-CAD people (the presenters, not Carl). Among other things, he discusses being fired by Carol Bartz, Autodesk’s role in Avatar, the benefits of piracy, iPhones, 3D printing, open source and Autodesk being green. I’ve embedded the two Bassy bits here for convenience; these embeds will display ads that are not under my control.

Edit: I’ve removed the embedded clips as they were slowing down this whole site for some users and even disabling some features. If you want to view the interview, please go to Press:Here and look at Episode 46 Autodesk Part 1 and Episode 46 Autodesk Part 2.

This is what I do in my spare time

Fencing. With swords, not pickets, barbed wire, etc. I gave it up 25 years ago, then took it up again about 18 months ago. I now fence all three weapons, having started Sabre about six months ago. Fencing is a very aerobic sport, and participating in it has done wonders for my fitness and mobility over the past year or so.

Here are a couple of videos of me fencing foil in a Masters competition last year.

YouTube link.

YouTube link.

Autodesk’s cloudy drawing offering

Autodesk’s Project Butterfly is its latest offering in the Cloud (Software as a Service, SaaS, web-based software, whatever) area. This is a Labs technology preview (i.e. it ain’t cooked yet) of browser-based drawing system based on Autodesk’s purchase of Visual Tao. The idea is that no software other than a browser is required to create, edit or just view drawings. To try it out, head to http://butterfly.autodesk.com/ and pick on Try Now. If you’re interested in going further with it, you will need to create an account, which is a quick and painless process. This account is separate from your Autodesk ID.

For more details, see Scott Sheppard’s posts here and here, the Project Butterfly blog, and the Project Butterfly page on the Autodesk Labs site, which includes a series of videos such as this one:

I’ve had a brief play with it and while it’s not as horribly slow as I had feared (the Ribbon is much quicker than AutoCAD’s, although that’s not difficult), it’s currently an extremely limited environment. Other than viewing and some very crude drawing operations, pretty much everything I wanted to do either couldn’t be done, or couldn’t be done in a satisfactory way. Once I had discovered how to get a drawing out of the clouds and in my own hands (it’s not Save As), the export crashed with an HTTP Status 500 error. Apparently, the server encountered an internal error () that prevented it from fulfilling this request.

Teething problems aside, it’s hard to imagine anyone accustomed to full-featured CAD software actually spending all day drawing with this mechanism. In fact, I can’t imagine spending more than an hour on it before tearing my hair out; a few minutes was enough. It’s perfectly adequate for viewing and marking up, but as a drafting tool it’s just a toy.

But it’s a start, and Autodesk is wise to get its head into the clouds. If SaaS really is The Next Big Thing in CAD, then Autodesk would have looked very silly if it had missed the boat altogether. I’m not convinced that SaaS is going to have the impact that some are predicting, but I’ll cover that argument in a separate post.

Some thoughts on AutoCAD Exchange

I’ve added a link to Autodesk’s new AutoCAD community site, AutoCAD Exchange. As with most things Autodesk, there are pros and cons. Here are my first impressions.

I think it looks good in a Vista-black kind of way. I know some of you don’t like the black look in software, but I do. The layout looks a bit cluttered and confused at first, but I’m sure visitors will quickly get used to where to find things. The site appears to be designed around 1024-wide resolution. If you have more than this, as most CAD users do, then there are wide areas of wasted space either side of the good stuff.

The front page is basically a teaser. To get to the useful content or do pretty much anything, you need to register or sign in. I don’t particularly like this, and it gives the impression (false or not) that Autodesk wants to own and control you, even if you’re just viewing a site. The registration process is the same as for other Autodesk sites such as the discussion groups, so if you have an Autodesk identity, you’re already registered.

As it is a “community” site, on first sign-in you are invited to fill in more details, provide an avatar and so on. Some people might not like this, but it’s optional and Autodesk knows where I live so it makes no difference to me. I know where Autodesk lives, too. It has yet to be seen if Autodesk manages to develop a real community on this site, and if so, how open that community is allowed to be.

Autodesk is encouraging bloggers to add an Autodesk Exchange widget to their blogs. I won’t be adding one in a permanent position because this is my blog and not Autodesk’s. I kind of like my independence, and if a company wants space on my blog they can pay for it. Anyway, the widget is available in three sizes and here’s what the largest one looks like:

I’m likely to appear in one of those little interview videos soon, as they were shot during the bloggers’ visit to San Fransisco in early February. When you do get to see it, yes, that’s really me (and Melanie Perry) saying nice things about AutoCAD 2010, it’s not computer generated. Except for the background, that is, which is computer generated. It was bright green in real life. Other than that, no deception, lies, arm-twisting or bribes were involved. Oh, unless you count the free trip to San Fransisco as a bribe. I interviewed Autodesk, they interviewed me, and I actually had positive things to say about AutoCAD 2010. More on that later.

AutoCAD Exchange is an important and potentially very useful site for AutoCAD users. Check it out, and if you feel like it, report back. You can pretty much say what you like here.

Bug watch – identify this insect

No, not the Bug Watch, just a bug you can watch. Does anybody know what this insect is? It is the second one of these we’ve found in our home in Western Australia. It’s very active and it smells horrible.

YouTube Link

For those of you who can’t access YouTube, here are some photos of the bug:

Mystery Bug

A higher resolution version of the above picture is available here. This is the bug about to be given its freedom:

Mystery Bug

On release, it buried itself in our lawn:

Mystery Bug

In 25 years in Australia, I had never seen one of these until recently. Any ideas?

A gaggle of geeks

Time to lighten things up a bit, I think. While attending the AutoCAD 2010 product launch in San Francisco on 5 February 2009, I conducted a series of micro-interviews with a collection of AutoCAD bloggers and Autodesk employees. One geek asks 14 other geeks if they are geeks; nothing too serious here. I hope Shaan enjoys my tabloid journalist editing job right at the end.

YouTube link.

Thanks to all the interviewees:

Heidi Hewett, Autodesk blogger
Lynn Allen, Autodesk blogger
Melanie Perry, blogger
Robin Capper, blogger
Brian Benton, blogger
Todd Shackelford, blogger
Jon Page, Autodesk person
Matt Stein, Autodesk person and personal blogger
Shaan Hurley, Autodesk blogger
Donnie Gladfelter, blogger
Ellen Finklestein, blogger
David Cohn, blogger
Mark Douglas, blogger
Guillermo Melantoni, Autodesk person (still waiting for that blog, Guillermo!)

What is the collective noun for geeks, anyway?