silentdeth

A video series covering everything you need to know about FAR. Individual videos: We cover center of life, and angle of incidence. Both of which are related to wing placement. jWe cover intakes: How many you need and the different types. Engines: How the thrust changes with speed, ect. Landing Gear: Pro's and Con's of the different configurations. jWe cover control surfaces and various forms of swept wings. jWe go over a list of important mods for use with FAR. jWe cover the dreaded stability derivatives page. j- - - Updated - - - We cover the FAR graph, how it interacts with stability derivatives page, and how it can be used to set up flaps and spoilers. http://youtu.be/a43OkEBZJj4?list=PLZ1Y6YBp3EkbXt1gu9Sm36IkzeUPHxi_ j To give some examples of the topics discussed in previous episodes, we do some case studies. This time a simple jet. http://youtu.be/vjDIvYjYSwg?list=PLZ1Y6YBp3EkbXt1gu9Sm36IkzeUPHxi_ j We do another case study, this time a high speed, high altitude world traveler. http://youtu.be/SLyB3bRXID8?list=PLZ1Y6YBp3EkbXt1gu9Sm36IkzeUPHxi_ j Another case study, this time a early single stage to orbit craft. http://youtu.be/6d33H3qxcfE?list=PLZ1Y6YBp3EkbXt1gu9Sm36IkzeUPHxi_ j Another case study, this time a SSTO capable of lifting an orange tank into orbit. http://youtu.be/fR1qhPU1vok?list=PLZ1Y6YBp3EkbXt1gu9Sm36IkzeUPHxi_ j Another case study, this time a vertical take off and landing craft for getting to those hard to reach places. http://youtu.be/ZU-lE8BfxM4?list=PLZ1Y6YBp3EkbXt1gu9Sm36IkzeUPHxi_j

Where can i find documentation for this?

Your equation for a, the semi-major axis, is incorrect for the circular orbit you wish to achieve. You need to calculate the semi-major axis for the desired orbit, not use the semi-major axis of the current orbit if you wish to use that form of the equation. Also there is no need to include the mass of the ship in your calculation of orbital speed, it is negligible relative to the mass of the body you are orbiting. For a circular orbit the equation for orbital velocity simplifies to: set v1 to sqrt(BODY:MU/(APOAPSIS + BODY:RADIUS)).

Is there a way to turn off FAR automatically setting the flaps at take off?

I'm working on a FAR tutorial for youtube and was wondering if anyone had any suggestion for what it should cover. Anything that they have, or had found it difficult to find the answers to. I already intend to cover the basics, and all the screens, ect. but I'm looking for things like Mach tuck, things that are not really covered in other tutorials and require a lot of searching to found out about. In essence I want to cover everything someone needs to know so that they don't have to go searching around for a bunch of different tutorials.

Have you edited the files in any way? My first thought is that it is missing a }. You are failing the contract because it is labeling both sats as Kerbol CommSat II.

I mean Boolean or requirement, either the player must have completed the InnerSystemSat contract OR they need >0.2 coverage. I guess your saying to have >.2 coverage they must have done so? I'm using FAR and deadly reentry so if I want to have a small UAV the atmo safe dishes are not really an option as they cause too many issues with the aerodynamics, thus I find myself needing to build another sat network just for dealing with UAVs. This is in addition to a traditional dish based comsat network, meaning the short range sats do not have to talk to each other, they can bounce signals off of the dish sats. The requirements tend to involve a bit of math picking the fewest number of sats that cover most of the surface without ever being more than 500km from any point in their area of coverage at sea level. It results in, more or less, a single solution. Thus I would like the option of one, being payed for something I have to do anyway, and two having a contract with an OrbitGenerator telling me the orbit I need to be in, and how many sats I need. I attempted to make my own for Kerbin... but it did not go as planned. (It seems you cannot use the HasAntenna parameter without specifying a target, this is a problem if you specify an Omni antenna.)

For the InnerSystemSat contract you have it set to only unlock with the 60Gm or longer range antennas, it should be unlocked with the Communotron 88-88, the 40Gm antenna as the longest distant target is Duna at 35Gm according to the wiki. This same requirement error is duplicated in the contracts for Duna, Ike, Eve, Gilly, and Moho. The Dres contract also requires a longer than necessary range antenna, it needs the 60Gm one(s). I would suggest adding the requirement for the InnerSystemSat contract to be complete, or that the selected body have a coverage > 0.2 before offering the specific body sat contracts. Just to ensure someone doesn't mistakenly do them out of order. I would also suggest adding a short range ComSat network contract for every place that has an atmosphere. The 500km Reflectron DP-10 is the only onmi antenna that can be used in an atmosphere, and most the current contracts put the ComSats outside of that range. You can use the debug menu, alt+F12 to complete the contract, I did the exact same thing.

