- User Since
- Dec 26 2013, 6:23 AM (396 w, 4 d)
May 10 2016
A simple search for "blur" would reveal this bug has already been reported.
Earliest that I could find: http://feedback.dayzgame.com/view.php?id=1547 (top comment saying it's a duplicate, but the link provided is for a different graphical issue)
Not trying to be an ass, it's good that you're getting involved, but try to find similar issues and upvote them in the future.
What mistakes have I made? Here's a list of things that happened in order:
- I post bug report on odd characters displaying on a certain book. (bookname.jpg)
- You come along and tell me it's a feature of damaged books, downvote the issue.
- I prove that this is not a feature of damaged books (BadlyDamaged.jpg and MoreProof.jpg, all titles intact)
- You tell me that isn't enough proof, say I need to find the same book in pristine condition.
- I find the book in pristine condition, (final_proof.jpg) still the same error.
- You still claim damaged books have this feature, and now also state that my issue is indeed a character issue, but that you told me so earlier.
- I remind you that there is no such feature for damaged books, again, and remind you that you were the one claiming my character issue was a feature, and not a character issue.
So I've been right on all fronts regarding this issue, whereas you've been wrong at every turn.
The only thing you've been right about, is that special characters are missing. My argument was that in the case of this book, they were being replaced by question marks. That's all. you said no, you got proved wrong. End of story, surely?
@Snapydubi: Hah, yeah. but that's a separate issue, see here to vote up:
No... that is not what happened at all, and I have your exact words to quote, so this should be easy to prove you wrong for the THIRD time in a row:
app0815: "It's not a bug, it's a feature. The book you have is DAMAGED so parts of it are unreadable."
This is false, As I proved, there is no such feature for damaged books at all. I reported a character issue. This is a character issue.
app0815: "You noticed missing characters, but that was it. Then I commented that it is only special characters that are causing the questionmarks"
False, again. I noticed characters replaced by question marks. YOU said that special characters are just missing without replacement, remember? Here, let me quote your exact words because you seem to be confused about what you said:
app0815: "special characters like ä, ö, ü are missing without replacement (just empty space), no matter what the condition. you however have questionmarks replacing regular characters, meaning the book is too damaged to read those."
So there's that, contradict yourself much? And for the last goddamn time, there is NO feature for damaged books, that's all in your head! Even IF it was a feature (which it isn't, again).. that is NOT what I'm reporting. This is a simple character issue on a specific book, which I have stated in the title, and in the description. YOU are the one who claimed it was a feature!:
app0815: "these are two different things:
- special characters missing = bug. (not the one you reported though)
- regulars replaced by questionmarks when damaged = feature."
Right there... you see it? "regulars replaced by questionmarks when damaged = feature." See that? Your words. Proven wrong. That feature does not exist. My bug was characters on this book getting replaced by question marks. This is a bug. I've proven it. Simple as that.
I've proven that damaged books do not display the same traits as your imaginary feature. I've proven that the same book in worn and pristine condition displays the same character bug I was initially reporting. I know there's a separate bug for special characters in pplayers names appearing as blank, I've no doubt this is connected, but the simple fact of the matter is, the characters on this book are being replaced with question marks and that is NOT a feature.
Still think you're right? I'd love to see you contradict yourself again.
There we go, stumbled across a pristine condition version of the book, check "final_proof.jpg" in the images above. I still have the item in my inventory if you need further images.
Now, if you could tell me why you jump around spouting "it's a feature" as if it were fact, that would be lovely. I mean seriously, I report it as a bug, provide proof. YOU claim it's a feature... it's not a far stretch to ask you for proof of your opinion.
I've edited out a lot of my anger, that was uncalled for. I'm just annoyed because I KNEW it was a bug, it's obviously a bug. It would have been okay if you'd (app0815) just said "I think this is a feature of damaged books", but to outright claim it as one, be all like "case closed" and then continue to downvote the issue based on absolutely nothing but your own incorrect opinion really grinds my gears.
I provide the image of the book in a better quality condition, same error. And then ELEVEN books ranging from various states of damage with NO indication of the same issue.
Got a whole bunch of screenshots from my last play through of damaged books. Feel free to man up whenever you want app0815.
"Case closed", as you put it. It's a bug.
There we are, more images added as proof. Are you going to admit that you're wrong now?
Please stop listening to the guy above me. This is clearly NOT a feature. More images added as proof. YouTube video in the notes also proves that this is not a feature for "damaged" books. Stop downvoting based on this guys opinion.
Skip to 1:52. Damaged book. No character issue.
It's also worth noting that of all the books I've seen in game, this is the only one to have this issue.
So again, unless you have proof, please don't just vote based on what you think is a feature.
Christ, I provide proof that this isn't a feature and people still downvote? The power of stupidity is overwhelming.
The "View Votes" link in the top left displays the most popularly voted on issues. It's worth checking from time to time. You can sort by various categories and do searches in the "View Issues" page.
The dupe you're looking for:
This is one of the more popular bugs, as found in the "View Votes" page (top left link). Please go vote it up, and in the future always do a quick search for existing bugs:
(The bug initially refers to zombie de-spawns, but player de-spawn is acknowledged)
This... is interesting actually. It could just be a massive coincidence but since purchasing DayZ my internet has died numerous times when playing, requiring me to physically reboot the router.
It could just be irregular down-time from my ISP caused by the Christmas season and therefore a lack of maintenance staff on their end. Buuuut I figure it's worth mentioning, just in case.
Just to clarify, this is an actual disconnect from my internet, and not DayZ servers going down.
@Mattastic: What "performance enhancing commands" are you using?
Is the problem here that it's full-bright without actually emitting any light in the environment? Or that you think it should turn off at night?
If you get this on the menu screen, just wait.
If you get this in game, do as JimmyJazz says, pressing tab to bring up the inventory will fix it. There is no need to exit your game.
It's still a bug, and I will vote it up, just echoing a temporary solution.
A possible exploit (I say "possible" because I don't know if it's intended) is to punch them in the head. They fall over every time, keep hitting them and when they stand up, BAM right in the head. Repeat until they're dead. This is much easier in first-perspective mode.
All melee weapons except for the fire-axe are pretty redundant (I've found). I can take on multiple zombies at a time with just fists and a good aim, but I always end up bleeding out if I take on just one with a crowbar, bat, wrench, etc.
Confirmed, in addition to this, see "rog_02.jpg" and you'll notice that you can pick up the items in the vicinity. This is odd because the detection radius for pick up is clearly a long way down the Y axis than the item itself.
I added my note to the bug ID: 0003407 for this issue of insta-death.
But yes, can confirm. friend insta-died on the firestation steps, I went to check it out (suspected player-kill, I checked the entire area out before entering, even checking the roofs), found his body inside, unlooted, crouch-walked up the steps and then I met the same mysterious fate.
Agreed, although I think even broken legs from a deer stand is a bit of a stretch. (especially when landing on soft ground/soil) A healthy person in reality would come away from that unscathed, but from a game perspective I suppose some amount of damage is needed, wouldn't want people parkour'ing all over the place.
I've noticed a lot of issues marked as solved are still very much unsolved. (floating loot, loot disappearing, loot falling through floors, etc).
I'd like to hope that what they mean is that they've solved the issues for this version, but we won't actually get the fixes until the next version/patch.
I did this twice. You will die eventually.
The "sick" flag goes away, I lasted for what seemed like hours, I assumed it was a bug, but died without warning eventually. Tested it once more to make sure, inflicting no wounds, got into zero fights, just ate rotten fruit and waited it out. You will die, it will just take a long time.
The charcoal tablet things might save you, I never managed to find any to test this.
Two insta-deaths at the fire station in Chernogorsk. Exact same location (uploaded image).
My friend died there out of nowhere (pictured), I come along to inspect a few minutes after. (suspected player-kill, area was empty, his loot was all intact too). I walk up the steps past his body, had barely reached the top and then I encounter the same mysterious fate.
Please try to find existing similar bugs and vote them up/add to them rather than reporting a new issue. This makes life a great deal easier for the developers.
(ironic that the top comment in that bug is pointing out that it too is a duplicate, but I couldn't find an earlier submission and the poster failed to provide a link)
Confirmed entry (applies to exiting too). Image shows multiple types of movement to attempt entry.
Agreed, I think at the moment the radius and fade-off of voice over direct communication is probably quite realistic, but it doesn't lend itself well to the game.
@DudesterRadman (love the name). The bug you linked is not a duplicate of this one. They are both graphical errors true, but separate issues none the less.
Workaround for issue: 0001542 = hit tab while in game.
Workaround for this issue (0001547) = hit ESC and access video options. No need to alter anything, just being in the menu restores sharpness.
Been playing the same character for a good 15+ hours now with a gas mask to try to replicate this. My character is in "healthy" condition. Absolutely no evidence of blood loss.
I initially didn't vote on this issue, but now I truly believe that people experiencing this actually just have infected wounds and aren't noticing it (since there's no character indication for this).
For people who think they're getting this issue, find some alcohol tincture, apply it to your wounds (your character will become "sick", this is normal)... over time you'll get messages about "my wounds look cleaner" until you get the green text of "My wounds are clean". Be sure to stay out of combat, especially avoid being hit by a zombie.
Then, stock up on food/drink until you get the "healthy" status in your inventory. (you need to eat/drink quite a lot to get to this status) Get a buddy to give you a saline transfusion if needed (to restore blood to 100%).
If your character is healthy, if your wounds are clean and you're eating/drinking well and you're STILL dying, I'll be happy to change my vote.
Yip yip yip, I have to make sure all explorer windows/programs are closed on my second monitor before I play the game, otherwise I might accidentally click them and lose focus, thus minimising the game.
Rusk has mentioned an interesting point there though, the game not losing focus so long as you're not in an inventory/cursor mode in the game. I've yet to test this.
A lot of people are adding notes about spacebar and right-mouse button to solve this issue, saying it isn't a bug.
It is a bug, I've experienced it. No amount of toggling right mouse button or spacebar works. The numpad enter key to change perspective is also tied to this somehow (ever had to tap it twice to change the view?).