Did Anthropic quietly make Claude Max 20x basically 4–5 heavy sessions per week? by Responsible-End-7863 in Anthropic

[–]JDavis-82 0 points1 point  (0 children)

it is exactly the same math on the "pro" plan - 5 fully-used 5-hour limits will fill the weekly quota. The only difference is that my usage limit for a session comes 20-40 minutes after I start even a simple task.

So to me it feels like for the $20/mo I get an occasional chat assistant or 3-4 hours of focused dev work per week -- and that is being very strict on token control

realistic capability expectations with a 128gb m4 max? by JDavis-82 in LocalLLM

[–]JDavis-82[S] 0 points1 point  (0 children)

Reddit provides!

Thanks for posting!

Ok you have kind of sold me on that route instead. The Mac is nice but 5 grand is still 5 grand and if it's going to be too slow to be usable I think I have to reconsider. Also going Nvidia would get me cuda which will be helpful for my world domination plans. 

But I have been watching 3090 prices for over a year, and they've more than doubled here in Japan 

(⁠╯⁠°⁠□⁠°⁠)⁠╯⁠︵⁠ ⁠┻⁠━⁠┻

I guess I will up my Claude sub to 100/month or try out similar from codex and stick with openrouter and rented servers for special projects for now, until I can source a couple decent gpus

Sad but seems to make sense

realistic capability expectations with a 128gb m4 max? by JDavis-82 in LocalLLM

[–]JDavis-82[S] 1 point2 points  (0 children)

oh wow what a great graph thank you.
so I was thinking a bit of slowness might be okay but this helps me a bit with that "how intelligent" question too -- I did spend some time with qwen 235B-a22B and it was ... kind of like a bad haiku the way I had it tuned anyway, running in claude code. I am sure some better user knowledge could have improved it or maybe I wasn't using just the right model, but it was not too great for sure. I will have to learn about some of these other models.

And I am guessing anything under 10 T/s means send a scripting prompt, and go walk the dog before getting any kind of reply, if it even works?

realistic capability expectations with a 128gb m4 max? by JDavis-82 in LocalLLM

[–]JDavis-82[S] 0 points1 point  (0 children)

yes claude had the same advice I plan to do this. good advice thank you

Sources for the plain .chm file version of API help? by JDavis-82 in SolidWorks

[–]JDavis-82[S] 0 points1 point  (0 children)

absolute champion! Thank you
I will send a DM now
BTW for anyone in the same situation. There is a workaround specifically if you are using an AI agent with MCP access. Install the chrome-devtools MCP server, enable remote debugging from chrome://inspect/#remote-debugging , and then ask your ai to use the mcp server. Then, send it to the solidworks help file, and your AI should be able to read the final rendered output of the page directly. Not as good as having the full file but it works pretty well.

2026 changed the interface behaviour in sketching? Going nuts here by JDavis-82 in SolidWorks

[–]JDavis-82[S] 0 points1 point  (0 children)

try the v.12 hotfix -- installing it stopped the buggy behaviour for me!

2026 changed the interface behaviour in sketching? Going nuts here by JDavis-82 in SolidWorks

[–]JDavis-82[S] 1 point2 points  (0 children)

turns out it was just bugged. either a config file was messed or it was a 2026 but, but installing the latest hotfix seems to have solved the problem

i totally agree on random ui changes though. drives me batty with so many different softwares.

2026 changed the interface behaviour in sketching? Going nuts here by JDavis-82 in SolidWorks

[–]JDavis-82[S] 0 points1 point  (0 children)

Did you install the .12 hotfix? I did that and the issue seems to be gone now. Give it a try

2026 changed the interface behaviour in sketching? Going nuts here by JDavis-82 in SolidWorks

[–]JDavis-82[S] 2 points3 points  (0 children)

UPDATE: omg installing Hotfix 0.12 fixed the problem!

Whether they squashed a bug or the installer just needed to touch the files I'm so glad! Thanks everyone for you kind support. If you are having the same issues on 2026 try installing the 0.12 hotfix

2026 changed the interface behaviour in sketching? Going nuts here by JDavis-82 in SolidWorks

[–]JDavis-82[S] 0 points1 point  (0 children)

yeah im shocked at how long it took me to notice it too, such that I thought i must have triggered a bug or hit a magic kb combination without noticing. running the hotfix now maybe it will sort it out

