From Gordon Price on RFO:

Go to the Revit program folder (C:Program FilesAutodeskRevit Architecture 2013Program for RAC) and look for a file called AdskHardwareCertificationReport.xml. Rename this file AdskHardwareCertificationReport.xml.OOTB and accept the warning about changing file extensions. You will now be able to enable Hardware Acceleration just like you did in 2012. Performance will not be as good as direct graphics hardware, but it will be much faster than WARP.

Revit on the Mac (OS X) – Page 6

Read the whole thread if you want to understand some of the limitations and risks of this method.

As per the Revit Architecture 2013 Known Issues:

 Hardware acceleration is not available in the Parallels 7 environment, and Revit will revert to a DirectX 9 based software graphics mode, which will not render materials, sky, artificial lights, and other features when the Realistic visual style is in effect.

o   Workaround 1: When you first start Revit and see the Graphics Options – Cannot Use Hardware Acceleration dialog, select the Save Hardware Acceleration Setting option, and then close and restart Revit. Upon restart, DirectX 11 software mode will be used and features will display correctly in Realistic visual style.

o   Workaround 2: Manually add the following to the [Graphics] section of the Revit.ini file before startup:   UseGraphicsHardware=0

EDIT: Workaround 3 (allow hardware acceleration hack) – from Gordon in the comments:

Dig down to the Revit folder in program files, where Revit.exe lives, and look for a file called AdskHardwareCertificationReport.xml. Delete this file. Revit will now allow you to enable hardware acceleration, and performance will be MUCH better than the no HA fallback of using WARP (which is an API that uses the CPU to mimic graphics hardware and manages to provide performance on par with, say Intel HD2000 hardware). WARP is much better than true hardware acceleration disabled as in earlier versions, but no where near as good as Parallels virtual hardware.
End Edit

This issue was also reposted at

Workaround 2: Manually add the following to the [Graphics] section of the Revit.ini file before startup: UseGraphicsHardware=0″
Workaround 1 did not present itself to me, but workaround 2 was pretty easy to achieve:


I added the last line above to the 2013 Revit.ini file, restarted RAC 2013, and….

As they say these days: “SWEET!!”

‘Scuse me, while I kiss the sky! � microsolresources

Yesterday I tutored two twelfth grade classes at a local high school in how to create and export walkthroughs in Revit Architecture 2011.

They had already modelled buildings in Revit as part of their classwork, and it was quite enjoyable to assist them in presenting their work.

One interesting anomaly came up during these sessions – the students were using good quality Mac workstations, running Bootcamp and Revit Architecture 2011. When modifying a walkthrough I use the Steering Wheel extensively, so it was quite frustrating when Shift+W suddenly failed to show the Steering Wheel!

How did we overcome this problem? There are two different ways to solve it:

  • you can assign a keyboard shortcut to ‘Full Navigation Wheel’. This will work even if Shift + W does not, or
  • Skip forward a few key frames, and then skip backward again. Try Shift + W. It will probably work now (one of the students discovered this).

Here at Dimond Architects, we are exploring a number of ways to deliver Revit training, both to students and to industry professionals. Feel free to contact us if you are interested.