controls are way too glitchy for the game to be considered playable.
SkyCharger
Recent community posts
On win 11:
LMB doesn't do anything.
While levels 1 and 2 can be done without it, on level 3 this seems to create issues that cannot be resolved by the player, rendering said level impossible. (even if you get a good shape [highly unlikely], there is little to no chance that you can grip it in the proper place)
For some reason the game renders only (what i believe to be) the skybox
checking log.txt shows two errors
A.
System.FormatException: String was not recognized as a valid DateTime. at System.DateTimeParse.Parse (System.String s, System.Globalization.DateTimeFormatInfo dtfi, System.Globalization.DateTimeStyles styles) [0x00029] in :0
at System.DateTime.Parse (System.String s, System.IFormatProvider provider) [0x00007] in :0
at System.Convert.ToDateTime (System.String value, System.IFormatProvider provider) [0x0000b] in :0
at System.String.System.IConvertible.ToDateTime (System.IFormatProvider provider) [0x00000] in :0
at System.Convert.ToDateTime (System.Object value, System.IFormatProvider provider) [0x00003] in :0
at Newtonsoft.Json.Linq.JToken.op_Explicit (Newtonsoft.Json.Linq.JToken value) [0x0005c] in :0
at Newtonsoft.Json.Linq.JToken.ToObject (System.Type objectType) [0x0027e] in :0
at Newtonsoft.Json.Linq.JToken.ToObject[T] () [0x00000] in :0
at Snapshot.Saving.SaveManager+d__14.MoveNext () [0x003e4] in :0
B. (recurring)
Screen position out of view frustum (screen pos 668.000000, 507.000000) (Camera rect 0 0 1600 900)
A. Stair climbing is for all intents and purposes non-functional. (it doesn't autoclimb the steps and 99 out of a hundred times jumping from step to step is auto-aborted for no legitimate reason)
B. Moving platforms should allow the player 'stick' to them. (made extra frustrating due to the aforementioned)
C. The physics puzzle in the first room with deliberate reset door doesn't seem to have a solved state. (behavior of ball (as if spork is always hanging [even after it's cut loose]) suggest that there is a state mismatch somewhere in the puzzle's coding)