Steam installeren
inloggen
|
taal
简体中文 (Chinees, vereenvoudigd)
繁體中文 (Chinees, traditioneel)
日本語 (Japans)
한국어 (Koreaans)
ไทย (Thai)
Български (Bulgaars)
Čeština (Tsjechisch)
Dansk (Deens)
Deutsch (Duits)
English (Engels)
Español-España (Spaans - Spanje)
Español - Latinoamérica (Spaans - Latijns-Amerika)
Ελληνικά (Grieks)
Français (Frans)
Italiano (Italiaans)
Bahasa Indonesia (Indonesisch)
Magyar (Hongaars)
Norsk (Noors)
Polski (Pools)
Português (Portugees - Portugal)
Português - Brasil (Braziliaans-Portugees)
Română (Roemeens)
Русский (Russisch)
Suomi (Fins)
Svenska (Zweeds)
Türkçe (Turks)
Tiếng Việt (Vietnamees)
Українська (Oekraïens)
Een vertaalprobleem melden
Every monster respawns when using a shrine, with all their gear - except me! I do not get back the very expensive bombs and other consumables that I had at the last save.
Inside the ziggurat the mini boss has a wave attack that is sometimes broken, leading to a floor that is mostly instant death.
Boss sword attacks go through some barricades like they aren't even there. Dark Souls quality collision detection.
Maybe focus less on the plushies that will go to a landfill and more on polishing the user experience.
Please help
After playing Tunic for 4 hours the first time, I am now always stuck on the loading screen after selecting "Continue" from the main menu. The loading icon just plays endlessly. I have an Acer Predator Helios 2019, so it meets the requirements in order to play.
I've tried a number of things to fix this and failed:
1) Restarting the game
2) Restarting my laptop
3) Reinstalling Tunic
4) Verifying integrity of game files through Steam
5) Updating graphic drivers
6) Quitting other processes that could interfere with Tunic
7) Deleting the save files, only for them to appear again
I believe I've narrowed down the issue to corrupted save files, because I'm having the exact same issue as this person on Reddit[http//%28https], down to my original save having no money or pages and 1 in every stat when I go into the "Load game" option.
I checked the save file (fortunately it's in plain text) after I already placed all hexagons in the temple and could find the following:
Placed Hexagons ALL|1
SV_HexagonPlinth Construction Yard_hexagon plinth|1
Got Hexagon 1 Red|1
inventory quantity Hexagon Red|0
Got Hexagon 2 Green|1
inventory quantity Hexagon Green|0
Got Hexagon 3 Blue|1
inventory quantity Hexagon Blue|3 (*)
Placed Hexagon 1 Red|1
Placed Hexagon 2 Green|1
Placed Hexagon 3 Blue|1
(* I went back and got the blue hexagon 3 additional times after it vanished from the inventory, that's why there is a 3 now)
Since the hexagon only disappears after the save file is reloaded and since only then you can get the hexagon from it's original place again, there must be some sort of $variable that is not stored or correctly stored in the save file.
If the player defeats the Scavenger Boss, then proceeds to rest and close the game, the player will be missing the Blue Gem. To be fair, I went back to the boss fight area for them and the Gem was right there- and I didn't have to redo the boss fight. It's just surprising. I imagine there is a check-point system in place to make sure the player doesn't miss anything, but I didn't realize it for a bit upon reloading my save.
Inputted the sequence, since it wasn't my first time around and i found the corresponding manual page spelling out the solution. Chest spawns at the exact place to completely block off the maze in the room. There's plenty of space at the entrance, pretty big platform in fact, but the chest is spawned at the path, completely blocking it. If i used the sequence from inside the maze - i would've been softlocked inside!
Please, just move the chest, like, 1 "tile" to the bottom-left/right!
Spoiler because of endgame area and mechanic.
I went to visit the swamp once again after obtaining the hero's laurels. After entering the area, I kept teleport-dashing in a straight line. There is a hole filled with water ahead, where a fast-travel platform would have been. I continued to dash when I arrived at the floor's edge, and somehow I did not hit an "invisible wall". Instead I went into the hole, fell through the water and died out-of-bounds.
Here is a video of what happened (actually recorded the second time it happened, so there is my soul from the first death floating there, but it is irrelevant to the bug) : https://www.youtube.com/watch?v=Y6hhberFnE4
I also tried a few times to walk to the edge and then teleport-dash into the hole, but the issue did not occur. Maybe I landed on just the right spot when dashing from the area's entrance, and I simply did not find it this time.
(Also, I spent a really good time playing the whole game, great work guys!)
I discovered that I can get the shield and focus buttons to work if I unplug the controller, rapidly tap the controller's shield and focus buttons while plugging it in, it will sometimes work properly, but it takes more than a few tries and doesn't always work. I have no idea why it happens or why it starts working, but this worked for me for some inexplicable reason. I suspect something to do with Steam Mappings, especially if your controller is an off-brand controller or something.
Try unplugging the controller, tapping the shield/focus buttons and plugging it back in as you do for a little bit if you can manage it. For some reason, this is the only controller I have that does this, and it's being filtered through an adapter, so it's much more likely to be a Steam/Adapter thing than a controller thing. Let us know if this works out!
Here's three short video examples of the Fire Sword card's hitbox issues:
https://drive.google.com/drive/folders/1ooAKPdsiFYsnKHls-HUkTJJNG3kmKR2-?usp=sharing
I can buy a bundle somewhere, where the game is included but I would like to have it here, which is why I ask if I can count on a key here when I buy it. I wanted to avoid this question since I don't know if the steam guys hit me on the head again for a unlucky sentence.
I think that is some emergency charity thing.
Your email doesn't work and it doesn't look like you have taken the friend request yet.