xeogl | based 3D engine for technical visualization | Graphics library

by xeolabs JavaScript Version: v0.9 License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | xeogl Summary

xeogl is a JavaScript library typically used in User Interface, Graphics, Three.js, WebGL applications. xeogl has no bugs, it has no vulnerabilities and it has medium support. However xeogl has a Non-SPDX License. You can install using 'npm i @wikifactory/xeogl' or download it from GitHub, npm.

xeogl is a data-driven WebGL-based engine created by xeolabs for 3D visualization in the browser without using plugins. xeolabs does not actively maintain xeogl, however we provide it here under an MIT lcense in case it's useful to the 3D Web community. If you need an actively-developed WebGL engine with all the capabilities of xeogl, plus more performance and features, consider using the xeokit SDK instead. Follow xeolabs on Twitter for updates: @xeolabs.

Support

Quality

Security

License

Reuse

Support

xeogl has a medium active ecosystem.

It has 1088 star(s) with 262 fork(s). There are 69 watchers for this library.

It had no major release in the last 12 months.

There are 57 open issues and 216 have been closed. On average issues are closed in 153 days. There are 5 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of xeogl is v0.9

Quality

xeogl has no bugs reported.

Security

xeogl has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

xeogl has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

xeogl releases are available to install and integrate.

Deployable package is available in npm.

Installation instructions are not available. Examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi has reviewed xeogl and discovered the below as its top functions. This is intended to give you an instant insight into xeogl implemented functionality, and help decide if they suit your requirements.

Build stroke string
Main RenderMeshDraw function
Creates a new outlayer object .
Creates an infotlet definition .
Define out an outbound transition object
Makes a function that will simulate a WebGL context .
load a node
Parse data from FBXTree . Objects . Geometry
load information from a texture object
Combines multiple regex patterns into a single string .

Get all kandi verified functions for this library.

xeogl Key Features

No Key Features are available at this moment for xeogl.

xeogl Examples and Code Snippets

No Code Snippets are available at this moment for xeogl.

Community Discussions

Trending Discussions on xeogl

stats.js shows FPS 0~2, render movement too slow

QUESTION

stats.js shows FPS 0~2, render movement too slow

Asked 2019-Oct-25 at 17:09

i'm beginner for three.js also using it for BIM project, when i load a gltf file of ~25mb i can barely move the whole object and stats.js monitor shows fps of 0~2 at max gltf file : https://github.com/xeolabs/xeogl/tree/master/examples/models/gltf/schependomlaan im using THREE js with vuejs

...

ANSWER

Answered 2019-Oct-24 at 20:54

On filesize —

Draco compression reduces network size, but not the final amount of uncompressed data that must be sent to your GPU and rendered. If your original mesh was 100mb and you compress it to 25mb, you will still get the framerate of the original 100mb mesh. Aside: Using the -b option of glTF-Pipeline will reduce the size by another 50%, to 13MB, but again doesn't affect FPS.

On framerate —

This model contains 4280 meshes¹, each requiring a GPU draw call. That is the source of your low QPS, and unfortunately it's a common problem in BIM models. You'll need to merge these meshes (in a program like Blender, or after loading in three.js) to as few as possible. A model like this should require < 100 draw calls, or even as few as 1.

¹ To see this, try opening the model on https://gltf-viewer.donmccurdy.com/ and opening the JavaScript console. You should see a printout of the scene graph, which will contain many different meshes.

Source https://stackoverflow.com/questions/58544126

Community Discussions, Code Snippets contain sources that include Stack Exchange Network