Rant time..........went to render a part today and poof the preview window flashes then nothing. First time for everything right? Decided to try to do a repair via installation and nothing, same problem. Anyone seeing this with SP 2.0?
Looks like I'm back in action with SP 1.0. It sucked doing an OS and SW clean install, but after three years of uninstalls and updates time had come to clean the clutter and start with a fresh everything. Now were screaming again. Not sure how much help this was for anyone else out there but this was the only way to get up and running again. Will skip SP 2.0 and wait for 3.0 then do an update. Thanks all for your input.
Nope! Works fine for me.
Any error messages shown in the Event Viewer?
Have you tried resetting the registry?
Nothing out of the ordinary. What would resetting the registry do? How's it done?
Service Ticket is in to the VAR
Wow, everyone at my VAR and SolidWorks must be dead because no one has replied or has a clue to this. Really starting to get frustrated with this thing! My rant for the day.
Are you using an approved GPU & driver?
Although the GPU isn't used to process the render, it probably is used to show the Preview window. Maybe update the driver?
All good on that front.
Is it hidden behind other windows or is it off-screen?
Are you using multiple screens? Or have you recently changed you screen configuration?
Check the Task Manager to verify whether it is running in the Applications or Processes tab.
Nope, even checked my task manager. Nothing. I've had issues with PV360 before but never has the program quit on me completely. Makes me miss PhotoWorks right now. Still no response from my VAR. saw another post with similar issue. Looks like SW has an issue with SP 2.0, or at least some others are having issues like I am. Already reset registery once. Would hate to do a clean install again. It's a pain and would perfer till 2014 is out.
Finally got through to my VAR. Seems I was on their spam list. They have a poor system of sending files too, My RX file was 9 meg and it still was to large to send via regular channels. They need to update their system something fierce. Oh Well.
see what they come up with and will let you know. I think there was one other post with a simila problem so the answer may be helpful short of a clean install.
Sometimes a simple unload and reload of the add-in works wonders...
Sure you have tried this but have you done a restart?
Yes, tried it but it didn't work. Thanks for the input.
Yep, no dice.
VAR wants me to rename Luxology Folder and clean out temp files, but this didn't work either. Still waiting on next idea. Getting close to doing a full / Clean install of OS and SW.
I've got the same issue...
Let me know how it goes. I'll keep trying here as well.
Didn't really get a solution from my VAR.......after feeling like I was left hanging, I decided it was time to do a complete OS clean install and start fresh. Not sure if I want to install with SP 2.0 though as it seems that once I updated the system with it the software went south on me. Right now I'm setting up my PC. I will do an image of it prior to putting SW 2013 on it, just to be on the safe side.
After the first two years working with SolidWorks and installing the latest versions and being on a first name basis with my Var I decided I would rather install and use SP5 of any given year. At that point it seems production acceptable.
Installing with SP 1.0 as I write.............
Just realized that I did some work in SP 2.0 and saved files. I may have no option but to upgrade to SP 2.0. Cross my fingers......
I would say go back to 2012 SP 5.0 and any work you have done in 2013 you can save as .iges and then run the feature recognition on it in 2012 and 99% of your parts will come back. Otherwise you will be reporting bugs weekly at a min.
I'm going to give it one more shot and see what happens. If it fails I'll reload my image and go that route. That said at some point what's the use of new software if you can't use it till SP 5.0? I used to install SP 0 then delt with all the nightmares. Then I waited for at least SP 2. Worked well with 2012 but these guys just can't stop screwing up what works trying to add small features to the software.
SW files are not SP specific, only version specific.
Well my test part opened in SP 1.0............
Retrieving data ...