Releases: ropensci/unifir
Releases · ropensci/unifir
unifir 0.2.4
- New
print.unifir_script
method hides some of the R6 internals backing the
package, and makes my dissertation chapter render nicer. - Bug fixes:
- Removed trailing commas in some calls to
glue()
to fix errors on R devel (#17)
- Removed trailing commas in some calls to
unifir 0.2.3
- Bug fixes:
- Fixed bug where spaces in path to Unity would cause
unity_version()
and
create_project()
to fail. - Fixed
InstantiatePrefab
C# requirements to now includeUnityEditor
. - Fixed test for new sf and terra versions.
associate_coordinates()
will now only reproject if both objects have
coordinate reference systems.
- Fixed bug where spaces in path to Unity would cause
- Documentation changes:
- Added citation information.
unifir 0.2.2
- Redocumented to keep the package on CRAN.
- Internal changes:
action()
is now much more modular, outsourcing to a handful of new
internal functions
unifir v0.2.1
unifir 0.2.1
This is intentionally a very small patch release, intended to fix three problems:
- Provides an appropriate citation via
citation("unifir")
and in the README - Addresses a failing test on M1 macs
- Uses
match.arg()
in appropriate places
unifir v0.2.0
unifir 0.2.0
This is the first version of unifir to land on CRAN
- Improvements and bug fixes:
find_unity()
now doesn't escape its Unity path (so the string returned
is the actual path to the Unity engine, not a quoted version).
Accordingly,action()
now wrapsunity
inshQuote()
. (#4)add_default_tree()
now imports its trees standing upright by default.
If you manually setx_rotation
to 0, however, the trees will import as
sideways as ever. (#7)- Examples are now tested (and work) (#8 1d5b1f3)
create_terrain()
handles non-local terrain files (#6)unifir_prop()
now checks to make surescript
exists and is a
unifir_script
. Previously this errored with a baffling message about
long vectors.
- Documentation changes:
- Vignettes have been fleshed out, and a full example added to the
user-facing vignette. (#7) - Return values are better documented (#5)
- Functions are consistently linked and documentation formatting is now
more consistent (#5) find_unity()
doesn't now have a weird break in its documentation
sections- The README now links to vignettes and explains why anyone would want
to deal with Unity in the first place
- Vignettes have been fleshed out, and a full example added to the
unifir JOSS release
This release is specifically intended to create a Zenodo copy of the release, in order to have a software DOI pre-JOSS publication. It is identical to v0.2.0.
unifir v0.1.0
This is the first released version of the unifir package! Clocking in at 25 exported functions, 2 vignettes, and 88% code coverage, this package is the first stab at creating a unified API for calling Unity from R.