[1.3.1] Ferram Aerospace Research: v0.15.9.1 "Liepmann" 4/2/18

[ferram4]

Like I said, depends on the configs. It's not FAR's responsibility to deal with easy-mode configs, especially when the heat shield has a lot of other parts that it can conduct heat to.

[TKFT_ExTr3m3]

Far seems to be causing phantom overheating of decouplers for me. At times when parts are under no major forces or non at all they will explodes do to overheating. This happens instantaneously as they are not gradually heating up. It has happened all sorts of places from flying in space to just sitting at the launch pad (explodes right after loading in). With far installed I have the problem and without it goes away.

[blowfish]

Far seems to be causing phantom overheating of decouplers for me. At times when parts are under no major forces or non at all they will explodes do to overheating. This happens instantaneously as they are not gradually heating up. It has happened all sorts of places from flying in space to just sitting at the launch pad (explodes right after loading in). With far installed I have the problem and without it goes away.

It's a stock bug which seems to be made worse by FAR. The simplest way to fix it is to bring down the conduction multiplier in the debug menu (Alt+F12) Physics->Thermals

Edited July 29, 2015 by blowfish
correct keyboard shortcut

[Wanderfound]

It's a stock bug which seems to be made worse by FAR. The simplest way to fix it is to bring down the conduction multiplier in the debug menu (F12) Physics->Thermals

It's troubling; the bug is bad enough that it is significantly impacting my design choices, but I don't know if it's frequently-occuring enough in stock for Squad to bother fixing it.

I've yet to be able to generate a reliable reproduction scenario. If anyone else can do so, it would be useful to post it.

[123nick]

i have a aircraft launched a rocket, and it seems that, even when the rocket parts are disabled, the control surfaces act like there infront of the CoM, although when the rocket is decoupled, they are behind the CoM, yet still act as if they were infront, moving up when they should move down. i tested it, without rocket in editor, it works perfectly, surfaces move like they should. and with rocket, ^ happens.

[gilflo]

It's a stock bug which seems to be made worse by FAR. The simplest way to fix it is to bring down the conduction multiplier in the debug menu (F12) Physics->Thermals

On which page do you call the debug menu?

Any page I try, settings, main menu page, main setting page, runway and building page,...F12 does not give any debug menu. I guess it's stock debug menu, because there's no such possibility on FAR debug menu

I just find some "conduction factor" in the Physic.cfg file in the KSP folder

[blowfish]

On which page do you call the debug menu?

Any page I try, settings, main menu page, main setting page, runway and building page,...F12 does not give any debug menu. I guess it's stock debug menu, because there's no such possibility on FAR debug menu

I just find some "conduction factor" in the Physic.cfg file in the KSP folder

Sorry, it's Alt+F12.

[gilflo]

Thank's, it's working

It's weird. When this factor is set to squad value, 20, the temp gauge show 508° on ground at night instead of 288°

As soon as I set 15 temp gauge show 288 and if I increase to 16 nothing happens then at 17 temps suddenly shows 508.

Is there a way to keep it permanently at the same value by modifying a config file?

Edited July 29, 2015 by gilflo

[steve_v]

Ironically, installing Deadly re-entry also helps with deadly non-re-entry (buggy) heating... as it sets conduction factor lower than stock.

I do wish this instability in the thermal system was sorted sooner rather than later though, it's a real ship-killer. And it's somewhat annoying that it keeps getting attributed to FAR.

Edited July 29, 2015 by steve_v

[gilflo]

It looks like, if you carry a space vehicle on the top of your spaceplane, there's a kind of multiplier for this overheat bug.

I must reduce thermal conduction from 20 to 15 with my spaceplane and if she is carrying another vehicle, I must reduce from 20 to 5 !!

[ferram4]

Given the extent that people seem to want to complain about FAR exacerbating this, I guess I'll try and rush out an updated version with the only heating tweak I could find.

So the basic problem seems to be that stock utterly sucks at handling parts with very low skin thermal masses; it doesn't have an overall cap on the amount of temperature change between physics frames for skin temperatures, so it can oscillate out to infinity if the skin thermal mass is small enough that the temperature change puts it well above / below the parts it's connected to. Then that difference continues to grow over time.

