XnView - SOLVED (kind of)
-
When I try to open a file in XnView or Drop a skp file onto the icon I get the attached warning.
-
Strange - it works for me with any version SKP ?
If I drop something like '.lsp' file [unsupported] it does give a similar error-message to yours... -
Mine is still working, but I only installed 2014. Haven't used it or uninstalled it yet.
-
So odd.
I restarted my machine in case it was just a glitch but still no thumbnail. And of course this comes when I really need it.
-
-
I'm using XnView version 2.13 is that what you're using? do you want my installer file?
-
I just downloaded the newest 2.2 and it still does not work. There must be something on our machines here that is blocking it for some reason. It was working last month no problem. Sheesh.
-
Thanks for sending that Kris but I get the same results.
Oh well. I will just open another instance of SU and file surf that way.Thanks again for the help.
-
Have you edited your file associations to go to 2013 or 8? When you double click a skp does it open in the right version of Sketchup.
-
It opens with 13 when I double click.
-
Well peachy. I reinstalled 2014 and the thumbnails in XnView came back. Apparently it was trying to use a nonexistent version of SketchUp on my machine to generate the thumbnails. Even though I pointed both my pc and Xnview to the 2013 version. Oh well, I can live with this.
-
Nice... So I guess I'm safe to upgrade. I didn't know there had been a few versions.
-
Happened to me when I uodated to newest Version XNVIEW.
Had MP64 & SStandard- MP 64 version worked on all before now nada.
XNVIEW would show SKP & SKB, 3DS & Obj.
Now will show only SKP not SKB & 3DS.
MP version shows 3ds & Not SKP or SKB.
BUt old files show new SKP show sometimes.
That AutoCad ref has been there forever. -
@krisidious said:
Nice... So I guess I'm safe to upgrade. I didn't know there had been a few versions.
Well Kris I am still running the one you just sent me so I can't vouch for the newest.
I still don't like the fact that I had to go to all the trouble. Makes sense that if you are pointing everything back to 2013 it should work. Oh well.
Advertisement