Live Viewer unrequested refreshes

[sdanaher]

i׳ll also send you big scene to test today. Pretty heavy but also organised.

Nice one Yambo. Mine is not really that heavy at all for a print job. 855MB vram

[sdanaher]

Some info for you:

(Automatic = off)
I resend the scene.
Info bar reports export time as ~300ms.
The Refresh button remains grey and there is no indication that the job is going to start rendering. No spinning beachball though.
It finally takes 1m 10s before it starts rendering.
It refreshes once for no reason as I mouse over the interface, and again because I select an item in the Object list.

-

I click resend again.
Button is grey, Spinning beachball.
Scene starts rendering in about 3 seconds this time
It refreshes again for no reason

-

(automatic=on)
Same behaviour as above

-

I click Stop & Reset Render Data, and I get spinning beachball for 10 sec
I click Resend and I get spinning beach ball for 1m 13s, (has it hung who knows?) then it renders
I'm writing this in Safari and I can see LV refreshing randomly in the BG...

The behaviour is incredibly unpredictable. Makes difficult to troubleshoot or work out its behaviour.

Note that while waiting over a minute for the LV to start rendering I can click the Resend button (grey) and it turns green even though it hasn't started rendering.

[aoktar]

Some info for you:

(Automatic = off)
I resend the scene.
Info bar reports export time as ~300ms.
The Refresh button remains grey and there is no indication that the job is going to start rendering. No spinning beachball though.
It finally takes 1m 10s before it starts rendering.
It refreshes once for no reason as I mouse over the interface, and again because I select an item in the Object list.

Appearently windows version is working much faster. Takes 20sec on your scene with a i7-4820K cpu. Macosx has some problems with opengl also. Are you with gtx980?
Also there is some options to check. "Syncronization on geo. updates". Things can be a bit better. This refresh issue not appear on windows version when you switch from other software.

[sdanaher]

Thanks for the investigation.

I'm using two Titan X's in a Mac Pro 5.1 12-core w 48GB RAM, OSX 10.10.5. Cinema R17.

Just had a look at my settings... sync on geo updates is already on.

Note that the refresh issue is not just when you switch apps, its lots of things when in Cinema, not things that should affect the render. Are you trying the scene on a mac?

[aoktar]

Thanks for the investigation.

I'm using two Titan X's in a Mac Pro 5.1 12-core w 48GB RAM, OSX 10.10.5. Cinema R17.

Just had a look at my settings... sync on geo updates is already on.

Note that the refresh issue is not just when you switch apps, its lots of things when in Cinema, not things that should affect the render. Are you trying the scene on a mac?

Yes i'm trying on a Hackintosh. I see this "spinning ball" thing. Weirdly we don't have this "ball" in Windows version. Also works much faster and better. Do you have a PC to check it? I'll try to narrow down the issue on Mac.

[sdanaher]

No, I don't have a PC (apart from in Fusion). I'm in production at the moment so haven't got a lot of time to test things.

[sdanaher]

BTW, what is causing the slow refresh in Windows (95s-20s=75s, still very slow). The scene really isn't that complex.

[aoktar]

BTW, what is causing the slow refresh in Windows (95s-20s=75s, still very slow). The scene really isn't that complex.

I'm not sure. Plugin spend most time in geometry compilation for GPU. This is not handling by plugin. Ex. see export info in image. export materials+collect obj+mesh creation is about 2sec. Update 1 sec. Rest is handling by geometry compilation and we don't have any control or feedback in this phase. But your times are very long against PC version. I'll investigate and discuss this more. Maybe a compilation problem for Mac version. Also i'll test it with old versions.

[sdanaher]

OK, I hope you find the problem.

PM'd

[aoktar]

While i'm working wished to notify somethings. Always check "Links" number while using "Auto" for geometries. Big numbers can cause slowdowns. Also i see you are using normal instances. Each instance will increase this number. Better to use "render instances" as much as possible.