Advertisement Jump to content
  • Advertisement

swiftcoder

Senior Moderator
  • Content Count

    10063
  • Joined

  • Last visited

  • Days Won

    5

swiftcoder last won the day on September 19 2018

swiftcoder had the most liked content!

Community Reputation

18908 Excellent

About swiftcoder

  • Rank
    Moderator - Game Programming

Social

  • Twitter
    0x21376B00
  • Github
    swiftcoder
  • Steam
    swiftcoder

Recent Profile Visitors

112230 profile views
  1. I'm pretty sure that section 2.3 was put there to make us negotiate a license if we wanted to use Unity as the homescreen on the Fire Phone (an idea that was thrown around a time or two). 3D smartphone UIs were a hot concept at the time (IIRC Nokia worked on one too), and Unity likely didn't want anyone using their tech for free in that scenario.
  2. Aside: flood fill was probably the single most common whiteboard coding interview question at the time when I joined Amazon. Learning both how to implement all the recursive search algorithms, and how to convert them to the iterative version using a stack, will serve you well in the future.
  3. swiftcoder

    Simulate The "No Man's Sky Effect"

    It's height-mapped. They've been focussing on the gameplay, networking, and UI the last couple of years, so the planet tech hasn't really moved from the last few journal posts here. Still gorgeous though.
  4. swiftcoder

    Simulate The "No Man's Sky Effect"

    He's still working on it. I played the alpha a few weeks back, seamless planetary landing and all
  5. swiftcoder

    Simulate The "No Man's Sky Effect"

    That's how it worked initially. I think that was mentioned in one of the early E3 demos (and in videos of NMS from that era you can clearly see the transition as ships pass through the cloud layer). It appears that by the time the game was actually released, they'd managed to get full seamless working. At any rate, I can't see a transition anymore (just the LODs popping), and they got rid of the thick cloud layer that used to surround every planet.
  6. swiftcoder

    Is limbo game 3d or 2d

    Limbo is purely 2D, but the sequel INSIDE is 3D. There's a great presentation on the rendering of INSIDE if you are interested.
  7. In the USA that is generally not legal under the Fair Labour Standards Act. I know there are similar laws in the UK, and I'm sure those exist in many other jurisdictions. In both cases, for unpaid internships to be legal they have to be carefully orchestrated in concert with the student's university, and not displace a full-time worker you would otherwise have hired.
  8. If you are also doing this "for exposure" (i.e. its a portfolio piece or going to be distributed for free/open-source), sure. It's straight up unethical if you plan to directly profit from their work. Even the much-maligned "revenue share" model is better.
  9. I feel compelled to link to @forexposure_txt. Not paying artists, musicians, or anyone else for their work is not ok.
  10. "number of polygons" isn't really a meaningful measure of GPU performance. Most games aren't geometry-bound these days. As higher resolutions, anti-aliasing, and full-screen effects have become common, fill-rate is usually the limiting factor (which generally has more to do with memory bandwidth than with compute).
  11. swiftcoder

    Diablo:Immortal

    Not to mention actively remastering a pretty good chunk of their back-catalogue. I'm really not sure I understand what decision folks want to see reversed. The decision to build a mobile diablo at all? The decision to announce a mobile game at their own conference? Or the decision to not have a finished Diablo 4 ready RIGHT NOW?
  12. swiftcoder

    Diablo:Immortal

    Wait. Hang on. Who died and made you the arbiter of what constitutes a Diablo game? Plenty of people do want Diablo on mobile. Personally, I can't figure out why Diablo wasn't their first mobile title - the Diablo gameplay and loot reward cycle is perfect for a mobile game. The hot pastrami on rye (I'm presuming you mean a PC-based D4 in this analogy) was never even on the menu in the first place.
  13. swiftcoder

    Diablo:Immortal

    There's nothing to be unhappy about here. Given a choice between (a) Diablo Immortal being announced, or (b) no game being announced at Blizzcon, how is (b) preferable to (a)?
  14. swiftcoder

    Diablo:Immortal

    Mobile gaming account for more than twice the total revenue of PC gaming, and that revenue is growing at ~15x the rate PC gaming. Any AAA games company not looking for revenue opportunities in mobile are likely signing their own death warrant at this point. So I don't really get the anger here. This isn't a zero sum game. D4 is clearly still in development (and just as clearly, nowhere near ready to show off). Betting some cash on NetEase to succeed in the mobile market is ensuring Blizzard can afford to float PC development for another decade, even if revenue on PC remains stagnant.
  15. swiftcoder

    OOP is dead, long live OOP

    I've always assumed that Linus objection is to the rest of the baggage that goes along with "not C", rather than the OO part. There's quite a bit of OO in the linux kernel. Besides, Linus clinging to C is a bit of an outlier at this point: operating systems written in high-level languages abound... Symbian was written in C++, and prior to the emergence of iOS/Android, it was the dominant mobile OS. Microsoft Research's Singularity uses a C# kernel and device drivers written over a C++ HAL. Redox is shaping up to be a fairly complete OS written entirely in Rust. And of course, if you go back a bit in computing history, LISP and Smalltalk were each operating systems in addition to programming languages for the machines they were originally developed on.
  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

GameDev.net is your game development community. Create an account for your GameDev Portfolio and participate in the largest developer community in the games industry.

Sign me up!