Forum Coordinators: RedPhantom
Poser - OFFICIAL F.A.Q (Last Updated: 2024 Nov 05 9:36 pm)
If I might make a suggestion ...
Posting feature requests in a forum thread inevitably will result in responses that go beyond feature requests (thread drift, multiple requests in a single post, debates, and so on). With the Poser development team being small and their workload and other priorities being high, the odds of them having time to sift through forum posts is small.
The beta testing area does have a category for feature requests and enhancements, and it would be easier for devs to track and monitor there. Just add one feature per report.
I do agree with DC. It is better to consolidate and restrict these requests to one thread for better access and review. The last locked thread became a slugfest with individuals relentlessly trying to repeatedly interject their views and opinions. It only became apparent that those well-meaning requests got buried under the rhetoric of controversy.
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.
Thread for Content Developers Only, to add Poser capabilities and improvements as they create.
Please post only Poser 13 FEATURE REQUESTS and Poser Content Development FEATURE IMPROVEMENT suggestions in this thread. Diversion into controversy will get the thread locked and may reduce visibility to the Poser development team. Recognizing ideas and problems developers struggle with will inspire further discussion, is not a thread to explore these ideas or expand Poser's scope so please create a new thread to explore these topics in depth so that this thread may exist only to provide a concise, convenient and complete list of feature suggestions.
Please AVOID Poser software general complaints, bug fixes and technological or solution approaches that are decisions of the Poser engineers.
When proposing a Feature Requests for new capabilities, provide a USE CASE so the developers may understand how the capability will improve Poser workflow by adhering to the following format:
______________________________________________________________________________________________________________________
FEATURE REQUEST: (Describe the CAPABILITY the new feature will add to Poser 13's existing toolset)
- USE CASE: (Describe how the capability would be applied in the Poser content workflow, and why it helps)
OR
EXISTING FEATURE IMPROVEMENT SUGGESTION: (Identify the existing Poser 13 feature to be improved, and then describe suggested improvement)
- USE CASE: (Describe how the improved feature would be used whether sameor different than prior version, and makes Poser content development better, easier or more efficiently.)