Should be ready in the second half of this year, but we won't release it until it's ready. Ultimately, we have to do what’s best for RuneScape - all we ask is that you keep an open mind, and trust us. We're going to make every effort possible to give you a better RS experience, without losing certain features of the Java client that some of you have grown to love. The list goes on, but I'll save details for future blog posts that will aim to satisfy the more technical among you, and hopefully answer your questions. Gamma correct and HDR rendering pipeline
Cascaded shadow maps (highly detailed sun shadows over larger distances) Global illumination lighting (irradiance via spherical harmonics and ambient occlusion) More platform and OS support (Windows XP/7/8, OSX, Linux, web browser) Better performance over existing Java client To whet your appetites, here's a brief summary of what the new client aims to deliver: We're nearly finished implementing the core client features, with visuals and performance already better than the Java client. We have to adapt, and this is the best way forward!
OLD SCHOOL RUNESCAPE CLIENT WINDOWS 95 SOFTWARE
the existing client software doesn’t do justice to what RuneScape can be and has significant drawbacks which are getting worse over time. Adding to that, C++ is the best cross-platform language and gives us more scope for getting RS working on non-Windows platforms with the best possible performance (e.g. Sounds too good to be true? Actually it isn't, and our progress so far gives us confidence we can meet these goals. It means that we'll be able to provide even better visuals than you currently enjoy, with better performance to boot. C++, on the other hand, gives us total control over performance and rendering. Secondly - and most importantly - both Java and Javascript have no real scope for performance-critical software and graphics rendering. Even major browsers are going to stop supporting it soon, starting with Chrome, and with Firefox following suit soon after. Now, you may wonder why we need to create a new client at all – why not just stick with the technology that’s served RuneScape so far?įirstly, the Java language is no longer fit for purpose as a modern game client solution. This way, we made the most of the work we’d already done, while focusing on fixing the bits that just didn’t work.
OLD SCHOOL RUNESCAPE CLIENT WINDOWS 95 CODE
The back-end code (rendering, audio, networking, build systems, etc.) would be written from scratch, but for the client code itself we would port the HTML5 code base to C++. This could only mean one thing: we decided to take everything we’d learned from our first attempt, and start afresh.Ī unanimous decision was made to begin work on a brand-new, cross-platform, C++ RuneScape client. In terms of performance, it would never be good enough to replace the Java client.Īfter much deliberation, we all agreed that the weaknesses of the HTML client couldn’t be worked around, and that the RuneScape community (and developers too) deserved something really awesome in its stead. We knew from the start that the HTML5 client was experimental, and as we came to the optimisation phase it became clear that it wasn¹t going to be good enough, due to fundamental constraints with the platform (Javascript and the web browsers).
As we mentioned at RuneFest, we’ve since begun work on another brand new game client, and you may be wondering why we’re trying this again. It’s been a year and a half since the beta release of the HTML5 RuneScape 3 client. The New Game Client - how it all started, past, present and future. What graphics modes will they use for this? DirectX, or something custom? Will a SMARTv9 become necessary? SRL-7? I believe we should start planning for this soon because they intend to completely phase out the Java client. As a botter and scripter, I am slightly concerned. As a legit player, I am beyond excited for this upgrade.
0 kommentar(er)
