Multiple Errors with the fizzysteamworks

Hi, I can’t find a solution online as well, Ive been looking foe a solution, I have tried I think almost everything to like reinstall Mirror, install the version he was using, and I did it twice. I would really love some help, thank you

It also says that the namespace ‘SteamWorks’ cant be found

From https://github.com/Chykary/FizzySteamworks

You must have Steamworks.NET installed and working before you can use this transport. Steamworks.NET FizzySteamworks relies on Steamworks.NET to communicate with the Steamworks API .

1 Like

Hi there, did you separately install fizzy steam works? The errors seem to be with regards to that.

Hello, I had the same issue with you.
And I find that the filesize of the lastest FizzySteamTransport-5.0.1.unitypackage is 12.7KB, which is much smaller than the filesize of v4.4.1 (881KB). So I removed the current v5.0.1 then importing the v4.4.1. And it finally works.

1 Like

Hi, I encountered this issue too. Like @TsingLoo , I noticed that the repo has stripped off the dependency files in the unitypackage files in v5, but had some issues with v4. I took @YRTV 's route where we need to download Steamworks.NET first. The instructions are also stated in the repo’s ReadMe. I copy pasted the below from my comment in Udemy.

I summarized the steps to the below:

  1. Install Steamworks.NET instructions found at https://github.com/rlabrecque/Steamworks.NET#unity-package-manager

→ Make sure to download SteamManager.cs (Point 6) to your Unity Project https://github.com/rlabrecque/Steamworks.NET-SteamManager/blob/master/SteamManager.cs

  1. Install FizzySteamworks from package manager as described here https://github.com/Chykary/FizzySteamworks#unity-package-manager

  2. In your “NetworkManager” object replace “KCP” with “FizzySteamworks” AND add SteamManager.

Read source instructions at: https://github.com/Chykary/FizzySteamworks#setting-up

5 Likes

Thank you @ByteNano, I had performed these steps but inadvertently performed step 2 before step 1. This causes a bunch of GUID conflict errors at Build time, so I removed both FizzySteamworks and Steamworks.NET, restarted Unity, and then installed them in the order you specified and the conflicts went away.

So at this moment I have a successful build of Mirror 55.3.8, Steamworks.NET 20.0.0 and FizzySteamworks 5.0.1.

The only problem now is that when I start the game, I get a console error that says “[Steamworks.NET] SteamAPI_Init() failed” with no other info… :thinking:

EDIT: turned out you have to actually run Steam first - I guess it’s obvious in hindsight, but in my defense I’m used to the SteamVR client auto-opening SteamVR and was expecting something similar here.

EDIT2: spoke too soon - Unity Editor seems to work, but a “built” and “added as a non-Steam game” does not, I get the same console error (I’m using an in-game console viewer to see the console in a built game).

EDIT3: I finally got it working by copying the auto-created steam_appid.txt file from my Project directory to the top level of my Build folder. Then when Steam starts the game it shows up as “Spacewar” (id 480) but successfully initialises the API.

3 Likes

Ah, yes. I got some of those error before. It was great you figured it out!

I actually documented my own problems and solutions in the Udemy RPG course’s Q&A section titled “[Tip] How to get Steam transport to work with RTS (with errors & solutions)” including your last problem. Hopefully it can be a one-stop guide for others having similar problems :slight_smile:

3 Likes

I was able to succesfully implement and play the game with my friend over Steam. I basically found the latest package of FizzySteamworks that still had the Steamworks.NET folder attached, imported it in to Unity. I did upgrade Mirror to latest version earlier which made me to fix up some override methods in RTSNetworkManager.

TLDR: I imported [FizzySteamworks v4.4] (Release FizzySteamworks v4.4 · Chykary/FizzySteamworks · GitHub)

2 Likes

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.

Privacy & Terms