Vred Assets Download

[Theodor Urena]

Theseare located under C:\ProgramData\Autodesk\VREDPro-7.53\data\Assets, for example. You can also right-click in the Asset Manager on a folder an select "Open in Explorer", that will show you the location.

But I would recommend you use another folder for your custom assets. By default VRED creates a folder under C:/Users/ (usernname) /Documents/Autodesk VRED/Assets for this purpose. This one should also be in the folder list of the Asset Manager. It is empty by default.

I can save a modified Material orginally found in the VRED Example Assets into the C:/Users/C-3PO/Documents/Autodesk VRED/Assets folder by dragging it there. I just don't understand the purpose of the Save button (green crayon icon over the "shaderball").

So, I'm wondering what is the point of that Save button that isn't working for me? Do I need to redirect the folder to where it's attempting to save? How? It's just a little confusing and I'm always afraid I'm going to overwrite the default Assets. Thanks.

Creating a new custom material asset in your own user folder based on the example assets is something you have to do manually. As you said, you can drag the modified material into your own user folder, and choose "Create New" in the dialog that pops up.

Then your material in the scene will be referenced to this newly created material asset. You can check by right-clicking the material in the material editor, Asset > Find in Asset Manager. That will select the corresponding asset in the Asset manager.

Hi,

you're welcome.

I just reproduced your steps with the example environment. Actually, here we have the same problem with missing write permissions. So the environment was not saved at all.

I admit that this is a bit inconsistent...

This would be a general advice: Look at the Terminal output when you perform some action and wonder if something has happened or not. Many error messages go in the terminal instead of error message boxes.

You can also notice that saving was not successful by seeing that the environment is still marked as modified. That would not be the case if saving was successful.

dawn wrote:

So, the workflow for saving a custom material or Modified Asset is to drag into a custom folder in C:/

Yes, if you want to save it as a new asset. For modifying existing (custom) assets you can use the save button.

I'm not sure what you mean with your last question. Could you rephrase it, please? I can just tell you that using assets don't reduce the file size, everything is saved in the project file.

Regards

Sinje

SO I've downloaded the trial, but I was aghast to find it comes with ZERO materials and environments. What good is that? I didn't see an option to download any add ons or assets with the trial. Is this possible or not? Thank you.

The Asset download is not public available for the mayor trial releases on the landing page. They are available in manage.autodesk.com to download afterwards which requires a valid subscription login.

There is not really a need for keeping them behind the wall. They are helpful for newbies that want to get their head around VRED for the first time while all the Pros have their own assets created in the meanwhile. We have escalated this to the web-team and I think they want to make the Assets available on the trial webpage in the future (if possible ).

I'm facing the same issue. As far as I know,assets are not available for trial versions. When I've started trial I reallywanted to buy a license afterward but without any ability to test the assets,I'm not sure I'll do that. What's the point in trial then? It pisses me off. I will have to go and find another software.I understand that pros have their own assets but I'm a newbie.... On -to-incorporate-yourself/ I've read how toincorporate myself and save my assets, so I guess investing money in VRED isnot really the best idea.

The VRED set of software tools from Autodesk let designers create and present high-quality product renderings of complex digital assets, such as automotive vehicles and other engineering-related artefacts. VRED has traditionally used an array of hardware to increase productivity, including multiple GPU and CPU configurations both locally and remotely, making low-latency and high-bandwidth networks and file systems necessary. Typically, this has required a substantial capital investment in hardware, leading to renewal cycles that are typically much longer than advances in technology for GPU and CPU architectures.

Leveraging a wide range of Amazon Elastic Compute Cloud (Amazon EC2) instance types and related services from Amazon Web Services (AWS), studios can now create workstations and cluster render nodes, with underlying performant networking, for a range of design and visualization workloads. This allows studios to capitalize on additional benefits:

