Finally got it! My on-line service, My Computer Works, helped me get the folders cleaned out. So I didn't have to re-download the install file.

I'm transfering my P9 runtime into it now.

wow that...that sounds kind of scary. How are you "transfering" that runtime exactly? I hope you're just linking to it and not actually copying stuff over. That could be dangerous.

Quote - wow that...that sounds kind of scary. How are you "transfering" that runtime exactly? I hope you're just linking to it and not actually copying stuff over. That could be dangerous.

Sorry I wasn't clear. Not copying. moving folder by folder into the Runtime.

New problem; First, when Pro comes up, The mainWacros window comes up with all of this:

Traceback (most recent call last):
**  File "C:Program FilesSmith microPoser Pro 2014RuntimePythonlibsite-packageswx-2.9.1-mswwx__init__.py", line 14, in **
**    import version**
ImportError: numpy.core.multiarray failed to import
Traceback (most recent call last):
**  File "C:Program FilesSmith microPoser Pro 2014RuntimePythonlibsite-packageswx-2.9.1-mswwx__init__.py", line 14, in **
**    import version**
**  File "C:Program FilesSmith microPoser Pro 2014RuntimePythonlibsite-packageswx-2.9.1-mswwx__init__.py", line 45, in **
**    from wx.core import ***
**  File "C:Program FilesSmith microPoser Pro 2014RuntimePythonlibsite-packageswx-2.9.1-mswwx_core.py", line 4, in **
**    import core**
ImportError: DLL load failed: %1 is not a valid Win32 application.
Traceback (most recent call last):
**  File "C:Program FilesSmith microPoser Pro 2014RuntimePythonlibsite-packageswx-2.9.1-mswwx__init_.py", line 14, in **
**    import version**
**  File "C:Program FilesSmith microPoser Pro 2014RuntimePythonlibsite-packageswx-2.9.1-mswwx__init__.py", line 45, in **
**    from wx.core import ***
**  File "C:Program FilesSmith microPoser Pro 2014RuntimePythonlibsite-packageswx-2.9.1-mswwx_core.py", line 4, in **
**    import core**
ImportError: DLL load failed: %1 is not a valid Win32 application.
Traceback (most recent call last):
**  File "C:Program FilesSmith microPoser Pro 2014RuntimePythonlibsite-packageswx-2.9.1-mswwx__init_.py", line 14, in **
**    import version**
**  File "C:Program FilesSmith microPoser Pro 2014RuntimePythonlibsite-packageswx-2.9.1-mswwx__init__.py", line 45, in **
**    from wx._core import ***
**  File "C:Program FilesSmith microPoser Pro 2014RuntimePythonlibsite-packageswx-2.9.1-mswwx_core.py", line 4, in **
**    import core**
ImportError: DLL load failed: %1 is not a valid Win32 application.

Then, I get a PoserPro Error message telling me there was an error importing wxPython API.

But then it worked fine till I went into the material room and,tried to remove an unplugged node. The remove Orphans window comes up, Wacro execution failed error message comes up, Pro whites out , The window telling me that the Poser Pro executable file has stopped working, another window comes up telling windows is gathering info and do I want to send it? I click no and the program crashes.

Anyone have any idea what the %^&*%^ is going on here??

That probably is because of the move you made. I don't understand why you didn't link to the runtime instead. Space issues? 

I wish I could tell you how to go about fixing it but at this point, I wouldn't know where to begin. You could try contacting Tech Support on Tuesday (I believe we have Monday off at the office). 

Quote - That probably is because of the move you made. I don't understand why you didn't link to the runtime instead. Space issues? 

 

I wish I could tell you how to go about fixing it but at this point, I wouldn't know where to begin. You could try contacting Tech Support on Tuesday (I believe we have Monday off at the office). 

This looks like a program issue- not content. Besides, I moved content in- I didn't take anything out of the program files.

 The thing is, that unless I try to delete a node, the stupid thing works fine- that's what I don't understand. I'm using it right now.

Well, it's the first I've seen of it. As I said, I would suggest contacting tech support with the steps leading up to this. You can send them a message today and they'll get back to you once they're in the office. I'm sorry you're having this issue though. That really sucks.

Quote - Well, it's the first I've seen of it. As I said, I would suggest contacting tech support with the steps leading up to this. You can send them a message today and they'll get back to you once they're in the office. I'm sorry you're having this issue though. That really sucks.

I tried sending in a request when all of this started, filled it out, clicked send and got "error on the page". It wouldn't go through.

Well, I'm not in Tech Support anymore so I don't know what's up with the site for contacting us but I would try again on Tuesday. If you still haven't gotten through by then, send me an IM and I'll try and get someone to take a listen to your issue.

