ok I give up. After a full day of trying to figure this out, I have no idea what is going wrong here. maybe someone else knows.
I am using Unity 5.3.5f1, the latest Adventure creator because I just redownloaded it a few days ago. Windows 7.
So... I add a hotspot. I start the game and click the hotspot and nothing happens. I set it to make the mesh glow when the mouse is over the hotspot and it does indeed glow so it knows my mouse is over a hotspot. But trying to interact with it does nothing at all. It doesn't trigger the unhandled handler, it doesn't trigger the actionlist for that hotspot, absolutely nothing. I don't know what other info to give because I have no idea where the problem might be. It just completely doesn't work.
Have started a brand new scene and it doesn't work there either. The demo scene is a little more weird. The sword, door, stairs, poster board don't work... but Brain and the oil drum you can tip over do work for some reason.
Comments
Check that there are no warnings or error messages in the Console - AC should warn you if it detects an issue like undefined Inputs or Layers.
We'll need to see what all your Interaction settings are set to within your Settings Manager, but if the Demo game is not working either it could be part of a wider issue. Let us know what the Console looks like, and post a shot of your Settings Manager, and we'll do our best to help.
This is a fresh project. AC is not the only plugin being used though. I have also imported UFPS (although I am not using a UFPS character in the AC scenes) which is a full project so overwrote some things from AC like tags, layers, and inputs, but I think I got them all back.
There are no warnings or errors in the console.
Here are some screen shots:
Thanks
Are there any other assets beside UFPS present in your project? It sounds like this is caused by some kind of unknown conflict between two assets. I haven't had any such issues with UFPS in the past - which version of UFPS are you using?
Try re-importing AC again, but only the AdventureCreator asset folder - not the Project Settings that will overwrite UFPS's things.
Sounds like not the same issue as Alverik has though.
@Alverik: If the UI was connected to the Menu Manager, the RectTransform field you assign will mark out an area under which objects in the scene can't be clicked - that may have been blocking it. Otherwise, it may be to do with the UI components naturally blocking raycasts due to their default settings.
One further thing to try is to disable the Menu on start, but have it turn on manually with the Menu: Change state Action in your OnStart Cutscene - that shouldn't make a difference, but it may do if a bug is present.
If you still need to send something over, leaving out the graphics should be OK. Same for the scripts, provided that they only get run when the UI itself is interacted with.