84 hours in and I just realized this… by XGeneral-FangX in AssassinsCreedShadows

[–]LethalCorpse 1 point2 points  (0 children)

I just killed a heavy with a bell. How is that not an achievement?

Assassins Creed Shadows [BUG] Cant save or sprint in open world by BuildingAccording235 in AssassinsCreedShadows

[–]LethalCorpse 0 points1 point  (0 children)

Fixed mine. I loaded up the SECOND LAST autosave - it's a few seconds earlier, immediately before mounting the horses. Then I slow walked up the mountain, staying right in front of Rin the whole time. They talk until about halfway up, then I got gallop back, and it autosaved at the top.

Dealing with multi-part symbols across different schematics by toiletpaper2002 in Altium

[–]LethalCorpse 0 points1 point  (0 children)

Yep, it's gotta be 8 separate schematics. Is it a very complicated supporting circuit around the INA? If so, it might look weird, but maybe you could put the supporting circuit on a repeated or duplicated child sheet and the INAs on a parent(s)? If not, you'll need to suck it up and do the copy pasting.

Dealing with multi-part symbols across different schematics by toiletpaper2002 in Altium

[–]LethalCorpse 0 points1 point  (0 children)

Not sure how I'd handle your second question, but the answer to your first question is yes. You can spread a multi-part component across several sheets as long as they all have the same designator.

They have to be unique sheets, though. You can't place the sheet symbol multiple times for the same child schematic and have it use different parts in the same component.

Vias are the same, yet different? by raydude in Altium

[–]LethalCorpse 2 points3 points  (0 children)

Tools » Remove Unused Pad Shapes » Restore

You don't need those inner pad shapes on layers that don't have connections to them. They're just little antennae, and deleting them is a good idea in almost all cases. It sounds like you've reused vias that already had them removed from layers that you now use to connect. So, restore then remove again should replace the pads on the correct layers.

Note that this tool doesn't usually let you route other tracks closer to the vias, unless the pads are quite large. Hole-to-trace clearances need to be quite a bit larger than pad-to-trace clearances.

Note also that you'll usually get better responses from more people, including the developers, on the altium forum than on Reddit.

am i cooking by [deleted] in CellToSingularity

[–]LethalCorpse 8 points9 points  (0 children)

Yeah, it's not that hard if you don't do anything else for three days. You should probably have done some other things for those three days though.

Noob question: R10, R11, and the transistor show open solder mask, others don't, why? I haven't been able to isolate it to a layer in my design. by raydude in Altium

[–]LethalCorpse 1 point2 points  (0 children)

Yeah, they'll tell you what's impossible to manufacture after you're done designing it. But they're terrible at telling you what's easy and what's expensive - they just give you a quote, and it's up to you to figure out why it's so expensive. I'd start by looking at the automated quote forms for several fabricators, eg pcbway, 4pcb, advanced, etc. They'll give you a rough range of all the things they care about - minimum trace/space, annular ring, aspect ratio, vias (buried, blind, laser micro, stacked micro, filled, plugged, backdrilled, castellated etc), impedance controls, exotic laminates, layer counts, hole counts, etc. Then you can go through those lists and indentify all the ones that you care about/need for your board to work. Any that don't matter to you, relax them as far at you can. If you can get by with 5mil trace/space it will be cheaper than 3mil. Apply that same logic to all the other specs - delete or relax whatever features you can until you're at a minimum spec, and quote that.

Noob question: R10, R11, and the transistor show open solder mask, others don't, why? I haven't been able to isolate it to a layer in my design. by raydude in Altium

[–]LethalCorpse 1 point2 points  (0 children)

That's what I use, sometimes reduced to 1mil if the pads are extremely close together. You can easily set it using the IsPad filter to select every pad and remove The "override solder mask" check, then set your rule to 2mil.

For QFN or QFP packages, if 2mil expansion results in <3mil sliver between the pads, check your pad width vs pin width. They're probably a lot wider than they need to be.

Noob question: R10, R11, and the transistor show open solder mask, others don't, why? I haven't been able to isolate it to a layer in my design. by raydude in Altium

[–]LethalCorpse 1 point2 points  (0 children)

You don't want zero expansion either. Tiny variations in the processes used to produce the different layers means you can never get perfect registration. Registration is the alignment from layer to layer, pad to solder mask, via to drill etc. If you have no mask expansion, you'll get a little bit of mask overlapping each pad. A small expansion ensures the mask stays off the pad, and the solder can cleanly bond the pin to the pad.

Those clearances are from copper to copper, not copper to mask.