The main reason that FAR seems to exacerbate it is that FAR sets the skin area (and thus, the skin thermal mass) from what's actually exposed (as well as setting the stock "shielded" flag if it is completely shielded), as opposed to stock that basically does all-or-nothing, only getting minor changes from stack-attached parts, not surface attached. Adding a very quick hack to make the skin area never drop below what stock would calculate should make the problem smaller.

It won't go away, because it's a stock bug, so don't get your hopes up. All of these issues are likely to continue, because it's a stock bug. And remember, I can't fix a stock bug.

[Hodo]

Given the extent that people seem to want to complain about FAR exacerbating this, I guess I'll try and rush out an updated version with the only heating tweak I could find.

So the basic problem seems to be that stock utterly sucks at handling parts with very low skin thermal masses; it doesn't have an overall cap on the amount of temperature change between physics frames for skin temperatures, so it can oscillate out to infinity if the skin thermal mass is small enough that the temperature change puts it well above / below the parts it's connected to. Then that difference continues to grow over time.

The main reason that FAR seems to exacerbate it is that FAR sets the skin area (and thus, the skin thermal mass) from what's actually exposed (as well as setting the stock "shielded" flag if it is completely shielded), as opposed to stock that basically does all-or-nothing, only getting minor changes from stack-attached parts, not surface attached. Adding a very quick hack to make the skin area never drop below what stock would calculate should make the problem smaller.

It won't go away, because it's a stock bug, so don't get your hopes up. All of these issues are likely to continue, because it's a stock bug. And remember, I can't fix a stock bug.

I quite frankly wouldnt be bothered with fixing it Ferram, it isn't your problem. As others have said, installing DRE actually fixes the issue.

[Nansuchao]

Thanks Ferram, I appreciate!

Actually, if the game decide to overheat your ship (without clipped parts and nothing weird), you can't TimeWarp in space also. It's a really annoying bug and I hope SQUAD will fix it ASAP.

[GorillaZilla]

Thank you so much for all your hard work on FAR Ferram :-)

I started playing kerbal space program to learn a little about and explore rocketry at an accessable hands on entry level, and get an idea on what can and can't be done with current technology, as I'd heard that Kerbal space program was a somewhat realistic physics sandbox game based on real life physics and rocketry and a good place to start exploring to learn a little about the subject and unlearn all the misconceptions gathered from movie physics... So I started playing around and experimenting with rockets and flying contraptions, not knowing much about the real physics of rocketry and aerodynamics and no idea at all about all the things that were dead wrong about the simulation in KSP. Such As:

The impossible magic reaction wheels.

Jet engines being Thrust to weight ratios way beyond what their real world equivilents are capable of.

The fact that aerodynamic stability/instability simply did not exist in stock and generated no torque forces around the center of mass.

That unimaginable madness such as drag based off part mass rather than shape/volume was a thing.

Not even knowing (At first) that all the planets were 1/10 scale compared to the real thing, yet having full gravity and improbable density.

And not knowing that as a result of the smaller planets and lower orbital velocities, that the engines and fuel tanks were much heavier than than real world equivilents to make getting to orbit artificially more difficult.

(but still too easy, single stage to orbit rocket still easy to do rather than almost impossible like in real life, ect)

So at first KSP misled me a great deal about what was possible in the reality of Rocket and aircraft physics, I was able to make Vtol Tail sitter craft and fly them easily with the aid of an unbeknownst to me at the time impossible Gyroscopic Reaction wheel, unopposed by the non existant stock aerodynamic model.

And so I began to question just how unrealistic KSP was... And a few searches later discovered or confirmed already existing suspicions about the aforementioned unrealities... And set out to find the truth And thankfully that led me to FAR, Real Solar system and all the other realism fixxes for KSP.

I see you chaps working on amazing things, making the KSP I enjoy better and better seemingly without end and want to help, but I've no modding ability whatsoever beyond just changing simple numerical entries in CFGs to make an engine produce more or less thrust ect, so all I can do is read through the threads in wonder and give whatever encouragement I can, and let you know how much what you do is appreciated

So thankyou, keep doing what you do as you wish to do it, and try not to let anyone put you under too much pressure, and above all have fun :-)

I'm hopeing someday to have a really good realistic as possible yet uncomplicated/accessible build of KSP ready for my Nephew when he is old enough, Aiming for realistic, but fun and uncomplicated, Realism isn't the opposite of fun, un-fun is the opposite of fun X-D, Hopefully it will be built on a future 64bit unity 5 KSP so he has the best first impressions of Kerbal Space Program :-)

