Revit 2019 is slow in perspective view when panning

[guillermo4JEUL]

Hello everyone, what could be the reason that the pan is so slow and sometime does not even move the view in perspective mode, It gets practically unusable.

Is there something I can do about it? 

This happens to me with any project regardless if is big or small and we have high end computers with pretty good specs.

Thanks, I hope there is a solution for this!

[Anonymous]

I am finding that my machine doesn't seem slow, it's just that the increment of panning is so small as to be unusable. If I center button click and pan, moving the mouse across my desk, the amount that the point of view moves is negligible. To be clear: the panning is smooth, but it doesn't move very far. I can't effectively use panning, and resort to orbiting and zooming in and out. This is in any display mode (consistent color, hidden line, etc.)

[Anonymous]

This is still an issue with the latest release. Panning is virtually useless in perspective. The "unit" of panning is so minuscule that my mouse crosses the screen, barely budging the model.

[hve-architecten]

A bit overdue but your cpu is really not very fast at all:

The passmark single thread rating is 1397 and for instance the rating of an intel i7 8700k is 2703.

That exactly twice as fast as the xeon.

Another thing to consider: when rotating, panning, zooming etc the CPU is working together with the GPU.

So with a faster CPU the GPU will work better.

There is a nice benchmark for revit: rfo benchmarking:

https://www.revitforum.org/hardware-infrastructure/35955-rfo-benchmark-v3-x.html

Its a program which runs revit standalone and reports some numbers which show your pc-system's speed.

Bottom line is, revit runs best with the fastest intel chip you can find. Ipc (instructions per clockcycle) is king.

As far as panning is concerned: its slow in revit anyway.

If you want to optimise your pc's for revit, then run the RFO benchmarking tool and compare that with other results.

You will see that intel cpu's with the highest turbo clocks will give you very good results!

[guillermo4JEUL]

Hi.

Yes I realize about this some time ago, I know the computer I'm using is not the newest and stronger. As I said before, all other heavy software moves beautifully in this computer (Including others BIM software and heavy 3D software), but Revit in perspective.

I don't see why Revit is so resource consuming. Autodesk gives you a price per year per Revit License, but at the end Revit is one of the most expensive software, cause you need to change computers and/or expensive pieces every year too. 

Of course the better and faster the computer, the better the program will work, that happens with any computer software. 

 By looking how other software works in this computer, I really believe Revit has a lot of space for graphic optimization.  Anyways while that happens (if happens) I don't have other option than updating the computer more often. 

Thanks for the Benchmark, I will use it to buy smarter and have Revit optimized computers.

[Anonymous]

I know a lot of people that are turning to BIMBox...a gaming like workstation without the fancy lights but still liquid cooled for the graphics and processor.  These have been getting some insane results with Revitforum's Benchmark utility.

[hve-architecten]

You are right, revit needs a lot of optimization, especially in the graphics departement (panning, zooming, rotating, realistic views, etc).

[hve-architecten]

Bimbox looks nice, until you see the prices!

I can make the same systems for 1/4 the price! (components in a cheap case that is)

[jeremy_evard]

Hi,

