Closed R-T-B closed 11 months ago
I've just been advised that a.) a modzip is not a good thing re licensing, and b.) a journaling system exists and I should use it. Stand by.
EDIT: Journal link below:
https://drive.google.com/file/d/1j9Rk3HU6eC9_7HRC-hJTjXLQDsJcCLoY/view?usp=sharing
These checks don't make sense because max_radius_time
and min_radius_time
are not necessarily the times when we cross the max or min radius, because of these statements.
These checks don't make sense
They don’t, but given how this is called it should work out. This looks fishy though: https://github.com/mockingbirdnest/Principia/blob/eebee0c928597fb35883b345a4fdf0885ca7c442/ksp_plugin_adapter/map_node_pool.cs#L189-L192
These checks don't make sense
They don’t, but given how this is called it should work out. This looks fishy though:
Interesting you should say that, because reverting that exact set of changes via dnspy (the map_node_pool.cs changes) fixed it for me.
Interesting you should say that, because reverting that exact set of changes via dnspy (the map_node_pool.cs changes) fixed it for me.
You mentioned that on Discord already; it is certainly true that ripping out the feature means you do not hit the bugs in that feature, but I would not say that it is interesting. But look more closely at lines 190 and 191 of the quoted code.
Interesting you should say that, because reverting that exact set of changes via dnspy (the map_node_pool.cs changes) fixed it for me.
You mentioned that on Discord already; it is certainly true that ripping out the feature means you do not hit the bugs in that feature, but I would not say that it is interesting. But look more closely at lines 190 and 191 of the quoted code.
It becomes interesting when you have no knowledge of C++ and don't know if that's doing something unseen.
I did however, indeed miss the "Latitude Latitude" mistake. That is kind of hilarious tbh.
Thanks for your attention on this anyways. :)
Log file created at: 2024/01/09 00:00:54 Running on machine: PROXIMACOMMAND Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg @ 00007FFDFFE144FF google::LogMessageFatal::~LogMessageFatal [0x00007FFDFFE144FE+46] @ 00007FFD5A7FB23F principiaVesselVelocity [0x00007FFD5A7FB23E+646798] @ 00007FFD5A893319 principiaVesselVelocity [0x00007FFD5A893318+1269608] @ 00007FFD5A72BD95 principiaUpdatePrediction [0x00007FFD5A72BD94+7604] @ 00007FFD5A72AACD principiaUpdatePrediction [0x00007FFD5A72AACC+2796] @ 00007FFE16A49363 recalloc [0x00007FFE16A49362+162] @ 00007FFE17E3257D BaseThreadInitThunk [0x00007FFE17E3257C+28] @ 00007FFE1902AA58 RtlUserThreadStart [0x00007FFE1902AA57+39] F0109 00:00:54.627553 22764 apsides_body.hpp:215] Check failed: Length{} <= height_above_terrain_at_time(max_radius_time) (+0.00000000000000000e+00 m vs. -7.84768058301880956e+02 m)
I still get a related crash after I dnspyed the change into ksp plugin adapter, but it doesn't seem to be reproducable now, I changed the inclination before the deorbit burn and the crash stooped
Shrug. We are not going to debug hacked binaries, so no point in dumping more crashes here.
If someone builds Principia from head and they still see the crash, then we want to hear about it. Otherwise, no.
Yeah you can't really expect them to try to debug anything hacked together with dnSpy. Good news is there should be a new release addressing this in just a few days, if the new moon schedule holds.
My personal modset + a savegame that will reproduce this issue shortly if in mapview returning to Kerbin at the poles on Flight "Shuttle Flight 14." Download and extract to fresh KSP 1.12.5 install root.
If it is not reproducible, I also had parallax installed and blackracks private eve build. I removed both for size + copyright concerns. I doubt they are related. Link to everything below:
[Link removed due to licensing afterthoughts, see below]
log follows: