3d max error osl not find include

OSL-error when opening specfic file

Hey,
when opening a specific file, the Vray message log appears. It has dozens of errors in it, please see attached screenshot. The OSL file mentioned there is not at that network location anymore, because we upgraded servers. However, the map name specified is not used anywhere in the scene. Problem is, I can not render the scene on backburner, because it errors because of that missing file. Also, the OSL does not get listed in the asset tracker. I already tried merging the parts into a new scene, and even then the message log pops up. What can I do to get this scene rendered?

Tags: None

V-Ray GPU Supported Features

This page provides tables of features supported by V-Ray GPU in 3ds Max.

Overview

These features are supported by V-Ray GPU in 3ds Max.

Supported Features

Cameras

Feature

Motion blur (transformation+deformation) 1

(On integer frames)

Camera motion blur 1

(On integer frames)

Geometry

Lights

Feature

Global switches

Textures

Feature

(deprecated)

(no alpha attribute)

(no alpha attribute)

Other

Texture Baking

Environment

Global Illumination Methods

Feature

Anti-Aliasing Filters

Materials

(without Emit light on back side option )

(without Roughness translucency mode)

(without Multiply By Front diffuse)
(shadows only, no GI on mattes)

(without raytraced (solid) and raytraced (refractive))

Unsupported materials and textures in V-Ray GPU are regarded as incompatible in the Material Editor of 3ds Max. They will not be displayed unless the Show Incompatible option is enabled in the Material/Map Browser.

Render Elements

V-Ray GPU

3rd Party Plugins

Footnotes

1 – GPU rendering supports motion blurred frames on integer numbers only. For example, starting the render from frame 1 produces correct motion blur, but starting from frame 1.25, will produce incorrect motion blur. Shutter efficiency is not supported with GPU.

2 – Displacement results between CPU and GPU rendering may differ slightly because of Pre-tessellation and Cache Normal settings.

3 – With V-Ray 6, update 1, instanced lights by VRayInstancer / Forest Pack / Rail Clone, etc. are part of the Light Select RE of the respective source light.

4 – Light Select modes always contain GI information in V-Ray GPU. The Raw and indirect modes are not supported in V-Ray GPU.

5 – The Sampler Info Render Element supports different UVW Coordinate types through its different pass types. For more details, please see the Sampler Info Render Element page.

6 – When rendering with V-Ray GPU CUDA, the VRayShadows Render Element is incompatible with Adaptive Lights and may render incorrectly if used together.

7 – Starting with V-Ray 3.6, the VRayColor2Bump texture is no longer needed for procedural textures in order to be supported by V-Ray GPU.

For earlier releases, all procedural textures are supported by V-Ray GPU when used for Bump mapping through a VRayColor2Bump texture attached to the Bump slot.

In V-Ray Next and above , the texture ensures that the procedural bump is fully consistent between V-Ray and V-Ray GPU. Without VRayColor2Bump there might be some difference in the rendered procedural bump amount related to the scene size and scale.

8 (8.1 / 8.2 / 8.3 / 8.4 / 8.5) – These plug-ins are only partially supported by V-Ray GPU.

9 (9.1 / 9.2 / 9.3 / 9.4 / 9.5 / 9.6 / 9.7)– The texture is baked for rendering on the GPU. This means that it will use more memory to render, than a fully supported procedural texture.

10 – V-Ray GPU supports VRayScannedMtl under few limitations. For more information, visit the VRayScannedMtl page.

11 – It is supported in V-Ray for 3ds Max 2019. Some OSL maps are not supported yet.

12 – V-Ray GPU supports all Bercon maps within the following limitations: Distortion map is not supported. BerconGradient Lighting, Random, Particle age, Particle speed and Particle size types are not supported. Normal and Distance types To Object and Object Z are not supported. BerconTile UV Mapping and Randomization are not supported. BerconMapping is supported via baking.

13 – Falloff map does not support Shadow/Light type.

14 – VRayObjectID is always rendered with Integer (no Anti-Aliasing) mode in V-Ray GPU.

15 – V-Ray GPU does not support V-Ray Mesh Light textures.

16– There is a limit of 6 layers per Composite map when using the V-Ray GPU engine.

17 – Particle shading set is not supported by V-Ray GPU.

18– Area shadows are not supported by V-Ray GPU.

19 – For detailed information on the V-Ray GPU support of VRayGLSLMtl and VRayGLSLTex, please refer to the GLSL Support page.

