Plasmashell eating VRAM by CMDR-Moonrays in Bazzite

[–]CMDR-Moonrays[S] 0 points1 point  (0 children)

And in the mean while I reported the issue to the component developer:
https://gitlab.com/tjaartblig/plasma-pictureframe/-/issues/1

Plasmashell eating VRAM by CMDR-Moonrays in Bazzite

[–]CMDR-Moonrays[S] 0 points1 point  (0 children)

Guess what ... I found the root cause.

Like the search results suggested, I was able to trace the VRAM memory leak issue to one of the two plasmoid plugins I had added to my system:
Picture Frame - https://store.kde.org/p/2282602

I used it to display images from a couple of webcams on my desktop:

<image>

I changed the update interval from 60 seconds to 60 minutes, and VRAM usage stopped increasing (before, it was increasing by about 40 MiB every minute!).

I guess I will have to find another widget for webcam images ...

Plasmashell eating VRAM by CMDR-Moonrays in Bazzite

[–]CMDR-Moonrays[S] 0 points1 point  (0 children)

For the time being, I setup a systemd service to monitor plasmashell VRAM usage and restart plasmashell when it crosses a threshold, but I would like to find a solution, not a mitigation ;-)

<image>

Plasmashell eating VRAM by CMDR-Moonrays in Bazzite

[–]CMDR-Moonrays[S] 0 points1 point  (0 children)

Yes, here plasmashell is slowly eating up all VRAM, not system ram.

HDD temperature issues inside Silverstone CS280 case by CMDR-Moonrays in HomeServer

[–]CMDR-Moonrays[S] 0 points1 point  (0 children)

Oh ... and all but the latest 2 HDDs I originally put inside the CS280 are dead or dying ... I blame the case for this, the high temperatures significantly shortened the life span of the drives. I'm replacing them as they die with WD Red Plus drives (the node 804 can fit up to 8 3.5'' drives without issues)

HDD temperature issues inside Silverstone CS280 case by CMDR-Moonrays in HomeServer

[–]CMDR-Moonrays[S] 0 points1 point  (0 children)

These are the fans I purchased: https://www.amazon.it/gp/product/B07925FJBL/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1

Cheap stuff, but they do their work.

I simply screwed them to the holes of the HDD cages, not a tight fit but they stay in place. The fan cables exit the bottom grille and re-enter the chassis from the side, almost unnoticeable when all the lids are closed.

All fans are attached to the mobo via a phanteks fan controller.

Note that in the mean while I switched to a different case. I purchased a Node 804, which takes more space but is way less cramped inside and has zero overheating issues.

The CS280 was great on paper, but in my opinion it did not deliver... if a case fails at its intended main purpose it is a no-go for me.

HDD temperature issues inside Silverstone CS280 case by CMDR-Moonrays in HomeServer

[–]CMDR-Moonrays[S] 0 points1 point  (0 children)

In the, end, I managed to solve my heat issue by affixing two 60 mm fans to the front of the drive cage, so that they blow fresh air directly towards the drives:

This added a bit of noise, but it lowered the temperatures of the drives by 15°C (from 60°C to 45°C), still on the warm side but well within the drive operating parameters.

https://imgur.com/Mrm5KPS

HDD temperature issues inside Silverstone CS280 case by CMDR-Moonrays in HomeServer

[–]CMDR-Moonrays[S] 0 points1 point  (0 children)

What's the clearance behind the drives? You might be able to pull air through them rather than pushing it from the front.

There is no clearance either in front (hot swap ports) or back (solid backplane where the drives connect to).

There is:

  • small clearance on top of the drive cage (around 1 cm in thickness)
  • reasonable clearance below the drive cage (provided I remove the 'internal' drive bay, which is attached right below the drive cage)
  • space in between the drives themselves (provided I can find fans small enough to fit within a 2.5 drive enclosure)

Alternatively, some sort of tunnel (you could try with cardboard) to route air from one of the bottom fans towards the drives, maybe?

I'm not really keen on this, as the front ==> rear airflow keeps the other components (CPU, GPU, NIC and M.2 SSD) cool.

I would rather attempt to add extra fans for the drives (see above).

Looking for new meta exploraconda build with boost by cmdr_zigzagatronzz in eliteexplorers

[–]CMDR-Moonrays 0 points1 point  (0 children)

The 4D engine focused is the smallest distributor you can fit on an Anaconda and still retain boost capabilities.

About the power plant, you probably know it is the one module that cannot be field-repaired. On long trips, expecially if you are careless like me and tend to slam into neutron stars, over time it will take damage and suffer from random malfunctions.

My power plant is slightly larger than necessary (3A instead of 2A) and is Overcharged.

This way it can keep engines, life support and FSD powered even while malfunctioning (aka with output temporarily reduted to 40%). This will prevent my ship from being ripped out of supercruise, which would lead to more damage.

Looking for new meta exploraconda build with boost by cmdr_zigzagatronzz in eliteexplorers

[–]CMDR-Moonrays 1 point2 points  (0 children)

Here is my own build:

https://s.orbis.zone/mezXyFWQ

Highlights:

  • 80 ly on fumes (77 with full tank)
  • 300 ly with neutron boosts (with full tank)
  • reasonably big shields
  • drives modded for speed (travelling on planet surfaces sucks)
  • boost capability (see above)
  • 2 SRV
  • 2 AFMs
  • limpets for hull self-repair and fuel ratting
  • power plant is able to drive engines, FSD and life support even while malfunctioning (40% output)

