Hey, this is a thread for reporting issues with the game, such as:
- Bugs
- Difficult/Impossible Levels
- Typos
- etc.
Please keep posts concise and on-topic please.
Hey, thanks for trying the game & reporting this issue;
First thing - what platform are you playing on? Windows/Mac/Linux
For Level 2, it should be what you're expecting: scroll up, put a token onto the node, then fill in the nodes to the final triangle node (When you drop your first token in that level it starts the countdown clock)
How did you scroll around the map? Arrow keys, mouse, something else?
This may be a tedious note, but can you give Level 2 another try using the arrow keys to navigate up to the top node? You want to have it close to the centre of the screen to trigger the next step.
Level 3 should just tick along fine, the only thing I can think of is maybe you were hovering your mouse over one of the tutorial panels? (They pause the game timer to let you read them)
(And yes, N skips ahead one second, but that's intended as a helpful button during gameplay, not the only way to make progress)
Hi! Thanks for the quick reply. I'm playing on Windows (installed the game via the itch desktop app, if that's relevant). I was scrolling using the mouse.
Just gave it a try with the arrow keys, and it then did proceed with the tutorial, showing the worker tokens and unpausing the game. On a second try, it now also works with the mouse. I also figured out why it wasn't working for me the first time: If I'm already at the top of the screen by the time the second tutorial box (the "Scroll up to the node" one) pops up, then it doesn't proceed unless I move the screen again. Sometimes it doesn't proceed at all.
Generally the game doesn't seem to handle early inputs well. If I manage to scroll to the top of the screen before the first tutorial box ("Pan with the mouse or arrow keys") finishes fading in, it doesn't proceed to the second box either until I move again. At some point I managed to pan before the "Level 2" pop up appears, causing none of the game UI to appear at all.
Level 3 is still not ticking - maybe I need to complete Level 2 first?
During my testing of Level 2 I found another bug: During the first loop, the clock didn't show up (the game did tick though), and after I failed to complete the task in time I got this screen:
where I cannot place a token in any node now and the game is not ticking again. I tried hovering and unhovering the hint texts, but that didn't unfreeze the game. Sadly I am now always stuck on the "tutorial not proceeding" bug so I can't test this bug any further.
Ok great - yeah I wrote the tutorial to be pretty slow-paced, I didn't think of people managing to pan during the "Level XX" title. I'll look into it now & attempt to patch it.
For your screenshot, I vaguely remember that bug, but can't remember how it triggers. Can you navigate to <username>\AppData\LocalLow\BigHandInSky\ForgetfulLoop\...
And send the Player.log & Player-prev.log to bighandinsky@gmail.com please?
Some more testing: Restarting the game seems to temporarily fix the "stuck" issue. If I correctly solve Level 2, the game proceeds to Level 3 and starts ticking, yes. Sometimes if I go back to Level 2 I get this pop up, which I believe belongs to Level 3? Can't reproduce the stuck tutorial bug at the moment.
Uh oh! Yeah that sounds like something isn't loading or setup correctly. Those levels are copies of the original gamejam levels, so yes it's bonus content, but should work fine.
When you have a moment, can you send me the player.log & player-prev.log files to bighandinsky@gmail.com?
Windows: %USERPROFILE%\AppData\LocalLow\BigHandInSky\ForgetfulLoop\Player.log
macOS: ~/Library/Logs/BigHandInSky\ForgetfulLoop/Player.log
Linux: ~/.config/unity3d/BigHandInSky\ForgetfulLoop/Player.log
Otherwise, try closing the app, launching it & try playing one of the levels again? Could be some game state that isn't being cleaned up.
(Edit: and thanks for the kind words 馃榿, sorry you ran into this bug)
Gotcha. Will look at the logs over the weekend.
With level 1, it's intended that the first few loops are "empty", as back in the Gamejam I used the popups to do some dialogue with. Just to clarify - level 1 just plain doesn't ever show nodes after a couple loops? or anything?
Oh - and which platform are you playing on btw? As I only have the ability to test Windows builds I'm afraid.
Ah no! Hmm, so ok: can you go to the game's save folder (see the FAQ) and send both .log files to bighandinsky@gmail.com? (Title "Tutorial bug" please)
After that, try playing it again, but take it super slow - don't move the node tree at all until the relevant panel shows (I think the bug is due to a very specific timing when moving the map. I thought I managed to address it in a patch, but sounds like I didn't 馃槵)
馃憢 hey, thanks for noting this.
Yes that sounds like a bug. iirc a Switch only considers "unfixed" nodes; but that should be a valid switch-back.
I'll try finding some time in the coming weeks to fix it, but it's unlikely to be soon as I concentrate on Day of Maintenance.
Please let me know if you find other odd interactions 馃檪 (Hope you're enjoying the game!)
Hey 馃憢
Hmm. It's been a long minute since I looked at the code for Forgetful Loop, and I'm going to be busy for the next few weeks. But from running into a similar issue with MDay's settings code, I think this is my settings menu code displaying the resolution/fps incorrectly.
Essentially I think you can ignore it - Unity defaults to the highest refresh rate regardless of what you pick - it's my code rendering the lowest refresh rate (Sadly I'm unsure why Unity/my code does this 馃槓)
Let me know if you do run into issues with the refresh rate being weird 馃檪 Sorry that I can't be more helpful right now.
Hey, you are absolutely right! When I use Windows G to capture frame rate, it is indeed 60Hz. Thanks!
The last (18th) level in Branches (chapter 5) seems to have a bug where one of the switch nodes will only 'go around' once and then get stuck in one position, making one of the connected nodes inaccessible. I managed to pass the level regardless by planning for a single 'go around' (so no rush!) but just wanted to let you know. I'm guessing it has something to do with how the switch will skip over 'finished' nodes, maybe it's mistakenly thinking an 'unfinished' node is finished? I don't have a mid-game screenshot, but i circled the node that breaks. I'm on Linux btw
