Print Friendly Version of this pagePrint Get a PDF version of this webpagePDF
Follow

Version History

v10.4.3 (1st July 2021)

Key Changes:

  • Expiration date for processing of legacy unencrypted iSTAR Pulsar+ data extended to 00.00 GMT, 1st February 2022.

General Improvements:

  • N/A

v10.4.2 (13th April 2021)

Key Changes:

  • N/A

General Improvements:

  • Fixes issue where some unencrypted iSTAR Pulsar+ datasets will not process, instead generating an error message.

v10.4.0 (26th March 2021)

Key Changes:

  • Expiration date for processing of legacy unencrypted iSTAR Pulsar+ data extended to 30th June 2021.
  • Raw GPS and IMU data produced alongside output as standard.
  • Option to insert alternative "utctime" timestamp into output framepos file. This can aid in situations where offset exists between systemtime and utctime help with syncronisation of the imagery with external device timelines.

General Improvements:

  • Data captured using indoor presets will assume poor/no GPS coverage and therefore ignore all GPS during processing.  This solves issue where frames were dropped unexpectedly during processing when GPS data against them was of low quality.
  • Fixes an issue where a number of frames proportional to the time spent in GPS-outage are dropped from the end of the capture when using in-software image spacing.  This would only typically have been noticeable when capturing in areas with poor sky-visibility.
  • Fixes an issue which can cause no output to be produced in the case of a static capture.

v10.3.1 (25th January 2021)

  • Extended expiration date for processing of legacy (unencrypted) iSTAR Pulsar+ data to 31st March 2021
  • General improvements

v10.2.0 (8th December 2020)

  • Bug fixes
  • Expiration date for processing of legacy (unencrypted) iSTAR Pulsar+ data remains to 31st January 2021

v10.1.1 (24th September 2020)

  • Bug fixes
  • Extended expiration date for processing of legacy (unencrypted) iSTAR Pulsar+ data to 31st January 2021

v10.1.0 (20th July 2020)

  • Extract fisheye images
  • Create cubeface images
  • Export KML
  • Define the maximum number of  frames to process
  • Auto levelling for vehicle and backpack (Roll+Pitch, Heading, Roll+Pitch+Heading)
  • User can specify output directory
  • User can specify naming convention for images (Enumerated, EpochTime, UtcTime)
  • Expiration date for processing of legacy (unencrypted) iSTAR Pulsar+ data remains to 30th September 2020

v10.0.15 (24th April 2020)

  • Bug fixes
  • Expiration date for processing of legacy (unencrypted) iSTAR Pulsar+ data remains to 30th September 2020

v10.0.14 (14th April 2020)

  • Extended expiration date for processing of legacy (unencrypted) iSTAR Pulsar+ data to 30th September 2020

v10.0.13 (27th January 2020)

  • Extended expiration date for processing of legacy (unencrypted) iSTAR Pulsar+ data to 30th April 2020

v10.0.12 (2nd October 2019)

  • Support for automatic selection of the number of threads added (iSTAR Pulsar+)
  • Bug fixes

v10.0.10 (16th July 2019)

  • Improved accuracy of GPS EXIF data in iSTAR Pulsar+ output
  • Bug fixes

v10.0.9 (27th May 2019)

  • Bug fixes

v10.0.8 (13th May 2019)

  • Bug fixes

v10.0.7 (3rd May 2019)

  • Bug fixes

v10.0.6 (16th April 2019)

  • Fixed bug with image count spacing and distance spacing options

v10.0.5 (28th February 2019)

  • Implementation of "Auto level images" option for iSTAR Pulsar+ data formation (beta feature, vehicle-mounted captures only, not suitable for data for synchronisation with external systems)
  • Bug fixes

v10.0.4 (20th February 2019)

  • New interface design implemented
  • Implementation of iSTAR Pulsar+ data formation
  • Added audible tone upon process completion of each item in queue
  • Bug fixes

v9.1.1.0 (18th October 2017)

  • Implemented 2048 x 2048 px cubeface image export
  • Bug fixes

v8.6.1.0 (7th March 2017)

  • Implementation of new algorithm to reduce/minimise Chromatic Aberration in images produced by iris360 units with serial numbers ending in 3xxx.
  • Bug fixes

v8.5.0.0 (3rd November 2016)

  • Uses new debayering algorithm
  • Bug fixes
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk