Xbox 365
Once again, I haven't done that. I, over and over and over again, have said I am looking forward to the system, that it's going to be cool, that it will be the main place I play when it comes out. Those are all signs of positivity.Fair, but you specifically state that the specs are not something to be positive (or negative about). I would disagree and say the specs are better than whats existing in the console space. I believe that is an disputably positive thing for console gamers. Will it take us from Halo 2600 level graphics to Halo 5 graphics in a single step, probably not. But constantly harping on on posts that show a modicum of positivity is off putting to fans. By all means reign in the MisterXmedia-esq posts. But we don't need to constantly (if gently) push down on every post that shows anything but the least common denominator of support.
You don't need to guess it , as they have shown images of the motherboard
Once again, I haven't done that. I, over and over and over again, have said I am looking forward to the system, that it's going to be cool, that it will be the main place I play when it comes out. Those are all signs of positivity.
But if someone came in here really excited that every Scorpio was coming with a real sex doll, it wouldn't be negative of me to point out they are incorrect, nor would that person be exhibiting more positivity than I. They would just be wrong.
I have now checked DF and they do indeed talk about the PSU so my bad but the the image purporting to be the dev kit still doesn't seem right when compared to the official (retail I assume) images.
I can't see how the dev kit ports being at the top (motherboard at top of case?) could work or why it would seem to differ to the retail images of how the components fit together as shown in the DF article?
So the dev kit image above is either very different inside or that image is fake/wrong.
The XDK has always been relatively fine in term of ease of use. The problem was the design of the Xbox One, which wasn't the best environment. Scorpio is obviously much better in that regard, but because devs still need to make XBO versions, the amount of work has just gone up overall.I know you probably can't say but have you noticed any differences in dev time or ease of functionality when using the Scorpio dev kit over the OG One? I think I read they had devs in mind when they were building it.
for yes and :| for no
Having dx12 instructions on og XB1 using a good portion of CPU compared to nearly zero and all on gpu on Scorpio is a major upgrade no question about that
The XDK has always been relatively fine in term of ease of use. The problem was the design of the Xbox One, which wasn't the best environment. Scorpio is obviously much better in that regard, but because devs still need to make XBO versions, the amount of work has just gone up overall.
If the Scorpio was replacing the XBO, then your answer would be
If I were in charge of naming the thing, this is honestly what I would go with. It jives with their marketing talk of "hardware without generations" and also serves as a play on their wacky numbering schemes.
It would also mean that their next console could be named the Xbox Infinity + 2. Also, holy shit would that last gif be a great play on Xbox Infinite having built-in Cortana support with mics and all. Let's go get jobs at Microsoft.
Xbox 365
I'm still gunning for,
Xbox One,
There's just so much they could do with it.
The XDK has always been relatively fine in term of ease of use. The problem was the design of the Xbox One, which wasn't the best environment. Scorpio is obviously much better in that regard, but because devs still need to make XBO versions, the amount of work has just gone up overall.
If the Scorpio was replacing the XBO, then your answer would be
The XDK has always been relatively fine in term of ease of use. The problem was the design of the Xbox One, which wasn't the best environment. Scorpio is obviously much better in that regard, but because devs still need to make XBO versions, the amount of work has just gone up overall.
If the Scorpio was replacing the XBO, then your answer would be
You're saying devs have to make 2 separate versions?
The XDK has always been relatively fine in term of ease of use. The problem was the design of the Xbox One, which wasn't the best environment. Scorpio is obviously much better in that regard, but because devs still need to make XBO versions, the amount of work has just gone up overall.
If the Scorpio was replacing the XBO, then your answer would be
I thought this was always going to be the case.
Eh, not exactly, but they are very different systems that of course can lend themselves to varying degrees of individual care to make the most out of their respective platforms, depending on how much work a dev wants to do.You're saying devs have to make 2 separate versions?
In not sure what you mean, I never said "holding back" in that post. I was talking about the totality of dev time.How is that holding the scorpio versions back though? Just lack of time for optimization? I know on PC with varying tiers of hardware devs start development with scaleability in mind. And I am fairly certain that MS has also started using a scaleable dev model for their first party games for xbpa. Project Helix I think it's called. Am curious to know why it would be different here.
I've said before that we have them.Matt, do you have a Dev kit? Or have you specifically developed for Scorpio?
You're saying devs have to make 2 separate versions?
Really? I don't think so.
Do they make 867 PC versions of games?
You're saying devs have to make 2 separate versions?
I don't think that's a good way to explain it.
It's more like PC development: you make a single game, but it's scalable to work on multiple hardware configurations-
In the case of Xbox, there just two configurations to consider.
I don't think that's a good way to explain it.
It's more like PC development: you make a single game, but it's scalable to work on multiple hardware configurations-
In the case of Xbox, there just two configurations to consider.
To take full advantage of the scorpio's capabilities, there will need to be a patch, because typically a games 4K assets won't be able to fit on a disc.
Fair, but you specifically state that the specs are not something to be positive (or negative about). I would disagree and say the specs are better than whats existing in the console space. I believe that is an disputably positive thing for console gamers. Will it take us from Halo 2600 level graphics to Halo 5 graphics in a single step, probably not. But constantly harping on on posts that show a modicum of positivity is off putting to fans. By all means reign in the MisterXmedia-esq posts. But we don't need to constantly (if gently) push down on every post that shows anything but the least common denominator of support.
I thought this was always going to be the case.
I guess it depends what you mean by "version." It's running off the same code, but the Scorpio game can have different settings, assets, and more if a dev wants to do that work. Or they can do very little and essentially there would just be increased performance up to whatever limits are in place.This is what it thought. Because they mentioned something about the extra ram having some kind API that accounts for the eSRAM didn't they?
I assumed it would be a patch at worst. Matt's post made it sound like 2 versions are being made, which I just wouldn't believe because not many devs are going to want to make 2 versions of their game for the non market leader.
I guess it depends what you mean by "version." It's running off the same code, but the Scorpio game can have different settings, assets, and more if a dev wants to do that work. Or they can do very little and essentially there would just be increased performance up to whatever limits are in place.
Calling it the Scorpio version and the XBO version isn't inaccurate considering they are closed environments with two presets, but profile also works.
This is what it thought. Because they mentioned something about the extra ram having some kind API that accounts for the eSRAM didn't they?
I assumed it would be a patch at worst. Matt's post made it sound like 2 versions are being made, which I just wouldn't believe because not many devs are going to want to make 2 versions of their game for the non market leader.
"The memory system we've got, we've got enough bandwidth to more than cover what we go from ESRAM," says Baker. "We simply go and use our virtual memory system to map the 32MB of physical address that the old games thought they got into 32MB in the GDDR5. So latency is higher but in terms of aggregate performance, the improved bandwidth and improved GPU performance means we don't hit any issues."
I apologize, I'm not clear what the "it" refers to. Can you elaborate what you mean here?How does it not effect the discussion?
It doesn't. But that's because it's about the command processor. You'll see my use of the "all the functionality" clause was instead referring to the audio block. Here's the DF quote regarding that:How does the quote above say that all the functionality is in the prior platforms?
Please ignore the part where Mr. Leadbetter appears not to know what HRTF refers to.Richard Leadbetter said:Scorpio is set to receive support for Dolby Atmos for gaming, Dolby Atmos for headphones plus a Microsoft proprietary format called HRTF, developed by the Hololens team. Because the APB (audio processor block) hardware is basically identical to that found in Xbox One, it means that all existing iterations of the console will get the spatial surround upgrade.
This is a weird thing to say. Games are being developed on and for Scorpio right now, using all the active hardware. Microsoft were clearly not referring to the launch date when they said the commander processor's potential is not being used yet. Otherwise the article would've just been them saying, "Well here's what we built, but we're not using any of it yet" over and over.Also of course the additional programmability isn't being used yet, the system isn't even out.
They said it has more capability, which is not being used. At no point did they say it handles DX12 extremely better. In fact, they said the exact opposite: that previous Xbox Ones receive about the same boost with DX12 and the customized command processor.The dx12 chip in Scorpio has more capability than the one in og XB1 as said from MS. The chip is more advanced and handles dx12 extremely better.
Where do you think you heard this? It's not something Microsoft has said. Scorpio does not perform intrinsically better at DX12 than prior Xbox Ones on a per-task basis. (Of course it does perform better overall, due to the increase in clockspeeds, CU count, etc. But that's about a rise in paper specs, not about its efficiency in using them.)Having dx12 instructions on og XB1 using a good portion of CPU compared to nearly zero and all on gpu on Scorpio is a major upgrade no question about that
Whether that premise is true or not doesn't affect the structure of the argument, so your prior objection isn't cogent.
But the premise happens to be true. Microsoft themselves have said that the command processor and attendant DX12 translation benefits are in all Xbox Ones.* They've additionally said that the Scorpio version has more potential for reprogramming, but they're not using that (yet). LukasTaves posited the audio block as another Scorpio assist, but Microsoft have explicitly said that all its functionality is present in prior Xbox Ones as well.
Everything we know, from the platform holder themselves, nullifies his claims.
*A programmable GPU command processor is in PS4 too, which may be relevant. It's an AMD feature.
I guess it depends what you mean by "version." It's running off the same code, but the Scorpio game can have different settings, assets, and more if a dev wants to do that work. Or they can do very little and essentially there would just be increased performance up to whatever limits are in place.
Calling it the Scorpio version and the XBO version isn't inaccurate considering they are closed environments with two presets, but profile also works.
In not sure what you mean, I never said "holding back" in that post. I was talking about the totality of dev time.
It was an Elite console too. It had an SSHD in it, which no other Xbox One console has had otherwise.
Think Scorpio will had an SSHD as well?
The XDK has always been relatively fine in term of ease of use. The problem was the design of the Xbox One, which wasn't the best environment. Scorpio is obviously much better in that regard, but because devs still need to make XBO versions, the amount of work has just gone up overall.
If the Scorpio was replacing the XBO, then your answer would be
At least for the base model it's confirmed already it doesn't.Think Scorpio will had an SSHD as well?
You are correct, I am swamped with kids atm. But still, the question you answered was in comparison. He just wanted to know if there was a difference. What you basically said was yes... but it doesn't matter because of x...
I used to lay tile. If someone asked me if it was easier to lay x tile vs y tile I wouldn't say well yes it is easier to lay x tile but it doesn't matter because I then have a bunch of y tile to lay as well... That doesn't make sense because if I have so many square feet to lay in the first place then it is a blessing that some of it can be done with x tile vs b tile. It also doesn't take away from the fact that x tile is indeed easer to lay period. I understand that you are basically saying that there is now more work overall... But that wasn't the question. Also, would you actually only make one version just for scorpio if it where the start of a new gen and it wasn't mandated? How often did that actually happen last time? How many developers made strictly next gen versions of games right off the bat? Are you saying that you would rather just work on a Scorpio version and leave all the money that could be made with an XB1 version on the table? So, if you where going to make both versions anyway, wouldn't it be a blessing that it is easier to dev on Scorpio than XB1?
I'm just saying that it's a good thing period that the scorpio version is easier to dev for, with or without a mandate to make a version for XB1 and it's ok to say so without any modifiers.
I'm seriously not coming at you man. I'm just trying to show you why some here think you are constantly downplaying advantages.
EDIT: I should say though, that you are nowhere near as bad as Liabe Brave lol and I don't know why people singled you out first. Probably because they figured you where more level headed/unbiased and willing to listen.
Even if it's the same code if one console requires more consideration (like for example managing data in and out of esram) it will impact dev time and results.I don't understand. How would the differing hardware change the environment? I mean I understand obviously having more hardware resources available. But don't the development environment updates benefit the Scorpio and current One? Phil seem to mention this on IGN's Unlocked awhile back too(here).