Description of the problem

It seems lack of some properties in MeshPhysicalMaterial document.

https://threejs.org/docs/#api/en/materials/MeshPhysicalMaterial

Ever what I noticed are

• clearcoatNormalScale
• clearcoatNormalMap
• sheen
• transparency

We should update.

Three.js version

• Dev
• r113
• ...

Browser

• All of them
• [ ]

Description:

• A-Frame Version: <script src="../../../dist/aframe-master.js"></script>
• Platform / Device: Windows, Google Chrome Version 81.0.4044.113
• Reproducible Code Snippet or URL:
  All of the text demos linked in components/text

Error message:

Uncaught TypeError: navigator.xr.requestDevice is not a funct

Reading the documentation, it is not entirely clear to me what are the differences of the joint control modes supported in pybullet.

I try to recap them here, please @erwincoumans feel free to jump in to add more details and address holes in my understanding.

Let's assume that in all cases (excluding torque), the reference error is the following:

error = kp *  (pos_des - pos) + kd * 

If a material has an existing prefiltered cubemap set, then updating the material's cubemap property material.cubeMap = cubemapAsset.resource will have no effect as this call doesn't update the prefiltered textures in the material.

Changing a material's cubemap should at least clear old cubemap data, and ideally update it to the new maps.

The ability to move around by rolling a hamster ball

Like this: https://gfycat.com/OpulentExhaustedGoldenretriever

I'll try and contact the author on reddit: https://www.reddit.com/user/Reil

In section 3.4 (Feature Dependencies), you'll find tables describing the features and their dependencies in terms of user consent and feature policy.

In particular, there's the information in the screen capture I have included here:

The table says that local requires consent for

Currently, the headless mode uses default parameters from PyChromeDevTools for connecting to a chrome headless instance.
https://github.com/maartenbreddels/ipyvolume/blob/e68b72852b61276f8e6793bc8811f5b2432a155f/ipyvolume/headless.py#L53
However, if you use a chrome headless running as docker instance and want to connect from another docker instance (e.g. when using docker-compose), the headl

ITMS-90809: Deprecated API Usage - Apple will no longer accept submissions of new apps that use UIWebView as of April 30, 2020 and app updates that use UIWebView as of December 2020. Instead, use WKWebView for improved security and reliability. Learn more ( https://developer.apple.com/documentation/uikit/uiwebview ).

react-viro uses UIWebView component, so since April 30 2020 it's will be rejec

The default value 0 0 -1 does not match type vec3.

kframe/components/sun-sky/index.js
line 10
sunPosition: {type: 'vec3', default: '0 0 -1', is: 'uniform'}
should now be
sunPosition: {type: 'vec3', default: { x: 0, y: 0, z: -1 }, is: 'uniform'}

Replace aframe version from 7.0 to 9.2 in head script, the network doesn't work anymore...
As a note, it works with aframe 8.0 ; and it seems to be linked to the fact that networked components are in a parent one.
https://github.com/networked-aframe/networked-aframe/blob/master/examples/tracked-controllers.html

Running the tabs default launch command (-t) does not respect redirects at the target.

$ node . -t https://aframe.io/a-painter

☝️ The above will error, even though the server will redirect to https://aframe.io/a-painter/ and serve HTML there:

$ curl -i https://aframe.io/a-painter
HTTP/1.1 301 Moved Permanently
Date: Mon, 03 Jun 2019 20:10:27 GMT
Content-Type: text/ht

Hello, it would be great if you could add some 3d text models. Thanks in advance :-)

It is now mapped to the touchpad. After giving a lot of demos most people trigger the teleport by mistake and it's very confusing.

Is it known that the inspector is not longer opening using the keyboard shortcut on Windows machines? I'm running Firefox 71.0... I'm sure it's not just my computer as I had it checked by someone running the Udemy course I've been following.

Cheers.

It may save a few headaches to mention in either the README or on the pages themselves the secure context requirement for WebXR, needing either https or localhost/127.0.0.1, and how to go about that. Via immersive-web/webxr-samples#47

Create a wiki page that discusses the combinations of these parameters:

• fixed delta time
• application framerate
• rigidbody interpolation
• frame optimization (provider setting)
• physics extrapolation (provider setting)

Some of the combinations of settings are good and some are bad, and it's not immediately obvious which is which.