[1.53.4] Multiple IRRS-T Spawns | Kodera Software | Page 1

tacit folio Aug 13, 2024, 3:39 AM

#

Long dive, approx 2 hours or so.
I leave G4A baseteroid, astrogate to Claim Beacon A
On arrival, I'm met with the pictured Pilot tab (LiDAR imaging)

I went to the one approx 90, it's discovered as 'Moonlet', and has melt holes like IRRS-T.
Contact pops in, I investigate: lifepod, grabbed. I then investigate the one approx 340, it is NOT discovered. I fly around it for a bit, and find a hole, it IS IRRS-T.
I travel back to the original one (approx 90* in the image). It is ALSO IRRS-T.

This now means that, not only do I have an AIrtist's Atelier, but I now also have TWO more copies of IRRS-T. Currently flying in the Titan, so I cannot investigate the passages. I'm going rn to grab the Kitsune and find out if they both remain, and both pop as AA.

Note: This is on the gaming laptop, different hardware from the desktop. Ryzen 7 4800H, Nvidia 1660 GTX, 16GB DDR4

steep nova Aug 13, 2024, 3:47 AM

#

i've also found two ateliers, but not this close to each other
the astro point for one disappears when venturing inside and updating the other

tacit folio Aug 13, 2024, 3:48 AM

#

Logs for this playthrough

📎 dV.zip

#

If it deletes the previous one, then I'm actually NOT going to go inside, because the one that's currently atelier is in the middle of a propeller, and I quite like it there. I can keep them as moonlet.

#

OOORRRRRR, go inside both, and see if they both pop AA astro targets, then just alt+f4 out to prevent the save?

tacit folio Aug 13, 2024, 4:10 AM

#

The one moonlet that provided an astro point has now moved. It was ~45* and 5km from my Claim Beacon. It is now here (image).

tacit folio Aug 13, 2024, 8:50 PM

#

Just got two more, side by side....interestingly, it appears they are at the same angle/ bearings as the previous double spawn.

#

Clearer image

#

And as last time, the 'bottom right' moonlet pops as astrogation target, while the 'upper left' does not.

tacit folio Aug 13, 2024, 9:37 PM

#

Am I being stalked for taking out AI ships? Or is this ACTUALLY some bug? Now IRRS-T is near G4A baseteroid.....

rocky nymph Aug 14, 2024, 7:59 AM

#

Interesting

#

I do have, however, some problems figuring out the exact order of events that happened.

tacit folio Aug 14, 2024, 4:54 PM

#

The images are all chronological, across multiple dives and playthroughs.

Astrogate to Beacon A, Encke Gap. Dual moonlets on LiDAR. Both are IRRS-T
I dive again, after heading home, and there is only one moonlet, 'below' the beacon, instead of 'above' it.
Another dive, while refreshing a random moonlet (little one) another double spawn, with both IRRS-T in the same 'formation' as the original claim beacon spawn.
The same random moonlet spawn, but with the PC sitting in between the IRRS-T moonlets.
Another dive, head to G4A baseteroid for some trading, and there's another IRRS-T ~45* from G4A. It is still there.

