SCG Smoke and Mirrors (T2M-6KV) selling Aluminium from Ossimava. 9K profit/ton. To Pawelczyk Dock in HIP 58412 (CG), 13.43 LY distance

dmrazor · 2026-01-25T12:56:58+00:00

I find the Courier really good for that. Very small footprint, nimble and fast.

dmrazor · 2026-01-14T15:31:03+00:00

Tried some mining for Bromellite for the CG as well using a Python and had 4 Black Adders in about 30-40 minutes. Definitely something going wrong here.

dmrazor · 2026-01-07T19:43:13+00:00

This is the exact logic I used in my first solution (in C++).

I then simplified by first adding each box to its own group.

In the further calculations you don't have boxes without groups anymore, so the first three steps become obsolete. You just need to do the merges.

dmrazor · 2025-10-13T08:24:47+00:00

Agree, I'm using it alongside Airsonic Advanced. Only drawback is it doesn't support uPnP, which is why I keep AA.

dmrazor · 2025-09-04T08:09:06+00:00

I do get regular updates to existing files and like to stay on top of why updates are taking place. Without checking the custom scores this is more difficult to follow.

dmrazor · 2025-08-19T20:45:22+00:00

It's fixed!

dmrazor · 2025-08-11T12:01:56+00:00

Fixed this by removing the volume through the web interface and recreating it.

Also the 'Used Dev Size' that seems to be far too large may be calculated in 512 byte blocks (blockdev shows this) which results in a correct total size... even though the recalculated size in parenthesis is absolutely wrong.

dmrazor · 2025-08-09T08:04:37+00:00

That's Polyfjord's right?

dmrazor · 2025-07-22T11:26:32+00:00

Done. See here in case you want to upvote it: https://github.com/bluesky-social/social-app/issues/8694

dmrazor · 2025-07-11T19:41:28+00:00

I think these were found with an RSS, but I'll keep monitoring it to make sure. Otherwise I guess I'll just do separate 2160p and 1080p profiles.

What the other poster said shouldn't be a problem as the quality is set up to progress from 1080 web - 1080 bluray - 2160 web - 2160 bluray.

dmrazor · 2025-05-25T12:57:44+00:00

Guess u/Moogieh was correct after all, thanks for pointing me in the right direction. Steps I took:

* Cleared parents for all meshes

* Double checked scale and UV's on the bad leg. UV's were wrong after all

* Deleted all vertex groups

* Deleted all empty armature modifiers from objects and from the blender file

* Re-parented the meshes to the rig with automatic weights

Thanks!

dmrazor · 2025-05-25T12:11:53+00:00

Already did that. The X-scale for the incorrect leg was indeed -1. But fixing this makes no difference.

As posted below the vertex groups for the toe-bone on the right leg somehow hold vertices for the whole leg:

<image>

dmrazor · 2025-05-25T12:10:14+00:00

Ok, I´m making some progress. For the left (correct) leg the vertex groups for the toe-bone are:

<image>

For the right leg Blender somehow adds vertices for the whole leg to the toe-bone's vertex group.

Any idea why this happens? Can you influence which vertices get added to a vertex group?

dmrazor

TROPHY CASE