Development

Testing quick reply.....


edit
working OK here.

Clear a cache, cookies.
Now all is work

But..It is problem start after a some time. May be due to the fact what I checked checkbox "Always stay logged".

I set up on a:-
AMD64 3800+ (2.39)

Where did you get such a rarity?

I purchased it new many years ago. It was one of the top AMD CPU back then 
(I have 2 other AMD64 chips)

When switching between view rotate(alt+LMB) and Zoom(alt+RMB) I was seeing a delay of about 0.5 to 1 second before view would rotate or zoom. But once view was rotating or zooming there was no lag. Are you seeing similar?

exactly! =)

It looks like a bug.
I will send in a bug report and see what IStonia can find.

It looks like a bug.
I will send in a bug report and see what IStonia can find.

such an bug is not noticeable on the your modern computer?

p.s. I am hate multi quotes here I saw a addon for selective quotes (for SMF forum), but it's old.

such an bug is not noticeable on the your modern computer?

If high number of polygons, yes.

I do not think there should be a lag in navigation just because an object is selected, not when there is no lag when no object selected. In such a situation, you are still only view-navigating the same number of polygons, so should be no difference.

i.e. Have you a two bugs?
1. Lags between rotate and zoom.
2. difference of speed between selected object and not selected.

p.s. Thanks steve for discussion and help I go to sleep

Hi Molebox,

IStonia did get back to me. The delay is due to geometry position update for screen. So the slower the CPU the longer it takes. He did not say why the difference between selected and non-selected. I did ask again, but no reply to that as of yet.
Maybe he will answer in thread himself?

Hi Molebox,

IStonia did get back to me. The delay is due to geometry position update for screen. So the slower the CPU the longer it takes. He did not say why the difference between selected and non-selected. I did ask again, but no reply to that as of yet.
Maybe he will answer in thread himself?

Could it be related to wireframe, I only see this problem when wireframe on shaded is turned off, so when something is selected it it is rendering more than non.

I am not sure what Nvil is doing.
With a new empty scene, just moving the mouse cursor around in main viewport Nvil is using CPU (approx)40% and GPU (approx)30%. I have a quad core (i5 3570K), with Nvil setting to use only one CPU core, yet it is using almost 2 CPU cores and GPU 30% just to track mouse cursor, that is excessive.