Forum Moderators: Staff
Poser Technical F.A.Q (Last Updated: 2024 Nov 13 12:50 am)
Welcome to the Poser Technical Forum.
Where computer nerds can Pull out their slide rules and not get laughed at. Pocket protectors are not required. ;-)
This is the place you come to ask questions and share new ideas about using the internal file structure of Poser to push the program past it's normal limits.
New users are encouraged to read the FAQ sections here and on the Poser forum before asking questions.
This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.
I'm running Poser11.2.319, on Windows 10, running AMD Ryzen 5 3600 with 32GB RAM and an old AMD Radeon R9-270X.
I''ve suddenly (as in just since yesterday) started getting Wacro errors poppinh up in a mainWacros window on inital start of Poser, and recurrng whenever I load a new figure or prop.
The text is:
"An errror occurred importing addon KinectCapture : ERROR: DLL load failed: The specified module could not be found. An errror occurred importing addon PythonShell : ERROR: DLL load failed: The specified module could not be found. An errror occurred importing addon KinectCapture : ERROR: DLL load failed: The specified module could not be found. An errror occurred importing addon PythonShell : ERROR: DLL load failed: The specified module could not be found."
I found this post and, following that advice, I moved the KinectCapture folder from Poser11 > Runtime > Python > addons to a separate folder outside of the main Poser11 folder (rather than deleting outright). Once I did this the KinectCapture errors were no longer appearing, so I did the same with the PythonShell folder, but now I'm getting a mainWacros popup reporting "AttributeError: loads".
What else should I try to correct this (and why might it have suddenly started after years of mostly trouble-free operation)?