Just noticed the "SkinVue fixed and added to VUE" in that list but it is before the python upgrade. I wonder if that means, because it has been incorporated into Vue it will be supported in python 3? However, I've also just noticed your important comment:- "However, note there is "no Python scripting" for the new Creator subscription edition." which suggests it won't work in Creator. That's a bit of a deal breaker for me as I'd say about 1 in 4 of my renders in Vue probably make use of SkinVue. At the moment I'm inclining towards passing on the upgrade. Can't really afford the next level up of licencing that would support python scripting.

Many thanks for these responses and the detailed information. Very helpful, especially the point about Python. I do use the SkinVue scripting utility and if there is no python 3 upgrade for that then I wouldn't want to move to a version that didn't support that. in terms of the other highlighted items, I've dabbled with displacement and might do so more if it has been improved. Can't say it's a wow factor improvement but, yes, it is interesting to me and counts as a mild plus. Ditto cloud improvements. I like playing with the clouds in Vue, so definitely some stuff that appeals to me in that list but whether it is worth the cost (and the risk of losing other things I am likely to use/need more) is still hard to say. I'll keep thinking!

And in fact this time around, deleting the album, recreating it and having a bit of patience worked. Within a few minutes the images were in the album. So I suspect (total guess) that when I first hit this problem, whatever process monitors/builds the albums wasn't running (and was incapable of picking up the backlog when it was restarted), but it is now running correctly.

Ah, not just me then :-) In my case, the images still aren't shown in the album even after waiting ten days so I don't think they are going to ever show! I guess from your description that some sort of background batch process runs to build the album from the galley, otherwise I might have imagined it was just linked dynamically from the image tagging. I might try to drop the album and recreate it again, since it's possible the album is now "corrupt" (perhaps whatever process builds it wasn't working properly at the time but well enough to think it had finished). A fresh start may fix it.

P.S. I was using Edge on Windows 10

Thanks everyone! That's why I love Renderosity. So many helpful people.... I've been away from the galleries here too long. I guess it's just my bad luck that my first post in a few years got swallowed up in a bug but as long as someone is working on it, that's fine. I've waited long enough to post, a little longer won't hurt.

Certainly if I don't click the checkbox, I just get an error returned saying I don't have permission to edit the image which is fair enough. But I only have three buttons available to me at the bottom of the screen when I am editing (there's a delete at the top as well). Save Changes reports success in a green text banner (if I've clicked the check box) but just puts the image back in the pending gallery and the other two options are Preview and Cancel. So the image seems to be stuck in Pending. I'm sure if I'd posted directly to the galley in the first place I'd have been fine but having got into this "preview" mode it doesn't seem possible to do anything other than edit in place or delete.

Thanks, I've tried that and there is no publish option. There is some text that tells me the image is a preview (and I did select the preview option at one stage when I was preparing the submission). The page says I can just save the image from edit to make it public but all that is doing is re-saving back to the Pending gallery. That was when I wondered if all images were reviewed now, but from what you are saying it isn't a new Renderosity policy so I guess I should have been able to publish to the public gallery. Not sure what's going on here but maybe a bug? I could try resubmitting the image without previewing it but it would be good to know if I'm missing something obvious...

Ok, fair enough!

Thanks guys, that pointed me in the right direction! I knew it had to be something obvious but though I've taken plenty of things out of the libraries before I haven't put much into them. When the set was restored from the library it was positioned correctly (the universe was aligned the same in my two scenes) so it is just the "memorise" and "restore" functions that didn't do what I was expecting and seem wrong... I can live with that now.

I think it might be because 10009012 is technically a beta build that I wasn't automatically notified to upgrade. Interested to how the new SDK works though (just in case it fixes some of the other import problems I've had historically), so I reckon I'll give it a try...

Ok thanks Guys. Interestingly when I ran a "check for update" on Vue it thinks it is up to date, so possibly something a bit wrong in the checking mechanism or the server I'm being connected to. I'll see if I can get hold if the update manually.

That's interesting... I can't find any reference anywhere to anything more recent than this one:- Poser SDK from August 2011?

I'm on build 10008945 for Vue which as far as I know is the latest version of 10 and I'm now on SR2 for Poser 2012 so I thought I was up to date with all patches but if there is another SDK out there I'd like to try it because there are still some scenes where the import logic messes up the geometry. I raised this with eon ages ago but no solution available and the SDK was blamed. I'm not holding my breath for a solution...

Back to this problem, editing the  "Poser UI Pref Map.xml" seems to have worked for me although I couldn't find that documented anywhere and I also suspect that if I were to try scenes based over different libraries I would have to edit this file to "hard code" the new library before import everytime. Haven't tried it and as I almost always use content in one library (just not the base poser one) I am unlikely to need to do it. Even so, that would still be a lot better than having to select every path on an import....

Forgot to add (and it could be important). I also edited AddLibraryLastPath in this Poser UI Pref Map.xml file. Note sure if that is what fixed it or the changes described above.

Sorry in the above post where I said...

<>

I meant

<>

It's getting late and my typos are getting worse. Hopefully the above makes sense and might help someone....