I was making a usual g4a trading run for cargo containers. Performance was degrading a lot over the course of the run, but it didnt bother me too much. Come a decent while later, I encounter a hybrid ship while i was docked at g4a for a while. I didnt think much of it, and moved to the next cargo container. I personally didnt expect the hybrid to astrogate with me, but it did, and as i collected the cargo container. By now the framerate had gotten pretty low, but it still was playable. I ended up getting too close to the hybrid, and it zapped me and knocked out my computer. In that instant the framerate jumped up to what it was at the start of the dive. It was only good for a moment, as when the computer booted again the framerate dropped again. After having it knocked out several more times, it became apparent that it was only when the computer was offline did the framerate improve.
#[1.52.11] Framerate degradation using prospector hud & racing autopilot
1 messages · Page 1 of 1 (latest)
okay, let's take a look
https://docs.google.com/spreadsheets/d/1vKXGPYhP_mbrBsK6wk2-kncbR9ht2_5aAkWCF99bHrk/edit?usp=sharing
logs
Time,IterationsPerSecond,FPS,Render time,Physics time,Memory: static,Memory: dynamic,Memory: static MAX,Memory: dynamic MAX,Memory: message buffer max,Objects,Resources,Nodes,Orphans,3D: Objects,3D: Vertices,3D: Material changes,3D: Shader changes,3D: Surface changes,3D: Draw calls
2024/06/...
You are running with DTSS off, this probably makes your performance much worse than it could be.
Framerate seems to be consistent with physics load, however, I don't really like how this chart looks:
from what i'm getting from it, looks like the load is on a constant incline
this is over more than one dive?
one single dive
just collecting cargo containers, and getting new ones from g4a station
is it taken during the dive?
yes, i took it soon after i found discrepancy with the ship's computer
There will be an important data point when you return to Enceladus, please submit logs after you do that.
I need to see if these objects are part of the game scene or something else, seeing if they get cleaned up will give me valuable context
i'd returned to enceladus since i did it and closed the game, i opened it once after but only sold ores, made repairs to ship, and switched to a titan. i'll quickly grab logs right now
that might be unfortunate
let me see if I can recover that data
it seems that your CPU was busy to the point where it could not perform timely log writes
these are supposed to happen every second
unfortunately, that doesn't give me data to work with :/
I can see that some objects persist during your dive, but I don't have data to figure out if thats a legitimate case (like, having more and more stuff in your cargo hold), or something is leaking. And if something is leaking, is it leaking in the dive scene, or outside of it.
the only thing i can safely say persisted was a lifepod i picked up at some point
I'm not sure I'm seeing anything, might need more time
now let's see
seems that if there is a leak involved, it get cleared up post-dive
expanded some logging facilities, another soak test:
hm
koder@Ancalagon MINGW64 ~/AppData/Roaming/dV/logs
$ grep -i stray engine_log.txt |grep -v exhaust
182355 - Stray Node: UberConversation/pirate (Type: InstancePlaceholder)
326711 - Stray Node: UberConversation/vilcy (Type: InstancePlaceholder)
326712 - Stray Node: UberConversation/helper (Type: InstancePlaceholder)
326709 - Stray Node: UberConversation (Type: Node, Script: res://tools/InstanceDependingOnParentAttribute.gd)
326710 - Stray Node: UberConversation/civilian (Type: InstancePlaceholder)
182351 - Stray Node: UberConversation (Type: Node, Script: res://tools/InstanceDependingOnParentAttribute.gd)
182353 - Stray Node: UberConversation/vilcy (Type: InstancePlaceholder)
182354 - Stray Node: UberConversation/helper (Type: InstancePlaceholder)
@floral tinsel are you doing a lot of ganymedean ore runs?
yeah, quite a lot
rephrasing:
...in the period the logs cover?
yes, I didn't collect any other containers after I took the logs
Okay, I think I know what's going on
sounds good