Does anyone have problem rending models in the new interface? Do you know where the log files are stored in system?
The render window is stuck with the error.
I cancelled the render and opted "No" for not to run the offline render in the background. However, the process is still running in task manager preventing the application to start new render operation.
Select hidden icons right under in your monitor , the icon at the leftside of your Windows logo then you will see that the offline renderer is still running
Rightmouse button and you will see that you can stop renderer
yep, I've seen it as well yesterday.
First of all, we are sorry that you are encountering such an issue. It could be related to available memory while performing an offline render.
regardless, you can find the logs here: C:\ProgramData\SOLIDWORKS\SOLIDWORKS Visualize\Log
Please submit those to support for investigation.
Hi David, I found similar issue as Shahid met before.
When i use Geforce GTX660 3D view and rending function works fine. but after switch to GTX1060 graphic card.
An internal rendering error happend. it happend each time when i try to render only with GPU. seems visualize SP0 can't work well with GTX1060.
can
OS: win7 x64 sp1
SW: visualize 2016 pro sp0
my graphic driver: 372.54
Frank -
I'm sorry to say but GTX1060 is Pascal based (latest gen of chip from Nvidia) which isn't supported by the current shipping version of Visualize. I believe the Visualize team (Brian Hillner) is working to make sure that the 2017 version due alongside SolidWorks 2017 does support Pascal based cards. Best to stick with your GTX660 until Pascal support is introduced.
hmm.. should be available now or extremely soon...?
Nvidia blog Iray 2016.2 SDK already has support for Pascal.
We are waiting for the latest version of Iray (2016.2) from NVIDIA to implement into Visualize. Our goal is to support the new Pascal chip architecture in our Visualize 2017 release, coming this October.
Hey Brian... thanks,.. ok,.. Oct..
I was just scanning/reading on what other iray devs and nvidia have currently estimated (~late Sept).. ..sdk was originally was planned for SIG (end July)... and it was interesting to read was some people at nvidia being surprised it has taken this long (mid Aug).
..what made me laugh,. old MentalRay (Maya) got support before iRay!?
..btw, I loaded/tested the latest GTX drivers and it shows as Cuda 8... so,... isn't Cuda 8 offically pascal supported?... (but, probably not iray)?
Crazy May got support before Iray...wonder if it is truly out for the public to use?
As you know SOLIDWORKS has a concrete release schedule, launching the major yearly versions each October, with 5 Service Packs between major releases. We have to align our implementation of the latest Iray versions with our own SOLIDWORKS product release schedule. If something is available to the public from NVIDIA at XX month, we have to make sure to align that availability with our own planned release schedule. We always try to make sure the waltz we dance stays coordinated.
..not sure,.. looks like much improved MDL support?
..maybe it's a intended waltz delay waiting for the quadro pascal release w/sync?
Thanks, Brian and David：
Found Visualize SP0 can‘t work on win10 x64, always flash then quit after program launch.
Did i missed anything？
Hey guys,
I've been having this exact issue for a while now and I've found a solution.
Try opening your task manager (Ctrl+Shift+Esc) and go to the Processes tab.
Find the Process named OfflineRenderer.exe and end it.
This should stop the offline renderer and allow you to start your next render job.
Kind Regards,
Matt.
Thanks for the reply, Matt!
You are correct...if any users experience this issue, then follow the steps Matt outlined. This is because a 'ghost' render job is stuck somehow and you need to cancel it before Visualize can kick off another one.
Thanks!
Brian
Thanks Mathew!
Your post helped me troubleshoot and resolve issue immediately.
Thanks Matt, I´ve just do it and works perfect!
I also got that internal rendering error during beta testing. They really should have been more specific about the log file's whereabouts. Asked the feedback team but got no response.
I only got the error when I tried rendering out using the "fast" render option. In my case I was rendering a turntable. After switching to "accurate" it rendered out as expected.