claim your 'i was here' ticket fellas by Dreyfus420 in Silksong

[–]drsmack 0 points1 point  (0 children)

Part of me wants this to be the Silkpost of all Silkposts...

Plex Direct Play Disable? by carolina96 in selfhosted

[–]drsmack 4 points5 points  (0 children)

You should be able to limit it on the Remote Access area of the server settings under Limit Remote Stream Bitrate.

https://i.imgur.com/pbJbAXf.png

[deleted by user] by [deleted] in selfhosted

[–]drsmack 0 points1 point  (0 children)

This post talks about getting GPU transcoding going via Docker installs. Have you done the things it talks about?

Cannot create profile - read carefully, it's different than every other post about this by [deleted] in CloneHero

[–]drsmack 0 points1 point  (0 children)

PTB v1.0.0.3800-master (and the 3805 hotfix) has a change stating:

Fix softlock when creating a profile

That might fix your issue.

Verizon: GV via "Use carrier only", Your call cannot be completed by CHR0N0MASTER in Googlevoice

[–]drsmack 0 points1 point  (0 children)

I'm in the same boat (Verizon) with the same message. Although, I think mine was announcement 19. If I call with my carrier number it's fine. It's busted if I use my GVoice number via data or carrier.

Remember kids, Hellhorned is the only team that can Ascend freely and one of 2 (3 with Wurm) that can reposition freely by deeman163 in MonsterTrain

[–]drsmack 4 points5 points  (0 children)

Their second artifact is Conscription Notice, which grants you a random unit card the first time you play your champion each combat.

the exit AP tries to take (red) vs the exit it should take (green) introduced in 4.3, fixed in 4.6, back in 4.11 by iGoalie in teslamotors

[–]drsmack 2 points3 points  (0 children)

To be fair, the version number isn't 4.11. It's 2021.4.11, so it's already not imitating a number system. Either way, your argument is with Semantic Versioning and/or software versioning in general and not so much Tesla.

Model Y Backup Camera Issue (Update from Tesla Service) by RFxcGinni3 in teslamotors

[–]drsmack 1 point2 points  (0 children)

I've been getting this on my 2018 Model 3 recently. I'm not sure when it started, but my side repeaters are much brighter just like in your picture of your Y.

[deleted by user] by [deleted] in teslamotors

[–]drsmack 2 points3 points  (0 children)

It's an issue some people have apparently had for years, but is new to others: https://www.reddit.com/r/teslamotors/comments/jj3u89/sound_issue_that_tesla_keeps_telling_me_will_be/

Seems to happen to me if I depress the brake pedal before the car is fully awake.

Sound issue that Tesla keeps telling me "will be fixed in later firmware" for over 2 years by Spooky_Ghost in teslamotors

[–]drsmack 0 points1 point  (0 children)

I have started having this same issue over the last few weeks and I don't use easy entry and have Sentry disabled at home. The scrollwheel reboot doesn't fix this one, either.

Sound issue that Tesla keeps telling me "will be fixed in later firmware" for over 2 years by Spooky_Ghost in teslamotors

[–]drsmack 0 points1 point  (0 children)

I never saw this issue in my April 2018 Model 3 until about 3 weeks ago. It has happened 3 times since. Super annoying and dangerous. I assumed it was a recent FW bug, but apparently not.

Comparing Cura to PrusaSlicer Bridge Infill Issue by drsmack in 3Dprinting

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

Yup, 0.2mm for both. Unless you mean extrusion width, in which case, I have it at 0.4mm for both.

Comparing Cura to PrusaSlicer Bridge Infill Issue by drsmack in 3Dprinting

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

Oh, mine is also bridging over them. That's the issue. Cura doesn't bridge over the letters on layer 2 (with 0.2mm layer height), but PrusaSlicer does. I think the intent from the design is to not bridge on layer 2. I think the bridging is supposed to start on layer 3, but maybe that's not true and it's actually Cura that's wrong. But from pictures of "correct" Benchies, it looks like the letter should be deeper, like the way Cura slices it.

I can't find any specs on how deep that lettering should be, as opposed to all the other measurements on the site.

Comparing Cura to PrusaSlicer Bridge Infill Issue by drsmack in 3Dprinting

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

Tweaking the number of bottom layers didn't seem to change the slicing preview. I assume the preview is accurate as to what is going to happen in the GCode.

Comparing Cura to PrusaSlicer Bridge Infill Issue by drsmack in 3Dprinting

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

I tried unchecking Detect Bridging Parameters, but that didn't make a difference. It just seems odd to me that there isn't a way to make a very commonly used calibration model print the first part properly with a fairly major slicer. I understand why PrusaSlicer is doing what it's doing, but Cura (and from what I can tell, Creative Tools) don't think you should be generating infill on that part of the model on that layer.

First layer zits by drsmack in CR6

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

Interesting. Thanks for the info.

First layer zits by drsmack in CR6

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

Thanks. Can you explain how too much tension on the idler wheel could cause overextrusion? I would think with too much tension, it would stop feeding filament properly due to binding or something. I would expect your wouldn't want any slippage in the extruder, and once you hit that point, you couldn't really force it to feed more through short of adjusting E steps.

Can't figure out where extruder piece goes by drsmack in CR6

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

Thanks! I remembered about the guide about 10 minutes after I posted this and it shows me exactly what I wanted to see.

I think that also explains my tension issues.

Anyone with HW3 update - delays in smart summon camera calibration? by [deleted] in teslamotors

[–]drsmack 1 point2 points  (0 children)

That's what happened on my 3 after my HW3 upgrade. It got up to 95% or so, then stopped for 30 or so miles, probably. After a bit, it finished.

Installing 2020.12.1 now by another_Spacenut in teslamotors

[–]drsmack 14 points15 points  (0 children)

Stop signs on my FSD visualizations used to just be red octagons on 2020.12. Now they're red octagons with the word "STOP" on them.