| 00:07.50 | blast007 | allejo: were the changes to the .svg files in your metadata removal commit intended? |
| 00:15.37 | allejo | oof did notice I had touched vendor files in that commit |
| 00:15.40 | allejo | didn't* |
| 00:16.50 | allejo | I just did a pass of all the assets to optimize the images. we can undo that in the vendor files |
| 00:29.24 | blast007 | mainly thing was that it nuked the plyr.svg file, so whatever you ran takes exception with that file :) |
| 00:29.27 | blast007 | main* |
| 00:30.43 | blast007 | do we still need the .gitattributes file if we're not using Git LFS now? |
| 00:31.27 | blast007 | we could put any large source art in that B2 bucket |
| 01:41.25 | allejo | Iâll revert the changes in those SVGs in a bit |
| 01:42.35 | allejo | and I donât think we need the gitattributes file so long as editorconfig is respected for line endings |
| 01:49.19 | *** join/#bzflag MatrixBridge (matrixirc@gateway/shell/matrix.org/x-yetukyorawrjmcjt) |
| 01:49.21 | *** part/#bzflag MatrixBridge (matrixirc@gateway/shell/matrix.org/x-yetukyorawrjmcjt) |
| 01:49.55 | *** mode/#bzflag [+o blast007] by ChanServ |
| 01:50.15 | *** join/#bzflag MatrixBridge (matrixirc@gateway/shell/matrix.org/x-yetukyorawrjmcjt) |
| 01:50.17 | *** part/#bzflag MatrixBridge (matrixirc@gateway/shell/matrix.org/x-yetukyorawrjmcjt) |
| 01:55.47 | *** join/#bzflag MatrixBridge (matrixirc@gateway/shell/matrix.org/x-yetukyorawrjmcjt) |
| 01:55.50 | *** part/#bzflag MatrixBridge (matrixirc@gateway/shell/matrix.org/x-yetukyorawrjmcjt) |
| 01:55.56 | *** join/#bzflag MatrixBridge (matrixirc@gateway/shell/matrix.org/x-yetukyorawrjmcjt) |
| 01:55.58 | *** part/#bzflag MatrixBridge (matrixirc@gateway/shell/matrix.org/x-yetukyorawrjmcjt) |
| 02:10.28 | *** join/#bzflag MatrixBridge (matrixirc@gateway/shell/matrix.org/x-yetukyorawrjmcjt) |
| 02:10.30 | *** part/#bzflag MatrixBridge (matrixirc@gateway/shell/matrix.org/x-yetukyorawrjmcjt) |
| 02:10.37 | *** join/#bzflag MatrixBridge (matrixirc@gateway/shell/matrix.org/x-yetukyorawrjmcjt) |
| 02:10.40 | *** part/#bzflag MatrixBridge (matrixirc@gateway/shell/matrix.org/x-yetukyorawrjmcjt) |
| 02:11.07 | *** join/#bzflag blast007[m] (blast007ma@gateway/shell/matrix.org/x-rinbqkbzjhjgyrxo) |
| 02:12.21 | blast007[m] | test 1 |
| 02:12.27 | blast007 | test 2 |
| 02:13.16 | allejo | test 3 |
| 02:14.07 | blast007 | got a Matrix room set up and bridged to here |
| 02:14.13 | *** mode/#bzflag [-o blast007] by blast007 |
| 02:16.21 | allejo | what's matrix? |
| 02:18.01 | blast007 | https://matrix.org/docs/guides/faq |
| 02:18.44 | blast007 | dunno if it's specific to the Riot client, but at least that one looks similar to Discord |
| 02:23.35 | Zehra | thinks Matrix will be good |
| 02:24.38 | Zehra | Minor question, which is the last player slot number available/open to players? |
| 02:25.04 | blast007 | probably 199, since we allow 200 players and it starts at 0 |
| 02:25.42 | Zehra | blast007: Thanks, much appreciated. |
| 02:26.12 | allejo | last valid player ID is 240-ish |
| 02:26.43 | blast007 | isn't that for replay servers? |
| 02:27.04 | blast007 | thinking that replay servers start the viewers of a replay at 200 |
| 02:27.28 | allejo | https://github.com/BZFlag-Dev/bzflag/blob/2.4/include/bzfsAPI.h#L444 |
| 02:27.48 | allejo | not sure, replay servers max at 16 obs so that'd be 200-216? |
| 02:31.07 | blast007 | MaxPlayers is set to 200, replay server uses that as the initial loop value when sending updates |
| 02:31.21 | blast007 | (to spectators of the replay) |
| 02:31.46 | allejo | ah |
| 02:31.52 | blast007 | during a normal game, IDs will be from 0 to 199 (inclusive) |
| 02:35.29 | blast007 | https://github.com/BZFlag-Dev/bzflag/blob/2.4/src/bzfs/bzfs.cxx#L1349-L1369 |
| 02:35.50 | *** join/#bzflag BZnotify (BZnotify@gateway/service/github.com/x-xuywhisvigvoqgjj) |
| 02:35.51 | BZnotify | [13bzflag.org] 15allejo pushed 1 new commit to 06redesign: 02https://git.io/fh6Zf |
| 02:35.51 | BZnotify | 13bzflag.org/06redesign 14c188839 15Vladimir Jimenez: Partially revert f5fe4cd to fix accidental SVG mods |
| 02:35.51 | *** part/#bzflag BZnotify (BZnotify@gateway/service/github.com/x-xuywhisvigvoqgjj) |
| 02:37.46 | allejo | ohhh that's good to know |
| 02:38.18 | allejo | i wonder if the last 216-243 slots are used anywhere |
| 02:39.37 | blast007 | not that I'm aware |
| 02:40.37 | blast007 | not really sure why BZ_LASTREALPLAYER exists or is set to 243 |
| 02:43.45 | allejo | shrugs |
| 02:46.13 | *** join/#bzflag BZnotify (BZnotify@gateway/service/github.com/x-kwrxqmmghfjrtczk) |
| 02:46.13 | BZnotify | [13bzflag.org] 15allejo pushed 1 new commit to 06redesign: 02https://git.io/fh6Zc |
| 02:46.13 | BZnotify | 13bzflag.org/06redesign 143dbc564 15Vladimir Jimenez: Remove LFS and PSD handling |
| 02:46.13 | *** part/#bzflag BZnotify (BZnotify@gateway/service/github.com/x-kwrxqmmghfjrtczk) |
| 02:49.54 | allejo | blast, how do you feel about the oxford comma? |
| 02:50.04 | allejo | regarding its use in our docs |
| 03:07.42 | blast007 | I tend to use a comma before the and or or |
| 03:16.13 | allejo | good man |
| 07:32.07 | *** join/#bzflag I_Died_Once (~I_Died_On@unaffiliated/idiedonce/x-1828535) |
| 08:52.26 | *** join/#bzflag I_Died_Once (~I_Died_On@unaffiliated/idiedonce/x-1828535) |
| 09:10.14 | *** join/#bzflag I_Died_Once (~I_Died_On@unaffiliated/idiedonce/x-1828535) |
| 13:27.57 | *** mode/#bzflag [+o blast007] by ChanServ |
| 13:29.11 | *** topic/#bzflag by blast007 -> https://BZFlag.org || https://www.openhub.net/p/bzflag || https://bzflag.org/help || Channel Logs: http://infobot.rikers.org/%23bzflag/ || 2.4.18 released! https://forums.bzflag.org/viewtopic.php?f=62&t=20030 |
| 13:35.26 | *** mode/#bzflag [-o blast007] by blast007 |
| 14:35.30 | *** join/#bzflag I_Died_Once (~I_Died_On@unaffiliated/idiedonce/x-1828535) |
| 16:26.03 | *** join/#bzflag Delusional (~Delusiona@unaffiliated/delusional) |
| 17:48.29 | *** join/#bzflag Delusional (~Delusiona@unaffiliated/delusional) |
| 18:16.07 | *** part/#bzflag BulletCatcher (~bc@bzflag/developer/BulletCatcher) |
| 18:58.27 | *** join/#bzflag BulletCatcher (~bc@bzflag/developer/BulletCatcher) |
| 18:58.28 | *** mode/#bzflag [+v BulletCatcher] by ChanServ |
| 23:03.20 | *** join/#bzflag Delusional (~Delusiona@unaffiliated/delusional) |
| 23:09.55 | kierra | allejo, Community event on T-roy server was a huge success. Thank you so much for the use of your server. |
| 23:10.06 | kierra | ~allejo++ |
| 23:14.46 | allejo | glad to hear :D |
| 23:29.40 | *** join/#bzflag Delusional (~Delusiona@unaffiliated/delusional) |
| 23:33.42 | spldart | If I may OT for a bit. After finding out just how 'SERIOUSLY' fast an ssd can speed up a desktop last year I was wondering if there are optimum SSDs to look out for. I wanna go ahead and get deb testing installed in a month or so and thoght a new ssd would be a nice safe way to do so. Currently running a SP slim S55 SSD 60 gig Sata III 3d TlC. New drive can be very small too (OS only) Gonna need to get a new slow but huge storage conventional |
| 23:33.42 | spldart | drive as well. |
| 23:34.51 | spldart | IB wrong channel exclamations. |
| 23:35.44 | blast007 | does your motherboard have an M.2 NVMe slot? |
| 23:36.08 | spldart | prolly not but I'm logged in to newegg so I'll check. |
| 23:36.14 | spldart | It's old new tech. |
| 23:36.33 | blast007 | (though are a somewhat newish thing, think it's Intel 7 series chipsets and higher, dunno for AMD) |
| 23:36.41 | blast007 | those are* |
| 23:37.08 | blast007 | NVMe can be crazy fast |
| 23:38.45 | blast007 | with SATA, you're limited to around 500MB/sec, but NVMe can hit more like 1500 to 2100 MB/sec |
| 23:38.46 | spldart | well crap. Newegg site is not working correctly right now so I can't pull up the Mobo I bought last year. |
| 23:39.16 | blast007 | in any case, check this site out: https://ssd.userbenchmark.com/ |
| 23:39.40 | spldart | However... I bought the mobo so I could mix old and new tech to get a pc together cheap last year as I was in the middle of getting my cruiser... Oh thank! I'll check out the link |
| 23:41.12 | blast007 | also, keep in mind that there are a variety of different, eh, types? of SSD media. or maybe how they use it. dunno the right term. there's some SSDs that will perform fast until you hit a specific amount of writes in a period of time (as they have a chunk of the media set up as SLC cache) |
| 23:41.48 | blast007 | and once you hit that limit, performance drops quite a bit, until the drive catches up and moves that data from the cache to the final destination |
| 23:42.07 | spldart | I have some serious studying to do :/ |
| 23:42.20 | blast007 | some of the cheaper drives also lack onboard DRAM |
| 23:42.35 | blast007 | and some NVMe drives are also only 2 PCIe lanes instead of 4 |
| 23:42.59 | blast007 | (and some mobos will only run your NVMe slot at x2 depending on what cards and other stuff you have attached) |
| 23:43.19 | blast007 | and some mobos may also drop another slot to a lower speed if you populate an NVMe card |
| 23:43.23 | spldart | Holy crap o_O |
| 23:44.43 | blast007 | most of what I said is irrelevant if you're just going with a SATA SSD, which is still far faster than a conventional hard drive |
| 23:45.00 | spldart | understood |
| 23:45.48 | blast007 | we've got some Western Digital Blue SSDs at work and they've been pretty solid so far |
| 23:46.27 | spldart | WD = reliable. gotcha :) thanks |
| 23:46.44 | blast007 | I mostly use Samsung at home |
| 23:47.25 | spldart | also reliable I assume? |
| 23:47.36 | blast007 | got an NVMe boot drive in my gaming PC along with another (non-Samsung) NVMe as a data drive, then a SATA SSD in my Thinkpad X200 |
| 23:47.50 | blast007 | yeah, Samsung is one of the top SSD manufacturers |
| 23:48.51 | spldart | excellent :) This will be usefull :D |
| 23:49.19 | blast007 | a suggestion for SSDs: leave a portion of the drive (say, 10%) unprovisioned (so size your partitions so that space is unallocated) so that the disk can use it for wear leveling |
| 23:51.23 | spldart | This is the first I have ever heard of 'wear leveling' I will google. Thanks :) |
| 23:52.09 | blast007 | flash cells have limited cycles, so the flash controller on the disk will attempt to distribute writes across the cells so it doesn't wear out individual cells |
| 23:52.11 | spldart | Fraid I didn't leave any unallocated space on this or my other machines SSD |
| 23:52.44 | blast007 | I believe that leaving some free space has the same effect, though perhaps only if TRIM is enabled |
| 23:52.55 | spldart | So the controller is smart enough to utilize unallocated space for this? |
| 23:52.56 | blast007 | SSDs don't like being filled to capacity |
| 23:52.58 | spldart | Wow! |
| 23:53.12 | spldart | That I do avoid. |
| 23:53.17 | spldart | I never fill my SSDs |
| 23:53.58 | blast007 | if I understand correctly, TRIM is where the OS tells the SSD what areas of a partition do not contain any data so that the SSD controller can wipe the cells (and use it for wear leveling) |
| 23:54.45 | blast007 | the flash controller also does stuff like determinging if a cell is failing and moving that data to another region |
| 23:55.47 | spldart | crap! No my brother is telling me how dumb I am. he says you set noatime in the fstab to save writes |
| 23:56.14 | blast007 | with modern SSDs, they aren't just storing a 1 or a 0 in a cell. it's storing a variable charge so you can pack more than 1-bit per cell. as cells age, they start to lose the ability to hold a charge, so the flash controller compensates for that until it can't any longer. |
| 23:56.14 | spldart | turn swap off ( I did this one ) |
| 23:56.45 | blast007 | I turn swap off only if I have more than enough RAM |
| 23:56.59 | blast007 | though depending on the setup, you might need swap if you intend to hibernate your system |
| 23:57.16 | spldart | trim running once a week he says... I'll hafta google that too. |
| 23:57.30 | spldart | I've been swap off for a long time no problem. |
| 23:57.35 | blast007 | k |
| 23:57.52 | blast007 | I tend to have more than enough RAM on my systems :) |
| 23:57.52 | spldart | My god i have a lot to learn |
| 23:58.10 | spldart | I'll be expanding my ram soon. |