Question Issues with ScreenToWorldPoint

I am trying to make a 2d game, and I am making the aiming system. Based on tutorials, I used camera.screentoworldpoint, but it keeps showing error cs1061, which makes no sense. I've looked through the forums and other tutorials for a while, but I can't seem to fix it.

 

No, it makes perfect sense when you're making typing mistakes.

Stop making typing mistakes. The computer will force you to correct them anyway before it can run.

The complete error message contains everything you need to know to fix the error yourself.

The important parts of the error message are:

- the description of the error itself (google this; you are NEVER the first one!)
- the file it occurred in (critical!)
- the line number and character position (the two numbers in parentheses)
- also possibly useful is the stack trace (all the lines of text in the lower console window)

Always start with the FIRST error in the console window, as sometimes that error causes or compounds some or all of the subsequent errors. Often the error will be immediately prior to the indicated line, so make sure to check there as well.

Look in the documentation. Every API you attempt to use is probably documented somewhere. Are you using it correctly? Are you spelling it correctly?

All of that information is in the actual error message and you must pay attention to it. Learn how to identify it instantly so you don't have to stop your progress and fiddle around with the forum.

Remember: NOBODY here memorizes error codes. That's not a thing. The error code is absolutely the least useful part of the error. It serves no purpose at all. Forget the error code. Put it out of your mind.

Tutorials and example code are great, but keep this in mind to maximize your success and minimize your frustration:

How to do tutorials properly, two (2) simple steps to success:

Step 1. Follow the tutorial and do every single step of the tutorial 100% precisely the way it is shown. Even the slightest deviation (even a single character!) generally ends in disaster. That's how software engineering works. Every step must be taken, every single letter must be spelled, capitalized, punctuated and spaced (or not spaced) properly, literally NOTHING can be omitted or skipped.

Fortunately this is the easiest part to get right: Be a robot. Don't make any mistakes.
BE PERFECT IN EVERYTHING YOU DO HERE!!

If you get any errors, learn how to read the error code and fix your error. Google is your friend here. Do NOT continue until you fix your error. Your error will probably be somewhere near the parenthesis numbers (line and character position) in the file. It is almost CERTAINLY your typo causing the error, so look again and fix it.

Step 2. Go back and work through every part of the tutorial again, and this time explain it to your doggie. See how I am doing that in my avatar picture? If you have no dog, explain it to your house plant. If you are unable to explain any part of it, STOP. DO NOT PROCEED. Now go learn how that part works. Read the documentation on the functions involved. Go back to the tutorial and try to figure out WHY they did that. This is the part that takes a LOT of time when you are new. It might take days or weeks to work through a single 5-minute tutorial. Stick with it. You will learn.

Step 2 is the part everybody seems to miss. Without Step 2 you are simply a code-typing monkey and outside of the specific tutorial you did, you will be completely lost. If you want to learn, you MUST do Step 2.

Of course, all this presupposes no errors in the tutorial. For certain tutorial makers (like Unity, Brackeys, Imphenzia, Sebastian Lague) this is usually the case. For some other less-well-known content creators, this is less true. Read the comments on the video: did anyone have issues like you did? If there's an error, you will NEVER be the first guy to find it.

Beyond that, Step 3, 4, 5 and 6 become easy because you already understand!

Finally, when you have errors, don't post here... just go fix your errors! See above.

When you have an ACTUALY error as opposed to just fatfinger typing, here is...

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, log output, variable values, and especially any errors you see
- links to documentation you used to cross-check your work (CRITICAL!!!)

Photographs of code are NOT A THING.

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

How to use code tags: https://forum.unity.com/threads/using-code-tags-properly.143875/

In this particular case, most likely you just made a script called Camera which is overwriting the Unity Camera you are looking for.

 

Just wanted to emphasise the bit which is most likely the issue. Since we don't see the actual full error message (which contains clues about exactly that issue) we can just speculate. Error messages usually mention the "full class name" in the error. So it it tells you that "Camera" doesn't have a method named "ScreenToWorldPoint" that would be a direct clue. If it said "UnityEngine.Camera" doesn't have that method, it would indeed be strange.

For the future:

• Don't post screenshots of code, use code tags here in the forum to post code. That way we can quote and copy relevant parts in order to write an answer.
• When you get an error, always post the full error message. You can actually copy the error message from the bottom half of the console window when you select a log entry.

That said, almost nothing in your script makes any sense. Having a bullet check the players mouse position at start to figure out in which direction it should rotate is a horrible design. The thing that shoots the bullet should determine the bullets rotation / orientation since it's the one creating the bullet. You can pass the rotation right at the moment when you instantiate the bullet.

The condition you have in Update also makes no sense. It's impossible that this condition will ever be true. That condition essentially states to destroy this object when the framerate is exactly 1 frame per second. However this can never happen because even if the framerate would drop that low, Unity caps the deltaTime at 0.33333. So it will never get higher than that. You probably had something else in mind because this just makes no sense.

You can actually call Destroy in Start and pass a delay as second argument. This would automatically destroy the object when that time runs out. However if the bullet "dies" earlier, that call doesn't matter.