Author Topic: VFB Slowdown  (Read 4474 times)

2023-07-12, 16:27:40
Reply #15

dj_buckley

  • Active Users
  • **
  • Posts: 875
    • View Profile
Problem persists with the latest drivers.  If anything, it's worse

2023-07-24, 11:38:04
Reply #16

rowmanns

  • Corona Team
  • Active Users
  • ****
  • Posts: 1892
  • Corona for 3ds Max QA Team
    • View Profile
Hi,

That is strange, we tried this in our office with a range of systems and GPUs (including 1050ti and 650ti) and we cannot reproduce this at all.

I will ask someone from our support team to get back in contact with you and see how we can investigate this further.

Thanks,

Rowan
Please read this before reporting bugs: How to report issues to us!
Send me your scene!

2023-07-24, 11:40:23
Reply #17

dj_buckley

  • Active Users
  • **
  • Posts: 875
    • View Profile
Just to give an update I think it could be an issue with my right-click menus in general, not strictly limited to Corona VFB.

I'm now having issues with simple right click commands in explorer.  The VFB is still slightly unresponsive and laggy with left click operations.

For example, if I try to expand one of the rollouts, it doesn't actually expand until I physically move my mouse again.

2023-07-24, 13:16:38
Reply #18

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 12768
  • Marcin
    • View Profile
Hi, sorry, but we could not reproduce anything like that, and we are not getting any similar reports from other users. Of course this is not 100% certain, but it suggests there may be some problem with your hardware. For example: outdated BIOS/chipset driver, missing Windows Updates, some hardware malfunction. Also, unless I am mistaken, you have Unreal open in your taskbar. Are you performing some CPU- or GPU-heavy tasks with it? Maybe you are just doing too many things at a time? (again, no offense please if I am wrong, this is just a guess)
Marcin Miodek | chaos-corona.com
3D Support Team Lead - Corona | contact us

2023-07-26, 16:21:51
Reply #19

dj_buckley

  • Active Users
  • **
  • Posts: 875
    • View Profile
Found the problem.

maxstart.max

I removed my custom maxstart.max file and low and behold the VFB is super quick as I'd expect

If i put the maxstart.max file back again, the problem returns.

I'm going to try making a fresh maxstart file

2023-07-26, 16:38:16
Reply #20

Aram Avetisyan

  • Corona Team
  • Active Users
  • ****
  • Posts: 561
    • View Profile
Found the problem.

maxstart.max

I removed my custom maxstart.max file and low and behold the VFB is super quick as I'd expect

If i put the maxstart.max file back again, the problem returns.

I'm going to try making a fresh maxstart file

Can you please share the maxstart file so we can have a look?
Aram Avetisyan | chaos-corona.com
Chaos Corona Support Representative | contact us

2023-07-26, 16:38:56
Reply #21

dj_buckley

  • Active Users
  • **
  • Posts: 875
    • View Profile
Sure

2023-07-26, 16:54:27
Reply #22

dj_buckley

  • Active Users
  • **
  • Posts: 875
    • View Profile
Trying to narrow it down further.

I've rebuilt the maxstart file and I tested the VFB after changing each individual setting.  The slowdown appears when I add a Curves operator to the stack.

I managed to rebuild the file and everything ran smoothly, as the last thing I did was add curves, it messed up.  So I tried again, this time the first thing I did was add curves, and it messed up straight away.  Without the curves operator in runs as expected.

I've not tested other operators, but the default stack on a clean install on first open works fine.  Will test other operators now.

2023-07-26, 17:09:55
Reply #23

dj_buckley

  • Active Users
  • **
  • Posts: 875
    • View Profile
To further add to this, all other operators are fine providing 'Curves' isn't in your stack.

If you add Curves this is when you get the slowdown.

All of this is being done directly in the VFB.

If you add the Curves from the 'Edit Tone Mapping' feature in the render settings, it operates smoothly UNLESS you have the frame buffer open.