Did anyone resolve this 3D panning issue?  It is not a video card/hardware issue or model size issue.  I can get uncropped perspective views to orbit very smoothly/quickly.  When i drag the scrollbar at the bottom, it will pan very smoothly/quickly (so I know it's not a hardware issue).  When I hold the scroll wheel button down to pan and move my mouse all the way across the screen, it only pans the model about an inch relative to the monitor.  seems like a software bug.  We're experiencing the same issue on multiple computers (with different hardware), different revit files, revit 2019 (full and lt).

[taituai · Accepted solution]

This is not a solution. The link to the slow zoom and panning is merely explaining the issues and then offering unrealistic solutions to the problem.

Potential causes (excuses!!!)

1. Graphic Cards not up to date or certified (N/A)
2. Number of reflective objects in the view (N/A)
3. Lights not grouped - all lights on (N/A)
4. Machine doesn't meet the minimum requirements (Mine definitely meets requirements)
5. Project Browser or Properties Pallete undocked from the main Revit Window (This was a beneficial feature added in a previous version of revit to give you more screen space)
6. Project is to big to be handled by the memory (N/A)
7. Multiple Monitors (I don't know anyone in the architectural industry that works on a single monitor)
8. Large Monitor set to a high resolution (N/A)
9. Software updates not installed (N/A)
10. A large number of detailed items are visible in the view. (N/A)
11. Large amount of Revit Links - can be copied around (N/A)

Solution:

1. Install a certified graphic card and driver (N/A)
2. n/a
3. Group the lights by room and only leave on the group in the view you are working on. (N/A)
4. Make sure the machine meets minimum requirements (N/A)
5. Dock Project Browser and Properties Dialog. (impractical) 
6. Make sure the project is at least 20 times smaller than the memory (impractical) 
7. Disable second monitor (ridiculously impractical)
8. Set the resolution of the monitor to 100%DPI (reduces graphical outcome)
9. Install all the latest updates (N/A)
10. Try hiding elements in the view (especially if there are large numbers or complex geometry), and confirm that the performance is improved. (Shouldn't need to do this)

How about actually fixing the issue which is obviously a bug of the new perspective feature.

[guillermo4JEUL]

Great! Thank you for this comment, at the end all comes down to this.

"How about actually fixing the issue which is obviously a bug of the new perspective feature."

[Anonymous]

The only solution is to use the slider bar when viewing a very detailed view. <shrug>

[dplumb_BWBR]

Came here looking for an answer to the same problem.

This issue isn't about graphics performance, it's about the distance the model moves.

It doesn't matter if you're in Wireframe, Hidden, or even Realistic. It's not slow, it just doesn't move very far.

In a 2D View, the model pretty much follows along with your mouse.

In 3D, the model pans about 2% of the screen while your mouse moves all the way across the window.

[zacharymoore]

I'll chime in a bit, since Autodesk's response to look at those articles is completely misleading, and avoids the issue.

I've noticed, over time, that the perspective 3D mode gets harder and harder to navigate, and the zoom extents sends you further and further out into space, until the view becomes useless for anything. You'll notice when, in the view properties, the "Eye Elevation" and "Target Elevation" start becoming huge values, such as 3839230' 3 21/32". My solution was to right click on the view cube, and orient to a view (of your choice. I chose a floor plan.) This seems to have reduced the issue drastically, and in a way, "reset" my 3D view. After doing so, my view elevations become values around 50' - 300' which is much more manageable.

Hope this helps the thousands of people that are apparently frustrated by this new feature that has so much potential but just can't seem to hold onto the ball.

[ldefelice]

These "solutions" are not addressing the problem. All they do is show your lack of understanding of the issue. Have you tried using a perspective 3D view in Revit before?

[guillermo4JEUL]

I don't think so, otherwise we wouldn't even need to complain about this.

[rodrigo_acker · Accepted solution]

As I was facing the same issue, I was not surprised with the responses in this forum. It is a typical Autodesk behaviour to blame everything except the software itself. The problem exposed here is clearly not about the graphics performance (framerate) of the viewport, but is that the PAN tool is anchoring somewere unreasonable (maybe too close from the camera) when in perspective. Sometimes I have the feeling that the support team doesn't use the software at all.

In my troubleshooting I have found this issue occurs when the crop region in the perspective view is too small (even if deactivated). The smaller the crop region, the slower the PAN.

My suggested workaround is to enable the "Crop View" and "Crop region visible" checkboxes in the Perspective Vew, and manually make the Crop Region larger from there (how much is a trial and error effort). When cheking the boxes off again, I found the PAN was working way better. (not perfect as it still anchors somewere utside than the geometry underneath the mouse, but acceptable).

I had a specific case where the pan was so slow that nothing moved. When enabling the crop view and crop region visible, my screen went blank as the crop region was too small. In this case I changed the projection type to Ortographic, resized the crop view form there, changed back to Perspective and disable the crop view checkboxes and it was working nicely.

Hope this helps.

[Anonymous]

Thank you, rodrigo.acker. Finally someone with a solution here.

[guillermo4JEUL]

Thanks! That helps.

"Sometimes I have the feeling that the support team doesn't use the software at all."

I feel that almost everyday, it's like if the developers doesn't use the software and either understand the needs of an Architect or Architectural drawing.

[Anonymous]

This solution worked! Thank you!!

[seanUFNGF]

I have experienced this issue for quite a while now, and if there was no other way to get the view how I needed it, I just dealt with having to pan the view in the miniscule increments Revit was providing. SO ridiculously frustrating! It feels like that dream you have where you're trying to run, putting out crazy amounts of exertion, but you're hardly getting anywhere.

So thank you, rodrigo!!! Expanding the crop region when in Perspective projection mode addressed the issue. Now when I'm in Perspective mode, I just expand the crop region to the farthest extent I can inside the viewport and the increment by which Revit is able to pan the view is increased to allow for panning that's actually useful and efficient.

I don't know what it indicates other than that there IS a difference, but I've noticed that the crop region responds differently whether you're in Perspective or Orthographic mode. In Ortho, the crop region actually zooms in and out when you zoom the view. In Perspective, while the model zooms in and out, the crop region stays stationary, not zooming in and out like it does zooming in Ortho mode. So obviously how Revit treats the view is different depending on which mode you're in.

So like several others have already said, this has everything to do with how the software works and NOTHING to do with the user's computer hardware. Here's a suggestion for Autodesk... how about disconnecting how a Perspective view pans from the crop region altogether? Yes, having a crop region sizeable is useful for controlling what you see in a Perspective view for presentation purposes, but having its size control how the view pans is not useful at all. If I need to pan the view only an infinitesimal amount, I'll do that with the mouse myself. I don't need the software to provide (force on me) that functionality. When in the act of panning... and the software knows when I am, because when I press my mouse scroll wheel and slide my mouse it knows to move the view in a panning type of way... tell the software to momentarily treat the view as if the crop region is all the way extended to the farthest extent. And when I let up on the scroll wheel, go back to "crop region as usual" mode. If I can get the panning to work the way I want by manually going in and expanding the crop region myself, why not just always treat panning a Perspective mode that way without my having to do those extra steps? The software already knows how to do it the "right" way, so... just do it that way. Plus if I have the crop region set just the way I want because it frames the view the way I want for presentation, I don't want to have to change it just so I can pan the view, and then have to change it back again to the way I had it. I can't think of any situation where having the view pan like a snail is useful. So just get rid of that behavior.