Quote - Well, I'm not in Tech Support anymore so I don't know what's up with the site for contacting us but I would try again on Tuesday. If you still haven't gotten through by then, send me an IM and I'll try and get someone to take a listen to your issue.

Thank you. I do appreciate it.

Here's a sample of what I'm talking about. Once the program's up, it runs fine- unless you try to delete a node:

http://mdbruffy.deviantart.com/art/Alsan-Court-take-1-374089649

If you dropped the Runtime from C:Program Files (x86)Smith MicroPoser 9 onto C:Program FilesSmith MicroPoser Pro 2014 (or whatever) then you will have replaced new files with older versions, from P9, which probably will fail to work or to work correctly in at least some cases. Certainly if you allowed files to overwrite, but even if not anything that was in P9 and doesn't have a match in PP2014 will have been moved and may have been picked up by PP2014 even though it won't work correctly. If that isn't what you meant then ignore this.

Quote - If you dropped the Runtime from C:Program Files (x86)Smith MicroPoser 9 onto C:Program FilesSmith MicroPoser Pro 2014 (or whatever) then you will have replaced new files with older versions, from P9, which probably will fail to work or to work correctly in at least some cases. Certainly if you allowed files to overwrite, but even if not anything that was in P9 and doesn't have a match in PP2014 will have been moved and may have been picked up by PP2014 even though it won't work correctly. If that isn't what you meant then ignore this.

Everything belonging to Poser 9 has been removed. Everything works untill you go into the material room- and then only if you try to remove a node, I've replaced runtimes ever since I upgraded from P5 to P6 and I've never had a problem related to that.

 BUT... now that you mention it, I replaced the entire runtime- which means the python scripts would have been replaced. I'm going to take a look at that...

Quote - > Quote - If you dropped the Runtime from C:Program Files (x86)Smith MicroPoser 9 onto C:Program FilesSmith MicroPoser Pro 2014 (or whatever) then you will have replaced new files with older versions, from P9, which probably will fail to work or to work correctly in at least some cases. Certainly if you allowed files to overwrite, but even if not anything that was in P9 and doesn't have a match in PP2014 will have been moved and may have been picked up by PP2014 even though it won't work correctly. If that isn't what you meant then ignore this.

 

Everything belonging to Poser 9 has been removed. Everything works untill you go into the material room- and then only if you try to remove a node, I've replaced runtimes ever since I upgraded from P5 to P6 and I've never had a problem related to that.

 BUT... now that you mention it, I replaced the entire runtime- which means the python scripts would have been replaced. I'm going to take a look at that...

I think that was the problem. When I swapped the runtime, I swapped the pyhton scripts. I went back and replaced the scripts with the right ones and now everything works.

 This never happened with Poser 5-9. I was able to swap the entire Runtime and go happily on my way. This was a new twist for me.  But everything seems to be working-  for the moment.

Quote -  BUT... now that you mention it, I replaced the entire runtime- which means the python scripts would have been replaced. I'm going to take a look at that...

That probably overwrote binary files that belong to wxPython with older, incompatible versions.

Don't copy any full runtimes into the Poser program folder. The Runtime folder next ti is more than just content, it also contains files that Poser requires at run time - UI resources, Python libraries, etc. Poser 5 introduced external runtimes and an installation of a current version of Poser with default settings will put all content in a runtime separate from the program files.

Keeping content separate from the program folder will also make reinstalls much less scary.

Next time, just add the old runtime but don't copy or move it.

Quote - > Quote -  BUT... now that you mention it, I replaced the entire runtime- which means the python scripts would have been replaced. I'm going to take a look at that...

That probably overwrote binary files that belong to wxPython with older, incompatible versions.

Don't copy any full runtimes into the Poser program folder. The Runtime folder next ti is more than just content, it also contains files that Poser requires at run time - UI resources, Python libraries, etc. Poser 5 introduced external runtimes and an installation of a current version of Poser with default settings will put all content in a runtime separate from the program files.

Keeping content separate from the program folder will also make reinstalls much less scary.

Next time, just add the old runtime but don't copy or move it.

So the reason I didn't have this problem before with Poser 5-9, is because of what? The new features that 2014 has required new scripts? That would make sense since this is a more drastic upgrade than what I have been making.

P.S. If there's a moderator listening in, would you plase tell Renderosity folks that's it's been damn hard to get on the site today? I've tried the link in the e-mails- both the direct one to replies and the one to the forum and I've only gotten through about half the time- same with coming in through the front door.  About half the time, I get the message that the "Page can't be found".