Edited July 29, 2015 by GorillaZilla

[gilflo]

Good luck and thank you, because it's really a big mess. The thermal conduction reduction to apply from debug menu is different for each vessel and I guess the more the parts, the bigger the mess....

[Nansuchao]

You're right completely. If you build a simple proble, or a simple rocket just for orbit or Mun/Minmus, you'll never (almost) have overheating issues.

BUT if you build a complex probes with two other little probes and a bunch of structural element to keep all togheter, or a big mothership for an interplanetary travel, you can bet KSP will try to burn you out fast...

EDIT: Maybe we can call it "The Krakenheat"

[ferram4]

Alright, so v0.15.4.1 "Goldstein" is out, with some attempt at helping that heating issue, but as I noted, it's a stock bug, so I can't fix it.

Also includes the return of the old aero viz coloring during flight thanks to mjn33 and a few other bugfixes; changelog is pretty short this time.

[BudgetHedgehog]

Nice one, cheers. One thing I never got round to asking you was in the changelog for Glauert, you said "Update win64 check code to MM method". What does this mean for users - does FAR not disable itself completely any more? Does it just show a warning in the loading screen? I looked at the source for Goldstein and Ferri, but I couldn't see any difference in the CompatibilityChecker files..

[Grossbeer]

Ive an issue with structural failure on load.

I have a station which launches and orbits fine. I have 4 Beams with tightly placed Solarpanels (1x6) which extend and perform fine in-flight.

if i change vessel and then change back however the panels and the beam have a structural failure:

[LOG 19:58:41.767] [00:07:46]: Structural failure on linkage between OX-4L 1x6 Photovoltaic Panels and M-Beam 200 I-Beam Pocket Edition.

and all other panels beak too. Admitting this really look quite beautiful :-), my station becomes useless after it.

As i searched the forums i found structural failure only connected to FAR, but i could be wrong.

Here are some pics what happens: 1 Pic when everything was fine, 2-7 after switching back to the station.

http://imgur.com/lMhRRpZ,YqoBbVb,pItdXYh,PDPoWZf,EV3OpVn,SPxXy6M,omnrecV

It seems to me that on load the physic is not applied instantly. When i change to a vessel it seems the camera starts centric to where the center of the vessel is and THEN moving to the center of mass. Maybe the centering applies a force which is calculated by FAR even in that situation. If this wild guess is the case, a kind of delay to calculate the forces after load could do the trick right? (like 1 2 seconds or some frames)

if its not at all connected to FAR please forgive me for bothering you guys. Then i guess i just have to build my vessel a little differend and more stable

here is some extract from my log, if it help.

