Jump to content

Forums Announcement

Read-Only Mode for Announcements & Changelogs

Dear Survivors, we'd like to inform you that this forum will transition to read-only mode. From now on, it will serve exclusively as a platform for official announcements and changelogs.

For all community discussions, debates, and engagement, we encourage you to join us on our social media platforms: Discord, Twitter/X, Facebook.

Thank you for being a valued part of our community. We look forward to connecting with you on our other channels!

Stay safe out there,
Your DayZ Team

Tatanko

Members
  • Content Count

    3505
  • Joined

  • Last visited

Everything posted by Tatanko

  1. Tatanko

    State of Development: The Future of DayZ

    Well the real problem was that global audio was that global audio was bugged. You could hear people even after you ditched the radio. Fix that problem, and everyone having radios doesn't have to be a bad thing (in my opinion).
  2. Tatanko

    State of Development: The Future of DayZ

    As a matter of fact, after I take a short break, I'd like to take a hard look into the past and present as well :)
  3. Tatanko

    Status Report - 12 Nov 2015

    The NWAF's actual name is "Chernarus International Airfield" ;) As far as I know, there hasn't been one for a long while either. I try to keep tabs on Experimental servers (with help from Odin Lowe!), and I've only ever seen them in the following geographical locations: -US (Central, East, Northeast, Southcentral, Southwest) -UK -DE (Germany) -AU/NZ (Australia/New Zealand) -SNG (Singapore) -SWE (Sweden) (mostly test servers) -GD (Grenada) (mostly test servers) EDIT: Is Brian thinking of the Grenada servers? They haven't been around since the main testing of 0.58 Experimental finished in late August. Those would have been about the closest to Brazil, and would technically be South America.
  4. Tatanko

    Status Report - 12 Nov 2015

    Something like this? https://www.reddit.com/r/dayz/comments/3sz4ol/a_guy_i_had_to_put_down_had_these_unsettling/ That guy had the right idea. For the record, a camera is something that various members of the dev team have expressed interest in implementing ;)
  5. Tatanko

    Status Report - 12 Nov 2015

    I hadn't even noticed that before. Another of my favorite recent games is already using it (ARK), so if the sky will be anything like that I'm pretty excited.
  6. Tatanko

    Status Report - 12 Nov 2015

    I've been curious about this since the second build went out. There's definitely been some changes.
  7. Tatanko

    Status Report - 12 Nov 2015

    Ask away, folks :)
  8. Tatanko

    Status Report - 12 Nov 2015

    Who needs sleep anyway? B) Any idea how soon we'll see the completed features in Experimental? I'm particularly interested in seeing the new weather elements.
  9. Tatanko

    Post Your Gear So Far

    Nice get-up! It's the perfect outdoorsman uniform, right down to the boar pelt backpack. Personally I'd prefer a B95 or Winchester, but you have to get that VSS testing in ;)
  10. Tatanko

    0.59: All New Enterable Buildings

    Nine more buildings were graced with a fancy new interior in 0.59. Let's take a look... Gray Brick Factory Building: Red Brick Factory Building: Wooden Shed: Sawmill: Corner House: Industrial Workshop: Silo Building: Yellow Church: Industrial Workshop #2:
  11. Tatanko

    0.59: All New Enterable Buildings

    Added a ninth building to the list! Industrial Workshop #2 :)
  12. Introduction Being part of an Early Access community as thriving and vibrant as that of DayZ Standalone is a privilege. Few online societies based around a game can compare in terms of sheer voraciousness and passion. Fans of the game may be a bit intense at times, but with a little guidance that intensity can be channeled into useful feedback that can be utilized by the development team for the benefit of everyone. Follow along, and I'll explain how you can earn the sweet feeling of satisfaction knowing you've helped your fellow players by taking the time to organize and properly share your thoughts about the game. Taking Notes First, let's talk about how to capture your thoughts, ideas, and observations so that you can reference them later and use them to submit feedback in some form or another. Personally, I'm a huge fan of keeping a pen and a notepad next to the keyboard when I'm playing, that way I can take notes about a bug I've encountered or write down ideas without having to Alt+Tab out of the game and without risking the possibility of forgetting it all later. Some may see this as old school, but it's important to have a quick and ready method of recording these things. Alternatively you could use a note-taking app on your phone or tablet, have a second monitor or computer available, etc. Now that you've got some way of getting your thoughts down on paper so to speak, you can begin training yourself to take notes as you play. By all means go crazy with your comments, draw doodles, whatever, just remember to be coherent and thorough so that you're not asking yourself, "What did I mean by that?" later on when you go to share the information. Also remember that bad or incomplete information can be worse than nothing at all because it can be misleading or confusing, so be as detailed as possible if you're recording information to report a bug. Feedback can be submitted in many forms, but the most helpful commentary is filing a ticket on the Feedback Tracker. Before you go and create a ticket however, let's discuss what kind of information to gather in addition to what else you may want to include with your submission. The goal of a feedback ticket (or really any constructive feedback) is to provide information that will hopefully result in a problem being fixed. In order to fix anything, the developers need to know how to reproduce that bug so that they can observe it for themselves and determine the cause. If you do not provide them with adequate information to reproduce the bug, then your feedback isn't nearly as useful because it's essentially just a statistic. If you want to be helpful, be detailed in your note-taking so that you can then be thorough in your explanation. When documenting an issue, try and be as scientific as possible. Eliminate variables as much as you can while still reproducing the bug, because the fewer outside factors there are, the easier it will be to determine the cause of the problem. If possible, recreate the bug a few times to be sure that it is both repeatable and consistent. Information you should record and include for submission:1. Where does the bug occur? If it is specific to a location, like the roof of City Hall in Chernogorsk, say so and include map coordinates if at all possible. When it is not bound to a particular location but instead only when walking on a hill, or only when climbing a ladder, etc. then that is what you should be indicating.2. When does the bug occur? Some bugs are triggered by being in a specific spot or by completing a certain action. Is it only at night, only when holding a weapon, only when riding in a V3S, etc.? If you are unable to reproduce it, you would want to indicate that instead.3. How frequently does the bug occur? This is important because not only does it help gauge how severe the bug is, but also tells the person trying to reproduce it how many attempts might be necessary to encounter it.4. Give a short, simple explanation of the bug -- a summary, basically.5. Basic information about your computer such as what operating system it is running and what version of the game you were playing when you encountered the bug (i.e. 0.58.129488). Compiling information for feedback doesn't have to be exclusively text either -- sometimes a picture or video is just as helpful if not better. If you are so inclined, I recommend checking out the the various methods of in-game video capture such as Fraps, Bandicam, Dxtory, ShadowPlay, etc. Many of these same programs will allow you to snap screenshots as well, but if you just want to create one quickly and don't want to install video software, the Steam in-game overlay is more than sufficient for providing evidence to include with your report. That overlay can be enable under your "In-Game" options on Steam. Submitting a Feedback Ticket When in doubt, submit a ticket. Don't assume that the development team is already aware of an issue that you've encountered. Others before you may have encountered the same issue and made the same assumption -- "they probably already know." You can't be sure until you check out the Feedback Tracker. If you've taken good notes and you're satisfied with the information and materials you would like to submit, then it's time to visit the Tracker. Before you go creating a new ticket however, do a search: find out if there is an existing ticket for the same issue. If a ticket has already been started for that issue, contribute additional relevant information or pictures/video as a comment to that original ticket rather than creating your own. This reduces clutter within the Tracker and aids the bug fixing process by making it as easy as possible to reproduce the issue thanks to all of the data being available to reference in one place. You can also vote an existing ticket up or down to help determine its importance relative to other issues. After you have searched and are certain a prior ticket for the same issue does not exist, you can create a new one by clicking the "Report Issue" link at the top. The form you are given will ask you for all of the information I outlined in the previous section. Provide everything that you are asked for and anything else you feel may be helpful in identifying and fixing the bug, including pictures and video which can be uploaded as part of the ticket. You aren't asked for too many things, but it's better to provide too much information than not enough, so detail as much as you know about the issue because you never know what may help track it down. Before hitting submit, ask yourself one last time if what you're submitting is helpful and informative; if not, consider going back and elaborating further or compiling more evidence. Be sure to keep the View Status of your ticket "public" to make sure it's able to be seen. Submitting a report for a bug that crashes the game requires a few extra steps in order to sufficiently inform the development team. In the future, the hope is that it will be possible to send the necessary data automatically, but for now it is a manual process. You will need to do the following things: 1. Add the -dologs command to your Steam launch parameters. Right click the game's name, select Properties, and under the General tab select "Set Launch Options..." In the text box that pops up, add the text "-dologs" (without the quotes). This will allow the game to generate a report about the crash when it happens.2. Gather those crash dump reports. They can be found here on your computer: C:\Users\<Name>\AppData\Local\DayZ\. You will need to copy all of the files from this folder and create a RAR archive from them. Include several for the same crash if at all possible.3. Get your DirectX Diagnostic (DxDiag) report. This program will generate a text file about your PC's hardware for you to include with your submission. Information about it can be found here: https://en.wikipedia.org/wiki/DxDiag Both of these reports can then be uploaded as part of your ticket. If you exceed the 5000kb file limit, please upload the file(s) elsewhere and provide a link to them. The Feedback Tracker can be found here: http://feedback.dayzgame.com/ Submitting General Feedback The Feedback Tracker is where you want to file bug reports, but what if you want to speak your mind about an issue or share an idea that you have? Practical conversation can be informative for anyone involved, and may help lead to a solution for the problem at hand. There is only one sanctioned place for such dialogue and that is the official game forums, but it would be silly to ignore other outlets for discussion such as the r/DayZ subreddit and Twitter. Each site has its own format you'll have to work with, and as such you may choose one place over another based on what kind of conversation you want to have. Before offering up your two cents about anything related to the game, make sure to do your homework. Start with a simple Google search about the topic and see where it leads you. You may also want to browse recent posts by the development team, including but not limited to: Status Reports, Trello posts, official forum threads in the Developer Discussion area, and Twitter posts (many of which are rounded up by the DevTracker on the official forums). With any kind of general feedback, you'll still want to follow the same ethos as submitting a ticket in that you'll want to give some thought to what you're saying first and make sure that not only is it worth saying, but that you've been clear in the point you're trying to convey. It very much helps to remain positive when engaging in talks about a bug or something you disagree with; don't view it as a problem that needs solving, see it as an opportunity to make the game better and do your part to ensure that it happens.
  13. Tatanko

    Do Your Part: The Guide to Feedback

    I'm not typically writing super-detailed notes or anything. I keep a notepad and pen next to my PC at all times regardless of what I'm doing, but when I'm playing Experimental I like to make note of anything new or interesting I find to share later. It's not all about bugs ;) I've had a few random game crashes, but I may have tracked down the issue and it hasn't been all that often really.
  14. Tatanko

    Do Your Part: The Guide to Feedback

    Indeed it is! Good advice, too :)
  15. Tatanko

    0.59: All New Enterable Buildings

    I'm partial to the yellow church myself, but they're all great! Only 6 buildings left to make enterable by the way :o
  16. Tatanko

    0.59 Map Changes: Berezino

    Just a little album of Berezino in 0.59. The southern end and the middle of the city have both seen some pretty extensive changes just like the northern end did in 0.57. Here are some highlights: 1. There's a little quarry! 2. A farm where the construction site used to be. 3. The crane has been moved next to the hospital. 4. The "tank square" has been modified, with added plants and seating area. 5. There's a new camping area (with tents)! 6. The area around the school is totally different, with all of the city's apartment buildings now shifted over to surround it. 7. Many other smaller or less obvious changes like more houses in the central part of town.
  17. Tatanko

    0.59 Map Changes: Berezino

    That's what I'm here for ;) The tents took me off guard. Definitely wasn't expecting them to be there. Sadly no, they're just static. They give the area a nice ambiance though! Now that the entire city has been redone, I don't think I would recognize it if I went back in time 6 months. It's completely different now, and it's mostly for the better in my opinion :)
  18. Tatanko

    Do Your Part: The Guide to Feedback

    MethylBenzine on Reddit made this graphic after seeing my post. I had to share it :) https://www.reddit.com/r/dayz/comments/3rjggz/i_made_a_quick_graphic_from_utatankos_post_about/
  19. Tatanko

    Do Your Part: The Guide to Feedback

    Excellent additions. Thank you very much for sharing :)
  20. Tatanko

    Do Your Part: The Guide to Feedback

    Very kind of you to say :)
  21. Hello everyone, and welcome to my third series documenting the places of Chernarus. This time I'll be showcasing Landmarks. That could really be anything, but it is meant to be iconic places throughout the country that are interesting or have some deeper importance to survivors. As always, head over to the album for full captions. Part 1: Green Mountain Part 2: Hill Figure, Grass Pyramid, Kumyrna Part 3: Prison Island Part 4: Central Railway Station, Grand Campfire Circle, Black Forest, Commissar Statue Part 5: The Witch Ring, The Stain, The Standing Stones, Topolka Dam, Drakon Island Part 6: Devil's Castle, Kozlovka, & Pik Kozlova Part 7: Northwest Airfield (NWAF) First in the series is the omnipresent Green Mountain: http://imgur.com/a/8BbpS
  22. Tatanko

    "The Landmarks of Chernarus" Series

    One last album in the series! Today is a very familiar place for most -- the Northwest Airfield: http://imgur.com/a/9U43X
  23. Tatanko

    A Halloween Cannibal Experience

    (In an effort to make sure my gallery posts on the forum get the "full experience," I'm attempting to figure out a good format for posts like this so that you don't need to click through to another site. Feedback would be appreciated :)) Setting: Main Street, Elektrozavodsk We didn't set out to be cannibals, but we did choose Elektrozavodsk. We thought we were determining our own adventure, but what we didn't realize was that Elektro had already chosen for us. Starring: Skyren, Jukebox Guy, and Tatanko The madam on the left, the musical wonder on the right, and yours truly as photographer. You Can Hear the Wind The evening begins innocently enough. We get the usual grief from bandits looking to take our weaponry, but that's standard procedure by now if we spend time here. It comes with the territory. Stick to the Middle We decide to do some looting, and we keep it to the boulevard to avoid losing sight of each other. Elektro Police Force After rummaging through the police station, we decide to spend the rest of the evening as the authority in Elektro. Surprisingly, many people obeyed our orders and chaos would not arrive for quite some time. We Make a Friend I don't believe he ever gave us his name, but this fellow would be the beginning of our undoing. He very generously gave me a vest that would later help save my life, but he would be the one to introduce us to cannibalism. Jukebox Guy, as he commonly does, disappeared for a little a while at this point. Raw Meat With Two Legs This poor fellow would be our first victim. Without even so much as hinting that we wanted to eat him, he went down on his knees and submitted to us. From there, he refused to say a word. It's like he wanted to be eaten... Make it Quick ...so we obliged. Skyren put the blade of her fire axe square into the silent stranger's skull. Cook 'Em Up One thing Sky and I wouldn't do was eat the meat raw. We felt it necessary to at least cook the meat first. Our new friend had quite the appetite, saying he couldn't wait that long -- downing two raw steaks immediately. Time to Consider We could have ended it there. That could have been our taste of human flesh, and we could have moved on to do something else. A Stranger Approaches Something about the human steaks made us even more paranoid than usual when it came to strangers. The next person to walk along made us very uneasy, and Jukebox Guy appeared from the shadows to protect us because he too could sense that something wasn't right. After making him feel uncomfortable, the second stranger lashed out at us and forced our hand to end him. The Chameleon Following our second kill, this quiet fellow joined our group. We didn't know it at the time, but he would come back to annoy us at several key times later on. He pretended to assimilate himself into the group as a cannibal, waiting until we would drop our guard. Losing It By this point, the brain prion disease was setting in for me. We had already been through trauma repeatedly to boot, and the worst was yet to come. Fill the Barrel Someone brought a barrel out into the street to join our campfire. The person who had introduced us to cannibalism (now wearing a mask in this picture) decided that our goal would be to fill the barrel with human steaks. At this point, yet another person approached the group and was conscripted to be a sacrifice to our cannibalism. Betrayal The silent stranger who I referred to earlier as the Chameleon makes his move, striking at Skyren with his fists and knocking her unconscious while he sits at the campfire with her back to him. This began a struggle that would leave the street filled with bodies. Now We're Talking The son of a bitch triggered a series of deaths that ended with me finally striking him down and avenging everyone else who had gathered. It was a minor setback, and ultimately served to assist in filling our barrel with meat. Cleaning Up the Mess Skyren and the original cannibal make their way back to the scene eventually, and we begin the task of carving up all of the bodies festering in the street. Strange Barbecue As quickly as the group had been slaughtered, our numbers swelled right back up. Many curious bypassers joined in on the fun, including one fellow who would turn out to be genuinely innocent. Cook Time: 20 Minutes We spent quite a while cooking up steaks. More Approach Additional people kept stumbling upon our illicit activity. They seemed okay with it, so we continued to let people join in. Cruel Intentions The man face down on the ground with rope around his wrists was the result of our boredom. We had gotten so used to the action that as soon as there was a lull, I snuck behind the fellow slipped the rope on him. This caused quite a ruckus, but everyone went after him... not me. Eye of the Storm Here we are seeing a rare moment of calm in the middle of a cloud of chaos all over this part of Elektro. While seemingly everyone else struggled against each other, a few of us sat and ate by the fire. Getting Crowded This doesn't quite convey the peak number of people at the feast, but this is about the time it started to go downhill completely. Watching Carefully In the battles that followed the crowd expanding in size, very few survived. I escaped to relative safety on the roof of a nearby office building and kept an eye on the campfire. Can't Keep Going Skyren and I decide that we've had enough for one night. Surveying the ruined remains of the poor souls that perished here this evening, we can say it was worth the fun.
  24. Tatanko

    A Halloween Cannibal Experience

    Thanks, Gary! I do wish I had more direct control over the image behavior, but alas...
  25. Tatanko

    A Halloween Cannibal Experience

    Soon, my friend! ;) I'll play around with it. Thanks for the tip!
×