Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror
×
Microsoft Programming XBox (Games) Games

Will Every Xbox Be a Dev Kit? 69

jfruh writes There were a lot of rumored features of the Xbox One that vanished after public outcry — that it would need an always-on Internet connection, for instance. But another rumor from that era was that every Xbox One sold would include a dev kit that would allow anyone to create games — and it looks like this is one dream that might be coming true soon.
This discussion has been archived. No new comments can be posted.

Will Every Xbox Be a Dev Kit?

Comments Filter:
  • Comment removed (Score:5, Interesting)

    by account_deleted ( 4530225 ) on Wednesday February 18, 2015 @10:11PM (#49084357)
    Comment removed based on user account deletion
    • Every PC running Windows, OS X, or GNU/Linux includes a rudimentary devkit comparable to the BASIC interpreter on early 1980s home microcomputers. It's called the JavaScript interpreter. Copy the following to a new text file called hello.html

      <!DOCTYPE HTML><html><body><div id="out"></div><script>
      document.getElementById('out').textContent = "Hello World";
      </script></body></html>

      And every general-purpose personal computer allows other developer tools to

      • The big draw of the OUYA console was its binary compatibility with Android, letting it use well-known tools such as Eclipse and Xamarin. Yet OUYA fizzled for some reason.

        Way too many glitches. Saw a keyboard as a game controller, and the keyboard would become controller #1 when the game controller went to sleep. But without a keyboard, life is bad, because you need to type stuff all the time. They kept changing the dashboard without fixing the stuff that was wrong with it. Support for third party controllers was poor, even though that was the whole reason for their controller library to exist. Then google announced that they were going to come up with a gaming hub app and m

      • Comment removed (Score:5, Insightful)

        by account_deleted ( 4530225 ) on Wednesday February 18, 2015 @11:12PM (#49084655)
        Comment removed based on user account deletion
      • by Blaskowicz ( 634489 ) on Thursday February 19, 2015 @01:01AM (#49085025)

        What the fuck is a div? where did that document.this_function().that_stuff got declared?
        How come that this html file works as well :
        Hello World

        Yea there are probably a lot of crappy tutorials on the internet, but there's no thick paper manual that came with the computer (CBM 64, Apple II, Amstrad CPC..) or a comprehensive help file integrated to the web browser (like in QBASIC) to explain all that crap in a friendly, up to date way.
        All I'm seeing is a blank page experience and a hello world.. It's like saying anyone can be a dev and make little games, because there's notepad and the Windows Scripting Host.

        • by tepples ( 727027 )

          Perhaps that's a symptom of another problem: the shift from printed manuals to manuals on the install media to manuals on the other side of the Internet.

      • Every PC running Windows, OS X, or GNU/Linux includes a rudimentary devkit comparable to the BASIC interpreter on early 1980s home microcomputers. It's called the JavaScript interpreter.

        Every cell phone and tablet these days, as well.

        • Every PC running Windows, OS X, or GNU/Linux includes a rudimentary devkit [...] the JavaScript interpreter.

          Every cell phone and tablet these days, as well.

          True, but I failed to mention one thing: a text editor in which to create an HTML file in the first place. The mobile operating systems tend not to ship with one.

      • Yet OUYA fizzled for some reason.

        There's always the Uzebox [belogic.com]. It may be a lot less powerful, but it's open source, anyone can code for it and anyone can build one at home at a very low cost.

      • The big draw of the OUYA console was its binary compatibility with Android, letting it use well-known tools such as Eclipse and Xamarin. Yet OUYA fizzled for some reason.

        "For some reason"? Were you one of those blind fanbois? It's many issues were pointed out all over the place. Penny Arcade pointed out that it was just mostly hype and then all the Ouya fanbois across the Internet got butthurt [giantbomb.com]. Acting as if the failure of Ouya was some freak accident that no one expected, is revisionist history.

      • Yet OUYA fizzled for some reason.

        Ouya fizzled because it was the answer to a question nobody asked. There are many platforms for independent development that already exist so yet another entry into the lowend was really not going to be successful. Being based on Android was in some ways advantageous but really that was the nail in its coffin, it was easy for developers to just develop an Android game and publish it independently, publish it to Google Play and publish it on the OUYA store so OUYA had no exclusivity, no reason to buy it. It

        • by tepples ( 727027 )

          Ouya fizzled because it was the answer to a question nobody asked.

          The question was "What platform for independent development can easily be connected to a TV?".

          • The question was "What platform for independent development can easily be connected to a TV?".

            Lots, including the PC. Now obviously the next question is why would you want to connect it to a TV, the answer would be that there are games (like local multiplayer ones with controller support) that people want to play that benefit from it.

            • by tepples ( 727027 )

              Now obviously the next question is why would you want to connect [a gaming PC] to a TV, the answer would be that there are games (like local multiplayer ones with controller support) that people want to play that benefit from it.

              A bunch of Slashdot users over the past several years have been repeatedly telling me that almost nobody is willing to do that. At first, it was because most TVs were CRT SDTVs that could not display PC video without an obscure scan converter box. But once HDMI took off, the big excuses repeated in past comments [slashdot.org] were that the family's PC has integrated graphics, or it's in a separate room from the TV, or just "it's too hard, and consoles are easy [pineight.com]". Instead, I've been told that people interested in developin

              • A bunch of Slashdot users over the past several years have been repeatedly telling me that almost nobody is willing to do that.

                Of course nobody is willing to do that, there is no advantage or reason to do it. But it is extremely easy to do if some reason to do it came about, like a decent game that required it or was made more enjoyable by it.

                You aren't going to get an audience without content.

                • by tepples ( 727027 )

                  You aren't going to get an audience without content.

                  I agree. But these naysayers have kept telling me that a PC game developer won't get an audience even with content because effectively all the audience for local multiplayer content are console users.

                  • I agree. But these naysayers have kept telling me that a PC game developer won't get an audience even with content because effectively all the audience for local multiplayer content are console users.

                    Well obviously you can't just put out the same experience that console users already get. Obviously it needs to be good content that people actually want, yet-another-local-multiplayer-game is not going to win anybody over because you can't disrupt the status quo with an unimaginative "me too" offering. Why buy title X and move my PC into the lounge when I can just play title Y on my console? Well you have to provide that reason.

                    This is the same reason Ouya failed, all they provided was a platform and were

    • Some of the games for the Odyssey2 console -http://en.wikipedia.org/wiki/Magnavox_Odyssey%C2%B2 - had some (extremely) limited programmability to them. I remember making my own maps on the pac man clone, and programming in their flavor of basic which was different from the basic I knew from the TRS-80 series and hand no real way to save your programs

    • by hitmark ( 640295 )

      A big glaring difference between the C64 of old and the "dev kit" of today is that you have to flip "the switch".

      With the C64 the command prompt was also the BASIC interpreter. You could enter the command to load other files into memory, and be on your merry way, or you could start entering BASIC code right there.

      You see something similar with *nix shell script.

      But with this "dev kit" you have to make the device enter a specific mode. And likely this mode will block you from accessing any of your gaming for

    • Imagine if Microsoft gave Unity $10 per full Unity Pro license on all XBoxes. If fewer than 1 in 150 users actually used the dev kit, Unity would come out ahead in revenue versus their $1500 permanent license.
  • by fuzzyfuzzyfungus ( 1223518 ) on Wednesday February 18, 2015 @10:13PM (#49084359) Journal
    Are you seriously telling me that if you slightly de-cripple a general-purpose computer that it can be used as a general purpose computer?

    Truly, I am living in the goddamn future now...
    • by epyT-R ( 613989 )

      I'll sure it'll be crippled.. Like XNA on the 360.

      • Re: (Score:3, Informative)

        by tepples ( 727027 )

        Xbox 360's Xbox Live Indie Games environment and Windows Phone 7's third-party app environment were crippled to run only C#[1], probably because these platforms lacked a full MMU. The type-safe sandbox was the only security means that the things had, much as in the Singularity research operating system [wikipedia.org]. That might also be part of why Windows Phone 7 devices cannot be upgraded to Windows Phone 8.

        [1] The actual restriction was "verifiably type-safe IL that uses the libraries available in the .NET Compact Fram

  • Apps... (Score:4, Interesting)

    by zarthrag ( 650912 ) on Wednesday February 18, 2015 @10:25PM (#49084427)

    Apps are not games. I get the sneaking feeling that this is just a ruse to get people excited about W10 development. If you're expecting to build your own A/AA/AAA title on XB1 - I'd continue holding your money/breath. This could easily be a repeat of XNA.

    Personally, I have no intention of even *touching* an XB1 unless they open-up *native* development. (That means a full directx sdk, kinect, ...the works. None of this .NET second-class-partial access)

  • It will soon be running the same win 10 that my laptop and phone use. I had better be able to make my own games for it.

  • by He Who Has No Name ( 768306 ) on Thursday February 19, 2015 @12:06AM (#49084833)

    XB1 devkit functionality is in software, not hardware. And part of that is account access to parts of MS Corpnet that allow correct devkit functionality. We have to have the correct authorized user account and sandbox entered for devkit functions to work correctly.

    Our devkits at MGS are stock retail kits that are pulled off the line and loaded with in house SDKs.

    I have no idea what the plan is, if any, to roll that out widespread. I'm just a polygon slinger.

  • by Mike Buddha ( 10734 ) on Thursday February 19, 2015 @01:38AM (#49085129)

    Sheesh. I'm surprised the original poster didn't point out that Microsoft was found to have abused monopoly power with Internet Explorer in the 90's in Europe in the summary.

  • Grand Theft Auto - Microsoft Bob Edition

    Or, Angry Bobs

  • Why does anyone find it surprising?

    If you register for a developer program you'll be able to (for a fee) compile and develop apps and sign them for your device. If you want others to be able to run them you'll submit them to MS' store and they'll approve them or not.

    And yes, just like for iOS you'll be able to do development and testing on the device.

    It's been done before by Apple and by MS (for Windows and Windows Phone). I'm not sure what is the shock that it's going to happen again.

    They're going to be Wi

  • "There were a lot of rumored features of the Xbox One"

    They were not rumors, but facts. Microsoft backpedaled on most of them. Short memory span or shill?

Single tasking: Just Say No.

Working...