Author Topic: UI buttons unresponsive in unity 4.5  (Read 3145 times)

Turandours

  • Newbie
  • *
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 7
    • View Profile
UI buttons unresponsive in unity 4.5
« on: June 13, 2014, 05:04:53 PM »
I've just started a new project with unity 4.5 using ngui 3.6.3. (I just updated to see if it would fix the problem, it didn't)

Currently while in play mode no buttons are responsive at all. Even in the example scenes that were included.

I even went as far as starting a fresh scene, making a new 2d ui and dragging a control - simple button prefab in to see if that would work and still no response to clicks or hovering.

I believe it to be a problem on NGUI's end, at least with the current version, because a project created in unity 4.4 with ngui 3.0.3f still was fully functional on the same machine.

Have I made some mistake? or is this a known problem and a fix is on it's way?

Turandours

  • Newbie
  • *
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 7
    • View Profile
Re: UI buttons unresponsive in unity 4.5
« Reply #1 on: June 13, 2014, 06:00:37 PM »
Actually having updated to 4.5.1 the problem still persisted.

But upon starting a new project and importing ngui it worked fine. So it must be something I have in the project that is interfering. The project also has ngui hud text and the ninjitsu games mini map. So I'll poke around more and see if I can find an answer.

Edit: Still no answer yet even removing the other two components listed. There are no listed warnings or other messages in the console when the game is run either.  Any ideas would be appreciated.

Turning on debug mode on the camera shows no information either, so it looks like the colliders aren't being hit.
« Last Edit: June 13, 2014, 06:13:00 PM by Turandours »

Turandours

  • Newbie
  • *
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 7
    • View Profile
Re: UI buttons unresponsive in unity 4.5
« Reply #2 on: June 13, 2014, 06:24:41 PM »
Looks like raycasts hit triggers were turned off. Problem is fixed now. Feel free to close this out. :)