20 — VRayDRBucket Render Element works only in Production rendering mode using Bucket sampler.

21 — Fire Lights ( Fire Rollout ) and Use Light Cache ( Smoke Color Rollout ) options are not supported with V-Ray GPU. For more information, refer to their relevant pages.

22 – Substance 2 is supported.

23 – 3ds Max OSLs can cause a progressive slowdown in animation. Use the VRAY_GPU_SL_SHADERS_LIMIT environment variable to control how much OSL cache is wiped out and to reduce the animation slowdown. If set to 1, the cache is deleted for every frame. For more complicated scenes, or when using an interactive render a higher value works better. The default value is 64.

24 – Support is confirmed for tyFlow v0.16122 [BETA] (June 13 2021) . There may be occasional failures with other versions while the product is still in Beta and major changes to it happen.

25 – All render elements which are not supported with GPU are also not supported as bake elements with GPU.

26 – Currently Lens File distortion type is not supported with V-Ray GPU.

27 – RailClone mapping features are not supported in Chaos Cloud Rendering with RailClone’s Use Instancing Engine option enabled. More details are available at Itoo’s RailClone requirements page under V-Ray RT/GPU.

28 – Animation of cloud parameters is currently not supported.

29– When Corona 8 is installed and a scene saved with the earlier Corona 7 is opened with V-Ray 6, the scene has its Corona Scatter objects converted to the more advanced Chaos Scatter objects. When Corona 7 is used with V-Ray 6, such scenes keep their Corona Scatter objects and respectively — the VRayCoronaScatterMod.

30 – Note that the noise pattern renders differently in Chaos Cloud/V-Ray Standalone. Use the VRayNoiseTex instead to keep consistent results.

31 – When using VRayEnmesh on V-Ray GPU the gizmo’s amount on the Z axis should be slightly greater than the bounding box size of the source object to avoid Z-fighting.

OSL Map Support Notes

Some 3ds Max shaders are problematic when V-Ray GPU is selected as a render engine.

Shaders with string outputs do not work on V-Ray GPU. In general, shaders which involve string operations may not function as expected, since V-Ray GPU has very strict limitations with respect to string handling. The following 3ds Max shaders are problematic and do not work on V-Ray GPU as they return strings:

• GetNodeName.osl
• SetFile.osl
• SetFilename.osl
• SetString.osl

The following shaders skip the automatic gamma correction (the gamma is determined by the file extension):

• HDRIEnviron.osl
• OSLBitmap.osl
• RandomBitmap.osl / RandomBitmap2.osl
• UberBitmap.osl

The following shaders do not work both on V-Ray and V-Ray GPU as the object picking is not implemented yet:

• CameraProjector.osl
• ObjectProjector.osl
• SphericalProjector.osl

GetParticleAge.osl does not work on both V-Ray and V-Ray GPU because the paLife attribute is not supported.

Here is an example of what GPU-friendly shaders are allowed to do:

• string initialization with a string literal, e.g., string a = «foo»;
• string initialization with another string, e.g., string b = a;
• string assignments, e.g., a = b; b = «foo»;
• equality checks: a == b; a != b;
• passing strings as arguments to function calls, e.g., string a = «foo»; bar(a);
• returning a string from a function, e.g. string bar()

Nоte that using any other string operations and string routines may lead to undefined behavior.

Additional Notes

• V-Ray GPU supports map channels from 0 to 15.
• V-Ray GPU only supports normal maps in tangent space.
• Currently, V-Ray GPU does not support animated formats for input.

Better in every way.

Blender Foundation and the online developers community proudly present Blender 3.5!

Featuring a viewport compositor, vector displacement sculpting, built-in hair assets, many lights sampling for Cycles, and so much more.

Released March 29th, 2023

The curves-based hair system first introduced in Blender 3.3 takes a major leap in this release.

KEEP WATCHING

Follow the full step-by-step tutorial.

Creating and grooming fancy hairdos is easier than ever.

Any kind of hair, fur, or grass is possible. Powered by the flexibility of Geometry Nodes.

With great power comes great complex-ability, so Blender now includes hair assets to make your life easier.

POWER WITHIN

For the first time ever, Blender ships with built-in assets!

The Essentials asset library comes with 26 Hair assets split into categories: Deformation, Generation, Guides, Utility, Read, and Write.

For the best results, VDM textures should be in OpenEXR format, with Color Clamping disabled.

3ds Max: Issues & Errors Solved

We’ve noticed that there have been a few issues and errors reported about 3DS Max, so we’ve outlined solutions below what we’ve come across.

