When I render, I always find the preview window pretty annoying. I can't find a way to get rid of it?My preview is often slower than the real render itself. So why the need for the preview?
Hello Flemming.. I and others have the same frustration/question... >7yrs and counting...
Turning off Preview Window?
Jesus, that's a long time waiting. Are we just ignored by SW? This seems like such a small and easy change..
Thanks for your reply Paul..
..yep,.. seems like only yesterday.. yet... we can't help but wonder,... why the hell does this take so freaking long to accomplish?
Is the expectation that if the Preview window is not displayed, then the final render window will immediately pop open and subsequently complete the render job faster?
Hello Ron,.. imho, it doesn't have a reason for being and I'm sure it takes resources.. and we also have to click/close it..
So,.. my question is,.. why was it ever there?... and/or who requested it to stay there?.. or why does this take so long for a request to have this removed from the program.
.. is PV360 development DEAD.. near EOL (end-of-life.... date?).... or is there any budget left to turn things on/off?
Please,.. is there a REGISTRY KEY we can use to turn it OFF?
As I mentioned in the other thread about this (Re: Turning off Preview Window? ) many years ago...hiding/not-showing the preview window won't get you any additional performance/time/memory benefit.
As you may already know, PV360 is really just a stripped down version of Modo being "talked to" by SOLIDWORKS via the Modo SDK. If you wanted to create a final render of your SOLIDWORKS project in Modo, the very first thing you need to do is load the file in Modo. This is the PV360 preview window. This is how your scene, is loaded and prepared for a final render. If it's not first loaded...there is nothing to actually render!!
Think of it this way, if you want to print a Word document...you first have to open the document in Word.
I know it seems like the Final Render window is it's own process...but it's not...it's just a dialog of Modo (or photoview360.exe in our case).
So I asked the above question ("...is the expectation that if the Preview window is not displayed, then the final render window will immediately pop open and subsequently complete the render job faster?") because ultimately that's rather impossible. Merely hiding the preview window will make no difference to the amount of time it takes to render. While the model is loaded and prepared for rendering (ie basically loaded into Modo/PV360.exe) you will see nothing happening for however long that normally takes.
None of this is to say that I don't totally appreciate that the workflow seems/feels odd. And that closing the preview window after the final render seems like a ridiculously unnecessary step. I'm just trying to set the record straight that hiding the preview window, won't make anything faster.
Maybe it's only me.. but I think, it's really super simple,... the USERS, the people paying for the software, think it useless and want it off.
OR,MAYBE........ HIDE IT!?!?!?? (super novel response?)
NEVERMIND... leave it was it is .....OR.. simply tell the users.. IT WILL NEVER BE FIXED!?... (another super novel response?)
Fair enough. I won't disagree with that.
Back to Flemming's original post:
"...My preview is often slower than the real render itself. So why the need for the preview?"
Why? Because that is how a model is loaded into the render engine, so that the Final Render can actually start.
Preview is slower than real render itself? Because loading a massive geometry set is often slower than rendering it. Hiding the preview window will not speed up the process. The overall time from hitting the final render button, to when the final render is complete, will be exactly he same.
When I use Final Render, it always completes before the preview rendering completes. I save a .jpg and close both windows before the preview ever finishes, so it seems that eliminating the preview rendering would significantly reduce the amount of time required. Perhaps I'm missing something.
It's not about the Preview "finishing". The preview never has to "finish" anything before you kick off a final render. And while the final render window is rendering, the preview pauses. It unpauses and continues after the final render is complete. So the preview will never "finish" before the final render. The point is that the model must be loaded first...which is the role of the preview.
For all intents and purposes, the final render button could be IN the preview window...OR the final render button could be disabled, until the model is loaded (and just starts to render) in the preview window (or integrated preview).
Ron, I think I understand what you're saying, but it is undeniable that the preview is taking up processing time, which is completely wasted if the user doesn't want a preview. Additionally, the extra window is in the way, which some users do not appreciate. Furthermore, there is no benefit of a preview if the final render is the goal and it is complete before the preview is rendered. When final render is selected, it makes sense to eliminate the preview window, even if the data has to be loaded.
Makes more sense now. I just couldn't help wonder why it behaved this way..
I think this is a fair explanation, even though it doesn't fix the issue, it does clarify it..
Retrieving data ...