zwischendrin.com blog
31Oct/101

quick bugfix for SnowPrint

For all those that have a little problem using SnowPrint the first time:
If you get an error that says that something is wrong with map channel 0, just click the "map channel" spinner once and set it back to 1. There seems to be something wrong with the starting value of that map channel. Sorry for that!

14Oct/100

About the ribbon/”error parsing xaml file” bug

I think I should look much more often for updates, hotfixes and service packs of my 3D Studio Max... Smile
Even after following my own suggestions about fighting the ribbon bug (read this post) I got the same error again after a long time of silence...
After applying the fix again ("read only" protection had gone?!?) I searched the autodesk website for an 3D Studio Max update and - lo and behold - there seems to be a service pack for that software!

The readme says: "Ribbon -> Customization of Ribbon features are now working as expected."
My problem should be history, I hope!

You can find the SP1 here: Autodesk 3ds Max Design Services & Support

26Aug/101

Bugfixing 3D Studio Max Design 2011

#1

Maybe you also got this error before: when starting 3D Studio Max you get an error warning that says "error parsing xaml file: root element missing" or another error message that says something with the new ribbon user interface is wrong. The solution is relatively simple:
go to [USERNAME]\AppData\Local\Autodesk\3dsMaxDesign\2011 - 64bit\enu\UI
(change the username to you username and remove the brackets, 3dsMaxDesign should be changed to 3dsMax if you have the regular version)
and search for a file called "MaxManaged.xaml.backup". Replace the file "MaxManaged.xaml" (which is zero bytes in size) with this file and 3D Studio Max runs as it should! I got this error several times until I checked "read-only" in its file settings. Those problems are now gone!

#2

My 3dsMax ALWAYS showed me an error when closing it. This was very annoying! Razz
All settings did not save and it was just... unnecessary?
This solution also was very easy! (btw. I never thought of this causing an error like that)
uninstall your graphic card's drivers and install new ones! This fixed it.