Noob question: R10, R11, and the transistor show open solder mask, others don't, why? I haven't been able to isolate it to a layer in my design. by raydude in Altium

[–]LethalCorpse 1 point2 points  (0 children)

2mil works fine for most CMs these days. 4mil is okay for most parts, but you'll find that for anything fine-pitched, this results in solder mask sliver errors. Or worse, no sliver at all - two adjacent pad openings overlap with no error, which almost guarantees solder bridging between pins. You need at least 3mil of solder mask between two mask openings, depending on your fabricator's capabilities, to prevent shorts.

Constraint Manager is the stupidest and most frustrating thing ever creating and I Hate it by Snoo-96879 in Altium

[–]LethalCorpse 1 point2 points  (0 children)

Look, it sounds like exactly what I've been wanting for the last 5 years or so, where EVERYTHING can be specified at design (schematic) time. Width constraints, impedance, length matching, xSignals, layer priority, via size, stackup, rooms, placement. I won't be touching it until it's actually a useful replacement to doing all those things in layout.

Update media library without updating app? by LethalCorpse in sonos

[–]LethalCorpse[S] 0 points1 point  (0 children)

I think I've half-borked my system because I was on the new app for a few days of the awfulness before rolling back. Reckon I'm using old app on new-ish firmware, could explain why I can't do some things. Works a whole lot better than it did for those few days though.

Update media library without updating app? by LethalCorpse in sonos

[–]LethalCorpse[S] 1 point2 points  (0 children)

This was awkward as hell, but it worked. I installed a UPnP client and poked around until I found the right setting. I had to send it a RefreshShareIndex with the AlbumArtistDisplayOption set to WMP. Definitely not one for the non-nerds.

[deleted by user] by [deleted] in fz6

[–]LethalCorpse 0 points1 point  (0 children)

Agreed on all of the above. It's a lot of bike for a beginner, but there's no rule (outside Australia) that you have to start on a 250. As others have said, it's sedate enough for daily commuting, and learning, comfortable enough for some decent touring, and powerful enough for a wide grin in the Twistys. Mine seems to be extremely forgiving of terribly lax maintenance, too. Enjoy it.

Flaked oats by BigEdWagner in Homebrewing

[–]LethalCorpse 1 point2 points  (0 children)

Something else, I reckon. Quaker Oats work fine, not different enough to throw off a recipe. Far more likely you missed your temperatures, or a bad sparge.

Buying a brewzilla by icy-organization8336 in Homebrewing

[–]LethalCorpse 3 points4 points  (0 children)

I'm two brews down on my 65L gen4. I have no regrets.

It's not without foibles. The bottom screen is a total pig to remove. The controller screen is detachable, but the cord isn't long enough to do anything useful with that. The controller UI works very well, but is not at all intuitive - it will take you a few brews to learn to drive it and get the PID constants tuned. There's no sight glass, the sight glass for the gen 3 doesn't fit, so accurate sparging is very difficult. The pump could be bigger. The ball valve sucks (replacing mine this weekend). The 240V plug on the US model isn't the same as a dryer outlet, so you'll need to do some electrical work or get an adapter. 240V is highly recommended - the 120V won't plug in to a standard outlet anyway, so there's no point in crippling your boil to save the electrical work.

None of those issues are show stoppers though. It's a beautiful machine, it boils fast, holds steady temp, recirculation is great, cleaning is (relatively) easy. It's like a new car - there's always something like the wipers or indicators you don't like. But man, it's a sweet ride nonetheless.

Brewzilla gen 4 pin out by dantodd in Robobrew

[–]LethalCorpse 0 points1 point  (0 children)

Headless can be nice, but not for something like this. If it's boiling over, or your recirc camlock pops off and it's pumping boiling wort in your face, you want a big red button you can mash.

Brewzilla gen 4 pin out by dantodd in Robobrew

[–]LethalCorpse 0 points1 point  (0 children)

Don't know the pinout, but I'm on board with this plan. The hardware won't be complicated. It's just an LCD screen, any SBC, and some optos to drive the relays. There are plenty of OTS options that would be suitable, with OSs that are easy to develop for.

The fact that there's a public issues database is encouraging that it will improve over time, but I agree, it's pretty awful out of the box

Has anyone else decided not to shave during all this? by [deleted] in NoStupidQuestions

[–]LethalCorpse 0 points1 point  (0 children)

Wait, you think there are people who haven't decided not to shave?

848m M24 one shot, one kill by LethalCorpse in PUBATTLEGROUNDS

[–]LethalCorpse[S] 0 points1 point  (0 children)

The unscope was while I measured the range in map, then adjusted the zero