It should be simple to test.

Open clean scene.

Open Render Settings

Open Edit Tone Mapping

Add Curves operator

Delete Curves operator

Add Curves operator back in

Everything seems nice and smooth so far

Open the VFB

Try and delete Curves from the Edit Tone Mapping window

This is where mine slows down and I get major right-click lag.

Close VFB

Try and delete Curves from the Edit Tone Mapping window now.  Nice and smooth again?  But if you reopen the VFB you'll find it's stuck in the laggy version despite the fact you've now deleted the Curves operator.

So it looks like either Curves is corrupting the VFB, or having the VFB open in conjunction with the Curves operator is causing a slowdown/corruption somewhere.  Or both.

2023-07-26, 18:10:26
Reply #24

TomG

  • Administrator
  • Active Users
  • *****
  • Posts: 5468
    • View Profile
I tried the steps above and I notice that at
"
Open the VFB

Try and delete Curves from the Edit Tone Mapping window

This is where mine slows down and I get major right-click lag.
"

the right click was instant and not laggy, but choosing delete took about 2 or 3 seconds for Curves to disappear - before that point, the "+, Reset, Presets" disappeared and Curves still seemed to be there, until finally things redrew and Curves vanished and the buttons came back. Once that has happened, the same thing happens whenever deleting the bottom operator in the stack (and does not happen if I restart Max and delete the bottom operator in the stack without adding Curves; also does not happen if I add other operators rather than Curves to the bottom of the stack and then delete those).

Is this what you are experiencing?

Video attached, showing first deleting before curves working smooththly, then addition and deletion of Filmic working smoothly, then Curves after which things get a bit strange :)


EDIT - just to confirm, once Curves is added, deleting ANY operator in the stack (not just Curves, and not just the bottom one) causes this redraw lag for the delete to take effect in a redraw.

Also, I notice that once Curves is added, when you click and drag to reposition an item in the stack, the blue line no longer shows up to show where the item will be dropped (but it still drops just fine with no lag).
« Last Edit: 2023-07-26, 18:14:50 by TomG »
Tom Grimes | chaos-corona.com
Product Manager | contact us

2023-07-26, 18:15:56
Reply #25

dj_buckley

  • Active Users
  • **
  • Posts: 875
    • View Profile
Basically yes, as soon as you add curves, everything else starts messing up from that point onwards.  It's very temperemental

2023-07-27, 11:08:50
Reply #26

Aram Avetisyan

  • Corona Team
  • Active Users
  • ****
  • Posts: 561
    • View Profile
Just to narrow it down to exact problem:

So the issue is not related to maxstart file. VFB is lagging for you when ever you have:
• VFB open
• There is Curves operator in it

right?
Aram Avetisyan | chaos-corona.com
Chaos Corona Support Representative | contact us

2023-07-27, 11:10:30
Reply #27

dj_buckley

  • Active Users
  • **
  • Posts: 875
    • View Profile
Yes, it just so happened that I had the Curves operator saved into the maxstart file.

Adding curves operator to the tone mapping stack screws things up in the VFB.  Simple as that

2023-07-27, 11:15:53
Reply #28

Aram Avetisyan

  • Corona Team
  • Active Users
  • ****
  • Posts: 561
    • View Profile
Yes, it just so happened that I had the Curves operator saved into the maxstart file.

Adding curves operator to the tone mapping stack screws things up in the VFB.  Simple as that

The report is made and is being tracked now.

(Internal ID=1168142509)

Can you please confirm if this was not the case and everything was working smoothly for you with Corona 9?
You can try using the multiloaders to test it out.
Aram Avetisyan | chaos-corona.com
Chaos Corona Support Representative | contact us

2023-07-27, 11:26:19
Reply #29

dj_buckley

  • Active Users
  • **
  • Posts: 875
    • View Profile
Corona 9 was absolutely fine