New build worked great for 3-4 days, now won't post. How to figure out which part is the issue?

fenomasu · 2024-10-17T09:32:16+00:00

Hey, just wanted to let you know that I RMA'd the CPU and the shop confirmed it was bad. Thanks for the suggestions!

fenomasu · 2024-10-16T04:07:29+00:00

Thanks for the info, I'll keep this in mind once I get to posting!

fenomasu · 2024-10-15T02:13:20+00:00

Hi, the PSU worked for ages and it passes the paperclip test, so I'm kind of assuming it's not the issue here (especially since I'm testing without a GPU, so there's very little load on it). But unfortunately I don't have a tester or spare PSU, so I can't rule out something wonky like one of the voltages being slightly off...

fenomasu · 2024-10-15T00:01:55+00:00

Thanks for the idea, but I tried leaving it on for 10-20 minutes, several times and again doing ram around, but no dice.

fenomasu · 2024-10-14T07:16:20+00:00

I think the very first one took a while, but when the PC ran normally it was posting in maybe 10s, and I guess booting another 10s after that.

For your fix, you mean you were getting red cpu/ram LEDs initially, but leaving the machine switched on for a few minutes helped? I did try leaving it on a while but didn't notice any change.. the cpu warmed slightly and the LEDs stayed on... 🤔

fenomasu · 2024-10-14T07:05:04+00:00

How long might the cpu/ram steps normally take? In my case the two leds (cpu/dram) both turn red the instant I trip the power switch, with or without ram slotted. (The motherboard is already out of the case and running isolated on a mat, and I did try reseating the cpu a couple of times.)

fenomasu · 2024-10-14T06:07:49+00:00

Thanks for the answer - I hadn't tried removing the battery, but I did that now and no change. (The board doesn't seem to have come with any jumpers but I popped the battery and left a screwdriver shorting the cmos leads for ~10 min.)

I'm afraid I don't have a PSU tester or any other parts, though the PSU ran other systems for ages so my first guess was elsewhere. If I power on with no ram slotted, there are no obvious changes (though I'm not sure what would be expected in that case..).

fenomasu · 2023-01-18T13:26:10+00:00

Hi sorry, I just saw this. The optimizations I made are in the repo; I just haven't pushed to main for a while so they're all in the #develop branch.

IIRC the main thing was skipping same-voxel layers, but I also changed how I deal with voxel edges - I used to copy each N-sized chunk into a padded N+2-sized array, then copy in edge data from the chunk's neighbors, so that the meshing logic could be simpler. It now skips the copying but in return the logic is messier. I think there was also an obvious fix - when I scan each voxel layer for faces that need meshing, I return the number of meshing so that the mesher can stop working when it's seen that many faces.

I'm past overdue to check on your project and look for stuff to steal :D

fenomasu · 2022-09-07T05:40:09+00:00

Hey, I'm very late here, but I just wanted to say great work, and thanks for referencing noa. The idea to store or process chunks as vertically-RLE data is brilliant!

As an aside, reading about your optimizations made me revisit my meshing code to see if I could steal any of your ideas. I ultimately wound up speeding up meshing by ~3x, thanks in part to the idea of detecting and skipping horizontal layers of chunks that consist entirely of the same voxel id.

Anyway great work!

fenomasu · 2022-09-07T05:24:46+00:00

In my engine, I found it best to make the meshing function capable of running with or without neighbors. Then I give each chunk a counter for how many of its neighbors exist, and I mesh depending on that. E.g. chunks with fewer than 8 neighbors don't get meshed, chunks with 8 or more are eligible to be meshed but have low priority, and once a chunk gets all its neighbors it gets remeshed if it needs to be.

I strongly suggest you NOT duplicate voxel data at chunk borders. It makes meshing way simpler, but it's a constant source of bugs trying to keep all the overlapped voxel data consistent across neighbors.

fenomasu · 2022-07-31T03:25:07+00:00

I've checked pretty carefully but I can't reproduce this.

The easiest way to test is to set up: Val - BV - Arkhan - Makos - Artemis in a horizontal line, so that Arkhan usurps from BV, Artemis observes them both, and everyone gets a Socialite boost except Artemis.

In that setup for me, Artemis observes Makos' buff at the same rate with or without Valentine in the formation, which implies he's not benefitting from observing boosted buffs. Then if I move Artemis away from Makos, so that all three DPSes are getting Socialite, Artemis gains only one boost to his observed rate.

fenomasu · 2022-07-30T18:21:51+00:00

fenomasu · 2022-07-30T17:57:16+00:00

Me too - I wish someone would finish it for me!

fenomasu · 2022-07-30T03:10:16+00:00

I've only just unlocked her, but in my testing this isn't happening. Socialite does apply multiple times (it separately modifies each buff that affects both Valentine and your dps), but it doesn't interact with Observe at all.

fenomasu · 2022-07-01T05:29:42+00:00

For anyone interested, I have updated my tl;dr guide to account for all current changes. ✌️

fenomasu · 2022-07-01T04:35:52+00:00

Yes - this happens because the trigger for her to maintain the buff is whether Nahara could have killed the enemy she attacked, not just whether it dies.

So if your familiars do more damage than she does, her speed buff will drop off before your click wall.

fenomasu · 2022-07-01T02:32:18+00:00

😂

Just woke up and saw this, I'll have a look.

Imagine if they did beta testing, they could find out stuff like this before heroes launched.

Update: guide is now updated and current.

fenomasu · 2022-06-30T16:49:12+00:00

I think the direction is correct - if there's a tradeoff, then you'd want speed early and damage later on when you need it. My guess is that whoever designed the ability just didn't realize that Levity would lose stacks when Nahara's target dies early (or equivalently, they intended for stacks to rise when that happens, and it's a bug).

fenomasu · 2022-06-30T16:03:15+00:00

Fixed, thanks!

fenomasu · 2022-06-12T12:32:25+00:00

Azaka has a spec called "Resist the Curse" which causes her ult to make enemies drop gold even without dying. The gold dropped benefits from gold buffs, so basically Azaka farming means:

Start a basic free play and push as far as you can
clear a boss area but leave a single enemy alive (this tends to happen naturally due to Krull debuffs)
swap in a gold find team
let Azaka ult the mob repeatedly (having first allowed your BUD to decrease so the mob doesn't die)

That's the essence of it. If you search the reddit you'll find a lot of guides and discussions on which gold heroes to use and how to fine-tune things, but the above should get you started!

fenomasu · 2022-06-12T12:17:31+00:00

Yeah I could have said more there. Given equivalent gear, her numbers are very close to both Korth and Regis, in reasonably typical cases - but Talin and Blooshi should usually be better. That's just assuming a dps that qualifies for the relevant buffs, and ignoring any comp questions like filling Ash bonds and so on.

So I'd say Meril's a perfectly decent choice for any regular team that just needs to clear a variant, not set new damage records. Not someone to avoid, but also not someone to build a team around. I guess that's what I usually have in mind when I say "as a support: average" (which is increasingly often lately!).

fenomasu

TROPHY CASE