Autodesk Revit Architecture

[#1]

Revit 2012 and Citrix Xenapp work great. We upgraded to 2013 and now everything as slowed down so much it is basically not useable. Has anyone else delt with this issue? Is it a by product of Revit 2013, are their some graphic issues present in this release currently not in 2012? Anyone else experiencing this issue?

[#2]

Dear jimk


The issue you are describing has been reported to development group and is currently under investigation.


Best regards



John Lipp
Support Specialist
Product Support
Autodesk, Inc.

[#3]

Any new info on this issue?

[#4]

I wish there was. The problem is still a glaring issue with no solution. I am fairly certain there won't be. I am hopeful that 2014 will run better, but we could be faced with the same problem in that release as well. We are looking at trying to accelerate the data with Cisco WAAS as it will work with citrix. Hopefully can get equipment in place in a few weeks and test. 2012 still runs excellent, and we try to keep as many projects in that version as we can.

[#5]

I'm seeing similar problems.  Was there ever an update on it?

[#6]

No I never received a solution for this. I am hoping 2014 is better, I see the did some video stuff in that release. What is so disappointing is 2012 works and runs like a champ.

[#7]

2014 is showing the same behavior as 2013. How could this not be addressed, is there anything we can do? Why say it works on Citrix when you can't hardly run it on Xenapp

[#8]

Attn: Autodesk Urgent!

This is a serious issue that could have major ramifications to the operations of some companies. 2012 had been working fine on XenApp but 2013 was just far too slow. My understanding from the documents I had read from Autodesk, was that Revit was supported for citrix for 2014 but by the sounds of it, that isn't the case. We are about to test it ourselves but this could have a serious impact on our systems and projects.

Having this fixed for 2014 would be great but we will still have a large number of projects in 2013 that would be affected if/when crossed over to XenApp so a fix for 2013 would also be needed.

Please give us some form of indication whether this will be addressed and addressed soon.

Cheers