Jump to content

michaeldcullen

Members
  • Content Count

    10
  • Joined

  • Last visited

Community Reputation

14 Neutral

About michaeldcullen

  • Rank
    Scavenger

Profile Information

  • Gender
    Male

Recent Profile Visitors

822 profile views
  1. michaeldcullen

    Stable Update 1.18

    And this is yet another issue; blaming "the community" for the FT being ignored by BI. Yes, there are a ton of low-effort tickets added by morons; "help, my base got raided", "fix cars", "game crashed 3 times in a row", etc. Please explain, with a straight face, how the following tickets aren't of acceptable quality and worthy of paying attention to. https://feedback.bistudio.com/T164039 https://feedback.bistudio.com/T164404 https://feedback.bistudio.com/T164508 https://feedback.bistudio.com/T164529 https://feedback.bistudio.com/T164531 https://feedback.bistudio.com/T164779
  2. michaeldcullen

    Stable Update 1.18

    Yep. And you just know that every time this inconvenient truth is brought up, one of the CMs scrambles to the internal Discord with "... guys, they're asking difficult questions about the Feedback Tracker again, what do we do? Just ignore them?"
  3. michaeldcullen

    Stable Update 1.18

    Why? You've literally ignored it for years. You're going to take the time to look at it for a minor localization issue when major issues like the VOIP noise gate that was introduced in 1.17 makes the game literally unplayable for a significant portion of the playerbase? It'd be nice if you treated the community with some respect, instead of just assuming we're fools. If you're not interested in taking steps to address issues when they're reported, stop asking people to report them. The Feedback Tracker is used as a way of burying issues with promises of "we're looking into it" rather than as a tool to improve the game.
  4. michaeldcullen

    Stable Update 1.18

    Thought I'd actually attempt using the Feedback Tracker again between 1.17 and 1.18, after having given up in the past due to things just being marked as "Assigned" by Geez and then ignored for years. Nothing in the patch notes relating to the VOIP issues which were introduced with 1.17, despite me - and others - documenting them heavily on the FT. I would advise anyone else concerned about issues to simply ignore the Feedback Tracker once again, since it seems like Bohemia aren't taking it seriously; and there's no point in us wasting our time on it.
  5. michaeldcullen

    Experimental Update 1.18 (Change Log)

    Once again, can we please get some attention directed towards these C++ side issues, prior to stable release. https://feedback.bistudio.com/T164404 https://feedback.bistudio.com/T164508 https://feedback.bistudio.com/T164529 https://feedback.bistudio.com/T164531 The change that introduced these issues wasn't QA'd, it would be nice if the fix was. Three of the four have been marked as "Assigned" by Geez, the same way every other bug report is - including the useless ones with no relevant information included - but with no actual acknowledgement of the issue. There's no point in people actually using the Feedback Tracker to report issues if they're just going to be silently logged and then ignored. There are numerous issues which have been documented in great detail over the past decade on the FT which remain unfixed and even, in some cases, unacknowledged. The community would appreciate greater transparency with the Feedback Tracker if the CM is going to keep recommending its use, as currently it seems like it's where bugs are swept under the rug, not tracked and actioned.
  6. michaeldcullen

    1.18 Experimental Release

    The code for MTU detection is *in* the engine, just disabled by default. They just need to uncomment a define lol.
  7. michaeldcullen

    1.18 Experimental Release

    Some great work on new content with this patch, but can we get some attention to the following engine-side issues before we enter final QA? https://feedback.bistudio.com/T164404 https://feedback.bistudio.com/T164508 https://feedback.bistudio.com/T164529 https://feedback.bistudio.com/T164531 Would be a shame if these issues persisted through another patch cycle.
  8. UK | FP Gaming | Vanilla DayZ | 4H Restarts | 1.8.6.1 A totally vanilla server for those of you who want a more classic experience! 2 hours day / 2 hours night; in-game time is set to 4pm on server restart, restarts every 4 hours with plenty of warnings in advance. Enabled: Side chat Anti-ghosting system Full moon nights Temperature system Disabled: Spawn selection Clutter cutter on dynamic loot events Weapon quick switching We have plenty of experience running DayZ servers, and previously had one of the most popular PVE DayZ Epoch servers. With the recent mass migration of people away from Epoch to Arma 3, we decided to instead look for an under-represented segment of the DayZ community, and so here we are with a brand new Vanilla server!
×