Why did a Poser 11 installer create a runtime on the root of my C drive ?

It was one of the installers for Poser 11.1.0.37674, but I'm not sure which.

There's a single file in this runtime:

I have the very exact thing. I never bothered to investigate that further because it involves a separate render process that I don't use any more.

WOW! I had skipped a bunch of updates because my old 11.0.7.33999 was working fine, but I just updated to 11.1.1.35540 so I can access 11.2 next week. I just now checked, and sure enough I have that Runtime folder at my Local Drive (C:) root. I probably wouldn't have noticed if you folks hadn't been discussing it.

Is it safe to delete it? What type of "separate render process" does it involve, as I only do the default type of rendering in Poser.

Or would it be safe to move it to my main Runtime Python Scripts folder?

Edited to Add: OK, I just checked and there's a copy of that script within my main Runtime Python Scripts folder, but it's dated 11/11/15, so this looks like a newer copy of it that just wound up in the wrong place. Any thoughts?

OK, I was wrong, the date of THAT copy of the file is the same as the one in the Runtime on my C: root.

If you are not dependent upon it, ignore it. Since it is nowhere linked to the core runtime, deleting it would not cause any problems.

Thanks, I think I will do that, especially since it does exist in my "real" Runtime.

Always nice to know it's not just me ! :o)

I was going to simply move it to the correct place, but there's already a copy in the correct place (as Miss B mentioned)...

C:/Program Files/Smith Micro/Poser 11Runtime/Python/poserScripts/ScriptsMenu/Partners/Dimension/3DRender Scenes.py

...so the C:Runtime folder was created for a spurious, duplicate, incorrectly located file.

I've just deleted the spurious C:Runtime folder.

However, this is clearly a bug in one of the installers.

Miss B - is the date on your C:Runtime folder the date that you installed 11.1.1.35540 ? If so then the 11.1.1.35540 installers have this bug, and so, I suspect, will the 11.2 installers.

How do we go about reporting bugs nowadays ?

3dcheapskate posted at 11:43PM Mon, 09 September 2019 - #4361569

Miss B - is the date on your C:Runtime folder the date that you installed 11.1.1.35540 ? If so then the 11.1.1.35540 installers have this bug, and so, I suspect, will the 11.2 installers.

Yes, September 6th, a few minutes after 7:00pm my time. I don't usually check what's what in the C: root on my computer, so I don't know for sure it wasn't there before, but I hadn't upgraded since 11.0.7.33999. which is quite a few upgrades back from 11.1.1.35540 that I had skipped, but I suspect this is an 11.1.x bug. Now I'll be making sure to check with each new upgrade.

As far as where to report a bug, try this link --> https://support.posersoftware.com/portal/newticket

Thanks - the folder date being updated indicatesthat one of the installers changed the contents,even if it was only overwriting the single file with an identical copy.

So I just created a ticket at the link you gave me without having to sign in. It said the ticket was created (on a little popup with a green line) but didn't give me any reference number. No email confirmation either yet.

Do I believe it?

I have yet to actually use that link. I just happened to bookmark it when I saw Jenn Blake post it in response to someone's query, as I wouldn't want to have to go hunting for it if, and when, I need it.

If you want to report an Early Adopter bug, there are actually two ways:

Post a ticket here:

https://support.posersoftware.com/portal/home

There is also a SLACK channel for you to get help if you need immediate assistance or if direct conversation helps you more. :)

you will need to install Slack and then click this link. OR just click the link and it will tell you how to install.

https://join.slack.com/t/posersoftwarebeta/shared_invite/enQtNzE5NTExMDQwNzIzLTUwNzhjYjMyZmIxZDA1ZDM0ZjhlMGFkZjljYTUyOGE5NjNjOWQ3NjY2Y2E4NDU5NmUxNmM4NjYxZTc2ZGMxYzY

((taken from the early adopter email sent a day after acceptance email))

Received an auto-email that seems to indicate the bug was successfully reported.

From the responses here it looks as if the bug disappeared (or was fixed) in the early 11.2 beta installers.

Excellent news! Thanks for letting us know.