Kavawuvi

Administrator
  • Content count

    4571
  • Joined

  • Last visited

Everything posted by Kavawuvi

  1. I have moved. Far away. Sadly I could not bring my PC, so I'm going to be building a new PC! The CPU is going to be an AMD Ryzen 9 5950X since they've come down massively in price and are thus way more affordable. Intel just doesn't look very compelling at the $490-$590 price point right now. I plan on buying an NH-D15 cooler as well, but I'll need to make sure it fits. The GPU is going to be my AMD Radeon RX 580. Newer GPUs are too costly right now. I'm looking to start on 64 GB of RAM, but I plan to maybe upgrade to 128 GB. I'm still deciding on a decent motherboard, but 128 GB requires four DIMM slots. I'd prefer if there was no chipset fan. I'm also still deciding on a case, but the Corsair 200R looks really good. I've used this case before and found it to be very affordable but also very sturdy. Yes it's almost 10 years old, but no one makes that much better cases for $60, so this choice is very compelling. The SSD is initially going to be my older 500 GB Samsung 970 Evo, but I plan on installing a 1 TB SSD to hold games. I would rather avoid a hard drive. PSU is probably going to be whatever decent 750 W power supply I can get my hands on for around $90-$120 that isn't a nuke. PSUs are pricey, but it is better to not risk blowing everything up. Use cases for the build are coding, video editing, and gaming! Here's the PCPartPicker: https://pcpartpicker.com/list/Rmg6qm
  2. 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.
  3. 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.
  4. 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.
  5. All right, I built it! There's a bit of clean up left to do, both inside the PC and outside. Basically, I haven't done any cable management yet outside of having things go through the back of the case, as my main goal for today is to just make sure it all fits and works. So while the airflow will at least be as good as it can be and there are no cables in danger of touching any fans, there are improvements to be made. Of course, this build isn't done yet. I have three upgrades in mind which I'll talk about later. When that happens, I'll post one final picture with the finishing touches. Here is the build successfully POSTing for the first time. And here is htop. So, what's next? Well, I made a mistake when planning my build and bought high profile RAM. This means the Noctua NH-D15 is missing a fan for now. I am going to be purchasing a full 128 GB kit of low profile DDR4 RAM later. This will cost about $500. I'll give the 64 GB of RAM to a close friend of mine. This 64 GB RAM will be a pretty nice, surprise upgrade for her. Next, I need a drive for Windows 11. I plan on buying a 2 TB NVMe SSD - enough for a large amount of games. This will cost around $200. Lastly, while the RTX 580 is a fantastic card, it is a mid ranged from 2017. Times have changed in the past five years, and Polaris no longer cuts it for modern games. Because Nvidia have decided to be nice recently and make open source drivers for their newer GPUs, Nvidia GPUs are going to soon be a viable option for Linux. Therefore, I have my eyes set on the RTX 3080. This would normally cost around $600, but GPUs suck to buy in 2022, so I'm going to be paying around $900 instead. Overall, this upgrade will cost me around $1500. But if Nvidia graphics cards stock stops being bad, maybe I'll pay even less? We'll see. But probably not. I've added a PCPartPicker link to the OP while I'll update as I go along, but as a "snapshot" of my current plans, it's https://pcpartpicker.com/list/Rmg6qm Note I will not be going with a dual GPU configuration. The airflow is not good enough to sustain this, and the maximum power draw exceeds my PSU rating. So, I will be dropping the current RAM and GPU once they have been replaced.
  6. To make custom reticles, you need to make a bitmap tag that has your reticle in it. To do this, you can use tool.exe or invader-bitmap to turn a color plate into a bitmap tag. To do things like setting position, scaling, type, or other things about the reticle, use a tag editor such as Guerilla or invader-edit-qt and make or edit a weapon_hud_interface tag.
  7. And one month later, I bought every part I need. Changes The case is a bit newer, the 275Q (2019) instead of the 200R (2012), although it is more of less functionally the same, except it's lacking the 5.25 slots and side panel vent. Anyway, I had a good experience with the 200R when I built a PC with it. It's a very solid, affordable case, and I think it is better than most cases that cost twice as much as it, prioritizing function over form with no side panel window but excellent sturdiness. Has Corsair kept up this trend with the 275Q? Who knows? Anyway, according to reviews, it will fit the NH-D15. I went with an 850W PSU as there was almost no difference in price at the time vs 750W PSUs (they're all horribly overpriced!). It should be a pretty good power supply. I don't know if it will be as good as my EVGA G2 and G3, but here is hoping!
  8. I've updated Invader's LICENSE.txt. This does not change any terms. Rather it clarifies what content you own when you use Invader. tl;dr - Invader is GPLv3. Your tags are not. If you make tags, you own them. If you use pre-existing tags such as tags from the Halo 1 Mod Tools, you (probably) don't own them. If you agreed to a EULA such as the MCC EULA, your usage of Invader does not modify this agreement, and while your usage of Invader, itself, is not bound by the MCC EULA, your usage of MCC content is.
  9. Invader is a work-in-progress, open source, cross-platform toolkit for creating Halo: Combat Evolved maps. There are a number of tools that come with Invader: invader-archive - CLI program for creating archives of all of the tags required to build cache files invader-bitmap - CLI program for generating bitmap tags invader-bludgeon - CLI program for backhanding uncooperative tags invader-build - CLI program for building cache files from scenario tags invader-compare - CLI program for comparing sets of tags and showing differences invader-convert - CLI program for converting between different tag types - highly useful for Xbox map porting invader-dependency - CLI program for listing the dependencies of a given tag OR the tags that depend on a given tag invader-edit - CLI program for scripting tag editing operations invader-edit-qt - GUI program for editing tags invader-extract - CLI program for extracting tags from a map invader-font - CLI program for generating font tags invader-index - CLI program for generating a list of all of the tags in a cache file or resource map (useful for invader-bitmap) invader-info - CLI program for getting metadata of a cache file invader-model - CLI program for creating gbxmodel/model tags invader-recover - CLI program for recovering source data from tags invader-refactor - CLI program for renaming tags (or directories of tags) without breaking references invader-resource - CLI program for generating resource map files (i.e. bitmaps.map, sounds.map, loc.map) invader-script - CLI program for compiling scripts. invader-sound - CLI program for generating sound tags invader-string - CLI program for generating string list tags invader-strip - CLI program for cleaning up tags Six Shooter (Windows only) - GUI frontend for Invader ... and (hopefully) more programs to come! You may be wondering, why am I taking time to replace the Halo Editing Kit, something that supposedly already works fine? I'm glad you asked (or I asked?)! The Halo Editing Kit... ...is closed source. This means that you cannot make changes to it or add functionality without resorting to modifying the .exe file directly. Also, information has been obfuscated away through compilation. Invader is open source. ...is unsupported. Since it's closed source, you cannot rely on the developers to issue any updates to fix problems with the program. If they never update it, then it is the final version you get. An ideal program should never need updated, but the HEK is very far from ideal. Because Invader is open source, anyone may fork and support Invader at any time. ...is limited. Since it's closed source, you have to modify the .exe file directly in order to make changes to it. If you don't, you're limited to building 384 MiB cache files. Also, singleplayer maps are tied to the resource maps you built them with, thus users must have the same exact bitmaps.map and sounds.map you used to ensure the correct assets are displayed/played. Invader does away with most of Halo's arbitrary limits, even the 384 MiB cache file size limit (it's 4 GiB now!). ...was made for older PCs. As robust as Windows's backwards compatibility may be, even it has limitations, especially with Win32 GUI programs like Guerilla and Sapien. Invader runs natively on 64-bit x86-based PCs and takes advantage of modern hardware to boot. ...is slow. This is due to thousands of unnecessary checks as well as the program, itself, not being compiled with optimizations. Invader is considerably faster than tool.exe! ...only guarantees to work on Windows. Not everyone uses Windows, and Wine compatibility on Linux is, at best, a mixed bag especially in regards to the GUI-based applications Sapien and Guerilla. Invader natively runs on both Windows and Linux without having to worry about Wine. tl;dr: You can't guarantee the Halo Editing Kit will continue to work indefinitely, and it doesn't meet all of our needs anymore. Invader is here to fix that. I recommend reading this post for more information on why it is important that the Halo Editing Kit should be replaced: Site: https://invader.opencarnage.net/ Source code: https://github.com/SnowyMouse/invader Builds: https://invader.opencarnage.net/builds/nightly/download-latest.html Original version of this post (for posterity):
  10. Invader has received some more fixes and is 0.50.4 as of last month. Note, however, that the download location has changed. Due to some changes to Open Carnage since the recent DDoS attacks, I can no longer directly upload builds to https://invader.opencarnage.net for the time being, so it has been changed to a redirect to Invader's GitHub page, and going to anywhere on the subdomain besides the main index will result in a 404. From there, you can download builds from the releases page. For the latest news and discussion regarding Open Carnage, you can go to the Open Carnage Discord server at https://discord.opencarnage.net/ or go to the forum announcements at https://opencarnage.net/index.php?/forum/5-site-matters/
  11. I'm going to be moving again soon (my current residence was always supposed to be temporary!), so I am considering whether or not to hold off on building the PC. Things have been going slowly but surely though!
  12. Just got the CPU! I went with the Ryzen 9 5950X. Yes, I know better CPUs are coming out at the end of the year. Unless you expect me to wait with an iPad, you can probably imagine why I would do this so hastily. The IPC improvements do not really justify this wait, either. Yes, I know I could just hold out on a 8 core CPU. However, the 5950X actually does not cost that much more and I need the threads for code compilation and possibly virtualization anyway. I may as well get the best possible CPU now even if it will probably be obsolete in a few months. Yes, I know I could just buy Intel and have an upgrade path and probably better gaming performance, but I would have spent more money on a CPU/motherboard combo that has 25% fewer threads and half the "performance" cores, and considering I am starting with my RX 580, I think it is OK if gaming performance can take a backseat. I feel like I made the right call here.
  13. It wasn't a customs issue but an "I don't want my PC to be turned into a football by TSA or pay gazillions of dollars to ship it" issue. I kept the SSD in my wallet and kept the graphics card in a canvas bag and brought them on the plane with me. And frankly, I was looking to replace it anyway. Basically, my old setup involved me using two PCs: one with Linux (Ryzen 5 2600, 32 GB DDR4, RX 580) and one with Windows 10 (Intel Core i7-6700K, 16 GB DDR4, GTX 1070). I found that having only 6 cores and 32 GB of RAM was becoming pretty limiting for my needs, so I needed a core count and RAM upgrade pretty badly.
  14. Aaa, this is a good suggestion, but I actually need the threads for faster compile times, as it is essentially more files I can compile at once. Funny enough, encoding performance, while nice, is not a high priority. If it's good enough to render a high quality 10 minute 1080p 120 FPS video within a few hours while also encoding a decent quality 60 FPS 720p video in real time, I'm OK with that. Also, the 5800X3D has an MSRP of $449, which is not much less than the current prices of the 5950X (~$540 in my region), so the savings, while nice, are not something I can really use to much benefit. It is also currently sold out everywhere, meaning I'd have to pay a high scalper fee, making the 5950X cheaper right now. I do agree having higher cache would be great too, but because I do not currently have a PC, waiting is unfortunately not an option, as waiting means more time spent being completely unable to work on my projects.
  15. Arguably the root of all evil. Aaa yes. Canola oil is amazing. I use it in so much stuff!
  16. Invader received a bunch of improvements and updates including support for hud_message_text extraction AND compilation. Sadly I can't upload anything to Invader's server for a while due to my current living situation. You will need to get the latest build off of GitHub here for now: https://github.com/SnowyMouse/invader/releases/tag/0.50.2 The script compiler was fully rewritten in Rust, is more accurate than before, and is just easier to maintain. There are also a few other improvement here and there including support for CEA's new cache file building method which involves using the data folder.
  17. What a ride.
  18. While the Doppler isn't fully accurate to Xbox (or I guess real life as the plasma pistol seems to bend in pitch when you are holding it and moving despite the fact its relative velocity to you is 0), the issue I was pointing out had to do with the firing effect not playing in both channels when strafing. Basically, it sounds like the firing effect is coming from near you rather than from you.
  19. CE's audio is pretty borked now. Oh dear.
  20. I've updated Invader to 0.49.1. This is mainly bugfixes, but support for the newer definitions of the April 2022 update of the H1AEK has been added, too. Sadly, I had to change Invader's name back. Sorry if you liked HEK++.
  21. AAA thank you!!!
  22. Cool!!!
  23. As of today, Invader has been renamed to HEK Plus Plus (or HEK++ for short). People have complained that HEK++ (formerly Invader) is not as user friendly as Halo Custom Edition's HEK. So, I'm going to right this wrong and make the following changes in all future builds of HEK++. All error messages will be replaced with register dumps and assertions to source files you don't have access to. Which one will you get? Who knows! If there are any problematic tags that prevent a cache file from building, HEK++ will not print the paths of the problematic tags. Instead, you must use trial and error. This is way more fun! Most of the error checking will be removed in HEK++. This means you can now build maps with tags that would've otherwise been rejected by Invader. Maps that will probably crash the game. If a map crashes the game, it's even more trial and error. Map creation hasn't been this exciting since 2004! HEK++'s argument parsing system has been removed overhauled for most tools, thus you now only have to specify paths for everything. Gone are the days where you make bitmap tags by specifying the type of bitmap you want. Now HEK++ makes DXT1 bitmaps by default, and if you want to change it, you have to open the tag editor! All tools will later be bundled into one executable, HEKPlusPlus.exe. While this does mean you will no longer be able to tab complete, it at least means you will no longer be able to do tab completion. It's a win/win, honestly. As always, thank you for using and supporting HEK++. It's very much appreciated!
  24. Due to Halo's master server being down, I've added a new command: chimera_master_server. You can use the HaloNet master server with chimera_master_server "gamespy.halonet.net" or use chimera_master_server "" to restore to the default one. You can also configure the default master in the ini.
  25. This command-line tool dumps definitions from guerilla.exe into a parseable JSON format. You can use this on both the Halo: Custom Edition and Halo: CE Anniversary guerilla.exe. Note that fields nonexistent in guerilla.exe won't be exported, thus you won't get a totally complete definition set. However, it should be good enough to make your own Halo: CE editing tools. There are a two main uses for this tool: Making tools that edit Halo: CE tags Checking for differences between releases (since they are rarely documented, at least 100% adequately) I'll primarily be using this tool for working on Invader (this was why I made it!). You may use it freely for whatever you need, however. Also note that this tool is written in Rust (if you are interested in editing its source code). Source code (GNU GPL v3 - GitHub): https://github.com/SnowyMouse/gorilla Download (win32 - 64-bit x86): gorilla-win32-0.3.1.7z (Note: This tool will work on Linux, but you will need to compile it from source!)