Quote - So the reason I didn't have this problem before with Poser 5-9, is because of what?

Luck.

Poser 8 I believe introduced wxPython 2.8, in Poser 9 it was updated to wxPython 2.9 which I think lives in separate files and folders. Copying files from Poser 8 to Poser 9 would then not overwrite files but only add files that Poser 9 would ignore. Poser 10 still uses wxPython 2.9, but includes minor updates and bug fixes that make the dlls from one version incompatible with the other (all scripts should still work as before).

Quote - > Quote - So the reason I didn't have this problem before with Poser 5-9, is because of what?

Luck.

Poser 8 I believe introduced wxPython 2.8, in Poser 9 it was updated to wxPython 2.9 which I think lives in separate files and folders. Copying files from Poser 8 to Poser 9 would then not overwrite files but only add files that Poser 9 would ignore. Poser 10 still uses wxPython 2.9, but includes minor updates and bug fixes that make the dlls from one version incompatible with the other (all scripts should still work as before).

Poser 8 never did work for me. Everytime I clicked on an object it would jump clear across the screen. Others had the same problem. The techs worked with me for week and couldn't give me an answer. I had to go back to P7 till P9 came out.

I know now, that 2014 will handle my existing scene files. Now, I'm working my way through this 900 page manual to see if there are any other surprises I need to know about.

Okay, I JUST received my physical copy of Poser Pro 2014. It arrived by Fed Ex, and I had to pay $36.45 in GST and PST.

I think next time, I'll just download the program . . .

