You could always write such a command. An excellent candidate for a small XP project...

Just a general comment about live streams, YouTube always needs to process them after they are done, so it is out of our hands when the video will appear, but usually it will be a couple of hours after the stream ends.

That's intentional for the traveller symbols. The gas giant symbol isn't a primary planet in it's own regard, it is an indicator that a gas giant is present in the system, just as with the bases, and other information, basically just a modifer for the main planet symbol.

Maybe I'll do that one day. But it is basically this:

When tracing, it is important when picking the entity to trace that you pick a point that is part of the traced portion. CC3+ uses this pick point to determine which way to send the trace around the entity.

Well, on those cliffs you could end up doing other kinds of rolls too.....

No. Not saying that you won't find anyone, but there isn't an official program/system for such support.

Don't hesitate to ask for help on the forums though, there are a lot of skilled users here which may help you with your problems.

Lovely. You're really good at putting these things together.

Attaching doesn't automatically make corners for you. The only thing that modifer does is to ensure the nodes are in the exact same place, so for your road, it would ensure the start node of the new road is at the exact same point as the end node of the existing one. But line endings are perpendicular to the the direction of the line, so unless the direction of the two road pieces are 100% the same, there will be gaps, which is what you see both with your original example with the effects, and the later one in the last post.

As for symbols, you cannot really attach these to each other. A symbol only have one node, the symbol origin (or placement point). You can attach them to a line or snap them to a grid, but using attach to make them line up won't work.

Look for EType in CStuff in the entity record first. That tells you what kind of entity this is. You'll find the ID's in _ESTRUC.H.

My issue from the very brief look I gave that one was that I didn't seem to actually get valid entities at all, just uninitialized memory. Which may be due to a mistake on my side, or perhaps something that needs to be done that I don't know about, there is no documentation about that call.