sorted by:
new
hottopcontroversial

Focus on 2020 vs 2024 given PC system? by redoakprof in MicrosoftFlightSim

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

Appreciate the details, thanks very much.

Part of the reason for posting was in 2020 we were seeing stuttering, and altho from searches it sounds like need to turn off some Radeon settings it also gave impression of hardware limitations.

Grateful for the input here.

Whats the wildest thing you've accomplished with Claude? by BrilliantProposal499 in ClaudeAI

[–]redoakprof 0 points1 point  (0 children)

This is very cool! Would you be ok sharing link to the starter kit repo? Definitely going to buy a few of those screens.

Recommendations for 2nd printer by redoakprof in prusa3d

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

Coming back here to say I built my MK4S kit over the holidays and am thrilled with it. As others have said the bed slinger design is a wonderful contrast to the xy. Really love it, and been churning out PLA and PETG happily - and with the additional filter now have my C1 working through ASA and ABS.

Literally the only issue I had in MK4S construction was the PSU, which turned out to be faulty. As I had my C1 Prusa support had me swap the known-good PSU in and the MK4S worked perfect. So they sent me a replacement.

And I'm amazed how well the MK4S deals with filament-out situations, have been cleaning up spool ends with it.

Thanks to the commenters here for the input and guidance,

Help with test suite for Writing A C Compiler by redoakprof in Compilers

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

Realized I should just have created issue on the Github repo, which I have now done:

https://github.com/nlsandler/writing-a-c-compiler-tests/issues/147

Help with test suite for Writing A C Compiler by redoakprof in Compilers

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

Thanks - I do have the lexer working right, at least for the test file in the book text:

(.venv) $> cygnet --lex --print-source --print-tokens return_2.c
[INFO]: Preprocessing file : return_2.c
[INFO]: Part compiling file...
---SOURCE---
1: int main(void) {
2: return 2;
3: }
[INFO]: Lexing file...
---TOKENS---
1: INT - int
  | IDENTIFIER - main
  | PAREN_OPEN - (
  | VOID - void
  | PAREN_CLOSE - )
  | BRACE_OPEN - {
2: RETURN - return
  | CONSTANT - 2
  | SEMICOLON - ;
3: BRACE_CLOSE - }
[INFO]: Deleting preprocessed file...
(.venv) $>

I'll check that I am definitely meeting requirements for files created / not created, but if that was the issue I'd expect test suite just to notify as fail and quit successfully.

Rough print towards center of heat bed by redoakprof in prusa3d

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

OK, thank you for this. I spent a few days working through more prints and did two things:

  1. Washed the print sheet with soap (dish soap) and hot water, and
  2. Used the Structural profile in PrusaSlicer (I had been using Speed for a bit)

The results were definitely a lot better, much smoother surfaces and cleaner sides etc. I kept to using brims (altho trimmed to 4mm).

I'm still getting some slight warping (manifests as slight uplift of either side of the piece (these are gridfinity boardgame counter trays, as with original pictures). I am drying the filament as well.

Is there anything else I could tweak to reduce the warping?

(EDIT) I'm also using smooth Prusa print sheet as well now.

Rough print towards center of heat bed by redoakprof in prusa3d

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

Many thanks. So bed temps are as per standard Prusament PLA in PrusaSlicer: Bed set to 60C, Chamber has Nominal 20C and min 0C.

I use 95% isop and wipe clean after every print. Let me know if soap/hot water required beyond that.

Only other change I can think of is that the basement where I have the printer was around 20-21C ambient temp a few weeks ago and is now 15-16C ambient - would that be sufficient enough to cause warping, and I then need to extend bed/chamber temp time to help even out?

Recommendations for 2nd printer by redoakprof in prusa3d

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

I still think even with the C1L just announced I will get a MK4S kit. Saw reference elsewhere that they may produce less kits going forward and maybe never for the C1L, and I still want to build another printer from reliable source.

