What you can open
Drag a file onto the Viewer, choose File › Open… (Ctrl+O), or open several files, a folder or a .zip at once. The model opens first and its results join it.
MIDAS Civil and MIDAS Gen
| File | What it holds | Read in |
|---|---|---|
| .mct, .mgt | MIDAS text model: nodes, elements, sections, supports, loads, stages, tendons | Server |
| .mcb, .mgb, .mgbx | MIDAS project files (Civil and Gen, including NX) | Server |
| .xlsx, .xls, .txt, .csv | Result tables exported from MIDAS: displacements, reactions, forces, stresses, modes, stages, moving load, spectrum, time history, buckling | Server |
| .nfxp, .GAX1 | MIDAS's own result files (Civil and Gen) | Server |
| .acs, .rcs | Design check reports, with MIDAS's own O.K. / N.G. verdicts | Browser |
| .out | Analysis log: warnings, errors, total weight and timings | Browser |
Open the model first, then its results. Text files in Korean, Chinese and Japanese code pages are recognised automatically.
ETABS
| File | What it holds | Read in |
|---|---|---|
| .e2k, .$et | ETABS text model (the .$et is the backup ETABS keeps beside the .EDB): stories, frames, walls, floors, sections, loads and combinations | Server |
ETABS result tables are not read yet.
Abaqus
| File | What it holds | Read in |
|---|---|---|
| .inp | Input deck: parts, assembly, materials, sections, steps, loads, interactions | Browser |
| .cae | Abaqus/CAE model database: parts, instances, materials, sections and steps | Browser |
| .odb | Output database: the mesh and every field and history output. Opens with or without its deck | Browser |
| .fea-results.json | Results saved by the Viewer's exporter script, for very large jobs | Browser |
| .msg, .sta, .dat | Job messages and status, read beside the results and explained | Browser |
The desktop app can also run the exporter script with your own Abaqus, and opens result files of several gigabytes.
IFC and Revit
| File | What it holds | Read in |
|---|---|---|
| .ifc, .ifczip | Building models from any BIM program (.ifczip is unzipped for you) | Browser |
| .rvt | Revit models, read without Revit and shown as their IFC equivalent | Server |
OpenSees
| File | What it holds | Read in |
|---|---|---|
| .zip | A run: its Tcl script and the recorder output files | Browser |
| .tcl, .py | An OpenSees or OpenSeesPy script, run with the OpenSees or Python on your computer | Desktop |
OpenFAST and NEMOH
| File | What it holds | Read in |
|---|---|---|
| .outb, .out | OpenFAST output channels (binary or text) | Browser |
| .zip | A whole run: channels, the .fst and the VTK meshes it wrote | Browser |
| .fst, .bts, .wnd | OpenFAST input decks and wind files | Browser |
| .cal | A NEMOH project (Nemoh.cal) | Browser |
Running OpenFAST or NEMOH needs the desktop app and the programs installed on your computer.
VTK and CalculiX
| File | What it holds | Read in |
|---|---|---|
| .vtu, .vtp | VTK XML unstructured grids and polydata, ASCII, binary or appended | Browser |
| .vtk | Legacy VTK, ASCII or binary | Browser |
| .pvd | A ParaView series of frames (open it with its files, or as a .zip) | Browser |
| .frd | CalculiX results | Browser |
Why are some files read on our server? The MIDAS, ETABS and Revit readers are our own work, built without those programs, and we keep them off the public web page. Your file is read in memory and the model sent back; nothing is stored. See the privacy notice. The desktop app reads every file on your own computer.