Finally got the picking/snapping events wired up right for the #xeokit measurement tools.

The challenge was how to re-use picking/snapping results across all the bits of xeokit that consume them (camera navigation, measurement, slicing..), reusing the results wherever possible, to avoid redundantly re-doing any picking/snapping. That is, without having mutually-exclusive modes for the tools, ie. where you could be slicing, measuring navigating all at the same time. 😅

On the home stretch now for the next #xeokit SDK beta release with all the essential tests running AOK.

One big doozie task remaining: reorganize the live examples by topic, with alias links.

But in the meantime - check out some sweet pointer snapping demos, designed to make measuring your buildings way easier. This uses pure GPU - ie. no nearest-neighbour searches that choke on on zillions of objects.

Playing around with the #xeokit #bim viewer. Funny features. The slicing tool does not work very exactly. But pretty nice for a web based viewer. Are there better (free) ones?

you can test it in this demo:
https://xeokit.github.io/xeokit-bim-viewer/app/index.html?projectId=OTCConferenceCenter&tab=storeys

WIP on #xeokit's 3D picking system: https://xeokit.github.io/sdk/docs/modules/_xeokit_collision_pick.html

Fun feature: collision/picking works "headless" on model representations without needing a Viewer. This means we can use the collision system for model analysis, in scripts etc.

"Holiday hacking is going well! Next version of #xeokit will use an entity-relationship graph to represent runtime model semantics 😎"
@xeolabs

#xeokit users, a quick question!

I'd like to have a more expressive way to represent semantic (AECO, IFC, CAD..) data in our JavaScript-based #xeokit viewer, that has

- low memory footprint

- supports SPARQL queries

- expressed relationships (eg. containment, adjacency...) as in-memory ER/ORM graph that we can query

Currently, we have a parent-child tree that only expresses containment.

Any tips on libs to look at, techniques etc? ORM, ER...?

#ifc #bim

Some of our swag at our #xeokit and HyperBIM stands at BIMWorld 2022 - traditional Polish sweet called Krowki. Like toffee, but super soft and even more toffee-like. Drop by stand #233 for a sugar hit.

#bim #ifc #opensource

On the road to BIMWorld Munich '22 - we'll be at Booth 233, and we even have xeokit candy!

#xeokit #bim #ifc #bimworld #opensource

#introduction
Hi, I'm Lindsay Kay, a developer of open source browser graphics libraries for architecture and construction.

Since 2009 I've been working on ways to squeeze more juice out of graphics APIs like WebGL (and lately WebGPU) so that we can view bigger medical & engineering models in the browser.

Before that, I was a Java/C++ dev in NZ with a thing for all that OOP design theory, which I still think is pretty rad.

Interests: #IFC #BIM #AEC #openSource #WebGL #WebGPU #xeokit

#introduction
Hi, I'm Lindsay Kay, a developer of open source browser graphics libraries for architecture and construction.

Since 2009 I've been working on ways to squeeze more juice out of browser graphics APIs, so that we can view bigger medical and engineering models in our computers.

Before that, I was a Java/C++ dev with a thing for all that OOP design theory, which I still think is cool.

Interests: #IFC #BIM #AEC #openSource #WebGL #WebGPU #xeokit

#xeokit #floss #3dprinting for the #browser - presenting now https://meet.jit.si/openbim