Open Cloud

Open Cloud VisualizeJS libriry is based on Visualize SDK (recompiled to javascript with emscipten). So there is no difference, but sometimes there is small delay with appearing new functionality.

To increase the storage limit you need to send request to the server:
PUT /api/users/<userId>

Yes, each user have it own storage limit. For сloud.opendesign.com each user has 200 MB available (this is default value) but you can set up a server locally and change the limits.

In this example  functions like "zoom in", "select", etc. with fingers don't work on iPad/iPhone because this example was designed for desktop solutions.

Yes, the cloud server is already included in the trial archive, so you can install a trial crowd server, for example.

When you select obj file to upload, there is another window ask to select resource files. In this second window you need to select mtl file and it will be uploaded with obj file.

Web viewer supports the following formats:

• DWG
• DGN
• DWF
• DXF
• OBJ
• PDF
• RCS
• RFA
• RVT
• IFC
• NWC
• STL
• NWD
• VSF

GLB file formats are not supported.

Yes, you can find it on this page. The demo viewer application is available here (please note, that you’ll need to register once more) : https://cloud.opendesign.com/docs/index.html#/

We do not provide these tools for the mac platform for now.

Unfortunately, the VisualizeJS library does not support working with several files at the same time. But you can create 2 instances of the library and use them with different canvases; here’s an example.

It is possible to view IFC files using our Open Cloud. Our Cloud viewer (based on Open Cloud SDK) illustrates it.

The most probably Web Viewer can't reach Open Cloud Server. You need to perform the next steps:

1. Change Web Viewer configuration: https://cloud.opendesign.com/docs/index.html#/webviewer?id=build. Parameter api_host should point to the IP address of the Open Cloud Server.
2. Run Open Cloud Server with urls " dotnet OpenCloudServer.dll --urls http://0.0.0.0:8080"

To create another user please use Open Cloud Server API.

If you want to proxy websockets requests through the Nginx server then you can use the standard instruction, for example this.

Example for selection sub entitiy and more lower level:

var opt = new tlib.OdTvSelectionOptions();
opt.setLevel(tlib.SelectionLevel.kSubentity);
opt.setMode(tlib.SelectionMode.kCrossing);

var selectionSet = viewer.activeView.select([0, 0, 1920, 1080], opt, viewer.getActiveModel());
var itr = selectionSet.getIterator();

for (; ! itr.done(); itr.step()) { var subEntity = itr.getSubEntity(); console.log('sub entity'); }

We are using our own graphic engine, it's Visualize with our render implementation.

You can even implement communication between your backend, some your server and our cloud server. For example if you want to do some operations with DWG files, so you can download it on your backend, perform some operations and upload the new version on the Open Cloud server.

Actually not, you do not need the GPU on the backend. It’s possible the all operations for conversion source files like DWG and so on to our VSF, these operations works without GPU unit.

Yes, you can implement converter to visualize stream format and then it's possible to convert the visualize stream format to different other formats for rendering in the browser, for example.

We are storing only geometry data in the browser. So from all files like revit, .dwg, we extract the geometry data, we use .vsf (from Visualize project), and this data streamed directly through Open Cloud server to the browser. So only this data is stored in the browser.

We use .NET core to point for our Open Cloud server and we use C++ code for our jobrunner and File Converter tools. On frontend we use JavaScript, but it used for our demo viewer application, but it’s only a sample.

There are 2 parts of our Open Cloud solutions and they’ve got different requirements. We’ve got Open Cloud server, that written in .NET core and actually it doesn’t have some heavy parts, heavy functionality. But the second part of our solutions is jobrunner, it actually, this part perform the really heavy work, because it performs opening of really heavy file like revit, .dwg and it will be depending on the file size, on the internal structure of this size.

The main idea that you need provide the really good hardware for jobrunner part. For Open Cloud server you can use some middle-size of your virtual instances.

Jobrunner is light application, which run File Converter application to convert files to another file format or to extract geometry data or properties data. The controller and the workers: we decided to leave them for supporting. So we’ve got tests, some basic documentation about it using. But currently we don’t develop them, they quite stable, but we’re don’t moving forward to support some new features with these tools.

The handle is identification of the object from the native database. It means that through this handle you can connect the visualization, the object that you can see in the browser and native objects in the original file, the source file. It is represented as string, because from the Open Cloud server you obtain all the data in JSON format.

You can start from this article.

Web application should connect to Worker app through WebSocket connections. Through WebSocket, you can send commands to be executed on the Worker side.