Terrifying / supernatural timeScale setting-changed issue??

[Fattie]

This has freaked me out.

In short, I was working on a project (folder “AA”) and strangely it basically would not run correctly - halted early in the scene.

I wound back to folder “BB” the most recent version. Worked fine. Zero changes between the two – diff identical.

I made copies “CC” and “DD” just in case.

I would quit Unity to change between AA, BB, CC, DD etc – sometimes I would just “Open Project”. (Perhaps this is relevant if anyone has experienced the issue.)

The next morning I opened BB and it also exhibited the problem

CC was still fine. Note that I changed nothing anywhere.

A little later … CC also had the problem. WTH !!

Another Mac on another desk … and again … in a word, the problem would seem to “infect” projects - along the lines of “after opening them about three times”

Recall that I did nothing to the project folders other than open them and run them. Later I would deliberately not even “save” when quitting … the “ongoing infection” problem still happened.

Anyway, I realized “it’s like the time scale is zero” … but we never touch .timeScale in that project and I confirmed that. I looked at the Edit - settings - time menu item. Sure enough … the timeScale had been set to zero, actually in the project settings

I have many (perhaps 5) backups at all time. The same thing kept happening, on a selection of Macs, I’d drag it out of backup, and after a few open/plays or even just opens (not even playing) this problem would “infect” the project.

In a word it would seem that … after taking a fresh copy of the project … merely opening it a few times … (not even ‘saving’) …

the project settings value of timeScale would be set to zero.

(to repeat, I do not touch timeScale at all in any script)

There must be a rational explanation for this ?? I’m concerned the most recent mac i bought is haunted, or there are other supra-conventional forces involved?

Has anyone ever seen anything, at all, like this ??! I’m scared

[RyanZimmerman87]

My guess is that somehow one of your PlayerPrefs must be causing this since the different builds share them.

I would double check your PlayerPrefs, or manually set your timescale to 1 when you launch the game in your Start() functions. You could use a public static int to set it if you can’t figure it out.You could even use a PlayerPref for the Timescale as a way to try to isolate or control the problem?

That does sound really weird though I’m not sure if my answer will help.

[Loius]

This absolutely did happen to me, though only one time and I have absolutely no idea how to reproduce it. I believe a Unity crash was involved with mine, and I distinctly recall being puzzled because I wasn’t playing with time. I don’t remember what exactly my time was set to; pretty sure it was zero, might have been 0.2

I, uh… I deleted the project. It was one of the first things I’d made just messing with Unity, I didn’t have any attachment to it. Probably… probably not a good answer.

And I’m on Windows. :S