For Revit 2013, you may wonder if there is an easy and fast way to swap the Revit UI from one language to another? There is now a way to make swapping UI langauge easier, refer to this post in the Autodesk Wikihelp for Revit.
Thanks to Harlan Brumm from Revit Clinic for sharing this tip.
You have a license server with a Maya and an Entertainment Creation Suite license and you will notice that the Entertainment Creation Suite licenses for mental ray batch [MMR1] will overide the mental ray batch count even though they are issued on the same date.
In this instance, if you have the following:
1 x Entertainment Creation Suite 5 x Maya
For each Maya license you have, you should have 5 mental ray batch licenses, therefore you should have 30 x mental ray batch [MMR1] licenses.
Using the License Parser, you will see the behaviour of the licenses and the problem will only happen if the licenses are combined.
Maya 2013 license
Entertainment Creation Suite2013
Maya 2013 and Entertainment Creation Suite 2013 combined into 1 license file
The reason for this problem is that the Maya 2013 license with has an all inclusive mental ray batch license [MMR1,MMR2, MMR3, MMR4, MMR6 & 2013-2010].
I know some of you have been asking about Windows 8 support for Civil 3D and the rest of the Infrastructure products. Just released is the current list of support Autodesk products on the new Windows 8 platform. At this time none of the Infrastructure products (Map 3D, Civil 3D, Infrastructure Modeler, etc.) are included in this list. The only one that is supported from the Infrastructure Design Suite at this time is 3DS Max Design.
Unless you like to hack the registry, please don't delete a deployment on your network until you are absolutely not using it. For example, if your site is not using any Autodesk 2011 product, then you can delete all the 2011 deployment packages on the server.
The computer that has the Autodesk software installed will be looking at deployment location for repairing, re-installing and patching of the software.
It is much easier to not delete the deployment than to hack the registry to a valid location of the software.
Even if you have created a new deployment, hacked the registry and you have duplicated the deployment path, another variable to consider is if you have included Service Packs in the original deployment which can then affect a repair & re-install of the product.
NOTE: This can potentially apply to just regular installed/extracted software as well. i.e. C:\Autodesk
love change. When Windows XP came, I embraced the big Start Menu. I didn't change
the theme to look like Windows NT. I used Windows Vista and I started to
love it as well. Trust me, I had some interesting workflows like not
logging out of my account and locking my computer to save precious login boot
time. I think I ran Windows Vista for 2 weeks straight! Windows 7
is perfect as far as I am concerned.
I have not used Windows 8 yet. The best thing to do is just
to read all the reviews and prep yourself of these new changes when you are ready to
upgrade your computer. I would probably wait until the next release of Autodesk products before jumping on the Windows 8 bandwagon.