Unity Scene Files not transferring properly through TFS between Windows and OSX - windows

This is a strange circumstance that my boss and I just got into this morning as we were trying to import my scene from the Team Foundation Server to his machine. I created a Unity Scene file and made my scene over the course of the past month or so and when I was finished I uploaded everything to TFS so he could pull it down and use it (we are quite far apart from each other so we can't just usb drive everything over to see what the problem might be). When he pulled the scene file down (and all the supporting scripts) one of the scripts that was in the scene was changed. It started out being a script called Smart_HUD4 but when he went in to the inspector the script was now called Smart_HUD2 and was an entirely different script than what I had written, not to mention I don't even have a Smart_HUD2 script on my machine. The same also applied to another script called laser (now called Laser1 and again, not something I wrote nor is it on my machine).
Has anyone else come up against a problem like this? Found any solutions? It's strange because I went ahead a re-downloaded the files I uploaded and everything was exactly how it was supposed to be, proper names and scripts in their proper places. We think the issue is because we are moving from Windows to OSX and the differences in operating systems might be leaving behind some residual code or something that is causing things to be switched around?
TFS never asked me to merge any files so if it is the case that TFS might be auto-merging files, none of the files its merging even share the same name, its just picking ones whose names are close and doing so (the scene file's name was completely unique so it has nothing to merge that with).

OK, few things to check:
Have you checked that the files do not exist in the TFS with similar naming? regardless of TFS requesting name changes?
do you have any other projects effected?
Have you checked (I'm guessing you have) that the unity versions are matching exactly?
Now, something to consider, The unity system does vary between Windows and MacOS, mainly in the fact that Unity Makes use windows bases features that are not present on a Mac and this can cause file issues.
When moving between systems, Unity packages the scene data on windows in a global and local format. So, sometimes folder structure can change.
From experience, the most likely issue is more to do with file locations than OS discrepancies, as it might have been a clash between your project and other similar.
Remote file management is odd at times when doing colab stuff. Have you checked with other colleagues made sure they don't have anything similar uploading?
But, scripts changing names and data is not something that I would expect. So my guess is that the issue lies with the upload on the TFS and not the MacOS vs Windows move.
Hope this helps,
Glenn

Related

Xcode files disappeared from Mac

Mostly I am just sad I guess. Yesterday I finished an iPhone app in Xcode 10.2.1, loaded it onto my phone (it works nearly perfectly), and shut down Xcode. The app is on my phone and working, but when I opened the Xcode again the code (viewcontroller, AppDelegate, and storyboards) have no data. To be clear, the folders and files are still there, but the code/data is not. I did not have time back up the finished version. Is it possible to retrieve these from my phone? Or is there some other place to look to find it? Or am I stuck rewriting it (there are some iterations so it is not starting over completely, but it still sucks).
thanks
Is it possible to retrieve these from my phone?
No, your phone contains only the compiled object code; it won't have any source code.
Or is there some other place to look to find it?
It's hard to imagine how the code could have simply disappeared, so one would think it's probably there somewhere. I wouldn't think that you could compile an app without saving the code, and if you saved your work then it certainly shouldn't just be gone. If you can remember even just a part of a phrase from the missing file(s), you can search your machine for files containing it. Use Spotlight or even just grep for that.
If you're unable to recover the file(s), then rewrite it as soon as you can while it's still fresh in your mind. And use the experience as a lesson. In the future you should do both of the following:
back up regularly: Use a backup system that works automatically. Apple's Time Machine works very well for this... all you need to do is plug in your backup disk and let the machine do it's thing.
use revision control: There are a lot of options here, of course, but git is free and private Github accounts are also free, so you can save your work remotely. If you don't know how to use revision control, learn -- it's an essential development skill.

How to share easily files between Mac OS X and Windows 10

I am asking if anyone of you know the best solution for this case:
This semester I have to make a project with an eye tracker (Tobii Eyex), but the problem with the hardware is that it is only compatible with Windows. So my question is: Is it possible to code on Mac and then get the stuff with ease on Windows, but only in a few seconds?
I tried it with file sharing, but the problem is that I can't keep two Unity instances running on the same project.
The perfect solution would be, if I have made any changes, the Windows PC should automatically update the files.
Use Github. It will allow you to keep your entire project synced across all devices with minimal effort.

Why is project and file saving/management so awkward in programming as compared to other digital media?

TLDR: What is the reason for the complex file management systems in place, such as Github repositories, when working in Visual Studio?
This has been bothering me for a while. I've finished a diploma course in Digital Media, and have started another course in programming. One thing that stuck out immediately after coming from 3D art is how incredibly awkward and obtuse basic file management is when working with Visual Studio. Presumably the same issues arise with other development environments, as if they didn't I can't imagine why anybody would ever use VS.
For example, let's say I want to work on a project in 3ds Max. It's stored on a shared network drive, so I don't want to risk two people accessing it at the same time and saving over each others work. I simply grab the folder or file that I want to use, copy and paste it with a new name, and then I'm good to go.
Saving things with a new name is easy, just save as, rename it. I can work from network drives, local drives, portable drives. The file can come from anywhere and be saved anywhere. Everything is fast, painless, and clear.
If I was to try and do the same thing in VS, for starters, it wouldn't let me build the program while saved to the network, so I'd have to copy it over to a local drive. Presumably this is to prevent the "multiple people accessing, saving over each other" issues that are easily avoided by just renaming the thing.
If I wanted to iteration save, that is, to frequently save the project with a version number name to allow easy rollbacks and troubleshooting, I'm not even sure how I'd do it. Renaming projects/solutions has proven so hard to do that I've had to delete projects and make them again with a new name, rather than try and figure out how to it properly.
There are all sorts of complex file management systems that VS seems to require for any large project work, all of which would be completely unnecessary if you could just copy, paste, rename and save-as with any real ease.
I'm obviously rather new to this, and I'm certain that there is an important reason why it's so awkward to manage files, I just don't know what that reason is. I feel like I'd have a far better understanding of how all these file management systems actually work if I knew why they existed in the first place. At the moment, just trying to be able to work from a network drive is taking up hours when it would be a non-issue in every other digital media field I've worked with.

File History in Windows 8.1

I know this question has been apparently asked here and here
But mine is different.
Do file histories include only extensions such as pdf, jpg, mp3, doc
etc
File history for moved files is available not just deleted ones?
At preset I am accessing C:\Users\Myname\AppData\Roaming\Microsoft\Windows\Recent folder
But here I am not able to see recently modified files which come under a directory in Users\Myname folder. Why do all recent files not get mentioned here?
Is there place where these settings can be changed?
Is it possible to look up recently accessed/modified folders?
I have a developing background in assembly and C but restarting after more than 6 years. I saw other threads where they were doing things programmatically but did not understand much and looked their requirements were different from mine. I am willing to try out programmatic solutions if an online source is pointed to.
I take a regular back up of my files, but yesterday happened to give my PC into someone's hand when learning something and the person was an impulsive shift deleter not even bothering with the messages on the PC and was not very aware of what was being done or happening.
Question 2 is because I have earlier accidentally moved folders into another folder in a previous PC
I found this when I was trying to help somebody else find a file they recently accessed
In Windows 8.1 there is something called "Recent Places" under Favorites in File Explorer. This was in the same favorite list where I had kept Recent Items and still did not notice it because of getting panicky. This showed me the folders I had accessed something I really wanted a week back. It would have saved me so much tension and my precious time.
Now am planning to update to Windows 10 and google searched if I will still have access to this data and found this
http://answers.microsoft.com/en-us/windows/forum/windows_10-files/restore-recent-places-to-windows-10/037af727-9b06-485e-bb45-4a6c60a3f222?auth=1
Hope this is useful to someone

What's the diff between VSS 6.0 and VSS 2005?

We've been using VSS 6.0 since time began, but yesterday I nabbed VSS2005 off of our MSDN subscription, it wouldn't let me install it off the ISO through Daemon Tools (not sure why, but I submitted error report to MS...). I noticed it had a program files directory right on the ISO, so I just copied the folder onto my hard drive. Well, I opened up the client and behold, a glamorous version of VSS 6.0 connected to the exact same DB.
Anyone know if I'm going to destroy everything by using it?
We moved from VSS6 to VSS2005 just over a year ago. The database structure is identical. The only caveat we found was if some people still used VSS6 on a database where others were using VSS2005. VSS2005 treats Unicode text files as text files, whereas VSS6 does not. Which means that when VSS2005 adds a Unicode text file, VSS6 sees it as binary (this affects csproj files among others).
Other than that, VSS2005 supports proper HTTP access to the database (provided server extensions are installed), improved LAN performance (again, with server extensions), and better file system dialogs (the nasty old ones are gone). However, the new file add dialog shows ALL files, not just the ones that aren't included.
Also, VSS2005 allows the provision of custom editors and differencing tools by file extension, which is very useful. For example, some of our XML files are encrypted, so we run a decryption tool before the difference tool by using this system, which has increased the efficiency of our review processes substantially.
There are also other tweaks here and there, mostly good but occasionally annoying.
Finally, nothing has been destroyed. In fact, there appears to have been less additional corruption in the database since the transition - but I wouldn't put this down to the new VSS as it wasn't a comprehensive test.
I'm pretty sure, that there is no more danger of destroying anything than when using VSS 6.0.
It's quite a long time ago since I last used VSS, but we also updated from version 6 to version 2005. As far as I remember, there were only some cosmetic changes in the client (VSS explorer), but the format of the database and also the available feature were exactly the same than in VSS 6.
You should be fine.
Since VSS just uses a file share for everything, and there's nothing that is really server based, you're fine. Not much has changed in the format of the database, mostly client side stuff.

Resources