Problemas con Botones Unity

[ISANOSUKE]

Bueno espero que alguien sepa ayudarme a solucionar un problemas que estoy teniendo con los botones
les comento lo que hice y como trate de solucionarlo pero lamentablemente no pude hacerlo en formato 3D

Cree un Canvas
acto seguido un botón y al la opcion OnClick() le asigne el Canvas y en la opción funciones seleccione el scripts donde se aplica el código correspondiente al botón (en este caso la acción de pausar del juego con un debug) cabe aclarar barias cosas
1- La plataforma es de móvil
2-el juego es tiene un solo control en donde se aplica el click izquierdo para manejar al jugador
(el click izquierdo representa el táctil en un móvil)
Si alguien me podría dar una posible solución desde ya muchas gracias

[Brathnann]

This is an English forum, so it’s best to post your questions in English, however, I translated your post.

Well I hope someone knows how to help me solve a problem I’m having with the buttons
I tell you what I did and how I tried to solve it but unfortunately I couldn’t do it in 3D format

Create a Canvas
then a button and the OnClick() option assign the Canvas and in the functions option select the scripts where the code corresponding to the button is applied (in this case the action of pausing the game with a debug) several things should be clarified
1- The platform is mobile
2-the game has a single control where the left click is applied to control the player
(the left click represents the touch on a mobile)
If someone could give me a possible solution, thank you very much.

However, I don’t see a question in this. Either it’s lost in translation or you never asked one.

[ISANOSUKE]

@Brathnann

Este es un foro en inglés, por lo que es mejor publicar sus preguntas en inglés, sin embargo, traduje su publicación.

Sin embargo, no veo una pregunta en esto. O se pierde en la traducción o nunca has preguntado una. [/CITA]

la traducción
la pregunta seria:
¿Alguien me puede dar una posible solución?

[Kurt-Dekker]

How to report your problem productively in the Unity3D forums:

http://plbm.com/?p=220

This is the bare minimum of information to report:

• what you want
• what you tried
• what you expected to happen
• what actually happened, especially any errors you see
• links to documentation you used to cross-check your work (CRITICAL!!!)

If you post a code snippet, ALWAYS USE CODE TAGS:

How to use code tags: Using code tags properly

You must find a way to get the information you need in order to reason about what the problem is.

What is often happening in these cases is one of the following:

• the code you think is executing is not actually executing at all
• the code is executing far EARLIER or LATER than you think
• the code is executing far LESS OFTEN than you think
• the code is executing far MORE OFTEN than you think
• the code is executing on another GameObject than you think it is
• you’re getting an error or warning and you haven’t noticed it in the console window

To help gain more insight into your problem, I recommend liberally sprinkling Debug.Log() statements through your code to display information in realtime.

Doing this should help you answer these types of questions:

• is this code even running? which parts are running? how often does it run? what order does it run in?
• what are the values of the variables involved? Are they initialized? Are the values reasonable?
• are you meeting ALL the requirements to receive callbacks such as triggers / colliders (review the documentation)

Knowing this information will help you reason about the behavior you are seeing.

You can also supply a second argument to Debug.Log() and when you click the message, it will highlight the object in scene, such as Debug.Log("Problem!",this);

If your problem would benefit from in-scene or in-game visualization, Debug.DrawRay() or Debug.DrawLine() can help you visualize things like rays (used in raycasting) or distances.

You can also call Debug.Break() to pause the Editor when certain interesting pieces of code run, and then study the scene manually, looking for all the parts, where they are, what scripts are on them, etc.

You can also call GameObject.CreatePrimitive() to emplace debug-marker-ish objects in the scene at runtime.

You could also just display various important quantities in UI Text elements to watch them change as you play the game.

If you are running a mobile device you can also view the console output. Google for how on your particular mobile target, such as this answer or iOS: How To - Capturing Device Logs on iOS or this answer for Android: How To - Capturing Device Logs on Android

Another useful approach is to temporarily strip out everything besides what is necessary to prove your issue. This can simplify and isolate compounding effects of other items in your scene or prefab.

Here’s an example of putting in a laser-focused Debug.Log() and how that can save you a TON of time wallowing around speculating what might be going wrong:

Coroutine missing hint and error

This is so unnecessary. Use the beauty and power of instantly and immediately putting a Debug.Log() statement into the very start of the coroutine, right at the top. Do this always at the very first sign of trouble or question in your mind. The instant you did this you would see “Oh man, this code is simply not getting run!” And you could LASER-FOCUS 100% your efforts on studying what you expect to run it, eg., the call location, and isolate why it is not running. You would look at literall…

When in doubt, print it out!™

Note: the print() function is an alias for Debug.Log() provided by the MonoBehaviour class.