:(

But, it DID come with a coupon for 15% off my next purchase of $5 or more at Renderosity . . .

Wardrobe Wizard.

 In the standard verisons of Poser, once WW was added into them, you had to contact PhilC for one more file before WW would work. There's nothing about this in the manual for Pro, yet, I've clicked on "Wardrobe Wizard Menu" under the scripts tab and it opened a window telling me to go to Windows:Python scripts and the buttons will be ready to go. Yet, when I go there and click on Python Scripts, nothing shows up.

Is PhilC still holding on to one last file?

Quote - > Quote - I am happy with firefly but see that others prefer to use other render engines. Could what those who use reality etc be written into firefly?

I personally use Octane although I also have a Reality 3 license.  Smith Micro would have to purchase the renderer.  Reality uses Lux under the hood which I believe is free/open source and Octane works amongst other tools also like Lux does.  It'd be more limiting for those renderers.

The main benefits to Octane/Reality is that they will use your graphics card to render.  You can render most scenes in under a minute.

That sounds like a blessing. I might get me an Alienware computer, which are mostly built for gaming. And you know how gaming online requires a monster graphic engine to work well. Yet those computers are around 4000 dollars, and that's just for the goddamn hard drive alone by itself! 

I'm going to throw this out and see if anyone has an answer. I've had this problem in Poser 7, 9 and now 2014. Why is it, when I apply a transparency map to an outfit, even if I'm just rasing the hemline- the whole outfit disappears till it's rendered??

Quote - Okay, I JUST received my physical copy of Poser Pro 2014. It arrived by Fed Ex, and I had to pay $36.45 in GST and PST.

I think next time, I'll just download the program . . .

 

:(

 

But, it DID come with a coupon for 15% off my next purchase of $5 or more at Renderosity . . .

Yeah gotta love the the extra they put on top of the original cost of the product, I downloaded mine and even after I worked out approximately the exchange rate what I had gotten from the currency exchange site Xe.com (have been correct in the past) and what I got charged  when I went through fastspring were completely different, so I am putting it down to some form of handling fee..

Quote - I'm going to throw this out and see if anyone has an answer. I've had this problem in Poser 7, 9 and now 2014. Why is it, when I apply a transparency map to an outfit, even if I'm just rasing the hemline- the whole outfit disappears till it's rendered??

I had this too. Is it still in 2014??This is annoying.

Instead of rendering you can also do a "Reload Textures".

Quote - > Quote - I'm going to throw this out and see if anyone has an answer. I've had this problem in Poser 7, 9 and now 2014. Why is it, when I apply a transparency map to an outfit, even if I'm just rasing the hemline- the whole outfit disappears till it's rendered??

 

I had this too. Is it still in 2014??This is annoying.

Instead of rendering you can also do a "Reload Textures".

Glad I'm not the only one. I'll try that and see what it does. Thanks.

Quote - > Quote - > Quote - I'm going to throw this out and see if anyone has an answer. I've had this problem in Poser 7, 9 and now 2014. Why is it, when I apply a transparency map to an outfit, even if I'm just rasing the hemline- the whole outfit disappears till it's rendered??

 

I had this too. Is it still in 2014??This is annoying.

Instead of rendering you can also do a "Reload Textures".

Glad I'm not the only one. I'll try that and see what it does. Thanks.

Are you using the OpenGL or SreeD preview? The latter iss till, I think giving only Poser 4/PoserProPack previews but the former should certainly do better.

Quote - > Quote - > Quote - > Quote - I'm going to throw this out and see if anyone has an answer. I've had this problem in Poser 7, 9 and now 2014. Why is it, when I apply a transparency map to an outfit, even if I'm just rasing the hemline- the whole outfit disappears till it's rendered??

 

I had this too. Is it still in 2014??This is annoying.

Instead of rendering you can also do a "Reload Textures".

Glad I'm not the only one. I'll try that and see what it does. Thanks.

Are you using the OpenGL or SreeD preview? The latter iss till, I think giving only Poser 4/PoserProPack previews but the former should certainly do better.

Open GL is what Poser's geared toward if your video card can handle it. The Program picks it automatically according to the manual. It's what mine is set to.

Quote - > Quote - > Quote - I'm going to throw this out and see if anyone has an answer. I've had this problem in Poser 7, 9 and now 2014. Why is it, when I apply a transparency map to an outfit, even if I'm just rasing the hemline- the whole outfit disappears till it's rendered??

 

I had this too. Is it still in 2014??This is annoying.

Instead of rendering you can also do a "Reload Textures".

Glad I'm not the only one. I'll try that and see what it does. Thanks.

"Reload Texture" had no effect. Anyone have any other ideas?

Quote - Well, I'm not in Tech Support anymore so I don't know what's up with the site for contacting us but I would try again on Tuesday. If you still haven't gotten through by then, send me an IM and I'll try and get someone to take a listen to your issue.

Could you pass on this transparency issue? I tried to send in an incident report- and I got "Error on the Page". It wouldn't go through.

Quote - > Quote - I'm going to throw this out and see if anyone has an answer. I've had this problem in Poser 7, 9 and now 2014. Why is it, when I apply a transparency map to an outfit, even if I'm just rasing the hemline- the whole outfit disappears till it's rendered??

 

I had this too. Is it still in 2014??This is annoying.

Instead of rendering you can also do a "Reload Textures".

Got this responce from Smith Micro about the transparency map problem after I chatted with a tech and sent him a scene file:

For your dress, I created a new image file based off of the existing "Vicky3eveningdress - Marble" one, but in my new image file I drew a bunch of green lines on it to make it obvious it's been edited by me. I saved that new image file under a new name. I then deleted all of the existing material settings for your dress, and re-created the materials using my own material settings and that new image file with the green lines, and the dress then showed up properly. So you can try any or all of those steps I mentioned. Maybe it's the image files itself, or it's the material settings, I don't know, as I just did a blanket wipe of the old materials and started over more or less from scratch (though I did use the same transmap image file) and I can't really troubleshoot third party and extremely old content.

Quote - Now.. I've LOVED Wardobe Wizard for years.
does anyone know if the fitting room is "just" an implemented WW or something else?

I think it clearly is a completely different process, although the Poser team could have derived some things from WW or used similar methods in places.  WW relies on data files, pre-correlated information which tells the script how to adjust one mesh relative to another.  Poser is doing the comparisons itself, directly, while the process runs.  This opens up a lot more possibilities.  The Fitting Room also has more interactive options which allow the user to control the comparison before it happens, which isn't possible with pre-built data files.  Whatever wizardry PhilC uses to create his data files, it has now basically been opened up to all users.  The Fitting Room can also be faster than almost any script, being a compiled process which is integrated into the main software.  It sounds like a truly magnificent addition to Poser, and I can't wait to be able to try it.  :lol:

Fitting room is great for shirts or pants. But things like long dresses, it don't do too good.

Speaking of which, has anyone else has problems getting Wardrobe Wizard to come up? I clicked on the Scripts tab, then on the Wardrobe Wizard Menu button. It says to go to the Windows tab and select the Python script tab and the buttons would be loaded and ready to use. Well, I do that and nothing ever comes up.

Quote - Fitting room is great for shirts or pants. But things like long dresses, it don't do too good.

Speaking of which, has anyone else has problems getting Wardrobe Wizard to come up? I clicked on the Scripts tab, then on the Wardrobe Wizard Menu button. It says to go to the Windows tab and select the Python script tab and the buttons would be loaded and ready to use. Well, I do that and nothing ever comes up.

Smith micro figured out what was wrong with my Wardrobe Wizard. Poser prefrences got corrupted during the installation. I had to remove the entire folder and let Poser create a new one.