GitHub and Unity

[mikha42]

I posted an update that fixed 'Weird Playmaker errors' and i recently narrowed it down to Github. I made a backup of the project and re-instaled the project from Github, i received 7 errors about the 'Photon Unity Networking' that where the same exact errors i got on the update. What can we do about that?

The error is "Assets/Photon Unity Networking/Plugins/PhotonNetwork/LoadbalancingPeer.cs(11,24): error CS0234: The type or namespace name Photon' does not exist in the namespaceExitGames.Client'. Are you missing an assembly reference?" and its the same thing seven times but at different directories.

[mikha42]

This error makes all playmaker FSM's not work. And when i reinstall it can't find any of the scripts.

[frenchjam]

I am going to look into this, but probably not until this weekend. The problem may be in the layout of the windows. One of the modules that I use is a custom module used to program sequences of events, called Timeline. I haven't given it to you because I do not yet have the right to distribute it. But that module creates editor windows and other resources that I don't know about. And it was included in my project when I made the first GitHub deposit.

So one thing that you could try is to reset the window layout to one of the defaults and then reconfigure it from there. I'm not very optimistic that it will fix the problem, but it is worth a try.

[mikha42]

I think it might be that, because when i open the GitHub client it says a few files are deleted.

[frenchjam]

I also have the message that certain files are deleted. In my case they are .meta files. I think that if .meta files are deleted they automatically get generated again, but that it’s better to track and save them with the original file. I had 5 .meta files listed as having been deleted, even though I did not delete them. I synced anyway with GitHub to see if it would cause a problem. I exited and restarted Unity and it’s working fine. Maybe you could make a change somewhere and then commit in GitHub and sync. We can see if it still works after that.

Joe

On Feb 13, 2015, at 5:41 PM, mikha42 notifications@github.com wrote:

I think it might be that, because when i open the GitHub client it says a few files are deleted.

— Reply to this email directly or view it on GitHub.

[mikha42]

I'll try that. But something weird happened yesterday. I was looking at the Top-Down SF models and Unity crashed. I reopen it and it continued to crash repeatedly. Could this be related to GitHub? Or is it just a Unity bug? It could be that it had a lot of stuff to render and couldn't handle it.

[frenchjam]

It could be GitHub, but I’m guessing that it isn’t. You may be right about Unity not being able to handle all of the Top-Down stuff. Maybe you could try creating a new, empty project outside of the directory that we are using for GitHub and then just load the Top-Down stuff in a new scene and see if it still crashes.

[frenchjam]

I have been playing a little bit with GitHub and with the Top-Down stuff.

I read that it is important to keep part of the Library files so as to keep links between instances. So I changed the .gitignore file (Settings tab in GitHub). Since then, it has been stable for me. But that does not necessarily mean that the problem is fixed.

In the Unity editor, I set the Edit->Project Settings->Editor Settings->Version Control to 'Visible Meta Files' and Edit->Project Settings->Editor Settings->Asset Serialization to 'Force Text'. You might want to check that your editor has the same settings before you do anything else. I cannot tell if these settings are updated when you sync with GitHub or not.

I also imported the Top-Down assets, but I excluded the parts that modified things in 'Standard Assets'. I also exclude Atlas1.tiff, because it is too big for GitHub. I then made some minor changes to see if everything still works.

So far, all is OK, but we won't know until you sync GitHub, make a small change, and sync it back again so that I can see what happens here.

[frenchjam]

[frenchjam]

GitHub is now ignoring Library/metadata, but this might cause some new problems. We will see after the next commits and syncs on both sides.