• Updated to 4.8 .NET Framework.
  • Added EV code signing certificate to reduce issues with antivirus and Windows SmartScreen.
  • Updated license manager


Bug fixes:

  • Fixed a crash on application launch due to Windows settings on file extension visibility.
  • Fixed a crash when displaying numeric results with extremely small models and low decimal precision setting.
  • Improved automated crash reporting to cover more scenarios.



  • You can now double-click on any column in the results table in the Iterative modes to load that iteration in the SOLIDWORKS model view (if Show processed hull is enabled), and also run Resistance calculations on that specific iteration.
  • Added an ability to generate SOLIDWORKS macro that will launch FLOATSOFT from within SOLIDWORKS. To generate this macro, click the dedicated button in the Settings menu.


  • Application will now display only the final solution render in the SOLIDWORKS model view area. The intermediate steps will not be shown. “Debug mode” has been added to Settings window that reverts this behavior to earlier one.

Bug fixes:

  • Fixed a bug that caused wrong units in the results table header row in Iterative modes.
  • Fixed SOLIDWORKS file extension getting added to the exported file names.
  • Fixed a crash when opening Resistance window with dual-monitor setup.
  • Fixed a crash caused by memory file usage by other applications.
  • Fixed a crash when taking CoG from invalid SOLIDWORKS files.
  • Added protection for resistance calculations with invalid models and unrealistic immersion.
  • Added write protection to exported files.
  • Fixed message boxes appearing behind splash screen.
  • Fixed Iterate Through Trim mode allowing invalid trim values.



  • It is now possible to adjust the smoothing of the FLOATSOFT solver algorithm to improve performance and reduce the number of failed solutions. The slider to adjust it can be found in Settings window. Increase this slider if FLOATSOFT jerks the hull model around, decrease if you get “no solution” errors.
  • FLOATSOFT will now color results in red if some of them are not valid to make a clear visual indication.
  • One additional report – Sink Rate. Displays approximate sink rate of the vessel, expressed in displacement units per length units, calculated based on waterplane area.


  • Minor GUI restructuring. Simulation attempt limit in the Settings window has been renamed to Solver attempts, because the solver is now used throughout the application, not just in Simulation mode.



  • It is now possible to limit the range of heel and trim angles when using Simulate Natural Buoyancy mode. This allows for a faster solution, and also to narrow down the required solution when the vessel can be stable in multiple orientations. The limits can be set via Settings Simulation angle limits.


  • If SOLIDWORKS API call fails to provide valid measurements for the hull at specific orientation and submersion due to invalid geometry, FLOATSOFT will attempt to slightly adjust the draft until a solution is possible. If this adjustment is included in the solution that is used to take final measurements, there will be a warning message to notify the user that the results might be slightly off, rather than providing no results at all.
  • Added a splash screen and changed the application icon to the new company logo.


  • Improved resilience to crashes due to invalid geometry SOLIDWORKS bodies.
  • Added a missing displacement check to Simulate Natural Buoyancy mode.
  • Fixed the Feedback window functionality and automated crash reports.



  • Fixed incorrect Metacentric Height report when analyzing hulls with multiple underwater bodies at 0° of heel.


  • Hydrostatics Calculator is now rebranded as FLOATSOFT, after the company name.
  • Implemented a new licensing system. Old license keys will still be valid for versions prior to 1.36. If you are an existing customer and did not receive a new license key, please contact us at info@floatsoft.net.
  • Added more verbose error messages for easier debugging.
  • Local logging is disabled until further notice.

Getting support

If you encounter any bugs, crashes, inaccurate/inconsistent results, or otherwise suspect any faults, please do not hesitate to use the Feedback button in the Main window, or contact us at support@floatsoft.net. Our team is standing by to fix problems and roll out an updated version to you as soon as possible. If you are submitting a bug report manually (not via Feedback), please include all of the following:

  1. The SOLIDWORKS .sldprt file that you were analyzing;
  2. The [model name].cfg and [model name].mem files in the Config and Memory folders next to the FLOATSOFT executable;
  3. A detailed description of the steps you took so we can re-create the issue.

Your help in finding and eliminating bugs is greatly appreciated!

Solutions to common issues

Error “FLOATSOFT failed to perform a required operation with this hull model”

The cause for this error is an imperfect Operations3 API call implementation by SOLIDWORKS that FLOATSOFT uses to cut the model hull at the waterline. This operation sometimes fails at a very specific hull orientation and immersion. If this occurs repeatedly, try to reduce the complexity of the model (roll back the Feature Tree to skip the features that are irrelevant to the hull hydrostatics), or try a slightly different Displacement or Draft value. Sometimes deleting the .mem file in the Memory folder for your model will cause the FLOATSOFT to take a different approach to solving your calculation, and skip the problematic immersion.

Error “Unable to connect to SOLIDWORKS”

Sometimes FLOATSOFT might fail to connect active SOLIDWORKS instance. Fortunately, this is easy to fix:

  1. Check if you don’t have multiple instances of SOLIDWORKS running. Open the Task Manager, and search for SOLIDWORKS instances – there should be only one. If unsure, restart your computer, and try again.
  2. Check if your anti-virus is not blocking the application. If you’re unsure, add FLOATSOFT to the Exceptions list in your anti-virus settings.

Simulate Natural Buoyancy mode fails to find a solution

Due to the complexity of this mode, sometimes the application may struggle to find the right heel, trim and draft values to locate the Center of Buoyancy above or below Center of Gravity. This usually happens with extreme CoG locations or extremely unusual and unpredictable hull shapes. If that is the case, please try the following suggestions:

  1. Try setting the CoG coordinates to a more moderate location (closer to the center of the vessel). If a solution is found, set the CoG to the actual position you need, and run the simulation again. FLOATSOFT features a learning algorithm that performs advanced positioning operations better with time, and setting the CoG in steps before setting it to the final position will help to “train” the algorithm.
  2. Try setting the Z value of the CoG coordinates lower. In many cases, we find that users often neglect setting the correct Z value, leaving it higher than actually necessary, which makes the virtual vessel a lot more unstable, and makes it harder for this mode to find a solution.
  3. If all else fails, open the memory folder next to the application executable, and delete the [SOLIDWORKS model name].mem file. This will reset the learning algorithm memory, and may help find the solution on the next run.

Heel and trim values are reversed

Make sure that the model is oriented correctly, as described in SOLIDWORKS model requirements. In most cases, this unexpected behavior is due to positioning vessel along the X axis rather than Z, or pointing it in the wrong direction along the correct axis. If your model is too complicated to redefine all planes, sketches and features in SOLIDWORKS, you can use Move/Copy feature to rotate the model as the last feature in the SOLIDWORKS Feature Tree. If that feature gets in the way, you can alternatively use the Insert Into Part on the solid body to create a separate part for use with FLOATSOFT, and orient it as needed.