Welcome to Open Carnage

A resource for gamers and technology enthusiasts, with 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 Kavawuvi

  • Birthday 04/10/1995

Extra Information

  • Gender
  • Contributed
    $100 (US) to Open Carnage

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
  • Storage
    250 GB Samsung 850 EVO SSD; 2 TB Seagate Barracuda 7200 RPM HDD
  • Power Supply
    EVGA SuperNOVA 750 G2
  • Case
    Fractal Design Define R5
  • Display
    Acer G257HU smidpx 25" 2560x1440 60 Hz
  • Keyboard
    MAX Keyboard Nighthawk X9
  • Mouse
    Logitech M510 Wireless Mouse
  • Operating System
    Windows 10 Home

Recent Profile Visitors

51,947 profile views
  1. Currently, the way to do this is to spam the console with empty messages (newlines, spaces, etc.) before sending your message, and you'd do this a few times a second to ensure it refreshes on the screen quickly. In Lua, this would look like this: for i = 1,26 do rprint(PlayerIndex, "|n") end rprint(PlayerIndex, "Insert message here") Or in events.txt, you could put this in your event: rprint $n "|n";rprint $n "|n";rprint $n "|n";rprint $n "|n";rprint $n "|n";rprint $n "|n";rprint $n "|n";rprint $n "|n";rprint $n "|n";rprint $n "|n";rprint $n "|n";rprint $n "|n";rprint $n "|n";rprint $n "|n";rprint $n "|n";rprint $n "|n";rprint $n "|n";rprint $n "|n";rprint $n "|n";rprint $n "|n";rprint $n "|n";rprint $n "|n";rprint $n "|n";rprint $n "|n";rprint $n "|n";rprint $n "|n";rprint $n "Message"
  2. Yes. Why are the numbers on the HUD so big as well as outside of where they should be?
  3. Oh yeah I rewrote the update notifier in Python. It is worth noting that each Python module can add a small amount of time to the startup time. However, the startup time has been massively reduced thanks to a custom strings.dll and keystone.dll file, so it should more than make up for any startup time penalty the new Python API may bring, provided that you don't overdo it. Chimera includes only one module, so you have a lot of room to work with this. Also, Python 3.7 is unsupported on Windows XP. Although Chimera has never supported anything below Windows 7, this does mean that if you do want to continue using Chimera on Windows XP, you might have to use an older version.
  4. Chimera development continues.
  5. If you don't want to make a new animation, you could try setting the seat label to something that is compatible for the cyborg's animation tag, such as W-passenger, but it'll look weird.
  6. Really hard to choose between 2 and 6 for me, so I random.org'd that. Plenty of nice screenshots this month.
  7. Yes. I'm still working on it.
  8. I've added a list of issues that I am working on. You can see the list here: https://github.com/Kavawuvi/Invader/issues I've already solved one issue since posting the source code, and that was an issue with antennae missing some values that weren't calculated, resulting in no antennae being easily visible. There are more issues to fix, and more issues may be added onto this list in the future. Also, model data is now deduped, similar to bitmap and sound data. This saves around 0.18 MiB on tutorial.map. Other things are now deduped, too, such as animation data and tag paths, saving a total of 575 KiB over tool.exe's tutorial.map.
  9. I put the source code online a few days ago. Here is a link: https://github.com/Kavawuvi/Invader Invader is not done and has lots of issues that need to be fixed before I can even consider releasing it. Therefore, it will be a while before I actually start posting binaries (e.g. exe files). If you want to use it early for some reason, you must compile it from source.
  10. Tutorial.map is almost entirely finished. There are more issues to work with, but for the most part, it works. I also wrote a feature to force a specific tag order, thus you can use the same tag order as stock tutorial. This means that, if there are no tags missing, the map can be network compatible, assuming you correctly spoof the CRC32. Here's tutorial.map: tutorial.7z Also, ui.map builds and works. Download that here: ui.7z Edit: I found an issue with item_collection tags' default timers. I've updated the map with the fix.
  11. I'm planning on open sourcing this pretty soon. My license of choice for this one will most likely be GPL version 3.0 or newer. Such an license ensures that my program stays free and open source whether it's being used standalone or as part of a bigger thing, and in this kind of community, I feel everyone benefits from this. People who make useful tools only to never share the source probably should steer clear of my work, though I suppose the one person I know of who actually said he'd do this probably wouldn't have used this, anyway, simply because I made it.
  12. I decided to benchmark Invader by building tutorial.map. While this map is not representative of what most people build, it is the example map that comes with the Halo Editing Kit, meaning this is repeatable by anyone. Each number is based on an average of five runs after running it once to cache everything. As you can see, tool.exe is much slower than Invader, taking over a second on average. This slowness will matter a lot more if you are building much bigger maps. You may also notice that there are three different Invader numbers: one for Linux, one for 32-bit Windows, and one for 64-bit Windows. On Windows, the 64-bit version takes around 10% less time to build tutorial.map than the 32-bit Windows build. I probably won't release a 32-bit binary, anyway, because there's no reason to support it. The Linux build takes 54% less time than the Windows build, and it takes nearly 80% less time than tool.exe. That 54% reduction might be down to a number of things: a less bloated operating system, better I/O, and no Antimalware Service Executable most likely contribute.
  13. Menus have been added. Some other stuff was fixed. There are still a few issues left to fix with tutorial.map: Part of the sniper rifle zoom is flipped Some particles look a little off The warthog is making the sliding sound when it shouldn't Some tags, namely those stored in loc.map, aren't indexed, so you will see English strings regardless of your language Download the map here:
  14. When the world rolls the Covenant armada and the Flood instead of you
  15. As of yesterday morning, I got Invader to build maps that work with multiplayer without crashing as well as mostly functioning vehicles. Therefore, you may use the in-game menu to load the map now. Note, however, that the menu tags are not in the map, so to exit, you will need to use console commands. You can download the resulting tutorial.map file here: In other news, Invader's source code works on the Raspberry Pi with no modification required. I will not support the pi or anything like that, but it was a neat test, nonetheless.