Issue:

The Shape Map is leaving Tile lines visible in 3ds Max 2016 Extension 2 and 3ds Max 2017-2018

Causes:

Shape Map Alpha channels are set incorrectly, and the Fill Background feature is checked On.

Solution:

• In 3ds Max, open the Material Editor (either Compact or Slate) and check each material using a Shape Map.
• In each Shape Map type, check the Alpha button, using Image Alpha as the source.
• Turning off Fill Background also enables the textures to be applied as “decals” on the surface and prevent hard edge lines from showing up in your renderings. Works on Diffuse, Bump and other map slots.
• To scale the Shapes on the surface of scene objects, use the Shape Map’s U and V tiling features. Uncheck the Tile buttons to place a single, non-tiling copy on objects in the scene.

Issue:

After installing Extension 2 for 3ds Max 2016, the Vector Map, ShapeMap, TextureObjMask and TextMap types don’t appear in the Material Editor Browser (either Slate or Compact.)

Causes:

This is a known defect logged with Autodesk developers, although it wasn’t reproducible on most machines, and is not present in 3ds Max 2017 or 2018.

Solution:

If possible, upgrading to 3ds Max 2017 or 2018 will eliminate this issue.

To fix this problem in 3ds Max 2016, users must be comfortable making changes to their Windows registry.

Warning!
Problems caused by improperly editing the Windows registry could render your computer operating system unusable. Microsoft provides a wealth of critical information that you need to know about the registry in the Microsoft Knowledge Base. Use the Microsoft Registry Editor only at your own risk and only after backing up the registry as outlined for your operating system in the Microsoft article How to back up and restore the registry in Windows and in the related solution How to backup the system registry. Additional information about the registry is also contained in the Help topics in the Microsoft Registry Editor.

If so, then proceed with the following:

1. Close 3ds Max, and in the Windows Start menu, type regedit. The Registry Editor appears.
2. Navigate to the HKEY_USERS\S-1-5-21-1935655697-515967899-682003330-13859\Software\Autodesk\3dsMax\18.0 key. (The exact numbers after the “S-1-5-21…” header may be slightly different on different systems.)
3. Open the Plug-ins_ENU key. There should be a very long list of plug-ins.
4. Scroll down to the textureobjmask.dlt key and delete it.
5. Scroll down to the vectormap.dlt key and delete it.
6. Close the Registry Editor, reboot the PC, then re-launch 3ds Max 2016.
7. Open the Material Editor and the Material Browser. The Vector Map, ShapeMap, TextureObjMask and TextMap material types should now appear.

The above solution also works for the reported issue: After installing Extension 2 for 3ds Max 2016, the Vector Map, ShapeMap, TextureObjMask and TextMap types don’t appear in the Material Editor Browser (either Slate or Compact.

Issue:

3ds Max 2016-2018 cannot archive .ai or .pdf files loaded as Vector Maps

1. If the file path for the loaded .ai or .pdf file is “stripped” out in the 3ds Max Asset Tracking menu, the file no longer stays linked in the Material Editor and must be reloaded and re-linked manually.
2. Archiving the scene file using the File > Save As > Archive Feature, or the Utilities > Resource Collector will gather and zip up all bitmaps used in the scene, but will not include .ai or .pdf files.

Causes:

Both of these behaviors are logged as defects for the 3ds Max development team and are under review.

Solution:

1. Manually reload and re-link the .ai file in the Material Editor (browse to the new file location, using UNC paths, and re-link the file.)
2. Open the Archived .zip file and manually drag the missing ai file into the .zip archive to include it, the re-close the .zip file.

Issue:

Dragging a map layer above or below another layer in the 3ds Max 2017 Composite map type doesn’t “stick” — the dragged map snaps back to its original position when exiting the Composite map, then opening it again.

Causes:

This was logged as a defect by Autodesk developers, and was fixed in 3ds Max 2017, Update 2. It is also fixed in 3ds Max 2018.

Solution:

Log into your Autodesk Account > 3ds Max > Upgrades and Add-ons, then download and install Update 2 for 3ds Max 2017. This should fix the issue.

If the update isn’t available, one workaround would be to clone existing maps to create new layers, drag the desired maps into those layers and modify their Composite settings, then delete the redundant/undesired maps from the stack.

We hope some of the solutions to the reported issues we’ve outlined above assist you with any problems your having with 3DS Max. If you have or are having any other issues with any of your other products, you can contact us HERE