Recommended Posts

Valve cranks up Linux gaming, makes it faster than Windows

Valve's distaste for Windows 8 has led the company to take on an increasing interest in Linux, and the new Valve Linux blog shows that, with some work, the Source Engine actually runs faster on it than it does on Windows. The company used a testbed with an Intel i7 3930k, Nvidia GeForce GTX 680, and 32GB of RAM to pit Left 4 Dead 2 on Windows 7 against Ubuntu 12, and the results are rather interesting.

At first, Valve's Linux port of Left 4 Dead 2 ran at only 6 FPS on the i7 machine, but after tweaking the game to make effective use of the efficient characteristics of the Linux kernel and OpenGL, the Valve Linux team was able to eke out a much higher 315 FPS. Using the same machine running Windows 7 and Direct3D, the same game ran at 270.6 FPS, or roughly 14 percent slower.

After optimizing the Source Engine for the Linux platform, Valve wondered why OpenGL was outperforming Direct3D at a technical level. Their research found that, on the same hardware, there are "a few additional microseconds [of] overhead per batch in Direct3D which does not affect OpenGL," indicating that Direct3D may not be as efficient as Microsoft would like developers to believe. There are still challenges ahead for the Valve Linux team, however, as the state of Linux graphics card drivers is still a tumultuous affair. The team has yet to work with AMD and Nvidia, but collaboration with Intel's engineers took place just last month.

Source: The Verge

Even though gaming on linux would be nice, not every company feels the same way about linux developing just because there isn't moolah$$ to be made there, compared to windows.

Also, stupid question but hey.. If linux is "open" wouldn't cracking/pirating be easier?

Also, stupid question but hey.. If linux is "open" wouldn't cracking/pirating be easier?

not really... you CAN run non-opensource programs in linux. There are plenty and games are among them. Piracy in Windows is as easy as in Linux, it comes with the demand.

  • Like 1

This would be more interesting if they did this with a modern engine. But since this is valve we'll only get to see this "it's faster than windows" thing with the hideously outdated source engine.

Well, the more support Linux gets, the more support my Macs get. I'll take OpenGL games over DirectX any day! (see Quake 3).

This would be more interesting if they did this with a modern engine. But since this is valve we'll only get to see this "it's faster than windows" thing with the hideously outdated source engine.

What exactly is wrong with the Source engine out of curiosity? it still looks and performs great!

  • Like 2

If companies jump on board with this like Valve is hoping and port their games over, could OS X and Linux really be the next gaming platform? I'll switch when all my games are supported, and Windows 7 is at end of life.

No, there are people who will NEVER use anything but Windows, just look at any thread involving Linux or OS X, it always devolves to Windows fanboys bashing everything and anything not Windows, performance enhancements like mentioned here are of no concern to them.

Even though gaming on linux would be nice, not every company feels the same way about linux developing just because there isn't moolah$$ to be made there, compared to windows.

Also, stupid question but hey.. If linux is "open" wouldn't cracking/pirating be easier?

1. Companies should be looking linux as an opportunity to make money in the future. Sure windows has marketshare now, and is obviously the best for immediate profits, but linux has a lot of potential to make them money in the future. If more companies do what valve is doing, linux has a very real chance to take off. Its the only way to get past this chicken and egg scenerio of "We don't support linux because it doesn't have marketshare" and "Linux has low marketshare because companies don't support it"

2. I doubt linux would have any effect on the prevalence of piracy, windows games area already cracked day 1, and drm has proven to be ineffective in the first place. The real way to combat piracy is to provide a convenient service to your customers and make high quality games. If you don't treat customers like criminals, they will be more likely to buy the games.

Well, the more support Linux gets, the more support my Macs get. I'll take OpenGL games over DirectX any day! (see Quake 3).

What exactly is wrong with the Source engine out of curiosity? it still looks and performs great!

You aren't forced to buy new games because it's incompatible with older versions, while Source is constantly updated without the forced upgrade or forcing you to purchase your games all over again

source engine is pretty amazing... even amazing for the year that was created. it still looks pretty good and they can optimize it if they want to... but anyway, linux is capable of running unreal engine games for example, that's a most up-to-date base for comparing. osx is also capable of running such games and afterall, osx and linux are both derivated from the same thing, so they're more equal than it seems

I'd like to see what "thenetavenger" has to say about this. He always claims on the front pages that Direct3D is superior to OpenGL. I guess this goes to show he couldn't be more wrong.

Linux and OpenGL are more than capable at competing against Microsoft's Direct3D. In fact, from every test I've seen, Doom3 also runs faster using OpenGL too. Not only that, but developers can target a much broader set of platforms with OpenGL (Linux, OS X, Android, iOS, and more).

  • Like 1

