[Version 2.1.13]

Fixes:

· [Fix] guard not fully initialized window on fresh import.

· [Fix] Compatibility update: detail clearing use detail scatter in new Unity versions.

· [Fix] Compatibility update: entity based TerrainLayer handling in new Unity versions.

[Version 2.1.12]

Enhancements:

· Improve handling of mismatched terrain resolutions setups.

· Detect user changing resolutions without selection change.

Fixes:

· [Fix] Correctly handle grossly mismatched terrain resolutions setups that could result in a broken state of the brush size.

[Version 2.1.11]

Fixes:

· [Fix] The detail resolution was incorectly setup on the FFT-F Demo terrains in the Demo scene.

[Version 2.1.10]

Fixes:

· [Fix] Latest Unity versions didn't (yet?) handle a custom importer, which was introduced earlier to avoid users needing to do clean installs for some updates. Custom importing is not needed now, but you may have to do a clean install (delete the earlier version before importing) if you are updating an older version of Path Painter.

[Version 2.1.9]

Fixes:

· [Fix] API Paint3D handled line caps like ordinary Paint & produced somewhat incorrect results.

[Version 2.1.8]

Fixes:

· [Fix] Import validation incorrectly checked for two components no longer needed and warned about them.

[Version 2.1.7]

Enhancements:

· [New] Adaptive, automated performance optimisation for large scale painting.

Fixes:

· [Fix] Removed the spacing optimisation that caused some unwanted terracing effects and shaping artefacts.

· [Fix] Fixed harmless errors caused by unanticipated (and highly unlikely) zero resolution Detailmaps with active layers.

[Version 2.1.6]

Enhancements:

· Path Painter now considers terrains Grouping IDs when looking at terrain groups.

· Warning messages will now advise regarding terrain tiles that deviate from the selected group too much.

Fixes:

· [Fix] Texture painting had an incorrect offset in some large environments in which terrains had mismatched Heightmap and Control Texture Resolutions.

· [Fix] Autoramp saved setting was only reset in the GUI at startup but PP used the default setting if not applied.

· [Fix] Switched off autoramp was occasionally not correctly handled and could cause terrain shaping anomalies.

· [Fix] Scene switching/loading could occasionally result in brush visualisation related Missing Reference Exception due to no longer existing terrains.

· [Fix] Autoramp did not ignore non-compatible tiles and painted incorrect ramps from them.

· [Fix] Missing terrain at scene loading could cause a validation related Missing Reference Exception.

· [Fix] Undoing some terrain settings changes was not expected by Path Painter and this could cause some temporary errors.

· [Fix] Depending on terrain settings some could deviate too much from the terrain group and was still considered part of the group.

[Version 2.1.5]

Enhancements:

· Unity fixed bug #1373388, so removed the workaround for it.

· Minimum Unity version is now 2019.4 as per Unity requirements.

· Layer names show up as tooltips for easy identification on the texture painting GUI.

· Updated the demo scene to include the Free Fantasy Terrain Textures environment.

[Version 2.1.4]

· Inlcuded a temp solution for Unity bug #1373388 that can affect users who build for Android.

[Version 2.1.3]

Fixes:

· [Fix] A bug was causing null reference exceptions with some terrain neighbour setups that have missing tiles.

[Version 2.1.2]

Enhancements:

· Completely reworked one of the painting mechanisms. The new solution could be more optimal for most scenarios and may only become disadvantageous in extreme circumstances+usage. The old mechanism could also possibly trigger some odd GC behaviour causing a build up of graphics memory usage by Unity as reported by two users. Could not yet conclude what part the old mechanism may have been playing in this but initial studies suggest that the new mechanism largely avoids the buildup. Also the pooling of the old mechanism could have caused some delays of paint readiness on some tiles in environments with hundreds of terrain tiles.

· Unity 2018.3 & 2018.4 still supports deprecated .NET 3.5 Equivalent runtime scripting. Support for this was dropped earlier but Path Painter II now supports it once again in those Unity versions.

· Path Painter will now use a lean, build optimised structure. This means that by default no part of Path Painter will be included in your builds.

· Resources are now in the Editor folder as part of the lean, build optimised structure.

· Removed the Runtime Demos from the package as part of the lean, build optimised structure. These are now downloadable separately. Use the option in the menu.

· [New] Build settings available in the menu. Use it to include/exclude Path Painter from your builds. You will want to include only if you use the API in runtime.

· Now you have options to go directly to the Documentation from the main Help, the more tab and from the menu.

Fixes:

· [Fix] Terrain square check had a bug for 4 years.

· [Fix] Painting with Texturing off painted textures in some circumstances if textures were otherwise selected.

· [Fix] Fixed a GUI styling bug that may have caused minor problems that were not detected by users.

· [Fix] Path Painter now expects that detail resolution can be zero.

[Version 2.1.1]

Fixes:

· [Fix] Fixed bug related to brush visualisation that in some circumstances threw null ref errors, but had no effect on functionality.

· [Fix] Fixed bug in tree clearing that in some circumstances threw null ref errors when vegetation clearing was off, but had no effect on functionality.

· [Fix] Fixed alphamap bounds bug that appeared in some circumstances when texturing was off, but had no known effect on functionality.

· [Fix] Fixed bug that in some cases threw null ref errors when turning on texturing on a non-texture painted path.

· [Fix] Shaping artefacts were appearing if some fairly specific conditions were met due to a conservative limit value. PP "thought" it didn't need to do some calculations for those areas and this produced artefacts.

[Version 2.1.0b4]

Enhancements:

· Removed the need to reference .Net libraries

Fixes:

· [Fix] Removed dev leftover hard coded min resolution that could brake things on very low res terrains.

· [Fix] Path Painter sometimes didn't detect right away if some terrain parameters changed between two brush strokes.

· [Fix] Over optimisation could cause spotty painting in some circumstances.

· [Fix] Terrain Trees are detected as terrain in runtime by Unity. Now Path Painter accounts for that.

[Version 2.1.0b3]

Enhancements:

· [New] Auto Ramp feature. You just do the painting and Path Painter will automatically create ramps as needed. This way of painting has been in the plans for about 5 years, from the very beginning, but got lost in the noise until now, when one of you reminded me of it (thank you!). Use the slope limit option to tame it to your needs.

· Done some clarification on some of the API XML documentation.

· Renamed runtime folders, so they can be easily moved into Editor (without colliding with folders there), so you can avoid them ending up in your builds.

· Added more tips/info that appears on the GUI.

· Fixed some typos and improved some information in the Documentation.

Fixes:

· [Fix] Turning off texturing didn't remove textures from (already painted) active paths.

· [Fix] After some terrain changes the brush could have been rendered slightly off.

· [Fix] Various small fixes.

[Version 2.1.0b2] Enhancements: 13 Fixes: 5

[Version 2.1.0b1]

Work started on Path Painter under Unity 5.6. This was almost 3 years before neighbour terrain tiles appeared, and supporting such thing didn't even cross the author, Frank's mind, who was new to Unity at the time.

Version 2 is pretty much a complete rewrite to add that feature. All these features are available in all supported Unity versions (Unity 5.6 and onwards).

Changelog exceeded the Store limit, so only writing numbers below. Please contact our support for the complete log or see in the product's Documents folder.

E: 18 F: 4

[Version 1.2.1] E: 1

[Version 1.2.0] E: 4 F: 1

[Version 1.1.1] F: 1

[Version 1.1] E: 9 F: 2