Changing the Reflection Map for Chrome in Inventor 2008/2009
By Dennis Jeffrey, AICE

Description of the problem
Upon installing Autodesk Inventor 2008, shiny objects such as chrome appear with undesirable colors and images.

Cause
Autodesk has changed the reflection mapping scheme, so that it is now controlled within each color scheme. Car3.bmp has been replaced by ParkingLot.dds or GroveCube.dds.

Suggested solution

  • Close Inventor 2008. See below for 2009 specific information.
  • Open REGEDIT form the Windows Command prompt, or from Start - Run
  • Back up your entire Windows registry.
  • Go to the HKEY_CURRENT_USER section, then browse to Software > Autodesk > Inventor > Registry Version 12.0 > System >Preferences > Color Schemes > Schemes.
  • Under Schemes, you will see a series of folders that are numbered. The numbers relate to named color schemes; for example, 7 is the Presentation color scheme, 5 is the Millennium color scheme. If you are unsure about which color scheme is the one that you want to change, then install and load the Inventor Color Scheme Editor and set the editor to the version of Inventor that you are planning on editing. Please note that you cannot edit the reflection bitmap from inside the Inventor Color Scheme Editor.
  • You will be selecting and editing the registry entry called: EnvironmentCubeTexturePath
  • Right mouse click on the name; EnvironmentCubeTexturePath and select modify. Replace the value - ParkingLot.dds with the value - Car3.bmp, or the name of any desired image. This image must also be stored inProgram Files/Autodesk//Inventor2008/Textures subdirectory.
  • Repeat this operation for each color scheme that you wish to edit.
  • When you're editing is complete, close REGEDIT. Restart inventor 2008 to update the changes.
  • In Inventor 2009, Go to Tools >> Application Options >> Color, to select and change the Reflection Environment.

Caution
Applying this fix will require editing the registry in Windows. Be absolutely sure to make a complete backup of your Windows registry before even attempting an edit.If you are not absolutely proficient in editing a Windows registry file, then do not attempt this fix.The author and Tekni Consulting LLC claim no responsibility for errors or omissions caused by editing a registry file.

                              

Tekni Consulting LLC