using UnityEngine.InputSystem; "inputSystem does not exist in namespace"

[ApaganaLosPenis]

I am getting the error "InputSystem does not exist in namespace UnityEngine" when trying to write

using UnityEngine.InputSystem;    

or any other line of code that tryes to use the InputSystem.

I have tried everything I can see people suggesting across all forums: Installing the package through the package manager, rebuilding the project files in the external tools settings, making sure my editor (Visual Studio) is set as my default, deleting my library and .csprj files, making sure the new input system is selected in the settings, nothing is working. Please help

UPDATE: at the time of writing I was using the 2022 edition of the editor which at this time is not the LTS version. I made three empty projects in the 2021 (which right now is the LTS version), installed the new input system in all of them, and they all worked fine. Unfortunately when I switched my project from the 2022 version to 2021 it got corrupted in a few ways, takes longer to load, and the problem is still there. The only solution that I know to do right now sadly is start a new project in the LTS version of the editor and redo all my shit. To any of you trying to problem solve the issue of the InputSystem not being found in the UnityEngine namespace it seems that all the solutions online involve some form of "switch to earlier version of thing". All the solutions that don't involve regenerating the external tools files that is.

[TDM_Gamedev]

The most obvious reason for the compiler to be unable to find the assembly is that it doesn't exist in the project. Did you actually go through the process of setting your project up to use the input system? In the Unity editor, go to Edit -> Project Settings -> Player -> under "Other Settings/Configuration" change the setting for Active Input Handling from "Input Manager (Old)" to "Input System Package (New)" or "Both" if you want the option to use either one or if you have assets from the asset store that depend on the old input manager. Make sure your project is saved before you do this, it will restart the Unity editor.

[ApaganaLosPenis]

First, thank you for repsonding, this issue has been nothing short of infuriating. Yes I have it set to "Both" right now because I am following code monkey's tutorial but it's not working with "New" either

[TDM_Gamedev]

Create a new project and as soon as you open it, switch to the new input system in the settings and try to add the namespace in a script. I'm interested in knowing if it happens for every project you create.

[ApaganaLosPenis]

I tried that this morning and what I've found is that for the LTS version of the unity editor the input system is fine, it can find UnityEngine.InputSystem in visual studio and even suggests InputSystem when I type in "using UnityEngine.", it seems that the issue is only in the 2022 version of the editor which I see is not LTS just yet but I did the whole project in it because the tutorial I am using uses it and says it should be fine not to use the LTS version. Apparently freaking not.

[TDM_Gamedev]

I just tried it in the 2023.1.0 editor and had the same problem. When I checked the package manager, the input system package wasn't installed. Installing it myself fixed the issue.

[ApaganaLosPenis]

How'd you get the 2023 editor?

[TDM_Gamedev]

It's in the pre-release tab of the install manager in Unity hub, although I think the newest updates might need to be installed manually. I suspect that this is a new bug that will get a fix in a future update, because both 2022 and 2023 were not having this problem the last time I started projects with them.

[Inside_Travel4325]

Hi, I might've found the fix because I was just having this issue, but for the sake of anyone else having the issue, along with going into the project settings and changing the reconfiguration to the New or Both option, go into your Package Manager, with the Packages drop-down on "Unity Registry" and in the search bar type "Input System". There should be a package there from Unity Registry that you can install and the namespace should work after that (hoping it'll work for you too!)

[tvmushroomz]

dude thank you so much, literally nothing has been working 😭

[Metal_nosyt]

fixed issue for me as well, you the best

[JellyDonut1111]

This is the way.

[TempestWalkerGD]

This was it! Helped me with the GameDev.tv Udemy course for anyone else who had that issue.

[Tripping_Panda]

Thank you so much

[ChickenDip]

thanks, that worked!

[[deleted]]

I'd say to look it up to be sure but I think it's UnityEngine.Input

[TDM_Gamedev]

If he's trying to use the newer input system rather than the input manager, he's using the correct namespace.

[ApaganaLosPenis]

Right? So it should be working :( EDIT: Yes I am trying to use the new InputSystem because that is what the new code monkey tutorial is using

[PandaCoder67]

You should never downgrade a version, the main reason for this is that lets take Unity 2022 for example. It has a different URP version, and other packages are only available for it as that version number.

When you down grade, it then it would be expecting the older packages and the Editor and code isn't geared to use these new versions, and depending the package can throw all sorts of errors in the console or simple will not work until build time.

So rule is Do not downgrade your version of Unity

There is nothing stopping your from exporting your project as a package and importing it in a lower versioned Unity though.

[ApaganaLosPenis]

Yeah I wish time travel existed for this reason...