Game State Saved as persistent[LOG 19:58:35.016] Clouds: Volume Destroyed
[LOG 19:58:35.063] Clouds: Volume Initialized
[LOG 19:58:35.064] Clouds: Volume Enabled=True
[LOG 19:58:35.443] Updating vessel voxel for Mun Station
[LOG 19:58:35.625] SCREENSHOT!!
[LOG 19:58:35.919] Unpacking Mun Station
[LOG 19:58:35.944] RemoteTech: Loading Flightcomputer from persistent!
[LOG 19:58:35.945] RemoteTech: Loading Flightcomputer from persistent!
[LOG 19:58:36.604] Updating vessel voxel for Mun Station
[LOG 19:58:36.843] SCREENSHOT!!
[LOG 19:58:38.103] SCREENSHOT!!
[LOG 19:58:39.244] [00:07:46]: Structural failure on linkage between M-Beam 200 I-Beam Pocket Edition and FL-R1 RCS Fuel Tank.
[LOG 19:58:39.273] RemoteTech: SatelliteManager: OnVesselCreate(2dbbadf7-e274-4007-8f19-ee91fd3f24ae, )
[LOG 19:58:39.313] IR: [ServoController] vessel Mark1-2Pod (Mun Station)
[LOG 19:58:39.314] IR: [ServoController] 0 groups
[LOG 19:58:39.368] RemoteTech: SatelliteManager: OnVesselCreate(dacea68c-7f9c-4b7b-aef5-18e3572a4fcd, )
[LOG 19:58:39.405] IR: [ServoController] vessel Mark1-2Pod (Mun Station)
[LOG 19:58:39.405] IR: [ServoController] 0 groups
[LOG 19:58:39.457] RemoteTech: SatelliteManager: OnVesselCreate(9e6351f1-0582-4a63-bb7b-19a07234460e, )
[LOG 19:58:39.493] IR: [ServoController] vessel Mark1-2Pod (Mun Station)
[LOG 19:58:39.493] IR: [ServoController] 0 groups
[LOG 19:58:39.545] RemoteTech: SatelliteManager: OnVesselCreate(cede18b5-6fed-4be0-b9a1-90c49690e407, )
[LOG 19:58:39.582] IR: [ServoController] vessel Mark1-2Pod (Mun Station)
[LOG 19:58:39.583] IR: [ServoController] 0 groups
[LOG 19:58:39.608] [00:07:46]: Structural failure on linkage between Reflectron KR-7 and FL-R1 RCS Fuel Tank.
[LOG 19:58:39.633] RemoteTech: SatelliteManager: OnVesselCreate(97598ee5-39a0-4332-879c-fc21fd91f9e8, )
[LOG 19:58:39.634] RemoteTech: SatelliteManager: Unregister(ModuleSPUPassive(, cbe627b6-ba0d-49d9-b021-df7cd41c8bde))
[LOG 19:58:39.635] RemoteTech: SatelliteManager: Register(ModuleSPUPassive(, 97598ee5-39a0-4332-879c-fc21fd91f9e8))
[LOG 19:58:39.635] RemoteTech: SatelliteManager: UnregisterProto(97598ee5-39a0-4332-879c-fc21fd91f9e8)
[LOG 19:58:39.636] RemoteTech: SatelliteManager: OnRegister(VesselSatellite(, 97598ee5-39a0-4332-879c-fc21fd91f9e8))
[LOG 19:58:39.636] RemoteTech: NetworkManager: SatelliteRegister(VesselSatellite(, 97598ee5-39a0-4332-879c-fc21fd91f9e8))
[LOG 19:58:39.637] RemoteTech: AntennaManager: Unregister(ModuleRTAntenna(Name: Reflectron KR-7, Guid: cbe627b6-ba0d-49d9-b021-df7cd41c8bde, Dish: 0, Omni: 0, Target: 00000000-0000-0000-0000-000000000000, CosAngle: 0.976296007119933))
[LOG 19:58:39.638] RemoteTech: AntennaManager: OnUnregister(Reflectron KR-7)
[LOG 19:58:39.639] RemoteTech: AntennaManager: Register(ModuleRTAntenna(Name: Reflectron KR-7, Guid: 97598ee5-39a0-4332-879c-fc21fd91f9e8, Dish: 0, Omni: 0, Target: 00000000-0000-0000-0000-000000000000, CosAngle: 0.976296007119933))
[LOG 19:58:39.640] RemoteTech: AntennaManager: OnRegister(Reflectron KR-7)
[LOG 19:58:39.650] IR: [ServoController] vessel Mark1-2Pod (Mun Station)
[LOG 19:58:39.651] IR: [ServoController] 0 groups
[LOG 19:58:39.699] RemoteTech: SatelliteManager: OnVesselCreate(49bb6d95-a1db-46e8-b98f-1472a7d43035, )
[LOG 19:58:39.699] RemoteTech: SatelliteManager: Unregister(ModuleSPUPassive(, cbe627b6-ba0d-49d9-b021-df7cd41c8bde))
[LOG 19:58:39.700] RemoteTech: SatelliteManager: Register(ModuleSPUPassive(, 49bb6d95-a1db-46e8-b98f-1472a7d43035))
[LOG 19:58:39.701] RemoteTech: SatelliteManager: UnregisterProto(49bb6d95-a1db-46e8-b98f-1472a7d43035)
[LOG 19:58:39.701] RemoteTech: SatelliteManager: OnRegister(VesselSatellite(, 49bb6d95-a1db-46e8-b98f-1472a7d43035))
[LOG 19:58:39.702] RemoteTech: NetworkManager: SatelliteRegister(VesselSatellite(, 49bb6d95-a1db-46e8-b98f-1472a7d43035))
[LOG 19:58:39.703] RemoteTech: AntennaManager: Unregister(ModuleRTAntenna(Name: Reflectron KR-7, Guid: cbe627b6-ba0d-49d9-b021-df7cd41c8bde, Dish: 0, Omni: 0, Target: 00000000-0000-0000-0000-000000000000, CosAngle: 0.976296007119933))
[LOG 19:58:39.704] RemoteTech: AntennaManager: OnUnregister(Reflectron KR-7)
[LOG 19:58:39.704] RemoteTech: AntennaManager: Register(ModuleRTAntenna(Name: Reflectron KR-7, Guid: 49bb6d95-a1db-46e8-b98f-1472a7d43035, Dish: 0, Omni: 0, Target: 00000000-0000-0000-0000-000000000000, CosAngle: 0.976296007119933))
[LOG 19:58:39.705] RemoteTech: AntennaManager: OnRegister(Reflectron KR-7)
[LOG 19:58:39.715] IR: [ServoController] vessel Mark1-2Pod (Mun Station)
[LOG 19:58:39.716] IR: [ServoController] 0 groups
[LOG 19:58:39.740] [00:07:46]: Structural failure on linkage between Comms DTS-M1 and FL-R1 RCS Fuel Tank.
[LOG 19:58:39.765] RemoteTech: SatelliteManager: OnVesselCreate(d173daff-f5b2-4f29-bc2d-29eb27ce913a, )
[LOG 19:58:39.766] RemoteTech: SatelliteManager: Unregister(ModuleSPUPassive(, cbe627b6-ba0d-49d9-b021-df7cd41c8bde))
[LOG 19:58:39.766] RemoteTech: SatelliteManager: Register(ModuleSPUPassive(, d173daff-f5b2-4f29-bc2d-29eb27ce913a))
[LOG 19:58:39.767] RemoteTech: SatelliteManager: UnregisterProto(d173daff-f5b2-4f29-bc2d-29eb27ce913a)
[LOG 19:58:39.767] RemoteTech: SatelliteManager: OnRegister(VesselSatellite(, d173daff-f5b2-4f29-bc2d-29eb27ce913a))
[LOG 19:58:39.768] RemoteTech: NetworkManager: SatelliteRegister(VesselSatellite(, d173daff-f5b2-4f29-bc2d-29eb27ce913a))
[LOG 19:58:39.769] RemoteTech: AntennaManager: Unregister(ModuleRTAntenna(Name: Comms DTS-M1, Guid: cbe627b6-ba0d-49d9-b021-df7cd41c8bde, Dish: 0, Omni: 0, Target: 00000000-0000-0000-0000-000000000000, CosAngle: 0.923879532511287))
[LOG 19:58:39.770] RemoteTech: AntennaManager: OnUnregister(Comms DTS-M1)
[LOG 19:58:39.770] RemoteTech: AntennaManager: Register(ModuleRTAntenna(Name: Comms DTS-M1, Guid: d173daff-f5b2-4f29-bc2d-29eb27ce913a, Dish: 0, Omni: 0, Target: 00000000-0000-0000-0000-000000000000, CosAngle: 0.923879532511287))
[LOG 19:58:39.771] RemoteTech: AntennaManager: OnRegister(Comms DTS-M1)
[LOG 19:58:39.784] IR: [ServoController] vessel Mark1-2Pod (Mun Station)
[LOG 19:58:39.785] IR: [ServoController] 0 groups
[LOG 19:58:39.834] RemoteTech: SatelliteManager: OnVesselCreate(de983174-f145-4ca7-ab04-b5089753efa2, )
[LOG 19:58:39.834] RemoteTech: SatelliteManager: Unregister(ModuleSPUPassive(, cbe627b6-ba0d-49d9-b021-df7cd41c8bde))
[LOG 19:58:39.835] RemoteTech: SatelliteManager: Register(ModuleSPUPassive(, de983174-f145-4ca7-ab04-b5089753efa2))
[LOG 19:58:39.836] RemoteTech: SatelliteManager: UnregisterProto(de983174-f145-4ca7-ab04-b5089753efa2)
[LOG 19:58:39.836] RemoteTech: SatelliteManager: OnRegister(VesselSatellite(, de983174-f145-4ca7-ab04-b5089753efa2))
[LOG 19:58:39.837] RemoteTech: NetworkManager: SatelliteRegister(VesselSatellite(, de983174-f145-4ca7-ab04-b5089753efa2))
[LOG 19:58:39.837] RemoteTech: AntennaManager: Unregister(ModuleRTAntenna(Name: Comms DTS-M1, Guid: cbe627b6-ba0d-49d9-b021-df7cd41c8bde, Dish: 0, Omni: 0, Target: 00000000-0000-0000-0000-000000000000, CosAngle: 0.923879532511287))
[LOG 19:58:39.838] RemoteTech: AntennaManager: OnUnregister(Comms DTS-M1)
[LOG 19:58:39.839] RemoteTech: AntennaManager: Register(ModuleRTAntenna(Name: Comms DTS-M1, Guid: de983174-f145-4ca7-ab04-b5089753efa2, Dish: 0, Omni: 0, Target: 00000000-0000-0000-0000-000000000000, CosAngle: 0.923879532511287))
[LOG 19:58:39.840] RemoteTech: AntennaManager: OnRegister(Comms DTS-M1)
[LOG 19:58:39.853] IR: [ServoController] vessel Mark1-2Pod (Mun Station)
[LOG 19:58:39.854] IR: [ServoController] 0 groups
[LOG 19:58:39.855] [ModularFlightIntegrator] MFI Start
[LOG 19:58:39.855] [ModularFlightIntegrator] Start. Current modules coVesselModule : 
  ModularFI.ModularFlightIntegrator active=True order=0
  FerramAerospaceResearch.FARAeroComponents.FARVesselAero active=True order=0
  FerramAerospaceResearch.FARGUI.FARFlightGUI.FlightGUI active=True order=0


