New Version available! 1.1.1 (31744)

Thu 6. Jul 2017, 13:45

Hi everyone,

a new version for the plugin is available! You can find the new version here.

This version is mostly fixes and performance increases.
Also the way packages are handled have changed and this could have an impact on your project.
So please check if that might be the case, see below for an in depth example of what this change implies.

Its also worth noting that from this point on forward, you can check for updates manually in the menu bar "Articy/Check for updates" or automatically once at startup of the editor and have a look in the database view in the lower leftcorner next to the version number.

new_version.png
new_version.png (2.69 KiB) Viewed 9452 times


Code: Select all
31744 1.1.1 release

** Important ** Please carefully evaluate the below mentioned changes to LoadPackage/UnloadPackage and the effects that it could have on your project.
This could affect you when you are using multiple packages where some contain the same object and/Or expect UnloadPackage to remove all objects.

- modified: LoadPackage(even if you don't use it, it is used internally) objects are now only loaded once even if multiple packages contain them. No more multiple entries of the same object (Has nothing to do with cloning)
- modified: UnloadPackage has a new parameter to greedy unload the package or(the new default) only unload objects that are not in any other still loaded package.
- fixed: issues with loading localization, especially with the general localization file when starting the game
- fixed: issues with localization excel sheets, when the filename contained a '-'.
- fixed: larger projects could cause a false positive "Please fix any errors" dialog boxes.
- fixed: Under certain circumstances the script fragments could not be assigned to the database after the import, causing a broken database.
- fixed: editor ui caused the language to switch constantly, draining performance.
- fixed: performance issue creating the internal database, uncessarily refreshing itself.
- fixed: performance issues with the object list in the database view. Should now create and scroll much faster.
- fixed: performance increase for object list filter in the database view.
- fixed: ArticyDebugFlowPlayer wrong check for component.
- modified: package list is now scrollable
- modified: object list in database view can now be collapsed.
- added: an option to check for new updates of the plugin, you can trigger this manually via the menu bar "Articy/Check for updates" or it is checked once per startup and can be viewed in the lower left corner of the database view.


If you have any problems you can still find the previous version here if you need to go back.

Happy coding!

Nico
Nico Probst
Senior Software Engineer | Articy | LinkedIn
User avatar
[Articy] Nico Probst
Articy Staff
Articy Staff
 
Posts: 217
Joined: Wed 23. Nov 2011, 09:45
Location: Bochum

Re: New Version available! 1.1.1 (31744)

Thu 6. Jul 2017, 13:47

Package changes explanation.

Lets say you have 2 packages:

Code: Select all
PackageA
   * EntityA
   * FlowFragment A


Code: Select all
PackageB
   * EntityA
   * FlowFragment B


Where EntityA would be the same object, with the same id in articy:draft.

If both packages where loaded, you ended up with a database that looked like this in the previous versions of the plugin:

Code: Select all
ArticyDatabase old
   * EntityA
   * EntityA
   * FloatFragmentA
   * FlowFragmentB


If you would unload PackageA now from the Database you would have

Code: Select all
ArticyDatabase old
   * FlowFragmentB


With the new version, your database with both packages would look like this

Code: Select all
ArticyDatabase new
   * EntityA
   * FloatFragmentA
   * FlowFragmentB


Also changed is the way how UnloadPackage works, as it now allows you to define how you want to deal with objects that could still be part of loaded packages.

calling UnloadPackage like this

Code: Select all
ArticyDatabase.UnloadPackage("PackageA", false); // you could omit false here, as it is the new default


would leave the database with the following objects.

Code: Select all
ArticyDatabase new
   * EntityA
   * FlowFragmentB


As you see, EntityA was not unloaded, even if it was in PackageA, because it is still in PackageB.

But calling UnloadPackage like this

Code: Select all
ArticyDatabase.UnloadPackage("PackageA", true);


would result in

Code: Select all
ArticyDatabase new
   * FlowFragmentB


As it was the old way of UnloadPackages and kicks all objects without further checking.

If you have any questions, let me know!

Best regards

Nico
Nico Probst
Senior Software Engineer | Articy | LinkedIn
User avatar
[Articy] Nico Probst
Articy Staff
Articy Staff
 
Posts: 217
Joined: Wed 23. Nov 2011, 09:45
Location: Bochum

Return to articy:draft Unity Importer

Who is online

Users browsing this forum: No registered users and 10 guests

Who We Are
Contact Us
Social Links