Kavawuvi

Administrator
  • Content count

    4582
  • Joined

  • Last visited

About Kavawuvi

  • Birthday April 10

Extra Information

Computer Details

  • Name
    Dark Citadel
  • Central Processor
    AMD Ryzen 5 2600
  • Motherboard
    MSI B450M MORTAR
  • Graphics
    MSI GeForce GTX 1070 Gaming 8G
  • Memory
    32 GB [2x 16 GB] G.Skill Ripjaws V Series
  • Storage
    500 GB Samsung 970 EVO SSD (NVMe) + 240 GB ADATA XPG SX930 SSD (SATA III)
  • Power Supply
    EVGA SuperNOVA 650 G3
  • Case
    Fractal Design Node 804
  • Display
    LG 27GL850-B 27" 2560x1440 144 Hz IPS
  • Keyboard
    MAX Keyboard Nighthawk X9
  • Mouse
    Logitech M510 Wireless Mouse
  • Operating System
    Arch Linux

Recent Profile Visitors

171855 profile views
  1. Good to see people still making maps for CE!
  2. I'm going to start releasing builds of the rewritten parts of Invader as those become more feature complete. For example, the new bitmap command is not only faster than old Invader but extremely accurate to tool.exe where it matters and straight-up better in all other cases, featuring higher quality DXT compression, highly accurate sprite sheet and bunpmap generation, highly accurate sharpening, and a superior blurring filter that is gamma-corrected. While an already superior tool in its own right compared to any other released bitmap tool, it also features more powerful data recovery, tag conversion, and script compilation, making it the best tool for all of these features. Being written in Rust, it is also inherently less prone to stability issues, being that nearly all code is "safe" Rust.
  3. It seems the download problem is an issue on the server's end, as it no longer works with the "new" way of downloading maps, where HAC2 uses the "old" way. I am planning to later push an update that uses HAC2's older method of downloading. Hopefully the problem will be solved then.
  4. Oh dear, I hope things are okay!!

  5. I thought I would put here that this guide is now a bit outdated. They have cache version 13 in the header (0x000D) and the tag data address is 0x50000000. They also no longer use compression of any kind, so they are clear to read in a hex editor or with Eschaton. Otherwise they are still really similar to the retail Halo PC cache files, being that the game is based off of it rather than them opting to use code or features from Halo Custom Edition.
  6. A bit of a year-long bump, but I think it is worth noting that, in recent news, 343 Industries are planning on dropping Custom Edition map support. This means that, if you want to run your maps on the latest version of the game, you will have to extract the tags and then fix them up and rebuild the map for Halo: Combat Evolved Anniversary. If any maps you liked were protected, then this will not be possible without fixing the maps. In fact, even today, map protection is still used. As previously stated, those map developers made a conscious decision to corrupt their maps, and in doing so, their content was essentially restricted to only one version of the game forever. All of this was to prevent people from extracting their tags and using them in new maps. However, moving forward, this is ironically the only way you will be able to play these classics on newer versions of the game. Despite this, there is a question raised in this thread: Should we respect their choices and leave their maps in the dust, the way the authors technically intended? Some people may say "Yes" here, and that's fair. Personally, I think we should absolutely not respect this decision. After all, it is unreasonable to expect someone in the 2000's to mid-2010's to know that this would be Halo PC's future. After all, Microsoft had long kept Halo as an Xbox console exclusive despite the player base having asked for a new Halo FPS on PC since Halo 2 Vista, effectively dashing away any hopes of us getting a new Halo PC release. Therefore, as a community, we should preserve Halo PC's history by porting our favorite maps to this newer engine. However, it does mean that a nontrivial amount of effort will be required for some maps, especially as later-generation protectors became a thing which did worse things than just nuke the tag paths. Now it's more important than ever to keep map protection out of Halo as: Map protection does not work with CEA Custom Edition maps will not work with CEA Protected Custom Edition maps are stuck on Halo Custom Edition Therefore, map protection should absolutely not be supported or enabled. Instead, we should support high quality map deprotectors that allow us to preserve these classic gameplay experiences. I, myself, am working on a new map decorruptor in Invader targeting various forms of map corruption, ranging from map protection to issues caused by Eschaton. One longstanding goal has been to port Phoenix 3 and Ice Floe into the CEA map format, but because of artifacts created by Eschaton's map rebuilding process among a few tag-related issues and weird tag paths (e.g. +++++++++++++++), it's not so simple to port it into loose tags.
  7. I love it! This is really good.
  8. Invader supports the new features of CEA introduced in the MCC August 2022 Update. This includes the following: Script parameters are now supported! This goes for both compiling AND decompiling scripts. New functions and globals for scripting! These are more features you can use to make your maps more dynamic and do things you were not able to do before. New definitions! One useful flag you might like is the ability to turn off the "Jason Jones" hack. This is the patch Jason Jones famously implemented which, when compiling a singleplayer map, the pistol and plasma rifle would get buffed significantly. Now you can turn off this hack, making the pistol and plasma rifle more in line with the multiplayer versions. Note that it is recommended you update all MCC-related tools immediately, including both Invader AND the MCC mod tools from Steam. Running old tools on new tags causes issues, and 343 Industries never devised a good way to prevent this.
  9. Invader's received more updates and bugfixes! It now has all of the original HEK limits in place, and we're going to be providing some extended limits for things the base game is OK with but the stock tools are not. I'm also working on a Rust rewrite, and it's about 5x faster at loading tags than the current C++ implementation. Here is how long it takes to load d40b.scenario_structure_bsp, one of the largest tags in the entirety of Halo. Top is current invader-edit.exe. Bottom is the Rust rewrite compiled for Windows. The new parser is about 5.1x faster than the older one. On the same system, this tag takes over two seconds to load on Guerilla.exe. If we want to compare it to Guerilla, we could say it is 423.4x faster than Guerilla, but this would be misleading as it doesn't include the time it takes to load widgets. The actual metric is more like only 5.9x faster, where the current parser is only 5.6x faster than Guerilla. Invader also now supports the August 2022 update. For more information on what this entails, check out the MCC post here:
  10. A few months in, I'm working on getting a decent Internet connection. I'm currently using a mix between 5G and neighbor's wifi. (yes, using the neighbor's wifi is legal. iirc they get a discount from their ISP if they have a public hotspot)
  11. Sauce:https://imgur.com/gallery/QydBStF
  12. Status update: I installed two more SSDs: a 1 TB SATA III drive for Windows 11 and a 2 TB NVMe drive for games. I think SATA III SSDs are fine for OS drives. Sure they have somewhat worse startup times than PCIe, but this really doesn't matter after that simply due to the fact that they are not hard disk drives. I think keeping video game loading times as low as possible is more important, and if my Windows 11 install decides to be a slow pile of garbage after a few years of updates, I can just nuke the whole drive and reinstall Windows without affecting my games. SATA III drive is a 1 TB Crucial MX500. It's a fairly affordable drive with a decent amount of cache. The NVMe drive is a 2 TB Samsung 970 Evo. This drive is a bit more expensive per GB, but the speeds speak for themselves, and no cables are directly needed for it which makes cable management nicer. I want to keep my Arch Linux install, so it's taking up my second NVMe drive slot.
  13. Blue Yeti microphone and another pair of K702s. Sound quality from the microphone is really good. This might be the best microphone I've owned yet. Also holy shit, the DAC in the Blue Yeti microphone is goooood. Basically there is a headphone jack for monitoring, but it can also be used to play back audio from your computer, effectively making it an external sound interface.
  14. I just gotta get an Internet connection, and then I can join you at 2 in the morning... because of timezones. -.- I'm currently using the neighbor's wifi. And yes it's perfectly legal since it counts as a hotspot. Only problem is it is absolute shit... Like, this is the best I can get, and I have to be in a certain part of the building to get it.