Following our first podcast with ProfessorKaos64 featuring his work on SteamOS, here is the second episode this time with the president of Codeweavers, James Ramey, recorded just a couple of weeks ago. We have already had the chance to feature James Ramey regarding DX11 support in the past, and it’s a great time to reconnect with his and his team to see what are the prospects for CrossOver/WINE in the near future. Including DX12 support down the road with Vulkan!
Here are some time-markets in case you want to skip to some particular content:
- 0:00 – Introduction
- 3:00 – How many users for CrossOver ?
- 8:52 – About the lack of Trial for CrossOver
- 14:00 – Legends of Eisenwalk and its CrossOver port to Linux – How things started
- 27.55 – Are you proactive to make ports of older titles working very well with WINE/CrossOver happen ?
- 30:29 – Why are publishers not interested by easy (i.e. working out of the box) WINE/CrossOver ports?
- 33:00 – How can we help change things ?
- 37:48 – The State of DX 11 support in CrossOver/WINE
- 42:40 – Can we expect “Overwatch” to work sometimes in 2016 ?
- 51:05 – What are the plans for Vulkan integration in CrossOver/WINE ?
- 56:30 – Anything the Linux Community can do to help the CrossOver/WINE project ?
Many thanks to Psppwner300 for hosting this podcast, and to James Ramey for accepting our invitation. As usual we’d like to get your feedback so that we can continue to provide more content in the upcoming weeks and months. Note that if you want to register to the podcast feed, please make sure you get the feed address right (we gave you the wrong one last time!).
At BoilingSteam, we want you to browse our content free from ads and trackers. But keeping this website alive is a constant investment. Why don't you support what we do with donations on LiberaPay? Everything you contribute is re-invested in infrastructure and ongoing content to better serve the Linux Gaming community now and for future, bringing the good news to existing and upcoming Linux users. You can follow what we do via our newsletter, our RSS feed, our Mastodon profile or our Twitter feed