The G5 instance comes in a variety of GPU, CPU, and memory sizes. These can be used to provide single, quad, or octet GPU-based workstations running either VRED Pro or a larger pool of machines hosting VRED Core, allowing designers to increase their render and streaming capabilities via clustering. With Amazon EC2 instances, machines can be stopped, reshaped into different sizes, and resumed, allowing the customization of the underlying instance to suit the task immediately at hand.

For single node installations, Amazon EC2 G5 instances can run VRED Pro on Windows Server to function as an artist workstation delivering high-quality graphics and rendering. Performant remote display protocols such as NICE DCV from AWS or HP Anyware (formerly Teradici PCoIP) can stream applications to any device, over varying network conditions and in a secure manner. With these remote display protocols, customers can access graphics-intensive applications such as VRED Pro remotely from simple client machines such as standard laptops or small form factor thin-clients such as Intel NUCs, eliminating the need for expensive dedicated workstations. This also offers the ability to work wherever a suitable network permits (we recommend a 20 Mb/s internet connection for dual 4k monitors).

To quickly load and transport VRED scene files and supporting data, performant file systems such as Amazon FSx for Windows File Server with fast underlying SSD storage can be mounted on workstation instances. This allows artists to easily share projects and render using offline machines for seamless collaboration. To achieve a rich design experience, using input devices such as Wacom Tablets in a lag-free manner, we recommend a latency of 25ms or less between the artist workstation instance and the end user client; with AWS you can accomplish this by creating your instances in one of the many global Regions or Local Zones that are closest to your designers.

Additional CPU or GPU-based instances can be formed into clusters within VRED environments, to allow the distribution of render tasks away from a single machine. This can be used to accelerate the rendering of images, or to increase the performance of a real-time streaming session. A VRED cluster consists of a main node (e.g. VRED Pro or Core) and multiple cluster render nodes, which are connected using a low latency network. Cluster nodes can be used elastically to augment a workstation as and when needed to bolster performance.

In the following diagram, the artist workstations / main nodes are deployed using a Windows G5 instance as previously discussed running VRED Pro on a Windows Server operating system. The VRED Render node cluster is built using G5 instances running a Linux operating system, with VRED Core installed to allow CPU and GPU rendering. The same render node cluster can be shared among multiple artists if the cluster has enough resources available to support the aggregate workload across the multiple main instances. Alternatively, multiple cluster node fleets can be created to scale to requirements. For workflows that require low latency and the highest bandwidth, the cluster components can be placed within an AWS Cluster Placement Group. This increased proximity enables higher per-flow throughput, both for scene and pixel data streaming, increasing frames per second.

In order for the render nodes to successfully connect and communicate with the main node, their IPs need to be added to the cluster settings within the VRED Pro UI. This is easily achieved programmatically with the following steps:

Components within AWS can be tagged to allow their isolation for the purposes of billing, etc. In this example, we used the Name tag to identify cluster machines from other Amazon EC2 instances (the Name is VREDCluster).

Providing a seamless interaction with both the display and input devices of cloud-based workstations is critical to the overall experience. This needs to include support for multiple 4K monitors, 4:4:4 color, and pressure sensitive Wacom tablet input. There are a number of solutions that meet these requirements, including NICE DCV. NICE DCV provides these features, and is licensed on all Amazon EC2 instances at no additional cost. With NICE DCV, artists globally can access flexible, secure, high-performing, and cost-effective virtual workstations on AWS that remove technological and geographic barriers for artists.

The VRED Stream App is a web interface for VRED that delivers real-time streaming of design content, with presentational controls for switching viewpoints and variants. Using VRED Stream, artists can run VRED on an EC2 instance and stream the session to browser(s) for presentation and review purposes. To enable VRED stream, follow instructions on the Autodesk VRED Stream page. Once streaming is enabled, an artist can provide the public IP address of the main node Amazon EC2 instance for reviewers to access the VRED stream.

To increase the performance of the streaming sessions, the EC2 instances can use the AWS Global Accelerator network service, allowing streaming sessions to intelligently use the AWS global network to accelerate performance, rather than relying on the public, congestion-prone, internet-to-route sessions.

3a8082e126