QT layout for vfb

[vmodo]

It is MODO901_sp1 on MacOSX 10.10.4 |V-Ray version: vray_beta_30007_modo_mavericks_x64_SOFTWARE_LIC build 2015-07-23

Clicking the arrow-button causes always the crash with or without characters in the "Auto save file" box.
This crash opens the foundry crash-report window though - Usually when a crash happen the activity monitor show: MODO (not responding)

[vladimir.nedev]

Confirming 2015-07-25 nightly has fixed the crash for me. What was the workaround?

Thanks Vladimir

I created all Qt widgets for the VFB window in my "start" command. This change is entirely in the C++ code.
Before, I was creating them the first time MODO initialized one of my custom VFB views.
Still don't know what was the actual reason, unfortunately.

Greetings,
Vladimir Nedev

[vladimir.nedev]

It is MODO901_sp1 on MacOSX 10.10.4 |V-Ray version: vray_beta_30007_modo_mavericks_x64_SOFTWARE_LIC build 2015-07-23

Clicking the arrow-button causes always the crash with or without characters in the "Auto save file" box.
This crash opens the foundry crash-report window though - Usually when a crash happen the activity monitor show: MODO (not responding)

For me MODO 901 SP1 doesn't crash if I have some text in the box, strange.
I am pretty sure this is a MODO bug, as these value cookies are managed entirely by MODO.
I can't find a MODO string channel that has the "arrow" next to it, to confirm that it is definitely a MODO bug.
My guess is, since no MODO string channels have these arrows, this particular part of their code hasn't been actually tested.

Only thing I could do is disable the arrows on Mac OS X for all string channels (like "Auto save file").

Greetings,
Vladimir Nedev

[vladimir.nedev]

For tomorrow's nightly build (the one from 2015-07-26), I have made some changes to the "Render V-Ray" layout:

- redid the layout from scratch, instead of creating it as a copy of MODO's "Render" layout to hopefully avoid strange MODO behavior
- made sure all "key", "hash" and "cookie" values in the resulting .cfg file are unique (by prefixing them with renderVRayLayout_)
- added the V-Ray Toolbox as a tab next to "Properties" and "Groups" (like janko22 suggested in the other thread)
- removed the "Render" and "Render window" buttons for MODO rendering (again like suggested)
- removed the "Gradient editor" tab as MODO refuses to import it (maybe because it is a viewport group within a tab)
- the Render Preset Browser now tracks the Preferences of the "Render Preset Browser" from the normal "Render" layout, so they always show the same directory

Greetings,
Vladimir Nedev

[BVA]

I found a way to work-around the crash when switching from the "Model" to the "Render V-Ray" layout. You no longer have to remove the 'Timeline".
The fix will be in the nightly build from 2015-07-25.
It will be very helpful, if everyone who had this issue tests that build, so any other issues can be found.

Greetings,
Vladimir Nedev

Thanks Vladimir, this build is stable for me 

[BVA]

[QUOTE=vladimir.nedev;660369]For tomorrow's nightly build (the one from 2015-07-26), I have made some changes to the "Render V-Ray" layout:

Hi Vladimir, I like the changes to the layout. One thing that is not a deal breaker but a bit odd to me is to have the render button on the VFB and the RT button on the toolbar. Is it possible to have both on the VFB? Not sure how other people feel about this?

[vladimir.nedev]

For tomorrow's nightly build (the one from 2015-07-26), I have made some changes to the "Render V-Ray" layout:

Hi Vladimir, I like the changes to the layout. One thing that is not a deal breaker but a bit odd to me is to have the render button on the VFB and the RT button on the toolbar. Is it possible to have both on the VFB? Not sure how other people feel about this?

Yes, it make sense to have the RT start/stop buttons in the VFB as well. Maybe even the pause updates button.
Maybe we will add them at some point later on. The VFB code is shared with our other plug-ins, so this change won't be as easy as it looks.

Greetings,
Vladimir Nedev

[jonmoore]

Yes, it make sense to have the RT start/stop buttons in the VFB as well. Maybe even the pause updates button.
Maybe we will add them at some point later on. The VFB code is shared with our other plug-ins, so this change won't be as easy as it looks.

Greetings,
Vladimir Nedev

I was going to make much the same comment as BVA so good to hear that you plan than adapt the button placement in a future SP.

[BVA]

The render progress bar is really nice showing the time completed, thanks for that!!!!

Currently it stays on top, even if I work in another program while modo render in the background. is it possible to change this behaviour?

[cyroz]

The render progress bar is really nice showing the time completed, thanks for that!!!!

Currently it stays on top, even if I work in another program while modo render in the background. is it possible to change this behaviour?

Same here, would be great if possible, as it's a bit annoying cause I usualy keep working in other apps while rendering

[vladimir.nedev]

The render progress bar is really nice showing the time completed, thanks for that!!!!

Currently it stays on top, even if I work in another program while modo render in the background. is it possible to change this behaviour?

I thought I might pass this as a feature, but it is actually annoying to me as well.
The reason I did it like that is because otherwise the progress bar might get hidden behind a secondary MODO window (like the VFB when it is in a separate window).
What you can do as a workaround at the moment is to minimize the whole MODO application (by left-mouse clicking on its icon in the Windows taskbar).
I will see if I can fix this in a better way, and write back here.

Greetings,
Vladimir Nedev

[vladimir.nedev]

The render progress bar is really nice showing the time completed, thanks for that!!!!

Currently it stays on top, even if I work in another program while modo render in the background. is it possible to change this behaviour?

For the next nightly build (the one from 2015-07-29), I think I managed to fix this in a better way, unfortunately only on Windows.
The progress bar will automatically raise itself above other MODO windows, and will no longer stay on top of all OS windows (on both Windows and Mac).
This automatic raising doesn't work on Mac OS X, so there you might lose the progress bar behind a secondary MODO window (like a palette or the Preferences or VFB window, for example).

Greetings,
Vladimir Nedev

[BVA]

wow, that was quick...thanks Vladimir