The original beacon A moonlet is still there (only one provided an astro point), the G4A moonlet is still there (I see it every time I astrogate to G4A now), and I have not yet checked the one that popped at the random small moonlet (but the astro point is still available, interestingly, it hasn't reordered itself in the list, along with the other 'moonlet' s like the rest have).

rocky nymph Aug 29, 2024, 9:06 AM

#

There is quite a lot of mess in the logs. Difficult to parse.

#

[1.53.4] Multiple IRRS-T Spawns

#

You encountered IRRS-T moonlets at:

[2024/08/12 20:07:20]
[2024/08/12 21:15:55]
[2024/08/12 21:20:45]
[2024/08/12 21:20:46]
[2024/08/12 21:45:46]

#

I assume 21:20 is the twin formation you mentioned?

#

hm...

[1.53.4]: [2024/08/12 21:15:56]: Location-based oddity BiggerMoonletSpelunker at (16401642, 27029552)
...
[1.53.4]: [2024/08/12 21:20:45]: Trying to spawn BiggerMoonletCaves:[RigidBody2D:2968736] at (18961.617188, -118610.703125) (global: (29897346, 13363386))

#

that's... pretty far (-1349.57, 1366.617)km

#

huh

#

okay

#

I see what happened

#

@tacit folio was that all a Titan run?

#

[1.53.4]: [2024/08/12 21:13:30]: Fast travel to POI_ANARCHY_STATION
[1.53.4]: [2024/08/12 21:20:26]: Fast travel to POI_CLAIM_ALPHA
[1.53.4]: [2024/08/12 21:43:33]: Fast travel to POI_ANOMALY|597-273
[1.53.4]: [2024/08/12 21:45:25]: Fast travel to POI_AIRTIST_WORKSHOP

#

An fascinating edge case

#

Please ping me when you have an opportunity to read & verify this

tacit folio Aug 29, 2024, 4:19 PM

#

rocky nymph <@340672064174424065> was that all a Titan run?

I don't believe so? I can see if it was during the times when I was recording, go back through. I've been running in the OCP pretty heavily.

#

What is the most interesting bit to me is, there were two instances in that same playthrough, where I encountered dual spawns, and they both appeared to be spatially identical. The 'left' one was ~1km above and 2km to the 'left' of the right one, in both cases.

#

I can say, I have not had that same artefact occur again, since making this post. No idea what happened, but it was funny as crap, to me.

rocky nymph Aug 29, 2024, 4:54 PM

#

tacit folio What is the most interesting bit to me is, there were two instances in that same...

In these logs I see just one candidate, there was a second one?

tacit folio Aug 30, 2024, 1:09 AM

#

I also re-read the first post, cuz old man brain, I was apparently in the TItan for that event sequence, yes. Sorry for old man brain 🤣

#

Yeah, multiple events, one on the 12th, and another on the 13th. This would mean this was between two different game loads. I did NOT supply the log for the second one, which I probably should have done, in hindsight.

rocky nymph Aug 30, 2024, 7:44 AM

#

Okay, I think this narrows this down sufficiently

rocky nymph Aug 31, 2024, 8:08 AM

#

performance logs for the run:
https://docs.google.com/spreadsheets/d/1JgCEwFeYuJzBcmvhemTgkJz7CsbyOn8wz5e_-SqE4SM/edit?usp=sharing

Google Docs

Performance logs analysis (ButItRuns)

#

hm. I might need to trim them down, 5h of data is too much to help diagnose

#

https://docs.google.com/spreadsheets/d/1jvIirSBWud6hRxi6WJwgKbKaGD2vBgmfHXme6rW1Kms/edit?usp=sharing

Google Docs

Performance logs analysis (ButItRuns) trim

#

this is the relevant part of the chart:

#

specifically, this timefame is interesting:

#

actually, no

#

this is the problem period

#

suprisingly

#

[1.53.4]: [2024/08/12 21:09:59]: Location-based oddity BiggerMoonletSpelunker at (13513994, 3573211.25)
...
[1.53.4]: [2024/08/12 21:15:55]: spawn of BiggerMoonletCaves:[RigidBody2D:2839261] (BiggerMoonletCaves) complete at (-1889.836914, -173525.703125) (global: (16394079, 27024410))

rocky nymph Aug 31, 2024, 8:46 AM

#

Okay so we have two connected, overlaping problems here

#

One is an suspiciously long dangling encounter. That's probably connected to intesection of playstyle and encounter size that I did not anticipate.

#

The second one is persistance of an dangling encounter through astrogation.

rocky nymph Aug 31, 2024, 1:33 PM

#

Should be fixed in 1.54.7, now availalbe in the Experimental branch.

tacit folio Aug 31, 2024, 4:41 PM

#

I'll have to get on the Experimental branch then, and see if I can't break something else 🤣 Does Experimental still log achievements? I'm 12 away from 100% 😄 😄

#

Also, did I read that right? You didn't expect players to spend 6 hours in game at one time? Am I the wierdo yet again? (Hoping yes :D)

rocky nymph Aug 31, 2024, 7:39 PM

#

tacit folio Also, did I read that right? You didn't expect players to spend 6 hours in game...

No, I didn't expect players to crawl around for 6 hours.

#[1.53.4] Multiple IRRS-T Spawns