KSP 1.8.1 RO - "Voxel CrossSection Area is NaN"

[scouarn]

Hello [edit : a lot of wrong stuff about the issue].

I get this kind of log message. [edit : some other wrong stuff]

[LOG 18:49:16.371] [FAR v0.16.0.1]: Voxelization Time (ms): 59
[LOG 18:49:40.872] [FAR v0.16.0.1]: Updating Untitled Space Craft
[LOG 18:49:40.874] [FAR v0.16.0.1]: Overall bounds error in Radial Tank (Integral) 0 meshes
[LOG 18:49:40.939] [FAR v0.16.0.1]: Voxel Element CrossSection Area: NaN
FAR VOXEL ERROR: Voxel CrossSection Area is NaN at section 0
FAR VOXEL ERROR: Voxel CrossSection Area is NaN at section 1
FAR VOXEL ERROR: Voxel CrossSection Area is NaN at section 2
FAR VOXEL ERROR: Voxel CrossSection Area is NaN at section 3
.
.
.
FAR VOXEL ERROR: Voxel CrossSection Area is NaN at section 164
FAR VOXEL ERROR: Voxel CrossSection Area is NaN at section 165
FAR VOXEL ERROR: Voxel CrossSection Area is NaN at section 166
FAR VOXEL ERROR: Voxel CrossSection Area is NaN at section 167
Std dev for smoothing: NaN voxel total vol: 8.30664434111419 filled vol: NaN

I don't really know if this is the problem comes from the parts models, the voxelization algorithm or my game/pc config (I am also not a ksp mod dev). For the moment I'll try to play without the mod, thanks for reading, hope to be useful.

[dkavolis]

Seems like an error in voxelization on FAR end, I'll have a look in the next few days.

[scouarn]

Thanks for the quick answer and merry christmas !

[scouarn]

Hello again, I weirdly fixed my problem. I found out my game was crashing because I had left the force-opengl flag on, maybe a glitch from unity or my new gpu...

However the long message kept randomly showing up in the debug console (not at all "in a loop" like I initially mentionned, I guess I missread the logs), not always consistent with the parts attached to the craft (and even stock ones). It may be related to a KeyNotFoundException I noticed from FAR. It also sometimes caused a lot of NaN errors when doing AoA swipes.

I messed around a lot trying to reproduce the issue but it gradually stopped occurring, even after restarting the game. So I ended up deleting all the generated config and cache files and it then only happened once. It's still working fine after repasting the config files I had backed up.

So I guess it's "fixed" but not "solved". I'll be keeping an eye on the console.

[azraelzephyrian]

@scouarn I was flummoxed by this... I tried adding -soft to a shortcut target and it seems to have restored FAR voxelization. Thanks! Sucks, though...it would save my CPU some blisters and calluses if I could let the GPU handle some of the graphics side (i have a suite of graphics mods installed). Then again, this game is terrible at multi-threading, and it seems to run well enough on the opening screen and in the hangar...gotta try loading a high-part-count model tomorrow to be sure though.

Heck, even if it lags a bit, I'd prefer it to flying in the souposphere...

[azraelzephyrian]

I'm getting the same issue even down to the fact that forcing software rendering doesn't completely fix it. It works, but reliability isn't fantastic. Great.

[azraelzephyrian]

Seems like an error in voxelization on FAR end, I'll have a look in the next few days.

Did you ever figure this out? I still get issues with voxelization.

[dkavolis]

63a9c11

I assume your issue was when attaching a previously unattached part to the ship in the editor. This should fix it.