I like some actual evidence of this. as all my experience shows that the linux kernel is not more efficient than the NT kernel(the NT kernel is newer tech with some stuff that the linux kernel should have had but doesn't). and OpenGL I've never on any system see perform better than D3D. I've seen it perform more stable with illegal meshes(basically handling more error before crashing and burning) but not outperforming.

Technically using Linux doesn't make it faster, OpenGL does.

It is good Valve are pushing Steam to Linux but i don't see many developers porting their games over to Linux, unless it is easy and cost effective for them.

It's Linux and the Linux OpenGL implementation that is faster.

Technically using Linux doesn't make it faster, OpenGL does.

It is good Valve are pushing Steam to Linux but i don't see many developers porting their games over to Linux, unless it is easy and cost effective for them.

Except the blog post specifically mentions that the Linux version ran faster than the Windows OpenGL version. They then improved the Windows OpenGL code and sped that up as well, but it's still not quite as fast as Linux .

After this work, Left 4 Dead 2 is running at 315 FPS on Linux. That the Linux version runs faster than the Windows version (270.6) seems a little counter-intuitive, given the greater amount of time we have spent on the Windows version. However, it does speak to the underlying efficiency of the kernel and OpenGL. Interestingly, in the process of working with hardware vendors we also sped up the OpenGL implementation on Windows. Left 4 Dead 2 is now running at 303.4 FPS with that configuration

Is the visual quality identical?

I have a sneaky suspicion that for more advanced engines, like Frostbite 2.0, D3D will win. I am all for linux gaming, but right now Windows dominates that.

it's not easy to tell.. i'm pretty sure that the game studio can "choose" in which API the game will be smoother.. depends on the work for each one upon the game dev...

In general, Direct3D is designed to virtualize 3D hardware interfaces. Direct3D frees the game programmer from accommodating the graphics hardware. OpenGL, on the other hand, is designed to be a 3D hardware-accelerated rendering system that may be emulated in software. These two APIs are fundamentally designed under two separate modes of thought.

As such, there are functional differences in how the two APIs work. Direct3D expects the application to manage hardware resources; OpenGL makes the implementation do it. This tradeoff for OpenGL decreases difficulty in developing for the API, while at the same time increasing the complexity of creating an implementation (or driver) that performs well. With Direct3D, the developer must manage hardware resources independently; however, the implementation is simpler, and developers have the flexibility to allocate resources in the most efficient way possible for their application.

Until about 2005, another functional difference between the APIs was the way they handled rendering to textures. The Direct3D method (SetRenderTarget()) is convenient, while prior versions of OpenGL required manipulating pixel buffers (P-buffers). This was cumbersome and risky: if the programmer's codepath was different from that anticipated by the driver maker, the code would have fallen back to software rendering, causing a substantial performance drop. However, widespread support for the "frame buffer objects" extension, which provided an OpenGL equivalent of the Direct3D method, successfully addressed this shortcoming, and the "render target" feature of OpenGL brought OpenGL up to par with Direct3D in this respect.

Outside of a few minor functional differences which have mostly been addressed over the years, the two APIs provide nearly the same level of function. Hardware and software makers generally respond rapidly to changes in DirectX, e.g. pixel processor and shader requirements in DirectX 9 to stream processors in DirectX 10, while new features in OpenGL are mainly implemented first by vendors and afterward retroactively applied to the standard.

http://en.wikipedia.org/wiki/Comparison_of_OpenGL_and_Direct3D

One gripe about OpenGL I have is the texture quality in games, they always seem to be more smudgy and unrealistic compared to its DirectX counterpart. Anyone remember the Rage megatexture fiasco. Actually everything from ID software after quake 3 looks horrid.

Well, the more support Linux gets, the more support my Macs get. I'll take OpenGL games over DirectX any day! (see Quake 3).

What exactly is wrong with the Source engine out of curiosity? it still looks and performs great!

Of course it performs great. It's something like 8 years old and relatively simplistic on the visuals front(from what i've seen) compared to games of other, more modern engines. It'd be kind of hard for it not to perform well on everything including your toaster.

Is the visual quality identical?

I have a sneaky suspicion that for more advanced engines, like Frostbite 2.0, D3D will win. I am all for linux gaming, but right now Windows dominates that.

OpenGL isn't any less powerful than D3D, its just that D3D is easier to develop for.

One gripe about OpenGL I have is the texture quality in games, they always seem to be more smudgy and unrealistic compared to its DirectX counterpart. Anyone remember the Rage megatexture fiasco. Actually everything from ID software after quake 3 looks horrid.

That's just because ID has been a joke lately, not because of opengl :rolleyes:

If companies jump on board with this like Valve is hoping and port their games over, could OS X and Linux really be the next gaming platform? I'll switch when all my games are supported, and Windows 7 is at end of life.

I don't think OSX and Linux will become the "next" gaming OSes, I just think that PC gaming will shift from Windows only to true multi platform (which is good for everyone...except MS)

One gripe about OpenGL I have is the texture quality in games, they always seem to be more smudgy and unrealistic compared to its DirectX counterpart. Anyone remember the Rage megatexture fiasco. Actually everything from ID software after quake 3 looks horrid.