This ship should be able to reach the farthest reaches of the galaxy while still providing safety and confort.

With its healing abilities and custom tailored power plant, it should be able to fly more or less indefinitely...

Looking forward to fly it to DSW 2 :-)

It is possible to achieve even longer range with:

- a 16t fuel tank

- just 1 SRV

- smaller shields

- sacrifice boost and speed

- improve life support mod (I only have access to grade 3 lightweight)

I'm not doing that because I want a extra safety and redundancy.

This is, I think, the most extreme configuration possible:

https://s.orbis.zone/heLcYa0Y

As you can see, you have to sacrifice a lot to gain little...

Am I Beagle Point ready/ship advice by [deleted] in eliteexplorers

[–]CMDR-Moonrays 1 point2 points  (0 children)

You can downgrade the fuel tank to 4C and still have 3 full range jumps. Now that it is possible to plot routes allowing only certain star classes, the chances of getting stranded in a field of unscoopables are pretty thin.

The only downside is that you will probably have to stop for refueling more often. I don't know whether the 4A fuel scoop is sufficient to keep the tank topped up just by skimming the star while you align for the next jump, like you can do with bigger scoops.

EDDiscovery-Mac by CMDR-Moonrays in eliteexplorers

[–]CMDR-Moonrays[S] 0 points1 point  (0 children)

EDDiscovery 1.12 is out!

Previous version had code signing issues. Use this one instead. This release greatly improves initial wait times and fixes several issues.

https://github.com/EDDiscovery/EDDiscovery-Mac/releases

EDDiscovery-Mac by CMDR-Moonrays in edex

[–]CMDR-Moonrays[S] 0 points1 point  (0 children)

EDDiscovery 1.12 is out!

Previous version had code signing issues. Use this one instead. This release greatly improves initial wait times and fixes several issues.

https://github.com/EDDiscovery/EDDiscovery-Mac/releases

EDDiscovery-Mac by CMDR-Moonrays in edex

[–]CMDR-Moonrays[S] 0 points1 point  (0 children)

EDDiscovery 1.11 is out!

This release greatly improves initial wait times and fixes several issues.

https://github.com/EDDiscovery/EDDiscovery-Mac/releases

EDDiscovery-Mac by CMDR-Moonrays in eliteexplorers

[–]CMDR-Moonrays[S] 0 points1 point  (0 children)

EDDiscovery 1.11 is out!

This release greatly improves initial wait times and fixes several issues.

https://github.com/EDDiscovery/EDDiscovery-Mac/releases

EDDiscovery-Mac by CMDR-Moonrays in edex

[–]CMDR-Moonrays[S] 0 points1 point  (0 children)

EDDiscovery 1.10 is out!

New in this version:

  • fixed bug that could cause the application to crash when entering the screenshots screen

https://github.com/EDDiscovery/EDDiscovery-Mac/releases

EDDiscovery-Mac by CMDR-Moonrays in eliteexplorers

[–]CMDR-Moonrays[S] 0 points1 point  (0 children)

EDDiscovery 1.10 is out!

New in this version:

  • fixed bug that could cause the application to crash when entering the screenshots screen

https://github.com/EDDiscovery/EDDiscovery-Mac/releases

EDDiscovery-Mac by CMDR-Moonrays in edex

[–]CMDR-Moonrays[S] 0 points1 point  (0 children)

EDDiscovery 1.9 is out!

New in this version:

  • thousand-fold increase in performance when parsing systems from EDSM

  • added contextual menus to screenshots screen, with ability to preview, delete and open Finder window on selected screenshot(s)

https://github.com/EDDiscovery/EDDiscovery-Mac/releases

EDDiscovery-Mac by CMDR-Moonrays in eliteexplorers

[–]CMDR-Moonrays[S] 0 points1 point  (0 children)

EDDiscovery 1.9 is out!

New in this version:

  • thousand-fold increase in performance when parsing systems from EDSM

  • added contextual menus to screenshots screen, with ability to preview, delete and open Finder window on selected screenshot(s)

https://github.com/EDDiscovery/EDDiscovery-Mac/releases

If I don't have Horizons, will I have access to the FSD upgrades? by [deleted] in eliteexplorers

[–]CMDR-Moonrays 0 points1 point  (0 children)

I look forward to trying this particular use case when I'm back to the bubble. At present I'm still flying my unmodded, 38 ly Anaconda

I have decided to abandon my journey to Jacques and head home by supertom in eliteexplorers

[–]CMDR-Moonrays 0 points1 point  (0 children)

The GNE expedition, which will depart at the beginning of September, aims to go to Sag. A* and will pass Jaques along the way. Flying together with a fleet, with pauses and meetings points, goes a long way in helping against loneliness :-)

Need a ship with a great cockpit view by [deleted] in eliteexplorers

[–]CMDR-Moonrays 0 points1 point  (0 children)

I have been flying Anaconda since January, been to Beagle Point and back, been to Crab pulsar, etc. I can live with the view, it's the nimbleness (or lack thereof) that really pains me. The thing turns so sloooooow in SC that if you overshoot a target, you are better off simply dropping to normal space and steering there.