Nainstalovat Steam
přihlásit se
|
jazyk
简体中文 (Zjednodušená čínština)
繁體中文 (Tradiční čínština)
日本語 (Japonština)
한국어 (Korejština)
ไทย (Thajština)
български (Bulharština)
Dansk (Dánština)
Deutsch (Němčina)
English (Angličtina)
Español-España (Evropská španělština)
Español-Latinoamérica (Latin. španělština)
Ελληνικά (Řečtina)
Français (Francouzština)
Italiano (Italština)
Bahasa Indonesia (Indonéština)
Magyar (Maďarština)
Nederlands (Nizozemština)
Norsk (Norština)
Polski (Polština)
Português (Evropská portugalština)
Português-Brasil (Brazilská portugalština)
Română (Rumunština)
Русский (Ruština)
Suomi (Finština)
Svenska (Švédština)
Türkçe (Turečtina)
Tiếng Việt (Vietnamština)
Українська (Ukrajinština)
Nahlásit problém s překladem
Please do, or default it to silent running. If we have to log out in a hurry this or being outside or hungry occasionally results in death.
For people who experience a long initial load, leaving the PC to grab a bite or drink or use the bathroom is not uncommon, and can cause problems in a game where you need to get O2 every minute or so or die.
This would be very nice. Along with keeping the sub in silent, or defaulting to silent.
Over the past few days, Klegran [developer] has been in constant communication with the forum and said some wonderful things. First, he was made aware of an issue that allowed the Cyclops to take damage from Ampeels (area damage oversight). He promised to take care of it. He then made it impossible for the Cyclops to take damage while the character was not in the Cyclops (no more going back to a destroyed sub). He also asked if we wanted to make it so that the running state (silent, slow, medium, flank) was saved on exit.
These changes make it so that the only way a Boneshark will shred it is through pure neglect from the player (i.e. sitting still, no counter-measures, ignoring fire, etc). Keep in mind, the Boneshark damage to the Cyclops is only 30 hp per hit and it would take many hits for a fire to spawn. The fire will then drastically increase damage if left unattended for too long.
I think you will find these changes beneficial.
So I jumped outside, as I hear the voice tell me the sub is on fire.
I used the seaglide to fully check the exterior of the ship, not a single hole to fix.
I then went back in to find the fire and put it out, but I could find no fire and there was no smoke either.
I was going to go to the bridge to check the damage display, but the screen goes black. And I spawned back at my life pod...
What the hell?
It sounds like some kind of graphical error. I think you clearly suffocated from the smoke, thus making your screen black and respawn. No idea why the damage wouldn't be showing or you wouldn't see fires/smoke.
I didn't even know it was possible to get kicked from the camera for excessive damage though... Lol. That's what the camera is for, so you don't hit things and take damage.
I figured I 'died' because the cyclops blew up. I was not inside very long (less than a minute) then the screen blacked out.
Things like having ampeels not damage it or making it invincible when I'm outside the sub don't "fix" me not enjoying the update. The reason I dislike it is that I find it hard to believe that you can cruise past bonesharks in silent running, yet if you switch the lights on, they attack and shred it with such ferocity. I don't find it satisfying that such they're so polarised and that such a tiny creature will ram such a large and solid vehicle like that.
It's not about balance so much as atmosphere.
Well I was thinking it might be an issue with the camera kicking you. Since it's never happened to me, I don't have any experience with it.
Maybe the game doesn't update the fires/damage until after you leave the camera view to help with performance (no idea, totally guessing). For some reason when the camera kicked you, maybe it didn't update.
As far as the Cyclops exploding, when I use the destroycyclops command you can see a series of explosions coming at you. This sequence should be the same without using the command from videos I've seen but I've never naturally destroyed the Cyclops myself.
If the smoke was killing you though, you'd just slowly lose health until you died. You probably would've noticed your health dropping however... BUT if the game isn't updating the HUD you may not actually know it. Then again, the explosions simply might not have displayed since nothing else was... You could try to reproduce it by slamming into that rock some more to see if it was something you can duplicate or a one off glitch.
I went around bashing the Cyclops into things at flank speed while in the camera view. I got pretty close to 90 degrees once and I got it completely sideways a few times. At no point did I actually get kicked from the camera view.
It took a pretty massive effort to actually destroy the Cyclops, without repair damage or putting out fires. I got an immediate fire warning (audio and visual) as soon as the first one started. I continued to get multiple warnings as the fire spread. In addition to that, I also had visual and audio smoke warnings. As the smoke thickened, a smoke animation started to creep in from the corners until I only had a circle in the center. I was also coughing, which got worse in response to the smoke.
I actually thought the whole thing was really well done. ¯\_(ツ)_/¯
Well it would certainly be more convenient. Personally I choose specific speed- and light-settings when parking my Cyclops for a reason.
That it resets on each time I load the game is just annoying :/
Aside from that, I love the changes to the Cyclops. It doesn't feel like a game-breaker anymore while still going strong.
Why do you think a pack of armored predators wouldn't attack a larger animal they perceive as a threat or pretty?
https://youtu.be/chVk5ziw0lM