Where are the tickets created? @Posersoftware.com?

structure posted at 2:33PM Thu, 03 December 2020 - #4406109

You might want to submit a ticket so that the devs can take a look at the issue to see if something is broken.

Quick question. My P11 Pro recently stop installing additional content. The runtimes are still accessible, and I do get a screen confirmation after attempting to install; but no other installs are registering in the library. Any suggestions?

Quick question; I'm working with VMs (VirtualBox, VMWare, etc.) and needed a good reference point for installing remotely. (Pipeline to servers, packaging to store distribution, etc.). The question: Which OS would be best for volume Poser Python VM functions?

Thx. I will make mention it in the forum.

Is there a readme file or installation configuration documentation?

The inquiry is for serious developers only. Please keep your personal grievances in site mail.

BTW: Thanks for the heads up.

On topic; They take Visa, Amex, MasterClass

Azure and their agent community DevOps are an IT service model typically used for ecommerce and corporate publishing/deployment. Currently, Poser has been centralized (sales-wise) at Renderosity with splinter cells elsewhere. Azure may help Poser content providers remain under Renderosity's EULA as well open new channels for content deployment and other revenue. It's like the Renderosity Marketplace plus an auto-update on your entire build process.

I personally suggest using Visual Studio to boot your content. They have a community (free) and professional edition as well as an online edition. It works fluently with Azure and teams under 5 membership may access the service without charge.

The Azure pipeline and workflow can very exhaustive. Teams may help mitigate productivity issues by equally distributing workflow. As a new user, it would be highly suggested to launch by requesting other content providers to join a team. I have initiated a working pipeline and may be available for team building. If interested; reply to this thread.

Habatchii-

UPDATE 122419.1

Quick note; We are now on LinkedIn! If you would like to participate in any of the discussions or publish a VSP-3 tutorial or extension there you must contact the moderator. Keyword, VSP-3 at LI. Here are our current directives:

UI Design: We are working closely with Visual Studio's parent group, Microsoft"s family of applications to produce one consistent theme using VS and Poser's UI. Color, elements, icons and accents are being mapped and one fluid design is the intent. A sample screen shot will be added to the next update.

Repositories: Github is currently hosting all of the project's operating files and VS is already kitted to use most of Github functions. Pipelines constructed from the IDE are being directed into Github with CI/CD presets making automated tasks easier.

Rendering The primary renderer, Firefly is still the top choice, both VS and NVIDIA have render engines as well, with NVIDIA also offering a full 3D SDK; including shaders, physics engines and other resources. A file of candidate additions currently is hosted at our group at Github.

Cloud Storage: Poser by nature consumes space on hard drives, our quick fix is cloud storage. By default, we are including three stock cloud storage options; Dropbox, OwnCloud and OneDrive. A link/folder within the extension will open to the cloud provider.Each individual user will have open an account with a provider before using.

Poser Pro: A nice member of the Renderosity community gave a link to a very well prepared script which compliments the Poser environment very nicely. The script; for licencing reasons, will not be mentioned in these notes yet will be used by the group in future extensions. Thx again to the author(s).

If you or your studio currently work with any of the programs above and would like to port your work into the Snippet Library, then simply post to this thread with the word support in curve brackets; exp. (SUPPORT) in the header.

Thanks in advance and happy rendering

Here's a link to the project at Github. It's being restored from various other repos, so it will have a code base shortly thereof. I am using Python via Visual Studio. If you wish to particupate, you will need to have an active VS account.

EPMD

Although PoserPython is a separate Python implementation, it still needs to be maintained to remain compatible with industry specifications. The EPMD is a maintenance utility for developers and studios to improve Python based code and script integration.

The concept is similar to a self support application emphasizing compatibility. If a user has an issue that callback to a Python reference, the EPMD will execute any library or document without the user needing to locate the library.

There is a startup project WIP using Visual Studio for this in the works at Github. For more info, leave a message below.

Just checking in. There wouldn't be any calls for beta would there?

UPDATE 101419.1

Quick note; the organization is currently auditioning new applications for the majority of its processing and IT networking ops:

UI Design: PAGE creates TCL based UI applications that are Python compatible and work well with PoserPython.

Linux OS: LinuxMint builds easily and blends well with most popular IDE's.

Rendering Firefly is still the renderer of choice due to its native environment and support from the PoserPython community.

Game Engine Unreal Engine hosts a formidable artist/developer community and industry grade User base.

Virtual GPU VirtualBox is conducive with basically all GPU extensions and flexible in working with Python scripting for scientific and R & D projects.

If you or your studio currently work with any of the programs above and would like to port your work into the Snippet Library, then simply post to this thread with the word support in curve brackets; exp. (SUPPORT) in the header.

Thanks in advance and happy rendering

UPDATE-

The repos are live! Accordingly, registered members may begin immediately to submit new or existing scripts. The file system and naming convention are still in development, but the infrastructure and thus workflow is active. Below is the workflow pipeline for each of the repos and acceptance criterion physics.

Introduction to the Snippet Library Please note that the library consists of two major types of scripts; software and hardware. Each type has a sub-branch in both the staging (initialization) block and the Snippet Library (complete) block.

1. Staging: The initial intake repo, used to document candidate scripts.

2. Trial Bench: The launch and load block used by script technicians in producing viability reports

3. Assembly Calibration: The first testing block used to calibrate script executions and build.

4. Prop Diagnostics: The 2nd testing block which hosts failed builds or build components.

5. Local Diagnostics: The final testing block used as a backlog for problematic or large scripts.

6. Engine Block: The final testing block used to complete script mergers and build pipelines to create the end product script. It produces documentation files, description sheets, promotional templates, etc.

7. Snippet Library: The permanent repo for all functional scripts.

Due to the necessity of resources, a decision has been made concerning a default editor. Visual Studio will be the official IDE for the organization, because of it's existing compatibility with Github. Extensions and plugins for the editor may be included in future threads.

Other default issues include the preferred GPU hardware. The organization will be partnering with NVIDIA based applications; due to their broad ray tracing and shader library API's.

Both OpenGL and DirectX technologies will be included in the library's build, so giving greater options in software based scripting.

Math implementations for Python will included SymPy, NumPy and IPython. Other software based components will include PyCollada and MyHDL; which is a collective of Python based hardware descriptive language libraries for embedded systems projects.

This thread will be updated regularly to keep all advancements posted herein.

Happy rendering!

Hi. I was leaning towards an upscale approach, featuring a product/project description page due to security and EULA concerns. But staff should have an unobstructed access to all scripts submitted. I have opened a Github account for the workshop. An admin invite will be waiting for you to see the progress thus far. Simply response via Sitemail.

I was enrolled as an early adopter yet the downloads came up corrupt. I have been in constant communications with Renderosity and SmithMicro since my software became dysfunctional. Any store credits/discounts or other consideration? We all have audiences to appease.