My script says that my photonmanager script should have a identifier expected at (348,60)
Unless you’re satisfied with a vague answer like “You should add an identifier where it’s expected in your code” it would be more helpful if you posted your actual code (inside code tags, not as a picture).
2 Likes
Inspect line 348 near character (column) 60 and you may be able to figure out what’s missing.
Note that the location is not always precise. It may indicate the location where a preceding syntax error just stops to make any sense at that location. So look to the left as well.
1 Like
Dear lord, cant you post from the pc, and copy the text, and at least highlight the line?
What is
supposed to be?
1 Like
Idk what that is
well its your code 
1 Like
These are some amazing posts! I really needed them—thank you!
Seriously, do you not know how copy & paste works?
Select text. Press Ctrl+C. Then hit Ctrl+V. It’s magic! 
Even if you insist on making a screenshot, Windows has the Snipping Tool and a ton of other ways to take a screenshot. Just don’t photograph your screen.
1 Like
global:: and more so lobal:: are just not valid C#. Whatever you copy from, it’s not C#. Looks more like C++.
Still doesnt work. The line that needs the identifier is the one I highlighted. Idk what is wrong with it
is not valid, so like the other line i posted
all the ones with :: in are not c#, so whatever you are doing, you need to stop randomly copying code
but that line
You have a name for something in the brackets but no class, or a class and no name for it… whichever fits…
but your code has a lot of other issues in it
global:: actually is, it is a very bad practice as it is only useful for separating between name conflicts of classes in different namespaces that are both being used in your code https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/operators/namespace-alias-qualifier?redirectedfrom=MSDN.
That aside, I predict this is going to be an epic discussion!
EDIT: Usually it is good practice to use in source generators to avoid any name conflicts
Where should i put the class name im new to coding
I just dont know
well, you have plenty of code it didnt complain about above it, look at how thats syntaxically formed.
@CodeSmile needs to come in with his post about follow and understanding tutorials
if you dont understand it, dont just blindly copy.
This isn’t a tutorial because the code is too complex and includes IntelliSense tags, it looks like production code. Additionally, there shouldn’t be any errors since the screenshot clearly shows the message: “No issues found.”
Regardless, this appears to be code from the public repository of the PhotonVR library.
https://github.com/fchb1239/PhotonVR/blob/main/PhotonVRManager.cs
I’m not sure why the OP posted this code; I can only make some educated guesses.
Two steps to tutorials and / or example code:
- do them perfectly, to the letter (zero typos, including punctuation and capitalization)
- stop and understand each step to understand what is going on.
If you go past anything that you don’t understand, then you’re just mimicking what you saw without actually learning, essentially wasting your own time. It’s only two steps. Don’t skip either step.
Imphenzia: How Did I Learn To Make Games:
Whenever and wherever you make typing mistake errors, DO NOT POST HERE. Go fix your typing mistakes and other errors. Here’s how:
You can fix your own typing mistakes. Here’s how:
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.
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? Are you structuring the syntax correctly? Look for examples!
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.
You need to configure Visual Studio so it recognises your project and shows errors, gives proper highlighting and autocomplete, and gives suggestions to resolve issues.
Without a configured IDE you’re almost coding blind.
Please use code blocks to post code here in future.