Verge3D 3.4 pre1 available!

Multi-line and Script Puzzles

A puzzle for typing multi-line text is now available in the Text category. It can be used with all puzzles that accept text as input.

We also implemented a puzzle for executing JavaScript, available from the Advanced category. Coupled with the above-mentioned multi-line puzzle, it allows you to use line numbering and syntax highlighting when editing your code.

Blender-Specific

You can now create custom real-time shaders using the Open Shading Language (OSL). This experimental (for now) feature can be enabled in Blender in the Scene tab by switching to Cycles first and then turning on the corresponding checkbox:

As a result, you’ll be able to use the Script node in your material.

The shaders themselves can be written using OSL code, or borrowed from some shader library. For example, here is how the code for the 3ds Max’ checker shader looks like:

shader Checker
[[ string help = "A simple Checkboard OSL sample shader",
   string category = "Textures"
]]
(
  point UVW   = vector(u,v,0) 
  	[[ string help="The position to shade. Default to the standard UV space." ]],
  float Scale = 0.25, 
  color Color1 = color(1,1.0,0.2),   
  color Color2 = color(0.2,0.2,1.0),  

  output color Col = 0
)
{
	point p = UVW / Scale;
	int x = (int)mod(p[0],2.0);
	int y = (int)mod(p[1],2.0);
	int z = (int)mod(p[2],2.0);

	if( ((x%2) ^ (y%2)) == (z%2) ){
		Col = Color1;
	} else {
		Col = Color2;
	}
}

3ds Max-Specific

We continued our work on supporting OSL shaders. For this update, we supported the OSL node called HDRi Environment (3ds Max 2021 only). This node allows to create environment lighting with custom background and ground surface. Uber Bitmap is another OSL node supported for this update.

Also, a new OSL-to-GLSL converter is now used in the exporter. It now works more robustly and generates more compact code.

Arnold’s node Map to Material is now supported. This node allows you to create custom shaders by using Maps.

The option in the Export Settings called Export within playback range now correctly works.

We fixed a rare exporter crash when a mesh without vertices, which at the same time has a UVW Map modifier applied, is present in the scene.

Other Improvements

The set style and set attribute puzzles now work in IE 11.

The replace texture and get texture param puzzles now correctly work with video textures.

The JavaScript method Material.toJSON() no longer crashes with node-based materials.

We added a new chapter to the User Manual where we outlined some hardware limitations you may encounter when creating your scenes. At the moment, it provides clarifications with regard to the “Too many attributes” error.

web wrote:

Think I found it. It seems to be in the “matGetEditableTextures” function

glad it’s working for you!

GLiFTeK wrote:

EDIT: do variables still have to be “passed” to the javascript text funciton as they would in Call JS app.ExternalInterface

yep!

GLiFTeK wrote:

how can one not use call js, use the new txt script puzzles, and still include the variables.

you can save your variable in some global namespace, for example, or even to window namespace.