1.3RC1 IR Restarting Bugs

[atelieryork]

Hi folks,

Max 2016 SP1, Nitrous, windows 8.1 pro, 1.3RC1.

I'm just adding here as I come across them but they're all basically related to one thing - IR restarting:

Selecting the camera being rendered causes IR to restart

Clicking on the phys camera underneath a coronacameramod causes IR restart (and visa versa)

Move mouse over any coronamaterial in material editor = popup tooltip = IR restarts
Also seems to apply to some other tooltips elsewhere in UI

Simply click on any other material in the editor and the IR restarts (not every time, only some times)

Close material editor and re-open it - IR restarts.

IR seems to get jammed a lot, with no visual update, but it's rendering away in the background, then dumps an update in one go to the viewport/floating window.

Select a light, IR restarts. Deselect light, IR restarts. No changes happened to the scene.

Keep cursor off 3ds max UI, IR rendering is fine. Move cursor back over the UI anywhere and IR restarts.

Maybe related to the one above - launch IR window, keep cursor over max UI. No update happening to IR. Move cursor off Max UI and bam - IR updates and image appears.

These last two, plus the one about tooltips, are probably the most obvious and problematic issues.

[atelieryork]

Another IR-related one, I have an object, a rug, which doesn't render in IR window when you change the view of the IR, until I hide and unhide the object in max, or move and unmove it, then it renders fine in both that view and all other views that it's visible in.

[Ondra]

I am not experiencing any of the restarts with tooltips/selecting objects. Is there something non-standard about your 3dsmax installation?

[atelieryork]

I am not experiencing any of the restarts with tooltips/selecting objects. Is there something non-standard about your 3dsmax installation?

There is a possibility that I was experiencing the other issue I mentioned where keeping the cursor on the max UI caused the IR to hang, and when you move it off the max UI it starts up and renders fine. I'm not in the office so can't test here unfortunately.

[atelieryork]

I am not experiencing any of the restarts with tooltips/selecting objects. Is there something non-standard about your 3dsmax installation?

There is a possibility that I was experiencing the other issue I mentioned where keeping the cursor on the max UI caused the IR to hang, and when you move it off the max UI it starts up and renders fine. I'm not in the office so can't test here unfortunately.

By the way, nothing non-standard about my max installation, no. Standard 2016 SP1 with dark UI (think that's the default now?), custom workspace but nothing crazy at all.

[atelieryork]

On RC5 here. The tooltips bug seems to have gone somehow, and the disappearing displacement objects, so that's great news.

Using IR in a viewport or floating window, same results, IR restarting:

- IR rendering away fine, select any scene object/light/anything and the IR immediately restarts
- If you have an object selected while IR is running and deslect it, IR restarts
- With IR running, use the select tool to draw an empty selection in a viewport. No objects are selected but the IR still restarts
- while IR is running, if Autosave kicks in, IR restarts (bet this is a max issue..)

These restarts happen both during IR rendering and after it's reached the max passes too. So even once it's hit 50/100/whatever if you do any of the above it still restarts.

It looks like basically any change whatsoever in terms of selection is causing a restart. You can select the object from any viewport, with select tool or with move tool or by selecting from the scene explorer. CPU goes down to 0% usage then right up to 100% again and the IR starts off from scratch.

I mentioned it in another thread as well but could we please have the IR pass limit set to 100/150 instead of 50? I feel like 50 is way too low for region and blow-up rendering and even for full view rendering.

[romullus]

I'm on max2014 sp5, win 7 and i don't experience any of your mentioned problems with IR. Could it be max or even OS specific?

I mentioned it in another thread as well but could we please have the IR pass limit set to 100/150 instead of 50? I feel like 50 is way too low for region and blow-up rendering and even for full view rendering.

You can specify IR pass limit in performance tab, by default it shoul de 0, i.e. unlimited.

[atelieryork]

I'm on max2014 sp5, win 7 and i don't experience any of your mentioned problems with IR. Could it be max or even OS specific?

I mentioned it in another thread as well but could we please have the IR pass limit set to 100/150 instead of 50? I feel like 50 is way too low for region and blow-up rendering and even for full view rendering.

You can specify IR pass limit in performance tab, by default it shoul de 0, i.e. unlimited.

I suspect this is the case too. Win 8.1 Pro with max 2016 sp1 here.

Regarding the passes - I did a clean install of 1.3RC5 and the passes are set to 50 max for IR, but perhaps this is an old value that's been pulled through the scene file and not reset with the installation, so if it's 0 by default then that's great.

[romullus]

You can easily change default yourself. In render settings performance tab enable devel/debug mode, new rollout will appear, in it click on open config dir, an explorer window with Corona's config files will open. Find most recent file named config-xxxxx.conf, open it with notepad, look for line "int interactive.passLimit", if there isn't one add it "int interactive.passLimit = 100". From now on by default IR will be limited at 100 passes.

[atelieryork]

You can easily change default yourself. In render settings performance tab enable devel/debug mode, new rollout will appear, in it click on open config dir, an explorer window with Corona's config files will open. Find most recent file named config-xxxxx.conf, open it with notepad, look for line "int interactive.passLimit", if there isn't one add it "int interactive.passLimit = 100". From now on by default IR will be limited at 100 passes.

Nice, thank you, will give that a try.

[Ondra]

it seems the restarting issues are random, we did no changes that could fix them

[atelieryork]

Another one - turning on show edges (F4) restarts IR.

This is on RC5.