Author Topic: Laggy; normal behavior?  (Read 1469 times)

2018-11-19, 16:45:32

aaouviz

  • Active Users
  • **
  • Posts: 1002
    • View Profile
    • Another Angle 3D
So when rendering (basically any mildly heavy scene and upwards) my Corona VFB and Max windows get very very laggy.

Most of my other windows, inc. Photoshop, chrome, spotify, etc don't really experience any issues. But if I try to minimize the VFB or zoom inside it, or do some sort of action in it while rendering, it will almost certainly completely lock up and take approx 1 minute to perform the action. It's not necessarily a very big problem, as there isn't much I can be doing during rendering anyway, but it is a bit frustrating to not view the rendering realtime.

I'm just wondering if this is normal behavior? I've got a fairly powerful PC and wouldn't expect to experience such bad lag. My RAM almost never exceeds 32gb (of 64gb physical). Right now my 12 core xeon 2.0Ghz is maxed out at 100% usage, but my RAM is steady on 20.3 gb. But - like I said - zooming in or minimising the VFB is very very laggy.

As far as I can tell, this has always happened, from when I join Corona at Version 1.7 right up until the current RC5.

Is this just what happens? Or am I due to for a hardware upgrade?

Any pointers helpful :) Cheers,
Nicolas Pratt
Another Angle 3D
https://www.instagram.com/anotherangle3d/

2018-11-20, 09:15:30
Reply #1

sprayer

  • Active Users
  • **
  • Posts: 803
    • View Profile
Some Xeon engineering samples may be laggy, i heard from some people. What CPU model you have?

2018-11-20, 10:55:11
Reply #2

aaouviz

  • Active Users
  • **
  • Posts: 1002
    • View Profile
    • Another Angle 3D
Thanks for the reply.

My master PC (the one lagging) has a single Intel Xeon E5 2658 V3 ES 2.0Ghz 30MB 12 Core 22nm 105W LGA2011-3 CPU

I guess I should test out my slave which has 2X 'Intel Xeon E5-2620 v3 2.4ghz'... Don't know why I never thought of this...
Nicolas Pratt
Another Angle 3D
https://www.instagram.com/anotherangle3d/

2019-01-28, 17:15:21
Reply #3

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 13722
  • Marcin
    • View Profile
If this is happening with some textures loaded from a network location, then disabling Corona Bitmap updates may help (available only in V4 daily builds - https://coronarenderer.freshdesk.com/support/solutions/articles/5000570015):
1. Enable the development/experimental stuff rollout - https://coronarenderer.freshdesk.com/support/solutions/articles/12000021288
2. Go to Performance > Development/experimental stuff
3. Find and uncheck "Enable CoronaBitmap auto update"
You may need to restart 3ds Max and reload your scene to make it work.
Marcin Miodek | chaos-corona.com
3D Support Team Lead - Corona | contact us