Language Selection

English French German Italian Portuguese Spanish

Games: Oxygen Not Included, Proton, GDScript

Filed under
Gaming
  • The first DLC for Oxygen Not Included sounds huge, free update soon too

    Klei Entertainment have been busy working behind the scenes on the next free update and first expansion for Oxygen Not Included and they've detailed what's coming.

    First, the free update coming within the next few days should fix plenty of issues, including one involving infinite digging which sounds annoying. More exciting is the DLC though, it's sounding like it's going to be massive!

  • VKD3D-Proton is the new official Direct3D 12 to Vulkan layer for Proton

    VKD3D was originally a project created directly by the Wine team, the compatibility layer that Proton is built upon. However, the original founder passed away and it seems Valve-funded developers are taking the torch to push it much further. It's actually been a thing for a while but today they adjusted the name of their project as VKD3D-Proton, to give it some official status plus preventing any naming conflicts elsewhere and just be clear about their goals.

    They're going for supporting the "full" Direct3D 12 API on top of Vulkan, with an aim of both performance and compatibility using modern Vulkan extensions and features, so this comes at the expense of compatibility with older drivers and GPUs. They're also not looking to keep backwards compatibility with the original vkd3d.

  • GDScript progress report: Type checking is back

    After completing the new tokenizer and parser as mentioned in the previous reports, I started working on the code analyzer, which is responsible for type checking and also for used for other features like warnings and some optimizations.

    This was done before as a second pass inside the parser but it was now moved to another class to make it clear that it doesn't happen at the same pass thus avoiding issues with functions being called out of order (which happened by a few contributions that missed this detail).

VKD3D at Phoronx

  • Valve Working On A VKD3D Fork For Getting Direct3D 12 Advanced For Proton / Steam Play

    While upstream Wine developers continue working on VKD3D for providing a Direct3D 12 to Vulkan translation layer for Wine, a developer on Valve's Proton team has now forked it as Proton-VKD3D for focusing their efforts on getting the D3D12 support moved along for Proton that powers Steam Play.

    While upstream Wine developers and in particular CodeWeavers do continue to work on VKD3D, VKD3D-Proton appears to be Valve's fork or downstream of that where they can more freely work on their game-focused support for enabling Direct3D 12 Windows games to be better supported on Linux with Steam Play. Presumably it will be more along the lines of a downstream / moving fork of VKD3D rather than a hard fork, similar to Proton re-basing against Wine every once in a while.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Today in Techrights

Android Leftovers

LibreOffice 6.4.5 finally for Slackware 14.2

The Document Foundation recently released version 7.0.0 of their Libre Office suite of applications. The packages for Slackware-current can be found in my repository. But the situation for Slackware 14.2 used to be different – I got stuck after LibreOffice 6.2 because the newer source releases (6.3 and onwards) require versions of system software that our stable Slackware 14.2 platform does not offer. From time to time during the last year, when there was time and the build box was not compiling packages, I messed around with the libreoffice.SlackBuild script in futile attempts to compile recent versions of LibreOffice on Slackware 14.2. I failed all the time. Until last week. After I had uploaded the new KDE Plasma5 packages to ‘ktown‘, I had an epiphany and decided to use a new approach. What I did was: question all the historic stuff in the SlackBuild script that got added whenever I needed to work around compilation failures; and accept that the compilation needs newer versions of software than Slackware 14.2 offers. The first statement meant that I disabled patches and variable declarations that messed with compiler and linker; and for the second statement I stuck to a single guideline: the end product, if I were able to compile a package successfully, has to run out of the box on Slackware 14.2 without the need to update any of the core Slackware packages. Read more

Web Browsers: New Tor RC, Firefox/Mozilla Trouble, and Web Browsers Need to Stop

  • New release candidate: 0.4.4.4-rc

    There's a new alpha release available for download. If you build Tor from source, you can download the source code for 0.4.4.4-rc from the download page. Packages should be available over the coming weeks, with a new alpha Tor Browser release likely in the coming weeks.

    Remember, this is a release candidate, not a a stable release: you should only run this if you'd like to find and report more bugs than usual.

  • Mozilla is dead

    If Mozilla wants to survive, the management will be fired with unearned compensation, the most important departments will be strengthened, products that nobody ordered will be discontinued and the organization will be limited to its core competence. Browser, email, security, adaptability and the fight for a free Internet. And they work with all their might to ensure that the products will become an integral part of everyday life and all operating systems.

    Three months. That’s all the time they have for a clear signal. After that, users have to make a decision. Unfortunately, it will probably only be something with chromium.

    Poor Internet.

  • Web browsers need to stop

    I call for an immediate and indefinite suspension of the addition of new developer-facing APIs to web browsers. Browser vendors need to start thinking about reducing scope and cutting features. WebUSB, WebBluetooth, WebXR, WebDRM WebMPAA WebBootlicking replacing User-Agent with Vendor-Agent cause let’s be honest with ourselves at this point “Encrypted Media Extensions” — this crap all needs to go. At some point you need to stop adding scope and start focusing on performance, efficiency, reliability, and security5 at the scope you already have.