[LOG 19:58:39.857] [ModularFlightIntegrator] MFI Start
[LOG 19:58:39.857] [ModularFlightIntegrator] Start. Current modules coVesselModule : 
  ModularFI.ModularFlightIntegrator active=True order=0
  FerramAerospaceResearch.FARAeroComponents.FARVesselAero active=True order=0
  FerramAerospaceResearch.FARGUI.FARFlightGUI.FlightGUI active=True order=0


[LOG 19:58:39.859] [ModularFlightIntegrator] MFI Start
[LOG 19:58:39.859] [ModularFlightIntegrator] Start. Current modules coVesselModule : 
  ModularFI.ModularFlightIntegrator active=True order=0
  FerramAerospaceResearch.FARAeroComponents.FARVesselAero active=True order=0
  FerramAerospaceResearch.FARGUI.FARFlightGUI.FlightGUI active=True order=0


[LOG 19:58:39.861] [ModularFlightIntegrator] MFI Start
[LOG 19:58:39.861] [ModularFlightIntegrator] Start. Current modules coVesselModule : 
  ModularFI.ModularFlightIntegrator active=True order=0
  FerramAerospaceResearch.FARAeroComponents.FARVesselAero active=True order=0
  FerramAerospaceResearch.FARGUI.FARFlightGUI.FlightGUI active=True order=0