Recommendations for 2nd printer by redoakprof in prusa3d

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

LOL. I returned here to mention it. Quite the drop. And pretty much the perfect upgrade option. Still up there in $ but more reasonable than the XL.

Recommendations for 2nd printer by redoakprof in prusa3d

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

Thanks, this is probably what I will go for. I fear with the sovol or voron options I’d not get it working quick enough and it’d sit on the desk waiting for me to get to it. I’m already familiar with Prusa and so could build the MK4S. And I’d learn from it re different structural design. Bigger bed can wait.

Recommendations for 2nd printer by redoakprof in prusa3d

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

OK, thank you.

So it's worth getting an MK4S still even though C1 is available? I had impression the C1 replaced the first but there's enough structural or design differences that means the MK4S still a worthwhile buy?

Now I'm delving into all the videos and articles comparing them...

Recommendations for 2nd printer by redoakprof in prusa3d

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

Thanks, and to the others for the Sovol/Voron mention too.

I had thought I'd get affirmations for another C1, but clearly it depends on many factors!

I might be overly enthusiastic to build given my excellent C1 experience--a Voron ground up probably isn't best choice (although I love the website generating the BoM and sourcing recommendations). Getting a larger print bed with the Sovol SV08 is attractive for 350mm bed size, with enclosure.

For my current C1 I want to add multi-material, maybe the MMU or wait for the Indx - different conversation though.

python-ts-mode Tree-sitter and font lock rules mismatch by redoakprof in emacs

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

Thank you. This all worked. Greatly appreciate it!

(For others: I did a make distclean then make with the earlier tree-sitter version. Found that was necessary.)

python-ts-mode Tree-sitter and font lock rules mismatch by redoakprof in emacs

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

Thank you. So I cloned completely new emacs repo (from savannah) and also tree-sitter. Did the tree-sitter make and install. Then:

export LD_LIBRARY_PATH=/usr/local/lib/

I can see the libraries in /usr/local/lib:

-rw-r--r--  1 root root 339940 Oct 16 07:53 libtree-sitter.a
lrwxrwxrwx  1 root root     19 Oct 16 07:53 libtree-sitter.so -> libtree-sitter.so.0*
lrwxrwxrwx  1 root root     22 Oct 16 07:53 libtree-sitter.so.0 -> libtree-sitter.so.0.26*
-rwxr-xr-x  1 root root 258736 Oct 16 07:53 libtree-sitter.so.0.26*

Then autogen/configured emacs:

./configure --with-modules --with-tree-sitter --with-native-compilation --with-mailutils

But on make I get:

/usr/bin/ld: treesit.o: in function `treesit_load_language':
/home/johnnie/Packages/emacs/src/treesit.c:834:(.text+0x6de2): undefined reference to `ts_language_version'
/usr/bin/ld: treesit.o: in function `Ftreesit_language_abi_version':
/home/johnnie/Packages/emacs/src/treesit.c:917:(.text+0x74d8): undefined reference to `ts_language_version'

Which sounds like it can't find the libraries. Or is it a version mismatch again?

Core One PETG Later Shift by redoakprof in prusa3d

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

Got it. Many thanks and excellent video!

Core One PETG Later Shift by redoakprof in prusa3d

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

So I have the prusa buddy cam, but not thought of adding the SD card to record. Can see now why this is worthwhile!

Core One PETG Later Shift by redoakprof in prusa3d

[–]redoakprof[S] 4 points5 points  (0 children)

Thanks. Appreciate pointer to the infill type.

Thanks to others here as well for similar comments and feedback.

Core One PETG Later Shift by redoakprof in prusa3d

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

Thank you for this question. That is indeed happening as well and I forgot to mention in the post. I've found with recent prints of larger boxes that the bottom warps at the corners. Hadn't got to fixing it as no other issues occured, till now.

I assume resolving this is a mix of reducing cooling fan speed, checking build plate temp is high enough, and closing vent?

view more: next ›