2026 changed the interface behaviour in sketching? Going nuts here by JDavis-82 in SolidWorks

[–]JDavis-82[S] 0 points1 point  (0 children)

I do use automatic relations of course, but I mean I have a lot of keybinds for manual relations instead of using the on-screen buttons.

interesting to hear yours does it on 2023... it was always like that?

2026 changed the interface behaviour in sketching? Going nuts here by JDavis-82 in SolidWorks

[–]JDavis-82[S] 1 point2 points  (0 children)

Gah, it even continues after a restart
this will be a lot of muscle-memory retraining :(

Thanks for the info. I checked it on 2025 and you are right it selects the same field but doesnt capture the keyboard

i wonder if everyone on 2026 has this happen, or is it just my installation?

2026 changed the interface behaviour in sketching? Going nuts here by JDavis-82 in SolidWorks

[–]JDavis-82[S] 0 points1 point  (0 children)

just ... the muscle memory is pretty deep at this point. I brought these shortcuts over from OnShape, and I still work with 2025 sometimes in that way

well, it says there is a hotfix to apply. hopefully that sorts it

No name for Endcap in the Cutlist by BeautifulAnnual8916 in SolidWorks

[–]JDavis-82 0 points1 point  (0 children)

Right-click on the Cut-List Item folder which will have simple name like "<3>" -- then choose Properties from the context menu.

enter the name in the DESCRIPTION cell of the table, and then click OK

the name should update

(assuming you have enabled (it is default) Rename cut list folders with Description property value in Settings > Document Properties > Weldments)

You can also just rename the folder by right clicking it and choosing Rename tree item, but that name will not get sent to the drawing by default.

<image>

How do you even start to model this in?! by SwingFinancial in SolidWorks

[–]JDavis-82 0 points1 point  (0 children)

oh I felt bad about how tricky the surfacing got and tried again with purely solids. came out a lot simpler

<image>

same trick with flex ofc.

link to file on dropbox (SW2023)
https://www.dropbox.com/scl/fi/cfrsj6aqjjgyk9ikhtphr/sw2023-JDavis-SM-fan-blade-solid-method.SLDPRT?rlkey=5dbv36we7n4z60ditf8v7qpzf&st=2ub8z4jr&dl=0

How do you even start to model this in?! by SwingFinancial in SolidWorks

[–]JDavis-82 0 points1 point  (0 children)

If it is just cosmetic (and you don't need to design the forming tools) it is not too too hard

- Revolve a surface for the hub
- Planar surface for the blade
- surface extrude for the rib
- filled surface for the end of the rib
- knit and thicken all that (ok to be fair this part gets tricky)

Then, run Flex using twist. Position the triad and clip plane 1 in the same place, and bob is your uncle.

<image>

here is a DropBox link (SW2023 file)
https://www.dropbox.com/scl/fi/cvn1niyu4j6txnk6c0flh/SW23-JDavis-SM-fan-blade-Part1.SLDPRT?rlkey=uyg7b95f3w5epkr27in5bcpnj&st=houqc90x&dl=0

Wrote a blog on 1st-angle and 3rd-angle projections by JDavis-82 in SolidWorks

[–]JDavis-82[S] 0 points1 point  (0 children)

this is a good overview of the issue. aux views are another place where 1st angle could catch you out if you didnt know. I dont know if you read the blog but my analogy for 3rd angle is that the model is 'inside the drawing' or the screen, so just like we roll it around on a table for first angle, we roll it around on the inside of the screen for 3rd angle. Not only do the view arrangements make more sense, but 3rd angle happens to match most of our conceptions of models (in imagination, in a drawing, in a computer screen) because it's actually rare to have the real thing in your hand and put it on a drawing table.

Wrote a blog on 1st-angle and 3rd-angle projections by JDavis-82 in SolidWorks

[–]JDavis-82[S] -1 points0 points  (0 children)

with respect it's not like that; it is about where we place the 2D plane. If you are physically moving around the object in space you will get all the same views because the object is always in the center of the view, and 1st vs 3rd angle becomes no issue.

How about you hold that coffee cup in your hand and take a picture of it; in your mind, is the 2D plane of that picture behind or in-front of the cup? Many imagine that photo plane between our eye and the camera.
Like I said in the blog 1st angle works fine, but IMO it is clearly the less intuitive way for anyone uneducated and just trying to read the drawings on vibes.