[LOG 19:58:39.863] [ModularFlightIntegrator] MFI Start
[LOG 19:58:39.863] [ModularFlightIntegrator] Start. Current modules coVesselModule : 
  ModularFI.ModularFlightIntegrator active=True order=0
  FerramAerospaceResearch.FARAeroComponents.FARVesselAero active=True order=0
  FerramAerospaceResearch.FARGUI.FARFlightGUI.FlightGUI active=True order=0


[LOG 19:58:39.865] [ModularFlightIntegrator] MFI Start
[LOG 19:58:39.865] [ModularFlightIntegrator] Start. Current modules coVesselModule : 
  ModularFI.ModularFlightIntegrator active=True order=0
  FerramAerospaceResearch.FARAeroComponents.FARVesselAero active=True order=0
  FerramAerospaceResearch.FARGUI.FARFlightGUI.FlightGUI active=True order=0


[LOG 19:58:39.867] [ModularFlightIntegrator] MFI Start
[LOG 19:58:39.867] [ModularFlightIntegrator] Start. Current modules coVesselModule : 
  ModularFI.ModularFlightIntegrator active=True order=0
  FerramAerospaceResearch.FARAeroComponents.FARVesselAero active=True order=0
  FerramAerospaceResearch.FARGUI.FARFlightGUI.FlightGUI active=True order=0


[LOG 19:58:39.869] [ModularFlightIntegrator] MFI Start
[LOG 19:58:39.869] [ModularFlightIntegrator] Start. Current modules coVesselModule : 
  ModularFI.ModularFlightIntegrator active=True order=0
  FerramAerospaceResearch.FARAeroComponents.FARVesselAero active=True order=0
  FerramAerospaceResearch.FARGUI.FARFlightGUI.FlightGUI active=True order=0


