Forum: Poser - OFFICIAL


Subject: HELP cannot run poser

Yaesu opened this issue on May 20, 2017 ยท 40 posts


EpicHealer posted Sun, 29 March 2020 at 6:35 PM

Ok, so bear with me on this because this is JUST a Theory.

So when poking around in the Poser 10 Program folder I see the Runtime folder. Within that folder is the Libraries folder along with other stuff. Well there is a folder called the "poserHtml". In that folder are various other folders like the ClothesRoom, the faceRoom, the poseRoom, etc. So if you go into those rooms you will see HTML files. Those files of course are for giving directions but what I think happens is as follows.

WHEN you boot up Poser the WHOLE Flash thing is that WHEN booting up it is 1) Checking to see if you are using the Internet and 2) connecting to SMITHMICRO's website (Mothership). IF you are NOT connected to the internet AND you have NOT connected to the internet then your Content Libraries do not get lost. HOWEVER, if you do connect to the internet prior to booting up Poser 10 then you are vulnerable to loosing your content. Here is why. When you connect to the net and THEN boot up Poser your system communicates with the Mothership (SmithMicro servers) and the servers tell your system everything is good OR it updates/fixes stuff related to what is in your Library. Think of it as an "Autoupdate" for your Content Library ONLY without having UPDATE as an option for ONLY that. When the boot up process is going, the communication of the Mothership (SmithMicro servers) are updating your content for you. Like a way to ensure no corruption of the Libraries files can happen perhaps. Then if something is amiss it just fixes it for you.

Now that SmithMicro sold Poser (the software), when you boot up and your system (using Flash or whatever it used) goes out looking for the Mothership (those SmithMicro servers) the connection is lost and so your system is automatically deleting the CONTENT Library because there is NOTHING to tell it to KEEP the files. The SOFTWARE is saying the files you currently have are corrupt because Mothership (the SmithMicro SERVERS) are NOT telling your software the Library content IS NOT corrupt.

So because Bondware does not have servers set up to do the SAME thing as SmithMicro's did (the Flash or Air pointing to the Content). Your software has lost it's libraries and it can't get them back BECAUSE bondware does not have any library to pull the (supposedly) UN-corrupted files from. This is also why the Poser 11 software does NOT use Flash or Air because they no longer worry about connecting to their servers. In this new version what you have on your computer is on you and if something goes wrong with your content, it is not their concern. SmithMicro had theirs set up so that the content Libraries HAD a direct link to their servers. Sell off or shut down those servers and BOOM all Content is lost because YOUR software on your computer said to the program, "Delete it all".

Again, this is a theory but when looking at the fact that the actual CONTENT was lost and there is the need for Flash and Air, everything seems to lead to the idea that there is a direct link to Smith Micro WHEN booting up the software. I know it is far fetched but look at what was lost. ANYTHING connected to the Libraries. The software must reach out to the SmithMicro website via Flash and the issue is no message came back to say all is good. So it removed everything and is now just waiting for the signal from mothership to reload all the content back. Now, we can OPEN an older file and see everything that can be worked with BUT nothing will go into any Libraries because there is no Mothership on the other end accepting anything. So open that old file, work with it and resave it and you might find the NEW File missing everything again BECAUSE there is no Flash/Air connection to Mothership to keep an active Library.

What we need is for Bondware to contact SmithMicro and see what they had setup with regards to their servers. Then at the very least they need to give US a fix such that our software stops reaching out to Mothership and instead tells our software the keep it's Libraries.

Again, this is ONLY a theory. I am not a Code Jocky and so take it as you will. At the very least it is a good Brainstorm and start.