{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by TB THE REAPER:
6/24/2017 11:40:43 PM
23
Bungie's prehistoric engine and NOT consoles, is the reason for no 60fps and small patrols
LOL, nice try Bungie, blaming your crappy performance on the platforms and NOT taking responsibility for your lazy decision to use the same engine in D2 that you used for legacy consoles and D1
Guess we can look forward to only seeing 1 or 2 other players on patrols and only about 20 enemies on the screen at a time, want to go to a new zone gotta load into it or take your ship there👎🏻
English
#feedback
-
2 RepliesIt's always bungie's fault... all their good developers left that sinking ship.
-
17 RepliesAre you basing your opinion on the video? Cause it was chock full of opinion, assumptions, and irrelevant facts. 1. Not sure why he decided to cite the 2015 Kotaku article regarding backend issues creating content (which was revamped for TTK, hence why the Live Team was able to produce all those Live Events, April Update, and RoI fairly quickly). This has nothing to do with any issues D2 has regarding framerate. 2. He mentions Halo 5 and how "pretty it looks" (with a pre-scripted space battle in the [i]background[/i], which takes up alot less processing power than rendering one real time), briefly mentions it's graphics techniques, but makes no mention of any techniques D2 is using and it's effect on framerate issues. 3. He even states in the beginning that 60fps should be priority. Occam's Razor would suggest that if 60fps [i]was[/i] a priority for Bungie, then they would have made the [b]necessary sacrifices [/b]to make that benchmark, like other games have done. It seems to me this guy in the video either as uninformed as the average gamer, or is just pandering to the lowest common denominator for views by reflecting their sentiment and telling people what they want to hear with an argument geared to that audience. If you're interested in [b]facts[/b] about the issue, I suggest you look elsewhere.
-
1 ReplyI've thought long and hard about the fps issue. I think it has to do with the original consoles more than anything else. Sony and Microsoft can come out and tout the power of the PS4 Pro and the Xbox One X all they want, but at the end of the day, both of those consoles are held back by the PS4 and the Xbox One, respectively. While the Pro and the X may very well be able to handle 60 fps (even though Bungie said they couldn't) I don't think the original consoles can handle those specs. Due to this, Bungie feels forced into locking the frame rate at 30 fps so that Pro and X users don't have a competitive advantage in the Crucible by being able to go to 60 fps. And they certainly weren't about to split the player base up by only allowing Pro to play with Pro users. I don't think Sony and Microsoft would allow that anyways. So...we're really stuck in the same boat we were in with D1, except it's not the PS3 and the 360 holding us back this time...just my thoughts. I'm not sure if that is 100% accurate or not, but it makes sense to me.
-
3 RepliesThe engine is theirs, and I am hoping they have improved it as technology has changed (although I can not confirm that), but also redesigning a gaming engine is not a weekend endeavor. The Tiger Engine prototype took years by itself, and that was not even starting from scratch (basically changing and altering the BLAM! engine, which was used to build the original Halo trilogy). Making an entirely new engine for a game is time consuming and extremely costly...and with Bungie under a strict timetable from Activision, I am guessing a new engine was off the table. However, this is why a lot of developers choose to instead of building their own engine, they just go to companies like Unreal and Havok and use their proprietary design, which those companies are constantly updating to stay current because that is what they do: they build and maintain engines.
-
PC will be 60 fps, and it's been stated that XBOX One X can handle it, so I'd say it's defiantly a budgie issue
-
1 ReplyEdited by TheShadow-cali: 6/27/2017 2:21:44 AMOverall they took the carburetor out of the car and had it rebilt only to find out replacing the gaskets didn't really work. So here we go again for another 3 years of instead of blaming last gen for not being able to add simple things like vault space. Now they will blame the new gen for whatever else they won't be able to add to this game. When you use old crap you have to expect problems. It's not that they didn't know this already. It's the fact that they still did it anyways knowing what was going to happen.
-
10 Replies1. Even the "high end" consoles have CPUs that are about half as powerful as what you find in a typical gaming PC, and is about 5 years behind where PCs are right now. 2. CPU power determines frame rate, not GPU. 3. The PS4 Pro and XB1X were gving MASSIVE upgrades in GPU power, but only very modest upgrades in CPU Power. IOW, THEY WERE DESIGNED TO RENDER GAMES AT HIGH RESOLUTIONS....NOT HIGH FRAMERATES. 4, Stop comnparing arena shooter like Overwatch or Battlefield 1 to Destiny. A better comparison for Destiny is to open world games like Horizon Zero Dawn or Mass Effect: Andromeda. ...and those games run at 30fps on consoles. In fact, try to run an oper world game like Witcher 3 at both high frame rates AND high resolution....and you have a game that will push even a modern gaming PC to its limits.
-
Though the issue seems to lie in both inadequate hardware and inefficient software, it's irritating that Bungie is incapable of taking at least part of the blame.
-
123 RepliesEdited by NoStatsHereMate: 6/27/2017 3:27:37 AMDamn, people are in for a generation of disappointment if they can't handle that these new consoles are seriously lacking in CPU power... Edit: After seeing these replies, it's hard to deny the main issue here is people thinking far too highly of their mid-gen consoles...
-
1 ReplyGDC 2015. They expected this engine to go the ten year publishing contract
-
I was honestly excited at first because I though the do-over in Destiny 2 meant using a completely different engine. Then they showed the game and it was the same old sh*t as before, looked like an "expansion" lol. After unshackling themselves from legacy consoles, their big bold claim was "areas twice as big as Destiny 1". Whoo hoo. A slightly wider, just as linear donut-shaped map to run through over and over again. Destiny 2 is just a ploy to trick the unsuspecting into believing its actually different from Destiny 1. [spoiler]It's not ;)[/spoiler]
-
2 RepliesDestiny's engine is very inefficient. and judging from the previews it is the same engine for Destiny 2. I do agree with you that it does look and from what many of those who played it have said., destiny 1.5. But we won't know for sure till it's released. But considering how Destiny 1 ended. I don't plan on being on this hamster wheel like I was in Destiny 1. I will play the game and move on. I will never invest that much time and effort for nothing again.
-
1 ReplyIt's baffling how they could have ignored SO many of the community's requests, especially something as basic as improved character creation. That's when it hit me: D2 is Vanilla D1 all over again.
-
11 RepliesEdited by xI Vorpal Ix: 6/27/2017 2:21:45 AMBungie have highly optimised fully scalable PC code for D2. Multiple non Microsoft developers have confirmed that X1X is doing amazing things with PC code in terms of port speed and raw performance. The X1X deserves to run the PC code.
-
1 ReplyThat was a good watch. Fingers crossed that those load times aren't omnipresent
-
5 RepliesOne word: anthem But I think they that destiny two will be fun it's a lot about social to at least for me so having a blast wreaking a raid boss with my buddies will always be fun. It I do hope for some more environmental detail. But wow anthem is gonna give them a run. And what I like about that is it'll make bungie raise there bar or fade away. I hope both feed off each other making two games fight for our attention. And that's what destiny needed. True competition.
-
-
56 RepliesEdited by Smithy: 6/26/2017 7:17:34 AM1) The "it takes forever to move objects" shit was explained [url=https://www.youtube.com/watch?v=7KXVox0-7lU]here[/url] and was a side effect of trying to get good performance on the PS3. That was fixed when TTK was released. Guess what isn't supported anymore? 2) Saying "just optimize more" is like telling the a business to "just cut costs more." It's meaningless unless you understand the underlying problems. 3) Shill
-
all companies choose different rendering techniques over 60fps. im not sure why but they do
-
2 RepliesTold you they were lying
-
-
Yeah agreed! A new engine should have been used
-
9 RepliesBump, agreed and good to see you doing your own post that isn't the same.
