


<?xml version="1.0" encoding="utf-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
<title>DBO Forums - Yes and No</title>
<link>https://destiny.bungie.org/forum/</link>
<description>Bungie.Org talks Destiny</description>
<language>en</language>
<item>
<title>Yes and No (reply)</title>
<content:encoded><![CDATA[<p>I've tried Windows Sonic, Dolby Atmos, and the default Xbox setting with no real change.</p>
]]></content:encoded>
<link>https://destiny.bungie.org/forum/index.php?id=167234</link>
<guid>https://destiny.bungie.org/forum/index.php?id=167234</guid>
<pubDate>Tue, 10 Dec 2019 00:59:06 +0000</pubDate>
<category>Gaming</category><dc:creator>cheapLEY</dc:creator>
</item>
<item>
<title>I am not (and I’m not having audio problems) (reply)</title>
<content:encoded><![CDATA[- No text -]]></content:encoded>
<link>https://destiny.bungie.org/forum/index.php?id=167233</link>
<guid>https://destiny.bungie.org/forum/index.php?id=167233</guid>
<pubDate>Tue, 10 Dec 2019 00:51:46 +0000</pubDate>
<category>Gaming</category><dc:creator>CruelLEGACEY</dc:creator>
</item>
<item>
<title>More bugs that affect the artists (reply)</title>
<content:encoded><![CDATA[<p>I'm on PC.  </p>
<p>Not tech savvy at all, I'll admit, but it's been a while since I heard something that messed up.</p>
]]></content:encoded>
<link>https://destiny.bungie.org/forum/index.php?id=167232</link>
<guid>https://destiny.bungie.org/forum/index.php?id=167232</guid>
<pubDate>Tue, 10 Dec 2019 00:21:40 +0000</pubDate>
<category>Gaming</category><dc:creator>SonofMacPhisto</dc:creator>
</item>
<item>
<title>Are you guys using virtual surround? (WindowsSonic, I think) (reply)</title>
<content:encoded><![CDATA[- No text -]]></content:encoded>
<link>https://destiny.bungie.org/forum/index.php?id=167231</link>
<guid>https://destiny.bungie.org/forum/index.php?id=167231</guid>
<pubDate>Tue, 10 Dec 2019 00:15:06 +0000</pubDate>
<category>Gaming</category><dc:creator>ZackDark</dc:creator>
</item>
<item>
<title>More bugs that affect the artists (reply)</title>
<content:encoded><![CDATA[<blockquote><p>Not exactly. The ghosting or double-vision issues I was talking about with Reach just look like a flat-out mistake or problem to me. You can freeze-frame Reach footage and literally see 2 images of a spartan as its moving overlayed on top of each other. </p>
</blockquote><p>No, I understand that.  That's a different thing.  That's the temporal anit-aliasing, which is gone now.  The ambient occlusion is different.  The edges of geometry in the original Reach look much &quot;softer,&quot; for lack of a better term.  The new Reach is similar to your example with the wall in TLoU Remastered.   The edges of the geometry are much more defined, and they look a little less natural than they used to, much more obviously like video game geometry.   It's a testament to Bungie's design that it still looks fantastic and fairly real, but it would look better with the proper ambient occlusion.</p>
<p>If you're interested, here's the Digital Foundry video.  I think Cody is vastly overstating how big of a deal this is (as it still looks great, and it's much easier to pick this stuff apart when just watching a video, and it's much less noticeable when actually playing the game), but I do think it could look better if this stuff was working correctly.  I think depth of field is even more important than ambient occlusion in terms of keeping the aesthetics of the original game. It was used heavily, especially in cutscenes in the original version of the game, and it's basically completely gone from the MCC version.  </p>
<p>The stuff I'm talking about starts at 10:49.  There's also a sound comparison that starts right at 15:00.</p>
<p><iframe style="border:none;" width="852" height="480" src="https://www.youtube.com/embed/c5kCLcu8hdk?autoplay=0&start="></iframe></p>
]]></content:encoded>
<link>https://destiny.bungie.org/forum/index.php?id=167230</link>
<guid>https://destiny.bungie.org/forum/index.php?id=167230</guid>
<pubDate>Mon, 09 Dec 2019 22:40:36 +0000</pubDate>
<category>Gaming</category><dc:creator>cheapLEY</dc:creator>
</item>
<item>
<title>More bugs that affect the artists (reply)</title>
<content:encoded><![CDATA[<blockquote><blockquote><blockquote><p>As my TLoU example illustrates, sometimes an improvement on paper actually harms the overall look. </p>
</blockquote></blockquote></blockquote><blockquote><blockquote><p><br />
And this is the one I am most curious about, because I never played the PS3 version. For me the remaster was 'normal'. I should try it on PS3.</p>
</blockquote></blockquote><blockquote><p><br />
It's sort of a funny example to choose while defending the MCC Reach port, because the ambient occlusion bug is sort of the same thing he's talking about, being able to see where geometry meets in a particular way.  </p>
<p>I think the MCC version would undeniably look better with the original ambient occlusion, but I also think it looks completely fine as is.  It does make it look noticeably like an old game running at higher resolutions than it was ever intended, though, but that was always going to be the case.</p>
</blockquote><p>Not exactly. The ghosting or double-vision issues I was talking about with Reach just look like a flat-out mistake or problem to me. You can freeze-frame Reach footage and literally see 2 images of a spartan as its moving overlayed on top of each other. </p>
<p>TLoU is more a case of art assets being polished to the level that was appropriate for the screen resolution that was available. Increasing the rendering resolution brings geometry outlines into sharper focus, but it makes the lower-resolution texture graphics more apparent. It’s kinda like me looking at a painting of a tree from 50 feet away without my glasses on. If the painting is detailed enough, it might look utterly real to me. But as soon as I put my glasses on, I can see that it’s just flat. That’s TLoU remastered in my eyes. Better image quality just made it more obvious when certain things looked fake. </p>
<p>Sticking with the same analogy, the original Reach felt like looking at the painting while being blasted drunk, while MCC Reach is like looking at it while sober, lol.</p>
]]></content:encoded>
<link>https://destiny.bungie.org/forum/index.php?id=167229</link>
<guid>https://destiny.bungie.org/forum/index.php?id=167229</guid>
<pubDate>Mon, 09 Dec 2019 22:18:36 +0000</pubDate>
<category>Gaming</category><dc:creator>CruelLEGACEY</dc:creator>
</item>
<item>
<title>More bugs that affect the artists (reply)</title>
<content:encoded><![CDATA[<blockquote><blockquote><p>As my TLoU example illustrates, sometimes an improvement on paper actually harms the overall look. </p>
</blockquote></blockquote><blockquote><p><br />
And this is the one I am most curious about, because I never played the PS3 version. For me the remaster was 'normal'. I should try it on PS3.</p>
</blockquote><p>It's sort of a funny example to choose while defending the MCC Reach port, because the ambient occlusion bug is sort of the same thing he's talking about, being able to see where geometry meets in a particular way.  </p>
<p>I think the MCC version would undeniably look better with the original ambient occlusion, but I also think it looks completely fine as is.  It does make it look noticeably like an old game running at higher resolutions than it was ever intended, though, but that was always going to be the case.</p>
]]></content:encoded>
<link>https://destiny.bungie.org/forum/index.php?id=167228</link>
<guid>https://destiny.bungie.org/forum/index.php?id=167228</guid>
<pubDate>Mon, 09 Dec 2019 22:03:43 +0000</pubDate>
<category>Gaming</category><dc:creator>cheapLEY</dc:creator>
</item>
<item>
<title>More bugs that affect the artists (reply)</title>
<content:encoded><![CDATA[<blockquote><p>As my TLoU example illustrates, sometimes an improvement on paper actually harms the overall look. </p>
</blockquote><p>And this is the one I am most curious about, because I never played the PS3 version. For me the remaster was 'normal'. I should try it on PS3.</p>
]]></content:encoded>
<link>https://destiny.bungie.org/forum/index.php?id=167227</link>
<guid>https://destiny.bungie.org/forum/index.php?id=167227</guid>
<pubDate>Mon, 09 Dec 2019 21:37:06 +0000</pubDate>
<category>Gaming</category><dc:creator>Cody Miller</dc:creator>
</item>
<item>
<title>I don&#039;t think that&#039;s true. (reply)</title>
<content:encoded><![CDATA[<p>I was using my Sennheiser 598s plugged into the controller.  Well, it's plugged into the Turtle Beach chat mixer thing that's plugged into the controller.  I suppose I could try eliminating that and seeing if it makes a difference, but I doubt it's an issue.</p>
<p>What I'm hearing might not be super noticeable, I suppose.  As I said, the mix just doesn't sound great, like all the sounds are always competing with each other, but that's a problem that I think every Halo game has always had, so I don't think that's a bug, necessarily.   </p>
<p>The gun sounds, though, are the real thing.  They are still as loud as they should be, but the actual effect sound itself sounds muted or muffled somehow.  I noticed it immediately with the assault rifle and the pistol, but I can also see how someone legitimately might not notice a difference.   Look up a comparison video and you'll be able to tell if it's something you legitimately didn't experience or just didn't notice.</p>
]]></content:encoded>
<link>https://destiny.bungie.org/forum/index.php?id=167226</link>
<guid>https://destiny.bungie.org/forum/index.php?id=167226</guid>
<pubDate>Mon, 09 Dec 2019 21:34:06 +0000</pubDate>
<category>Gaming</category><dc:creator>cheapLEY</dc:creator>
</item>
<item>
<title>I don&#039;t think that&#039;s true. (reply)</title>
<content:encoded><![CDATA[<blockquote><p>I'm playing on a One X.</p>
<p>I haven't really looked into, maybe there are multiple, separate issues across the different builds, but the One X version definitely did not sound right or particularly good to me.</p>
</blockquote><p>Are you using a surround setup, or stereo?</p>
<p>What I’m wondering is if the issue is directly related to the audio stream being sent to the Xbox’s optical audio output, or the optical and HDMI outputs, but NOT the controller (which would explain why I didn’t experience any audio issues through my headset).</p>
]]></content:encoded>
<link>https://destiny.bungie.org/forum/index.php?id=167225</link>
<guid>https://destiny.bungie.org/forum/index.php?id=167225</guid>
<pubDate>Mon, 09 Dec 2019 21:00:31 +0000</pubDate>
<category>Gaming</category><dc:creator>CruelLEGACEY</dc:creator>
</item>
<item>
<title>I don&#039;t think that&#039;s true. (reply)</title>
<content:encoded><![CDATA[<p>I'm playing on a One X.</p>
<p>I haven't really looked into, maybe there are multiple, separate issues across the different builds, but the One X version definitely did not sound right or particularly good to me.</p>
]]></content:encoded>
<link>https://destiny.bungie.org/forum/index.php?id=167224</link>
<guid>https://destiny.bungie.org/forum/index.php?id=167224</guid>
<pubDate>Mon, 09 Dec 2019 20:50:06 +0000</pubDate>
<category>Gaming</category><dc:creator>cheapLEY</dc:creator>
</item>
<item>
<title>yeah, it&#039;s a PC build issue afaik (reply)</title>
<content:encoded><![CDATA[- No text -]]></content:encoded>
<link>https://destiny.bungie.org/forum/index.php?id=167223</link>
<guid>https://destiny.bungie.org/forum/index.php?id=167223</guid>
<pubDate>Mon, 09 Dec 2019 20:43:04 +0000</pubDate>
<category>Gaming</category><dc:creator>kidtsunami</dc:creator>
</item>
<item>
<title>More bugs that affect the artists (reply)</title>
<content:encoded><![CDATA[<blockquote><blockquote><blockquote><p>I maintain that if you have to look at a side by side comparison to even notice it (which you totally do for almost every single one of the things Digital Foundry talks about), then it doesn’t matter.  </p>
<p>Play the MCC version of Reach without having someone point out those issues, and they’re not even noticeable.  Cruel is right—it just looks like Reach.  </p>
<p>I disagree with him on the sound, though.  That was immediately noticeable to me.  It didn’t really affect my enjoyment, but I knew something was off the entire time I played.</p>
</blockquote></blockquote></blockquote><blockquote><blockquote><p><br />
I played through half the game using nothing but my TV speakers with the volume way down, so I probably wouldn’t have noticed any problems with the audio unless they were extreme. But when I played through the 2nd half of the campaign, I was wearing a stereo headset (plugged straight into my controller). I didn’t do any A/B comparisons, but the audio sounded just as I remembered it.</p>
<p>What kind of issues are you hearing?</p>
</blockquote></blockquote><blockquote><p><br />
Headset user here.  Voices were obnoxiously loud in the mix.  Everything else was in a can.  I laughed outloud at how bad it was.  Was glad my friend and I were just messing around in campaign and having a good time.  </p>
<p>If I was going through &quot;seriously&quot; solo I might get irritated enough to just stop playing.</p>
</blockquote><p>Yeah, I didn’t have any of those issues at all. Very strange. Was your headset plugged into the Xbox, or into the controller?</p>
<p>Or is this specifically a PC issue? I’m on Xbox One X.</p>
]]></content:encoded>
<link>https://destiny.bungie.org/forum/index.php?id=167222</link>
<guid>https://destiny.bungie.org/forum/index.php?id=167222</guid>
<pubDate>Mon, 09 Dec 2019 20:31:20 +0000</pubDate>
<category>Gaming</category><dc:creator>CruelLEGACEY</dc:creator>
</item>
<item>
<title>More bugs that affect the artists (reply)</title>
<content:encoded><![CDATA[<p>The thing is, this “technical vs artistic choice” issue is not black and white. As I already described, light bloom can be an artistic decision, but it also has technical implications. It’s very possible that the bloom was added to hide other visual shortcomings. I’m not arguing that this was the case for Reach... I don’t know one way or the other. But that’s the point: it isn’t obvious or clear. In the world of video games, technical issues and artistic choices directly impact each other in such a way that they cannot be easily separated. Frame rates have an aesthetic “look”, completely separate from their impact on gameplay. Remember all the backlash to the 48fps Hobbit movie? It didn’t look the way people like/expect a movie to look. Well, they effect the look of video games too. But within video games, there is also a relationship between frame rate and gameplay, plus other visual performance issues, so all that stuff needs to be balanced out.</p>
<p>My point here is that we really have no way of knowing which elements of Reach’s visuals were purely artistic choices, which were purely technical issues, and which were some kind of compromise between the two. I suspect that almost everything to do with game development falls into that 3rd category. But even if we could say with certainty that specific elements were purely technical in nature, it isn’t obvious that changing them would be an improvement. As my TLoU example illustrates, sometimes an improvement on paper actually harms the overall look. </p>
<p>Playing MCC Reach, I was quite impressed by the overall clarity and crispness of the image. Had the light bloom been cranked up, the visuals might not have made such an impression on me. Or, perhaps I would have liked the look of the game even more. Who knows. My point is that ANY changes are nonetheless changes, and whether or not a player likes or dislikes those changes is going to be a question of personal taste.</p>
]]></content:encoded>
<link>https://destiny.bungie.org/forum/index.php?id=167221</link>
<guid>https://destiny.bungie.org/forum/index.php?id=167221</guid>
<pubDate>Mon, 09 Dec 2019 20:26:35 +0000</pubDate>
<category>Gaming</category><dc:creator>CruelLEGACEY</dc:creator>
</item>
<item>
<title>More bugs that affect the artists (reply)</title>
<content:encoded><![CDATA[<p>Gun sounds, mostly.  They sound sort of muffled.  </p>
<p>I also don’t think the mix in general is particularly good, but I think that’s true of the original.</p>
]]></content:encoded>
<link>https://destiny.bungie.org/forum/index.php?id=167220</link>
<guid>https://destiny.bungie.org/forum/index.php?id=167220</guid>
<pubDate>Mon, 09 Dec 2019 20:22:11 +0000</pubDate>
<category>Gaming</category><dc:creator>cheapLEY</dc:creator>
</item>
<item>
<title>More bugs that affect the artists (reply)</title>
<content:encoded><![CDATA[<blockquote><blockquote><p>I maintain that if you have to look at a side by side comparison to even notice it (which you totally do for almost every single one of the things Digital Foundry talks about), then it doesn’t matter.  </p>
<p>Play the MCC version of Reach without having someone point out those issues, and they’re not even noticeable.  Cruel is right—it just looks like Reach.  </p>
<p>I disagree with him on the sound, though.  That was immediately noticeable to me.  It didn’t really affect my enjoyment, but I knew something was off the entire time I played.</p>
</blockquote></blockquote><blockquote><p><br />
I played through half the game using nothing but my TV speakers with the volume way down, so I probably wouldn’t have noticed any problems with the audio unless they were extreme. But when I played through the 2nd half of the campaign, I was wearing a stereo headset (plugged straight into my controller). I didn’t do any A/B comparisons, but the audio sounded just as I remembered it.</p>
<p>What kind of issues are you hearing?</p>
</blockquote><p>Headset user here.  Voices were obnoxiously loud in the mix.  Everything else was in a can.  I laughed outloud at how bad it was.  Was glad my friend and I were just messing around in campaign and having a good time.  </p>
<p>If I was going through &quot;seriously&quot; solo I might get irritated enough to just stop playing.</p>
]]></content:encoded>
<link>https://destiny.bungie.org/forum/index.php?id=167219</link>
<guid>https://destiny.bungie.org/forum/index.php?id=167219</guid>
<pubDate>Mon, 09 Dec 2019 20:16:29 +0000</pubDate>
<category>Gaming</category><dc:creator>SonofMacPhisto</dc:creator>
</item>
<item>
<title>More bugs that affect the artists (reply)</title>
<content:encoded><![CDATA[<p>I’m fully admitting it is not as bad or noticeable as the Halo 1 classic mode visually.</p>
]]></content:encoded>
<link>https://destiny.bungie.org/forum/index.php?id=167218</link>
<guid>https://destiny.bungie.org/forum/index.php?id=167218</guid>
<pubDate>Mon, 09 Dec 2019 20:14:24 +0000</pubDate>
<category>Gaming</category><dc:creator>Cody Miller</dc:creator>
</item>
<item>
<title>More bugs that affect the artists (reply)</title>
<content:encoded><![CDATA[<blockquote><p>I maintain that if you have to look at a side by side comparison to even notice it (which you totally do for almost every single one of the things Digital Foundry talks about), then it doesn’t matter.  </p>
<p>Play the MCC version of Reach without having someone point out those issues, and they’re not even noticeable.  Cruel is right—it just looks like Reach.  </p>
<p>I disagree with him on the sound, though.  That was immediately noticeable to me.  It didn’t really affect my enjoyment, but I knew something was off the entire time I played.</p>
</blockquote><p>I played through half the game using nothing but my TV speakers with the volume way down, so I probably wouldn’t have noticed any problems with the audio unless they were extreme. But when I played through the 2nd half of the campaign, I was wearing a stereo headset (plugged straight into my controller). I didn’t do any A/B comparisons, but the audio sounded just as I remembered it.</p>
<p>What kind of issues are you hearing?</p>
]]></content:encoded>
<link>https://destiny.bungie.org/forum/index.php?id=167217</link>
<guid>https://destiny.bungie.org/forum/index.php?id=167217</guid>
<pubDate>Mon, 09 Dec 2019 20:11:27 +0000</pubDate>
<category>Gaming</category><dc:creator>CruelLEGACEY</dc:creator>
</item>
<item>
<title>More bugs that affect the artists (reply)</title>
<content:encoded><![CDATA[<p>I maintain that if you have to look at a side by side comparison to even notice it (which you totally do for almost every single one of the things Digital Foundry talks about), then it doesn’t matter.  </p>
<p>Play the MCC version of Reach without having someone point out those issues, and they’re not even noticeable.  Cruel is right—it just looks like Reach.  </p>
<p>I disagree with him on the sound, though.  That was immediately noticeable to me.  It didn’t really affect my enjoyment, but I knew something was off the entire time I played.</p>
]]></content:encoded>
<link>https://destiny.bungie.org/forum/index.php?id=167216</link>
<guid>https://destiny.bungie.org/forum/index.php?id=167216</guid>
<pubDate>Mon, 09 Dec 2019 19:19:12 +0000</pubDate>
<category>Gaming</category><dc:creator>cheapLEY</dc:creator>
</item>
<item>
<title>I’d almost forgotten how great Bungie campaigns used to be. (reply)</title>
<content:encoded><![CDATA[<blockquote><p>I think there's probably some additional reasons why Destiny isn't quite like this</p>
</blockquote><p>I have written about this before:</p>
<p><a href="https://destiny.bungie.org/forum/index.php?id=35662">https://destiny.bungie.org/forum/index.php?id=35662</a></p>
<p>The answer is the investment system combined with the Journey style seamless matchmaking.</p>
]]></content:encoded>
<link>https://destiny.bungie.org/forum/index.php?id=167213</link>
<guid>https://destiny.bungie.org/forum/index.php?id=167213</guid>
<pubDate>Mon, 09 Dec 2019 18:53:53 +0000</pubDate>
<category>Gaming</category><dc:creator>Cody Miller</dc:creator>
</item>
</channel>
</rss>