[LOG 19:58:39.876] Updating vessel voxel for Mun Station
[LOG 19:58:40.041] [CHATR] Capsule starts the exchange...
[LOG 19:58:40.113] SCREENSHOT!!
[LOG 19:58:40.172] [00:07:46]: Structural failure on linkage between M-Beam 200 I-Beam Pocket Edition and M-Beam 200 I-Beam Pocket Edition.
[LOG 19:58:40.177] RemoteTech: SatelliteManager: OnVesselCreate(10a3eca8-a63f-4d78-8bda-6adae4d802bd, )
[LOG 19:58:40.203] [00:07:46]: Structural failure on linkage between OX-4L 1x6 Photovoltaic Panels and M-Beam 200 I-Beam Pocket Edition.
[LOG 19:58:40.206] RemoteTech: SatelliteManager: OnVesselCreate(0154ffb2-f039-4a3c-88bd-5a4a6bbd2dbe, )
[LOG 19:58:40.212] RemoteTech: SatelliteManager: OnVesselCreate(012d4de2-0a02-4f43-af7c-96029a635d9d, )
[LOG 19:58:40.218] RemoteTech: SatelliteManager: OnVesselCreate(9cb116c2-2b94-465a-936e-cbca6415b815, )
[LOG 19:58:40.224] RemoteTech: SatelliteManager: OnVesselCreate(ec251816-3475-4b03-90ea-ba6a365619ca, )
[LOG 19:58:40.231] RemoteTech: SatelliteManager: OnVesselCreate(257f0910-2ee1-40be-ac12-34af5d9b6a50, )
[LOG 19:58:40.237] RemoteTech: SatelliteManager: OnVesselCreate(39ba4ea0-4ec5-4889-a58e-6aae98321da5, )
[LOG 19:58:40.243] RemoteTech: SatelliteManager: OnVesselCreate(8a4d0f6d-8d84-4c58-816c-8b3569369fc9, )
[LOG 19:58:40.249] RemoteTech: SatelliteManager: OnVesselCreate(98decdf7-10d2-4407-9dd7-f1486a7c0f51, )
[LOG 19:58:40.252] [ModularFlightIntegrator] MFI Start

[ferram4]

If it fails in space, then FAR is not the cause. FAR does not apply any forces if the density is 0.

In addition, the only structural failures that FAR applies directly note that the failure is due to aerodynamic forces; none of yours do. Your issues are either due to a stock bug or due to another mod, not FAR.

[sashan]

I've just had this bug. Root is the cockpit, it's from OPT spaceplane pack and it worked perfectly on this same plane yesterday. Previous version of FAR, I think it's Glauert?

[ferram4]

Not possible. There were no changes to the code that calculate the main axis between 0.15.4 and 0.15.4.1. I see that the FAR icon isn't showing up for you; did you install this using CKAN, or make any error in a manual install?

[Hodo]

Not sure if I want to get 15.4.1

Seeing as I fixed the heating problem by just installing DRE. LOL

On a serious note, Ferram4 what is in the plans for FAR in the near future? Because you have already done an outstanding job and are honestly a true beacon of light in this community.

[run1235]

it seems that whenever my ship breaks apart the cockpit always survives and seems to have 0 drag as it will continue at a set speed in a straight line. this has happened multiple times using cockpits from Kashcorp. i'm posting this report here as it is a problem with the aerodynamics that was adjusted by far. if needed i will also report this on the kashcorp thread. i'm using ksp1.0.4 x32 on windows 7 64x. all mods were installed/updated using ckan.

[Gryphon]

it seems that whenever my ship breaks apart the cockpit always survives and seems to have 0 drag as it will continue at a set speed in a straight line. this has happened multiple times using cockpits from Kashcorp. i'm posting this report here as it is a problem with the aerodynamics that was adjusted by far. if needed i will also report this on the kashcorp thread. i'm using ksp1.0.4 x32 on windows 7 64x. all mods were installed/updated using ckan.

Keep in mind that some mods, including FAR, have had problems when installed via CKAN. You might try manually installing your mods (especially FAR) to make sure that is not is the cause of your issue.

- - - Updated - - -

Oh, and I'd suggest following the instructions found here so that you can a) maybe fix your problem yourself, and provide the information required for folks to help you with your problem.

In addition to those instructions, make sure you identify the minimum set of mods required to reproduce your issue. (In this case, that would ideally be only FAR and the mod providing the part you see issues with.)

Speaking of that, isn't Kashcorp responsible for like 5 different mods? Which one are you having an issue with?