Every year, BIM World event is kind of unmissable. 2h hours of train make this travel pretty easy – even with the social movements of the day, which did not affect us by the way.
Since 2019, BIM World is held at Paris Expo – Porte de Versailles which is the biggest exhibiting centre in France and recognizable by his central ring of screens.
After a complete tour of the show to see most of the exhibitors, we went to the Autodesk booth. We were happy to discuss with some “Autodeskers” about APS and products news.
We attended some great presentations around the show.
We attended to four talks. Starting with the future of technologies in AEC, where we had a great preview of the way AI can be more integrated into current software. Followed by two different cases about train tracks construction and train station building.
Then, for the second time of the day we followed the vision of XR presentation, from the current VR products to the new developments on their roadmap.
We spent our second day discussing with some acquaintances and customers. As usual, for us the greatest value added of this event is to strengthen relationships with people we already know or have not met in person.
The focus was made on digital twins and sustainability and we were a little disappointed about the lack of great innovation of some exhibitors on these subjects compared to the previous years.
But at least some of them are trying to attract people on their booth with childhood references !
This week, there is the Laval Virtual event which is dedicated to VR / AR. I will be there on Thursday and I will give you my thought about it.
The Autodesk Platform Service – APS (formerly Forge) Viewer has a built-in extension to take measures of 2D and 3D models.
Sometimes, you can have a model or a sheet with inconsistent units ending up with wrong measure values. So a calibration tool is allowing you to set the right length between two points. It defines a scaling factor applied to all measures.
How to make it persistent?
Here is some tips to get the current calibration, save it and then set it when the viewer loads.
Access to the measure extension.
For that, we can wait for the EXTENSION_LOADED_EVENT and check if the extension id is Autodesk.Measure to be sure that the extension is loaded.
viewer.addEventListener(Autodesk.Viewing.EXTENSION_LOADED_EVENT, function(event){
if(event.extensionId === 'Autodesk.Measure')
{
//Now we are sure that the extension is loaded
}
});
This tool provides valuable methods and we are going to use these three.
// Return the calibration unit
calibrationTool.getCurrentUnits();
// Return the current factor
calibrationTool.getCalibrationFactor();
// Modify the calibration factor value
calibrationTool.setCalibrationFactor([NEW SCALE FACTOR])
React to calibration event
We don’t want to get the last calibration manually, so we can subscribe to the event emitted when you finish a calibration.
viewer.addEventListener(Autodesk.Viewing.MeasureCommon.Events.FINISHED_CALIBRATION, function(calibration){
// Now we have the latest calibration factor so we can store it
});
Making an extension to save calibrations and set the latest
Now that we have all the functions we need, let’s create an example to demonstrate this.
First, we will create a custom viewer extension with a button in the toolbar. As I want to add some UI, this extension is going to open a panel to display our calibrations values and some action buttons:
For now, we only have a simple extension with a toolbar button that opens a UI panel. Let’s add some logic to it.
As explained before we can subscribe to the FINISHED_CALIBRATION event, to get the latest calibration and make a request to the server to store it in database. For this example, I am using a simple text file, but it can be easily improved with a database.
We can use the docking panel to display current values, show the different calibrations that we got from our database and implement actions in our interface.
Take a look at my demo below. I change the calibration factor from previous calibrations with a fresh new calibration and we see the measure difference. Everything done here in this 3D view will work the same in a 2D view.
The complete code of this example is available on my github.