The deprecated decodeDracoFile method should be removed and replaced with a parse method similar to other loaders. Currently decodeDracoFile does not propagate errors, and should do so. So probably a signature like:

dracoLoader.parse( arrayBuffer, /* options, maybe? */, onLoad, onError );

Issue details

Camera.unproject does not return original value

Reproduction steps/code

    public void create() {
        Vector2 tmpvec = new Vector2();
        tmpvec.set(0, 0);

        Stage stage = new Stage(new ScreenViewport());
        stage.stageToScreenCoordinates(tmpvec); // has the correct screen coords;
        stage.screenToStageCoordinates(tmpvec);
        

<a-scene>
  <a-entity camera></a-entity>
</a-scene>

With the above a default camera is injected incorrectly

Documentation

The connection between the docs for nodeMaterial blocks and the API needs to be tighter. Can we add the link to the API doc page https://doc.babylonjs.com/api/classes/babylon.nodematerial to the node material doc page https://doc.babylonjs.com/how_to/node_material at the start of the list of available blocks?

We should also add language around the setting the value of a block:

Frequent bug: while sorting by y-coordinate, the vertices are sorted, but the data coming with the vertices is not.
Gouraud shading, forgot to sort intensities

In my case I was calculating a barycentric coordinate of one vertex and assigning it to a different vertex by mistake.
The artifacts looked exactly the same as you presented, if it is the same problem then the description could be

I think this is a simple issue.

I try the simple demo pbut I only get the next error:

Uncaught Error: Zdog.Illustration element required. Set to null
at r.s.setElement (zdog-docs.min.js:18)
at r.s.create (zdog-docs.min.js:18)
at new r (zdog-docs.min.js:5)
at prueba.js:5

  |s.setElement zdog-docs.min.js:18

  s.create zdog-docs.min.js:18
  r zdog-docs.min.js:5

Sandcastle example: open any basic shape (e.g. Rectangle) and try to set an outlineWidth, or search "outlineWidth" on this tracker and read any of a bunch of existing issues, starting with #40 (!)

Browser: any

Operating System: Windows only, apparently

Since the very beginning of Cesium, people have been trying to use the outlineWidth property on EllipseGraphics, RectangleGraphics, Po

The icons for "Multi-view Images", "Volumetric", etc are cute, but it is (1) impossible to use them for searching, and (2) hard to remember what they mean. Maybe use text keywords (tags) instead?

Priority

Low

Issue Description

In the screenshot below, LAST MODIFIED shows Sat, 26 Oct 1985 08:15:00 GMT,which is incorrect.

Expected Results

LAST MODIFIED shows correct timestamp, so that users know when this file is modified.

Screenshots/Related files

![image](https://user-images.githubusercontent.com/25629006/52917615-75906980-32a2-11e9-8825-10885a5955d2

Dear YadiraF,
Thanks for your help!

By modifying demo_texture.py, I tried to rotate the vertices of one image then change its texture to another image's texture.

In "1. 3d reconstruction -> get texture.", I added this line :
rotated_v = mesh.transform.rotate(vertices.copy(), [30, 0, 0]) # pitch, yaw, roll : positive : looking down, looking left, tilting head right

And I didn't modify

From https://en.wikibooks.org/wiki/OpenSCAD_User_Manual/Using_the_2D_Subsystem#polygon :

paths

• ...
• multiple vectors
  • Creates primary and secondary shapes. Secondary shapes are subtracted from the primary shape (like difference). Secondary shapes may be wholly or partially within the primary shape.

This makes it sound like any secondary paths act as purely "negative

I'm noticing that png files with alpha values don't have the setColor alpha values applied when using Flat3D shader (ex. setColor({1.f, 1.f, 1.f, 0.f}) still displays the image).

I'm currently using StbImageImporter for image importing.

Other Peculiarities

• png images with transparent backgrounds have their transparent colours displayed as hard colours (ex. black or white instead of tr

Lines 37 and 38 of https://github.com/gfxfundamentals/webgl-fundamentals/blob/master/webgl/lessons/webgl-how-it-works.md state

That’s all very interesting but as you can see in our examples to up
this point the fragment shader has very little info per pixel.

"to up" should be "up to"

How do I find these tools in the 2.8 interface? If you've updated to 2.8, why haven't the instructions been updated to match?

I have noticed some of the routes end with an underscore like the following.

http://docs.claygl.xyz/api/clay.Shader_.html

when the underscore is removed the route works as expected.
http://docs.claygl.xyz/api/clay.Shader.html

Expose raytracing render-path in Armory and document implementation details.

It would be helpful to document the minimum version(s) of Mac OS X / macOS that are supported by the binaries/source.

It seems that for v1.0.0-beta.6 binaries the minimum Mac OS X version is 10.10 (which I guess is driven by the use of Qt 5.9).

[Unrelated: This is a really nice overview of the evolution of the project and your process/learning: <http://docs.dust3d.org/en/latest/origin_and_fu