Earlier this week, the team behind Ashes of the Singularity released an updated version of its early access game, which updated its features and capabilities. With support for DirectX 11 and DirectX 12, and adding in multiple graphics card support, the game featured a benchmark mode that got quite a lot of attention. We saw stories based on that software posted by Anandtech, Guru3D andExtremeTech, all of which had varying views on the advantages of one GPU or another.
That isn’t the focus of my editorial here today, though.
Shortly after the initial release, a discussion began around results from the Guru3D story that measured frame time consistency and smoothness with FCAT, a capture based testing methodology much like the Frame Rating process we have here at PC Perspective. In that post on ExtremeTech, Joel Hruska claims that the results and conclusion from Guru3D are wrong because the FCAT capture methods make assumptions on the output matching what the user experience feels like. Maybe everyone is wrong?
First a bit of background: I have been working with Oxide and the Ashes of the Singularity benchmark for a couple of weeks, hoping to get a story that I was happy with and felt was complete, before having to head out the door to Barcelona for the Mobile World Congress. That didn’t happen – such is life with an 8-month old. But, in my time with the benchmark, I found a couple of things that were very interesting, even concerning, that I was working through with the developers.
Microsoft is moving at a very quick pace with Windows 10, from new technical previews being pushed at a semi-regular pace, to also building Windows 10 for phones at the same time. It goes without saying that all the engineers at Redmond are putting in long hours to bring you technical previews that have already been released, but there is light at the end of the tunnel for the final build.
The next logical question is when will the OS be completed? We are hearing that Microsoft is targeting the month of June at this time, but as with any timeline, this could slip.
Why is the company targeting June instead of its traditional August release? Well, the month of August did not make a lot of sense if you were trying to sell licenses and devices for the back to school market. Previously, when an OS hit RTM in August, hardware from OEMs would not be ready until October which is good for the holidays but misses the back to school shoppers.
So, Microsoft is doing the logical thing here and will push for Windows 10 to RTM in June so that it can have devices ready for the school shoppers, like the next generation Surface.
While we are still digging around for more details, Microsoft knows that it can't ride the Surface Pro 3 forever, it will need to include a Broadwell chip in the device in the near future to remain competitive. Sure, the rush is not immediate, but it needs to happen sooner rather than later, and why would Microsoft launch a new Surface with Windows 8.1?
If you look back to last year, Microsoft released the Pro 3 in June, perfect timing for the back to school market. It would make a lot of sense for the company to release the next generation Surface around the same timeline with Windows 10, and we believe that is their current intention at this time.
Look for Microsoft to talk a lot more about Windows 10 at its upcoming developer conference, BUILD, that takes place at the end of April.
For Windows 10 the 'consumer preview' arrived in January which means for Microsoft to hit the June RTM schedule, they are on-track as they only need to shave about 30 days off of the Windows 8 release patterns which they have already done so far with Windows 10.
Skype is a freemium voice-over-IP service and instant messaging client, currently developed by the Microsoft Skype Division. The service allows users to communicate with peers by voice using a microphone, video by using a webcam, and instant messaging over the Internet. Phone calls may be placed to recipients on the traditional telephone networks. Calls to other users within the Skype service are free of charge, while calls to landline telephones and mobile phones are charged via a debit-based user account system.
Fixed bugs since 6.14
- blocked contacts appearing in Skype Home,
- no input fields (blue window) in login Window,
- crash when chat name contains "&#" characters.
Looks like the folks that still hate Windows 8 will have one less reason in August, as Microsoft have announced that both a more classic start menu and the ability to run "modern" applications within a Window as shown below.
I am always pleased to see such great momentum with operating system developments, but I must admit I was starting to get used to the new full screen menu but I am sure I can adjust back just as quickly if it is done correctly.
I do find the live tiles fairly useful in some applications but must admit for services like Twitter and Facebook I continue to use the web versions just as well, although I appreciate that on Tablets the apps are always far more accessible.