If large companies like Valve get behind OpenGL, development will speed up and OpenGL will become more competitive with DirectX
This topic is now closed to further replies.
  • Posts

    • The fact I need to use "Show more" like 99% of the time is so annoying. Or why I have 7-zip under 3 submenus when it could be in top. And Microslop keeps saying how they'll improve Start and I've not seen ANY improvement yet. In MONTHS. WTF?! I'll believe any of it when they actually deliver anything.
    • LosslessCut 3.69 by Razvan Serea LosslessCut aims to be the ultimate cross platform FFmpeg GUI for extremely fast and lossless operations on video, audio, subtitle and other related media files. The main feature is lossless trimming and cutting of video and audio files, which is great for saving space by rough-cutting your large video files taken from a video camera, GoPro, drone, etc. It lets you quickly extract the good parts from your videos and discard many gigabytes of data without doing a slow re-encode and thereby losing quality. Or you can add a music or subtitle track to your video without needing to encode. Everything is extremely fast because it does an almost direct data copy, fueled by the awesome FFmpeg which does all the grunt work. Features Lossless cutting of most video and audio formats Losslessly cut out parts of video/audio (for cutting away commercials etc.) Losslessly rearrange the order of video/audio segments Lossless merge/concatenation of arbitrary files (with identical codecs parameters, e.g. from the same camera) Lossless stream editing: Combine arbitrary tracks from multiple files (ex. add music or subtitle track to a video file) Losslessly extract all tracks from a file (extract video, audio, subtitle, attachments and other tracks from one file into separate files) Batch view for fast multi-file workflow Remux into any compatible output format Take full-resolution snapshots from videos in JPEG/PNG format Manual input of cutpoint times Apply a per-file timecode offset (and auto load timecode from file) Change rotation/orientation metadata in videos View technical data about all streams Timeline zoom and frame/keyframe jumping for accurate cutting around keyframes Saves per project cut segments to project file View FFmpeg last command log so you can modify and re-run recent commands on the command line Undo/redo Give labels to cut segments View segment details, export/import cut segments as CSV Import segments from: MP4/MKV chapters, Text file, YouTube, CSV, CUE, XML (DaVinci, Final Cut Pro) Video thumbnails and audio waveform Edit file metadata and per-stream metadata Edit per-stream disposition Cut with chapter marks Annotate segments with tags View subtitles Example lossless use cases Cut out commercials from a recorded TV show (and re-format from TS to MP4) Remove audio tracks from a file Extract music track from a video and cut it to your needs Add music to a video (or replace existing audio track) Combine audio and video tracks from separate recordings Include an external subtitle into a video Quickly change a H264/H265 MKV video to MOV or MP4 for playback on iPhone Import a list of cut times from other tool as a EDL (edit decision list, CSV) and run these cuts with LosslessCut Export a list of cut times as a CSV EDL and process these in another tool Quickly cut a file by its MP4/MKV chapters Quickly cut a YouTube video by its chapters (or music times from a comment) Change the language of a file's audio/subtitle tracks Attach cover art to videos Change author, title, GPS position, recording time of a video Fix rotation of a video that has the wrong orientation flag set Great for rotating phone videos that come out the wrong way without actually re-encoding the video. Loop a video / audio clip X times quickly without re-encoding LosslessCut 3.69.0 changelog: Add lossless cropping & aspect ratio override via bitstream and container metadata #643 Alow shifting tracks for each file (-itsoffset) #216 Add "decimate video" tool to filter away all non-keyframes #2111 Add Windows ARM 64 native build with native ffmpeg Move timecode out of timeline and make it copy-able #2592 #2691 #2800 #483 #2808 Upgrade Electron to latest Add new "opposing" align mode #2654 Add FFmpeg -hwaccel auto setting for hardware acceleration of certain operations Add API events export-start and export-complete Allow deleting track metadata #2819 Improve shift segments dialog #2839 Show keyboard shortcuts inside button tooltips in UI Warn if trying to cut with too few keyframes around cutpoint #516 #2780 #2756 (Linux) include app name in notification #2794 Pull latest translations Other notable changes: Advanced output directory selector #2101 #2115 #2755 increase max file name length to 250 (truncation) #2779 don't reset playback speed when using special playback modes #2889 preserve chapters when merging files that already have chapters don't merge adjacent segments in combineOverlappingSegments #2896 don't transfer segment name when filling gaps #2754 always scroll up to zoom in #2703 #2786 increase max keyframes to 10000 Don't bind ctrl/cmd+c by default (they interfer with copying text) Many other improvements and fixes Download: LosslessCut 3.69.0 | ARM64 | ~100.0 MB (Open Source) Links: LosslessCut Website | Other Operating Systems | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Doesn't even need a UI for point 2 - use some sort of JSON/XML container - because MOST users won't even bother.
  • Recent Achievements

    • Conversation Starter
      FBSPL earned a badge
      Conversation Starter
    • Week One Done
      I2D earned a badge
      Week One Done
    • Week One Done
      Dr Jared Dental Studio earned a badge
      Week One Done
    • Week One Done
      RG INVESTMENT GROUP earned a badge
      Week One Done
    • Very Popular
      The Norwegian Drone Pilot earned a badge
      Very Popular
  • Popular Contributors

    1. 1
      +primortal
      488
    2. 2
      PsYcHoKiLLa
      263
    3. 3
      Skyfrog
      85
    4. 4
      FloatingFatMan
      64
    5. 5
      Michael Scrip
      62
  • Tell a friend

    Love Neowin? Tell a friend!