• 13 Posts
  • 136 Comments
Joined 1 year ago
cake
Cake day: June 27th, 2023

help-circle

  • Well as a brand new player of ARPG and LE and doing my own blind thing…. for me to be at level 60 and not truly encountering real issues with my build I would absolutely agree with that statement!

    I also think that’s what makes this game so approachable. It lets you do your thing and enjoy the game. If you want a challenge and truly test your build then stick around and do the endgame stuff. While you do your own thing with your blind build, you gain tons of experience and understanding as to what it takes to refine your build (even without looking at guides or YouTube videos which is what I’m doing for my first play through).









  • I’ve watch a few videos that compare a few headsets and for the “lower” audio and mic quality ones, they usually say that with their tweaking software you can make it a bit better. I was wondering about it since usually those type of programs are made for Windows only plus I don’t really think I want something that I must use software to make better. Long story short, thanks for the heads up!!




  • Something else to check is your infill percentage. Make sure you don’t have it at 100% (unless you absolutely need to build something completely solid). Another thing to check is your print speed. Too low and it will take a decade to print something simple. Too fast and it cause your print to fail. At this point we will all be throwing spaghetti against the wall. Can you share a screenshot of your settings?




  • Not quiet. I was running gitea before so my mount was ./gitea:/data but since switching over to forgejo, I renamed my ./gitea directory to ./forgejo. Adjusted my compose file to have a mount of ./forgejo:/data.

    Now inside of that renamed forgejo directory, there are a bunch of gitea references and even one more directory called gitea. When I migrated everything worked right away but since I wanted a cleaner transition, I renamed and switched all gitea references to forgejo but went I brought the stack back online, it went belly up.

    As a troubleshooting step, I recreated my compose file and created a new empty ./forgejo on a different machine just to see what a new and fresh install would look like and the forgejo stack itself created all kinds of gitea references and gitea directory once I brought it up. So to fix my original deployment, I reverted all the references back from forgejo to gitea and everything worked again.

    For fun, I went out to codeberg to look at the Dockerfile and saw that they had a bunch of gitea things within their own Dockerfile so nothing I can do for now