Messages

1

Other Packages / Re: Tasharen Fog of War

« on: January 04, 2016, 03:58:13 PM »

That makes sense, thanks!

2

Other Packages / Re: Tasharen Fog of War

« on: January 02, 2016, 07:20:48 PM »

Thanks for getting back to me! I'm not sure I asked my question correctly, but I'm not trying to switch to an XY 2D, I want to keep the XZ plane but have multiple stacked height points. So for example, if I'm standing in a room, I'd like to not see the room below me as well as the other rooms on the same floor. With the 2D heightmap the rooms around me get blocked but not the ones above or below, even when I have the raycasting set to collide with the floor layers.

Thanks again!

3

Other Packages / Re: Tasharen Fog of War

« on: December 27, 2015, 04:48:14 AM »

Hi Aren,

Thanks so much for making such a great plugin! I know this question is very specific to my scene, but I have multiple floors that are stacked on top of each other, and when a revealer is on an inner floor it seems as if there aren't any nodes on that floor. I'm guessing this is because the FOW system is set up to only make one node in the heightmap per xz point, and it's colliding with something above or below it already, but I was wondering if there was a way to make layered floors work within the system. Each floor is exactly 10 units high.

Thanks again!

4

NGUI 3 Support / Re: UIInput temporary freeze on first use in build

« on: August 11, 2014, 11:32:32 AM »

Hi Aren,

Thanks for responding. I just tried updating to the newest version and the delay was no longer there. I'm not sure what the original cause was but I just wanted to respond in case anyone has this problem in the future.

Thanks!

5

NGUI 3 Support / UIInput temporary freeze on first use in build

« on: August 10, 2014, 12:53:23 AM »

I'm having an issue with the UIInput. When I open a build and type in any input field that doesn't have a starting value, the game freezes for around 10 seconds, and then everything is back to normal and it never happens again, even if I load a new scene. The same thing happens if I select an input field with a starting value.

Is this a known issue, or is there something I could be doing wrong? I've copied over the tutorial into my scene but the same problem remains.

Any insight would be appreciated!