Getting an odd error. I can attach a all moving surfaces to a part, I can attach a single wing to a part, but if I try to attach two wings using symmetry things go wonkey, the cost is added but the wings are not attached. Error log below. [LOG 12:17:02.344] [SCANsat] start: in editor [LOG 12:17:02.344] [SCANsat] sensorType: 0 fov: 0 min_alt: 0 max_alt: 0 best_alt: 0 power: 0.05 [LOG 12:17:02.345] Tac.LifeSupportModule[FFF74192][251.47]: OnStart: Editor [LOG 12:17:09.895] deltaWing added to ship - part count: 2 [LOG 12:17:09.896] SAFix.onPartAttach(): Host = deltaWing | Target = Mark2Cockpit | Symmetry Count = 1 [LOG 12:17:09.897] stage count is: 0 [LOG 12:17:09.897] deltaWing added to ship - part count: 3 [LOG 12:17:09.898] SAFix.onPartAttach(): Host = deltaWing | Target = Mark2Cockpit | Symmetry Count = 1 [LOG 12:17:09.898] [VersionTaggedType] found KSPAPIExtensions.PartMessage.KnownPartMarker_1_7_2_0 for KSPAPIExtensions.PartMessage.KnownPartMarker [LOG 12:17:09.899] [VersionTaggedType] found KSPAPIExtensions.PartMessage.KnownPartMarker_1_7_2_0 for KSPAPIExtensions.PartMessage.KnownPartMarker [LOG 12:17:09.901] stage count is: 0 [LOG 12:17:11.042] deleting part deltaWing [LOG 12:17:12.411] deltaWing added to ship - part count: 2 [LOG 12:17:12.412] SAFix.onPartAttach(): Host = deltaWing | Target = Mark2Cockpit | Symmetry Count = 1 [LOG 12:17:12.413] stage count is: 0 [LOG 12:17:12.413] deltaWing added to ship - part count: 3 [LOG 12:17:12.414] SAFix.onPartAttach(): Host = deltaWing | Target = Mark2Cockpit | Symmetry Count = 1 [LOG 12:17:12.415] [VersionTaggedType] found KSPAPIExtensions.PartMessage.KnownPartMarker_1_7_2_0 for KSPAPIExtensions.PartMessage.KnownPartMarker [LOG 12:17:12.416] [VersionTaggedType] found KSPAPIExtensions.PartMessage.KnownPartMarker_1_7_2_0 for KSPAPIExtensions.PartMessage.KnownPartMarker [LOG 12:17:12.416] stage count is: 0 [LOG 12:17:13.193] deleting part deltaWing [LOG 12:17:14.197] deleting part deltaWing [LOG 12:17:18.248] B9.Aero.Wing.Procedural.TypeC added to ship - part count: 2 [LOG 12:17:18.248] SAFix.onPartAttach(): Host = B9.Aero.Wing.Procedural.TypeC | Target = Mark2Cockpit | Symmetry Count = 1 [LOG 12:17:18.261] stage count is: 0 [LOG 12:17:18.262] B9.Aero.Wing.Procedural.TypeC added to ship - part count: 3 [LOG 12:17:18.262] SAFix.onPartAttach(): Host = B9.Aero.Wing.Procedural.TypeC | Target = Mark2Cockpit | Symmetry Count = 1 [LOG 12:17:18.263] [VersionTaggedType] found KSPAPIExtensions.PartMessage.KnownPartMarker_1_7_2_0 for KSPAPIExtensions.PartMessage.KnownPartMarker [LOG 12:17:18.264] [VersionTaggedType] found KSPAPIExtensions.PartMessage.KnownPartMarker_1_7_2_0 for KSPAPIExtensions.PartMessage.KnownPartMarker [LOG 12:17:18.277] stage count is: 0 [LOG 12:17:19.429] deleting part B9.Aero.Wing.Procedural.TypeC [LOG 12:17:20.492] deleting part B9.Aero.Wing.Procedural.TypeC [LOG 12:17:23.149] B9.Aero.Wing.Procedural.TypeA added to ship - part count: 2 [LOG 12:17:23.150] SAFix.onPartAttach(): Host = B9.Aero.Wing.Procedural.TypeA | Target = Mark2Cockpit | Symmetry Count = 1 [LOG 12:17:23.162] stage count is: 0 [LOG 12:17:23.163] B9.Aero.Wing.Procedural.TypeA added to ship - part count: 3 [LOG 12:17:23.164] SAFix.onPartAttach(): Host = B9.Aero.Wing.Procedural.TypeA | Target = Mark2Cockpit | Symmetry Count = 1 [EXC 12:17:23.165] ArgumentOutOfRangeException: Argument is out of range. Parameter name: index System.Collections.Generic.List`1[PartModule].get_Item (Int32 index) PartModuleList.get_Item (Int32 index) ClawKSP.SAFix.UpdatePartAndChildren (.Part SourcePart, .Part UpdatePart, SymmetryMethod SymMethod) ClawKSP.SAFix.onPartAttach (HostTargetAction`2 AttachedPart) EventData`1[GameEvents+HostTargetAction`2[Part,Part]].Fire (HostTargetAction`2 data) Part.setParent (.Part p) EditorLogic.attachPart (.Part part, . attach) EditorLogic.attachSymParts (.[] cAttaches) EditorLogic.<SetupFSM>m__B4 () KerbalFSM.RunEvent (.KFSMEvent evt) KerbalFSM.updateFSM (KFSMUpdateMode mode) KerbalFSM.UpdateFSM () EditorLogic.Update () [LOG 12:17:23.543] deleting part B9.Aero.Wing.Procedural.TypeA [LOG 12:17:24.794] deleting part B9.Aero.Wing.Procedural.TypeA

Can you not also change maxIntakeSpeed? I understood that had an effect, or is that outdated information?

Thanks for the many helpful responses.

I'm attempting to get more versed in FAR, and have a couple of questions: In stock it is easy to determine how much lifting surface you need, 1 unit of lift per metric ton. I'm wondering is there similar rule of thumb for FAR? Something like square meters of lifting surface per metric ton, or square meters of lifting surface per metric ton per unit of thrust? Since, as I understand it, the lift and drag coefficients in the graphs are dimensionless, it doesn't really tell me how much lift I am getting, just the relative lift to drag, correct?

Having an issue when I right click on a procedural wing, it doesn't show a right click menu, and prevents any right click menu on any other parts until I exit and reenter the SPH. [LOG 15:50:34.094] [ScenarioDestructibles]: Loading... 0 objects registered [LOG 15:50:34.095] [ScenarioUpgradeableFacilities]: Loading... 0 objects registered [LOG 15:50:34.102] KerbalEngineer -> BuildToolbar->OnGuiAppLauncherReady [LOG 15:50:34.223] TechManager: Skipped 43 parts with multiple assignments [LOG 15:50:34.762] [AS] removing 0 unused target parts [EXC 15:50:50.394] NullReferenceException: Object reference not set to an instance of an object UIPartActionResourceItem.SetSymCounterpartsAmount (Double amount) UIPartActionResourceEditor.OnSliderChanged (IUIObject obj) UIPartActionResourceEditor.Setup (.UIPartActionWindow window, .Part part, UI_Scene scene, .UI_Control control, .PartResource resource) KSPAPIExtensions.UIPartActionResourceEditorImproved.Setup (.UIPartActionWindow window, .Part part, UI_Scene scene, .UI_Control control, .PartResource resource) UIPartActionWindow.SetupResourceEditorControl (.PartResource r, Int32 row) UIPartActionWindow.SetupResourceControl (.PartResource r, Int32 row) UIPartActionWindow.SetupResourceControls (.PartResource r, System.Int32& row) UIPartActionWindow.CreatePartList () UIPartActionWindow.Setup (.Part part, DisplayType type, UI_Scene scene) UIPartActionController.CreatePartUI (.Part part, DisplayType type, UI_Scene scene) UIPartActionController.SelectPart (.Part part, Boolean allowMultiple) UIPartActionController.HandleMouseClick (UnityEngine.Camera cam, Boolean allowMultiple) UIPartActionController+ .MoveNext () [LOG 15:51:53.207] Game State Saved to saves/Temp/persistent

Thanks I'll give it a try.

How do I make a module manager config to increase the range I can collect science from the goo canister and the material science bay? I'm tired of having to shove my kerbal's big green head all the way into the science jr. to collect data.

Is there any way variable geometry wings could be added to this? Something like having wings switch from one shape to another via an action group? You may wish to look into the mod oriented tech tree mod, it puts this mod at 90 science.

I tend to agree with the above post, if you can make a regex thing that can fix the craft files in 5 mins, sure do it. But, if it is going to take an hour or few, then I'd rather you spent your time working on making the mod more awesome.

This looks fantastic, I can't wait for a stable version to use in my Let's Play.

RoboTruss and RoboTube style/size docking adapters would be useful to allow us to assemble things far from home. Also, is it possible to release the untextured/solid colored, but functional parts as well? They still look better with the RoboTubes and RoboTrusses, and I won't have to worry about ship ceasing to function due to model changes when this is finished.

thanks, that was what I was looking for.

Not quite, those are 3.75m to multiple 3.75m adapters. I'm looking for 3.75m to multiple 1.25m adapters.

Is it possible to add 3.75m to 1.25m versions? I've edited the 2.5m (TRV-400L-Quad-Adapter) part's cfg file to create a 3.75m to 7x 1.25m adapter, but I lack both the know-how and artistic skill to create a new model for it. The coordinates for the nodes are there if someone can do the model. [noparse] PART { // --- general parameters --- name = adapterHugeSmallSeptet module = Part author = Necessity // --- asset parameters --- mesh = model.mu scale = 0.666666666667 rescaleFactor = 1.5 // --- node definitions --- // definition format is Position X, Position Y, Position Z, Up X, Up Y, Up Z node_stack_top = 0.0, 0.0, 0.0, 0.0, 1.0, 0.0, 3 node_stack_bottom01 = 1.275, -1.125, 0, 0.0, 1.0, 0.0, 1 node_stack_bottom02 = 0.638, -1.125, 1.104, 0.0, 1.0, 0.0, 1 node_stack_bottom03 = -0.638, -1.125, 1.104, 0.0, 1.0, 0.0, 1 node_stack_bottom04 = -1.275, -1.125, 0, 0.0, 1.0, 0.0, 1 node_stack_bottom05 = -0.638, -1.125, -1.104, 0.0, 1.0, 0.0, 1 node_stack_bottom06 = 0.638, -1.125, -1.104, 0.0, 1.0, 0.0, 1 node_stack_bottom07 = 0, -1.125, 0, 0.0, 1.0, 0.0, 1 TechRequired = veryHeavyRocketry entryCost = 8800 cost = 2600 category = 2 subcategory = 0 title = TVR-700H Stack Septet-Adapter manufacturer = O.M.B. Demolition Enterprises description = After realizing 'larger circles' wasn't a very patentable concept, O.M.B. Enterprises rolled out a new line of ingenious multi-connector adapters to fit Rockomax sized parts. Lawsuit still pending. Converts a single 3.75m stack into seven 1.25m stacks. allowSrfAttach, allowCollision attachRules = 1,0,1,0,0 stackSymmetry = 4 //for stock, 6 for mods that have 5x and 7x symmetry mass = 0.3 dragModelType = default maximum_drag = 0.3 minimum_drag = 0.3 angularDrag = 3 crashTolerance = 12 maxTemp = 3400 fuelCrossFeed = True NoCrossFeedNodeKey = bottom } [/noparse]

Is it possible to add 3.75m versions of the TRV-400L-Quad-Adapter style parts? I've edited the 2.5m part's cfg file to create a 3.75m to 7x 1.25m adapter, but I lack both the know-how and artistic skill to create a new model for it. [noparse] PART { // --- general parameters --- name = adapterHugeSmallSeptet module = Part author = Necessity // --- asset parameters --- mesh = model.mu scale = 0.666666666667 rescaleFactor = 1.5 // --- node definitions --- // definition format is Position X, Position Y, Position Z, Up X, Up Y, Up Z node_stack_top = 0.0, 0.0, 0.0, 0.0, 1.0, 0.0, 3 node_stack_bottom01 = 1.275, -1.125, 0, 0.0, 1.0, 0.0, 1 node_stack_bottom02 = 0.638, -1.125, 1.104, 0.0, 1.0, 0.0, 1 node_stack_bottom03 = -0.638, -1.125, 1.104, 0.0, 1.0, 0.0, 1 node_stack_bottom04 = -1.275, -1.125, 0, 0.0, 1.0, 0.0, 1 node_stack_bottom05 = -0.638, -1.125, -1.104, 0.0, 1.0, 0.0, 1 node_stack_bottom06 = 0.638, -1.125, -1.104, 0.0, 1.0, 0.0, 1 node_stack_bottom07 = 0, -1.125, 0, 0.0, 1.0, 0.0, 1 TechRequired = veryHeavyRocketry entryCost = 8800 cost = 2600 category = 2 subcategory = 0 title = TVR-700H Stack Septet-Adapter manufacturer = O.M.B. Demolition Enterprises description = After realizing 'larger circles' wasn't a very patentable concept, O.M.B. Enterprises rolled out a new line of ingenious multi-connector adapters to fit Rockomax sized parts. Lawsuit still pending. Converts a single 3.75m stack into seven 1.25m stacks. allowSrfAttach, allowCollision attachRules = 1,0,1,0,0 stackSymmetry = 4 //for stock, 6 for mods that have 5x and 7x symmetry mass = 0.3 dragModelType = default maximum_drag = 0.3 minimum_drag = 0.3 angularDrag = 3 crashTolerance = 12 maxTemp = 3400 fuelCrossFeed = True NoCrossFeedNodeKey = bottom } [/noparse]

These spin in the opposite direction of winglet force.