New bug or new feature?

Last night jumped to a system with 3 stars. To my surprise jump dropped me at the second star (B) instead of the main (A). This is first time such thing happens to me. Anyone else seen this?
 
Happened to me today.

While uncommon arriving at B stars does happen. Doing so when they are close together might be a behavior added in 2.2 to help avoid arriving between them (I think this was the case for me today).

Judging by your forum rank you've been exploring for some time now? Isn't it great we still notice things we haven't noticed before? I'm near 10k systems now and still see interesting stuff, even in the bubble.
 
Happened to me today.

While uncommon arriving at B stars does happen. Doing so when they are close together might be a behavior added in 2.2 to help avoid arriving between them (I think this was the case for me today).

Judging by your forum rank you've been exploring for some time now? Isn't it great we still notice things we haven't noticed before? I'm near 10k systems now and still see interesting stuff, even in the bubble.

Yes, i am not new to exploration. Have 31000 jumps and 740000ly total distance traveled on my account. And this never happened to me before. I dont think it is a mechanism to avoid arriving between stars as this is still happening. Last time was just an hour ago.
Probably just a weird 2.3 bug...:rolleyes:

- - - Updated - - -

Just means you're a B list Commander.

:D must be it
 
I dont think it is a mechanism to avoid arriving between stars as this is still happening. Last time was just an hour ago.
Probably just a weird 2.3 bug...:rolleyes:
They only decreased the chances, they didn't stop it completely. It still happens.

It is certainly not 2.3 related I've had it a few times before, especially with real life star systems.
 
Last edited:
It is certainly not 2.3 related I've had it a few times before, especially with real life star systems.

IME there's a number of hand-authored systems set up that way, but I've never seen it on a proc-gen system, except for close binaries where the jump-in brings you close to both stars and by chance closer to the smaller of the binary pair. Was it a proc-gen system, Pirin?
 
They only decreased the chances, they didn't stop it completely. It still happens.

It is certainly not 2.3 related I've had it a few times before, especially with real life star systems.

They removed the chance of dropping into a star, but if two or more are close enough, dropping at the usual distance from the primary can still put you at a dangerous distance of the second or third one, no change there.
 

Deleted member 38366

D
If I understand correctly, the issue (OP) isn't dropping "into" a Sun (crashing/overheating), but arriving at not-the-A-Sun?

This actually has always been this way - we arrive at the Star that has the greatest Mass.
In most cases, that's the A Sun. But in some cases, it's not.

Unsure if they fixed it, but in V2.2, the arrival Sun type listed in the HUD for example was always the A-Sun, even for Systems where the arrival Point is another Sun (highest Mass).

LALANDE 25224 is a nice example :
A-Star is a scoopable Class F Sun, indicated in HUD when initiating the Jump.
B-Star.. is a Neutron and actual arrival Point, since it has the higher mass ;)

AFAIK this has surprised numerous CMDRs in the past, planning (and HUD-Indicated) to arrive at a scoopable Sun, but finding themselves at an unscoopable Sun instead. Arrival just wasn't the A-Star...
 
Last edited by a moderator:
I wish I had footage of these. I'm sure it's happened in one or proc-gen stars. If it happens again I'll save the clip.
Maybe I was arriving in a way that looked like the B was in front and A beside. I don't know.

Btw, off-topic but saw your name in the Trappist-1 system @Jackie (among many other places around the bubble)
Well done on that.
I'm nearing 10k systems and still just a new kid lol

LALANDE 25224 is a nice example :
A-Star is a scoopable Class F Sun, indicated in HUD when initiating the Jump.
B-Star.. is a Neutron and actual arrival Point, since it has the higher mass ;)

Another reason to throttle down when jumping. Those jets freak me out lol
 
Last edited:
IME there's a number of hand-authored systems set up that way, but I've never seen it on a proc-gen system, except for close binaries where the jump-in brings you close to both stars and by chance closer to the smaller of the binary pair. Was it a proc-gen system, Pirin?

Yes, it was proc-gen: Gludgai AA-A G0. Actually i do have few pics from the event, not sure why i didnt post them in the initial post :rolleyes:

So, this is where i was dropped

b1eKktV.jpg

Looking left the main star can be seen some distance away:

tIsapIL.jpg

And this is the system map:

xOACEh4.jpg
 
How strange! (I would rep you, but the forum crashes each time I try for some reason.)
I'll swing by that system next time I'm out that way.
 
Last edited:
- It is no longer possible to travel through or end up inside another star if you hypespace into a multi-star system. If an intervening star is detected your hyperspace will be redirected onto that star. This process repeats if the new path is also obstructed. Note that you can still end up dangerously close to other stars and get more than a little cooked

I assume that it would be this from patch 2.2

If you still close to the system it might be worth trying to jump in from a different angle to see where you spawn
 
Last edited:
I assume that it would be this from patch 2.2

If you still close to the system it might be worth trying to jump in from a different angle to see where you spawn

I suspected that is what happened to me yesterday. I could see both stars arriving and I landed at the nearest one. It was the B star. I'm fairly sure it was proc-gen and I had a feeling I'd read something about it back when 2.2 was launched.
 
Back
Top Bottom