Hello Guest

Author Topic: Editor bugs migrating from 2.3 to 2.4 ?  (Read 4792 times)

pan_henryk

  • Newbie
  • *
  • Posts: 20
    • View Profile
Editor bugs migrating from 2.3 to 2.4 ?
« on: April 04, 2014, 03:36:33 pm »
Hi,

We are trying to migrate from 2.3 to 2.4 version, but have encountered some bugs:

1. When initially use app menu, threre is serious lag (several seconds on intel i7 with ssd), probably related to resource loading - we are using pngs as source format on PC

2. We found a case, where adding new object to the scene causes shader to disappear from another object:
http://www.incuvo.com/terrain_01.jpg - terrain on the scene
http://www.incuvo.com/terrain_01_shader.jpg - shader is present

After adding character (eyes are tk2dsprite) using in-game UI, not from Unity editor

http://www.incuvo.com/terrain_missing.jpg - terrain becomes invisible, because...
http://www.incuvo.com/terrain_missing_shader.jpg - shader disappeared


None of this is present in 2.3 version.
Both situations happen only in editor, not on device (iOS).




unikronsoftware

  • Administrator
  • Hero Member
  • *****
  • Posts: 9709
    • View Profile
Re: Editor bugs migrating from 2.3 to 2.4 ?
« Reply #1 on: April 05, 2014, 10:18:22 am »
1. What app menu is this?

2. This may well be a bug - the old version was leaking memory when PNG atlases were used, and the new one seems to be overly aggressive.

The difference in behaviour between 2.3 and 2.4 is - whenever materials are reloaded PNG textures are similarly reloaded. This is different to how 2.3 behaved, where the png textures were just leaked.

pan_henryk

  • Newbie
  • *
  • Posts: 20
    • View Profile
Re: Editor bugs migrating from 2.3 to 2.4 ?
« Reply #2 on: April 09, 2014, 03:57:13 pm »
Quote
1. What app menu is this?

Our (Createrria) in-app menu, using tk2d

Quote
2. This may well be a bug - the old version was leaking memory when PNG atlases were used, and the new one seems to be overly aggressive.

Could you point me to the part of code responsible so I could revert it to 2.3 behaviour and check results?

unikronsoftware

  • Administrator
  • Hero Member
  • *****
  • Posts: 9709
    • View Profile
Re: Editor bugs migrating from 2.3 to 2.4 ?
« Reply #3 on: April 09, 2014, 06:48:37 pm »
1. png atlases are much slower to load, very much more so if your texture is compressed. Not much you can do about this, except turn off compression if it is compressed, and turn off mips if you have that enabled.

2. Its tk2dSpriteDataUnloader.cs - you can disable the unload manager altogether or revert to the 2.3 file.

pan_henryk

  • Newbie
  • *
  • Posts: 20
    • View Profile
Re: Editor bugs migrating from 2.3 to 2.4 ?
« Reply #4 on: April 09, 2014, 08:46:56 pm »
1. png atlases are much slower to load, very much more so if your texture is compressed. Not much you can do about this, except turn off compression if it is compressed, and turn off mips if you have that enabled.

The problem is that it didn't happen in 2.3 Will check tomorrow if changing data unloader fixes this one too.

2. Its tk2dSpriteDataUnloader.cs - you can disable the unload manager altogether or revert to the 2.3 file.

pan_henryk

  • Newbie
  • *
  • Posts: 20
    • View Profile
Re: Editor bugs migrating from 2.3 to 2.4 ?
« Reply #5 on: April 10, 2014, 09:05:27 am »
2. Its tk2dSpriteDataUnloader.cs - you can disable the unload manager altogether or revert to the 2.3 file.

Disabling it (removing #define ENABLE_UNLOAD_MANAGER from tk2dEditorSpriteDataUnloader.cs) fixed both bugs.

Thanks!