[wateraction]

Hi, everyone, here is my problem.

In Gambit GUI, when I use left mouse button to rotate the geometry, there will be about 5 seconds delay to display the geometry in the new position, that is, I could do nothing but wait during the 5 seconds.
However, it's OK when I use right mouse button to room-in or room-out the geometry, and it's also OK when I use middle mouse button to drag the geometry to a new position.

Plus, I did it on a server with linux platform. The server has a independent nvidia video card(driver successfully installed).
My geometry is a little bit complicated, but the .dbs file is not very big as I think, only about 5MB.

Anyone meets the same problem? Thanks for your attention!

[-mAx-]

is shaded mode turned on?

[wateraction]

Originally Posted by -mAx-

is shaded mode turned on?

Hi mAx, shaded mode is not turned on, because I wanner see inside the model.
I think I've already found the reason. In my model, there is a certain part containing a lot of circular pipes, which seems complicated in some extent. Each time I turned off the visible option for all the faces in this part, the display delay problem would disappear, while then I couldn't see clearly the pipes as well, cos the circular pipe is not like geometry in other shapes which can be seen from there wireframe (or by edges).
Moreover, my server supplier did a test for me. First they changed the video card for another better one, I would say the best they have. While the display delay problem still exists. After that, they use some monitor software to see how the cpu would behave when they were doing the rotate operation in gambit. The result shew that when they rotate the model, the cpu resources been occupied would rise sharply.
I think the result indicates that the bottle neck is not the video card, but the CPU.
However, today I cannot ask for a much better CPU, cos the CPU in use is already 2.1GHz, there is limited space for update.
In another aspect, the gambit software cannot run in parallel mode, unlike fluent. Therefore the problem wouldn't appear in Fluent, if I turn on the "doulbe buffering" option.
If I draw a conclusion, that would be another software is needed to help doing the geometry build-up step, then transfer to gambit, where meshing could be done. And if you are doing the meshing step, just bear the uncomfortable feeling of display delay.
A little pessimistic, haha.

Anyway, thank you for your time, mAx.