Welcome to Open Carnage

We're a community of gamers and technology enthusiasts, with a very unique means of rewarding content creation and support. Have a wander to see why we're worth the time!


  • Content count

  • Joined

  • Last visited

About 002

  • Birthday April 10

Extra Information

  • Gender
  • Location
    < joke here>
  • Occupation
    <Another joke here>
  • Interests
    24.9% interest
  • Contributed
    $100 (US) to Open Carnage
  • Raffle Victor

Contact Methods

Computer Details

  • Name
    Black Comet
  • Central Processor
    Intel Core i7-6700K
  • Motherboard
    Gigabyte GA-Z170-X-Gaming 5 ATX
  • Graphics
    MSI GeForce GTX 1070 Gaming 8G
  • Memory
    2x 8 GB Corsair Vengeance LPX DDR4 @ 3000 MHz 15-17-17-35
  • Storage
    250 GB Samsung 850 EVO SSD
  • Power Supply
    750 W 80+ Gold EVGA G2
  • Case
    Fractal Design Define R5
  • Display
    1080p ASUS junk
  • Keyboard
    MAX Keyboard Nighthawk X9
  • Mouse
    Logitech wireless junk
  • Operating System
    Windows 10

Recent Profile Visitors

18,166 profile views
  1. I want to finish college and get a permanent job. That's my resolution. Also, I'm on 1920x1080 currently. My laptop is 1366x768. My tablet is 2048x1536.
  2. Kaby Lake didn't really have much. I knew long before it was released that it would hold absolutely no IPC improvement because Intel pretty much stated themselves that it's a refresh of Skylake, but that it would have some extra features. The only good things that I found to be notable was adding hyper-threading to Pentiums, slightly more cache to the i3, slightly better video decoding, and a slightly better GPU. Otherwise, their only way of increasing performance was just increasing the clock speed. At least Skylake brought a (small) IPC improvement, support for DDR4, and an upgrade to the PCH to PCIe 3.0 and a decent number of PCIe lanes. Right now, there is absolutely no reason for anyone to upgrade from even Sandy Bridge, as even a modestly overclocked i7-2700K will perform just fine in any task. If AMD is coming out with powerful CPUs once again (which I can only hope that's what they're doing), then this can change. I want both companies to do well, which is why I and everyone else wants AMD to slap Intel awake by defeating Intel's mainstream and enthusiast processors in both price and performance, because $120 dual cores, $300 quad cores, $410 hexa cores, $1000 octa cores, $1730 deca cores, the $200 motherboards you need just to have more than 4 cores, and the $50 you pay if you want the right to overclock your quad or dual core processor on top of the extra you pay just to cool the damn thing all need to die in a fire.
  3. Welcome to the forum. I hope you like it here!
  4. Probably the 2nd slightly overclocked version of the i7-6700K until Cannonlake. Basically, Intel is doing an AMD and increasing the clock speed of their processors rather than improving the architecture. And no, you're not getting any more overclocking headroom with this, either.
  5. Nope. Just sehe's site sucks and he's using buggy software that's just garbage. The forum is up at least. http://halo.isimaginary.com/forum/ I keep telling him about it and he still hasn't replaced it. This is why I wrote the SAPP documentation as a PDF - no buggy software is required to host it.
  6. Unfortunately, not without creating a Lua script. This is a really silly issue, and blame sehe for being lazy here.
  7. I saw The Lego Batman Movie.
  8. Was out for this weekend again and didn't get back home until about an hour after when it would start, but it looks like @ShikuTeshi wasn't here, either, anyway. Is next Saturday okay? Does anyone want something else streamed on Saturdays if nobody shows up?
  9. Here's a demonstration of Tritium: its speed compared to even the Mac version of Eschaton, which happens to be around 3x faster than the Windows version for an unknown reason. Note that the dependency swapping part does not use Tritium, so ignore it if you want. There's also some elevator-like music that YouTube provided. If you want some numbers: Expanding Fire Dragon took 204 ms total. Retrieving the map from the SSD took 19 milliseconds and Tritium's tritium::map::Map::from_cache_file() function took 30 milliseconds parsing the opened map file. The remaining time was spent with the application processing Tritium's resulting struct into its user interface. In comparison, Eschaton's H1.map_expander took 4.69 seconds, nearly 23 times longer than Fire Dragon. One of my assumptions was that Eschaton was being bottlenecked by my SSD, so I put bloodgulch.map onto a RAM disk. As a result, Eschaton took 4.69 seconds. Importing The tag used was b30.map's characters\marine_armored\marined_armored actor variant tag. Fire Dragon took 3 milliseconds to extract, with Tritium's tritium::tag::tag_array::TagArray::insert_recursive taking 2 milliseconds when extracting and isolating the tag. It then took 191 milliseconds to import the extracted tag with tritium::tag::tag_array::TagArray::insert_recursive taking 9 milliseconds, with the rest of the time spent on the user interface. In comparison, Eschaton's H1.Map.expandTag took 1.41 seconds to recursively extract and H1.Map.addTags took 1.74 seconds to import. Rebuilding Unlike in the video, I reopened bloodgulch.map when recording these numbers, so this is done using a stock bloodgulch.map with no tags imported. Fire Dragon took 117 ms total. Tritium's tritium::map::Map::to_cache_file() function took 60 milliseconds. Saving the result to the SSD took 55 milliseconds. In comparison, Eschaton's H1.map_writer took 2.85 seconds, 24 times longer than Fire Dragon. Writing directly to a RAM disk took 2.67 seconds, an 8% improvement. Specs: Intel Core i7-3667U. 8 GB of RAM @ 1600 MHz. Mac OS X 10.11.5 "El Capitan"
  10. This is my brother's dog, Cinnamon Bun. These are my gerbils. The one on the left is Lucy. The one on the right is Sugar who very sadly passed away last week.
  11. Happy birthday. You're one year closer to being an old fart.