Jump to content

Search the Community

Showing results for tags 'failure'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • General
    • Announcements
    • Welcome Aboard
  • Kerbal Space Program 2
    • KSP2 Dev Updates
    • KSP2 Discussion
    • KSP2 Suggestions and Development Discussion
    • Challenges & Mission Ideas
    • The KSP2 Spacecraft Exchange
    • Mission Reports
    • KSP2 Prelaunch Archive
  • Kerbal Space Program 2 Gameplay & Technical Support
    • KSP2 Gameplay Questions and Tutorials
    • KSP2 Technical Support (PC, unmodded installs)
    • KSP2 Technical Support (PC, modded installs)
  • Kerbal Space Program 2 Mods
    • KSP2 Mod Discussions
    • KSP2 Mod Releases
    • KSP2 Mod Development
  • Kerbal Space Program 1
    • KSP1 The Daily Kerbal
    • KSP1 Discussion
    • KSP1 Suggestions & Development Discussion
    • KSP1 Challenges & Mission ideas
    • KSP1 The Spacecraft Exchange
    • KSP1 Mission Reports
    • KSP1 Gameplay and Technical Support
    • KSP1 Mods
    • KSP1 Expansions
  • Community
    • Science & Spaceflight
    • Kerbal Network
    • The Lounge
    • KSP Fan Works
  • International
    • International
  • KerbalEDU
    • KerbalEDU
    • KerbalEDU Website


There are no results to display.

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



Website URL



About me



Found 11 results

  1. OhScrap! (OHS) (formerly UPFM) ScrapYard (SYD) based part failure and maintenance addon plugin for Kerbal Space Program. By zer0Kerbal, originally by @severedsolo adopted with express permission and brought to you by KerbSimpleCo Preamble by @severedsolo Features See more YouTube video Lu Localization Installation Directions 1 Dependencies ScrapYard (SYD) to keep track of how many times a part has been built/recovered so that is a hard dependency. (obtained separately) Either 2 Module Manager /L Module Manager Kerbal Space Program 3 Recommends Kerbal Construction Time designed with this with in mind, so would recommend that mod (make sure you use the latest dev version) StageRecovery If you plan to actually re-use your parts (and have them fail), you'll probably want StageRecovery too KRASH Supports USI MKS Suggests On Demand Fuel Cells (ODFC) GPO (Goo Pumps & Oils') Speed Pump (GPO) SimpleConstruction! (SCON) SimpleLogistics! (SLOG) Kaboom! (BOOM) Papa Kerballini's Pizza (PIZZA) TweakScale (twk) Tags plugin, config, information, editor, sound, career, crewed, uncrewed red box below is a link to forum post on how to get support Be Kind: Lithobrake, not jakebrake! Keep your Module Manager up to date Credits and Special Thanks @severedsolo for creating this glorious bad-day plugin! see Attribution.md for more Legal Mumbo Jumbo (License provenance) How to support this and other great mods by zer0Kerbal Connect with me Track progress: issues here and projects here along with The Short List Release Schedule this isn't a mod. ;P↩︎ Be Kind: Lithobrake, not jakebrake! Keep your Module Manager up to date!↩︎ may work on other versions (YMMV)↩︎
  2. So it's been about 2 1/2 years since I last played KSP 1. When KSP 2 came out I started playing that, but found it wasn't ready for me, but that got me interested in going back I'm doing KSP1 again. I'm about 1/2 to 2/3 through the tech tree and I'm at the point where I want to start doing some space construction. So far just little stuff, practicing and developing the techniques necessary. So I've run into a problem, I've got my engineer on EVA, I've got my construction window open, and I'm ready to move a part from the storage container over to my Kerbal and as soon as I do that everything blows up. I lose total control over my engineer, he freezes and goes drifting and tumbling off into space. So I tried this at least half a dozen times or more, I've quit the program and restarted it, shut the computer down and restarted it, opened a new save and a older save. Tried it at a space station and then with a spaceship free in orbit. What seems odd is that the space station or the spaceship seems pretty stable in orbit but the engineer almost appears as if he's going in a retro direction keeping pace with rotation of the planet. It's almost like he was planet side and everything else is in space. So I know that there have been issues with things in the past, but I've never experienced it. Is this something new or is it a conflict or a bug with mods? Other than that everything seems to be Operating okay. Mod list ASET Consolidated Agency (ASETAgency v2.0.2) ASET Consolidated Props Pack (ASETProps v2.0.7) Breaking Ground (BreakingGround-DLC 1.7.1) Camera Focus Changer (CameraFocusChanger 1: ClickThrough Blocker (ClickThroughBlocker 1: Community Category Kit (CommunityCategoryKit v112.0.1) Easy Vessel Switch (EVS) (EasyVesselSwitch 2.3) Filter Extensions - Plugin (FilterExtensions 3.2.9) Fuel Tank Expansion Rebuilt (MunarIndustriesFTX Harmony 2 (Harmony2 Interstellar Fuel Switch Core (InterstellarFuelSwitch-Core 3.30.0) Kerbal Attachment System (KAS 1.12) Kerbal Engineer Redux (KerbalEngineerRedux Kerbal Inventory System (KIS 1.29) KSP Community Fixes (KSPCommunityFixes 1.34.1) KSP Recall (KSP-Recall v0.4.0.1) Making History (MakingHistory-DLC 1.12.1) MechJeb 2 (MechJeb2 Minimum Ambient Lighting Updated (MinAmbLightUpd Module Manager (ModuleManager 4.2.3) Procedural Parts (ProceduralParts v2.5.8.0) Procedural Parts - Hazard Tanks Textures (HazardTanksTextures 1.0) Procedural Parts - Ven's Revamp Style Textures (VensStylePPTextures 1.1) RasterPropMonitor Core (RasterPropMonitor-Core 1:v0.31.13.4) SpaceTux Library (SpaceTuxLibrary Surface Mounted Lights (surfacelights 1.19) The Janitor's Closet (JanitorsCloset 0.3.8) Toolbar (Toolbar 1: Toolbar Controller (ToolbarController 1: Tracking Station Evolved (TrackingStationEvolved 7.0) TweakScale - Rescale Everything! (TweakScale v2.4.7.4) TweakScale Redistributable (TweakScale-Redist v2.4.7.4)
  3. how i lost jeb: so recently i was playing KSP and doing yet another minmus mission when i realised i had like 2000-1000 delta v left, which i thought was more then enough to go to the mun, so i went to the mun and tried to leave with about 800 delta v left, i escaped but ran out of fuel, so i used bob kerman's jetpack to push it, bob, some random kerbal on the ladder, and the mk.3 capsule were constantly switching jetpacks until i accidently moved the capsule causing both kerbals to get flung, after a while of trying to save both kerbals, jeb ended up the one needing saving and with no EVA fuel. TLDR: i flew too close to kerbol (the sun) in terms of what i can do, flung 2 kerbals across the universe, somehow only lost jeb, now jeb shall happily float around kerbin and cause i left the capsule for a while its now somehow orbiting the sun. ( i am complete trash lol)
  4. 1 of 3 parachutes failed to deploy yesterday. They were all on the same craft, snapped on with the triangular symmetry tool. All on the same stage. One of them would not deploy even when manually hitting deploy. It was not damaged. Identical clone to the other two as far as I can tell. The Kerbals did survive. Good thing it came down over water. Do we have random part failures?
  5. astra 3.3, firefly alpha, vanguard tv3 and many others..... Put pictures of big oofs but no pictures of oofs with humans or animals as we commemorate them in how far we come from them
  6. I want to have some sort of Failures with Aircraft Engines (for example i wanna add support for such thing to My mod) The mod should -just include basic failure system (or it should have availability to turn anything besides failures off) -it should not be a big mod Bonus: If the mod can do particles or animations when the part fails, it would be a bonus TL;DR: Searching for Simple Part Failure Mod
  7. A simplified but more comprehensive concept for a new breed of part failure mechanics. Failure is facilitated by interaction with planet mods or the universe and not (as usual) letting yourself be taken by surprise by an RNG and a countdown machine. Its purpose is to add more tangible gameplay value to planets. This rises from an unrelated discussion on a planet mod's Discord server, of how planetary rings in this KSP could be more tangible and hence, hazardous, and I saw a connection back to my earlier post, linked here: Some folks I discussed with: @WarriorSabe @StarCrusher96 Some folks who may find this evolved concept interesting: @linuxgurugamer (who showed interest in taking a shot at coding the predecessor), @Angel-125 (who owns a mod that contains a whipple shield and interstellar engines: WBI DSEV), @R-T-B @prestja (Kopernicus devs). The component concepts that came up were as follows: Durability How a part fails is decided by the health gauge itself and the saturation and mitigation system. In a nutshell, saturation is how much punishment the part can take before it starts actually failing (this has its own gauge). If saturation is below a certain minimum, no damage is taken. If that minimum is exceeded, health (and if possible, other stats) start falling. The higher the saturation bar is, the faster the positive stats fall. The relevant stats to implement would be crash tolerance, heat tolerance, joint strength. A bonus feature of the impact system is that parts with certain attributes or modules, if hit with seemingly non-lethal force, can still stand to have modules shutdown or status flags raised that can be used by other mods to represent a situation. Example: an exposed crew cabin gets hit: the glass shatters, all its resources empty out, its modules stop working, and a life support mod uses the flag (or more) for a compromised habitat. It will require a kerbal with the relevant trait and skill to "repair" the part and clear the status flag(s). The part could have a flag that requires a scientist, and a flag that requires an engineer. While these flags up, modules can refuse to start, and resources can continue to empty out. Debris Fields Assuming planetary rings and Kopernicus asteroid fields could have tangible micro-meteor debris fields, their threat would take the form of raycasts occurring, with random vectors, speeds and virtual masses, trying to strike the active vessel. The saturation and mitigation system are virtually not present when traveling at leisurely low interplanetary speeds. It's mostly the small and basic matter of building your ship to be extra sturdy (whether by using struts, structural parts with higher crash tolerance, or involving ablative hull plating in your ship designs). These systems begin to become prominent when encountering extremely dense debris fields such as the proto-planetary discs of young stars. The faster you go, the more the impacts tend towards the frontal surfaces of your ship, and saturation of your forward shields become a concern. Visualization: A basic and sufficient visualization for an impact would be sparks (there's an engine flameout plume or 2 for that, for example) at the point of impact. The planet-level collision areas would ideally be setup like resource bands for ISRU or Kopernicus asteroid fields themselves, but instead of customizing resources, you're customizing ranges of micro-meteor speeds, sizes, force, frequency. Corrosion This is heavily detailed in the linked thread above, and concerns any and all planets that were made to be corrosive but cannot be as no mod for this mechanic does exists to date. But to simplify for here, this manifests in the ability to set corrosion parameters for a planet's: Atmosphere (including strength, whether acid or alkaline, and an altitude curve so there can be a safe region and a hazard region); Surface (strength, whether acid or alkaline, whole planet or per biome); Ocean (same params as surface); Exosphere (possibly. I'm not aware of any case of corrosives in vacuum but having it still makes for some creative freedom). The health bar and saturation system are the most prominent here as parts are subject to DPS (damage per second) due to prolonged and heavy exposure. Measures can be taken to reduce the effect of ambient corrosives on individual parts or the whole ship. Hull parts could be tailor made (being fabricated the right way and with the right stuff) or boosted (painted with ablators or potentially toxic anti-corrosives, or insulated by an electromagnetic field) to have great(er) resistance. Visualization: A part that is overwhelmed by corrosion could have indicators in the form of the black-body overlay (but that it starts glowing purple. Seems fitting for a starter. It's like having the poison status in an RPG) and a purple saturation bar. This glow and this bar show how much the part is being punished and is the same as hearing a geiger counter crackling increasingly loudly. If you can get away in time then this bar empties and health stops falling-- you don't die immediately if you let that bar fill up but you know you won't last that long a 2nd time. Heat (Conductivity/Thermal Stress) Everyone knows that if you heat certain substances enough, they physically weaken, and melt, but some can stay strong or become stronger. When the saturation bar (due to heat) stars filling up (let's say, it acts up between 80% and 100% of the part's heat tolerance), joint strength and crash tolerance for parts with low resistance start going down and they become increasingly wet noodle, increasingly easy to break something off if it is impacted or if a high powered engine suddenly fires at full throttle. Health doesn't drain away in this case, however it adds a new dimension to "Deadly Reentry." Heat (Reflectivity) Certain heatshields work by being mirrors and not sweaters or ablators. (See: Icarus ship in the Sunshine movie.) A shield in this case is ideally only useful for reflecting light and heat from a star, and would be appropriate for the likes of Parker's Solar Probe. If appropriate and if KSP allows, this may be as simple as giving the part an emissiveConstant value > 1 so that it's exceptionally radiative, and values for the keys concerning insulation which will lessen the part's ability to exchange heat with other parts. If I have the right image, a mirror heatshield is very slow to absorb heat and very quick to emit or reflect heat. However, it should not allow to be used as a cheaty new form of radiator or reentry-rated heatshield. This may easily be done by giving it a very low dynamic pressure rating (as in deployable antennas). Cryo-Hazard A big one that's been sorely overlooked by Squad. Parts (including kerbals) should have a defined lower temperature limit (skin and internal, not too far from Kerbin's ambient temperature of roughly 290K). If the ambient temperature (especially on splashdown, as in cryogenic seas) is extremely far below these limits, the part will suffer module failure or instantly shatter. Module failures here may possibly be unfixable unlike from debris impact. Parts that have extreme lower limits ideally should not also have good overheat resistance. Thermal gradients become serious business. Visualization: There's no special effect to add here. Relativistic Speed Impact This one only becomes important to vessels using reaction engines to travel interstellar. As your ship reaches speeds measured in fractions of c, you face the debris field mechanic in a different and more aggressive way-- a constant rain of micrometeor impacts, which brings relevance to whipple shields in KSP. The faster you go, the harder you're hit by even the tiniest of objects, and the more frontal surface area you have, the more impacts and DPS you have to face. The more you have to face will add up to saturation from relativistic impact forces. If your frontal surfaces start saturating, their health chips away, so you'll have to watch your cruise speed, buff the shield somehow, or add ablative layers. Whipple shield parts would have the unique property of having resistance to the relativistic virtual masses that fire at it during these speeds. Any other parts, if struck by a single relativistic virtual mass object can be blown off or melted, not being recognized as able to withstand it. Whipple shield parts would be expected to come not only in the form of frontal shields, but a suite of modular pieces like stock structural panels so that you have plenty opportunity to get creative with your armor design. Visualization: The frontal surface of your ship could be peppered by little flares representing explosions of the tiny masses on impact. Some heat could be picked up as a side-effect. This is not necessary at all but only for a hint as to where you're being hit and could be switched off by default. ... Documentation I was asked by @ValiZockt to produce documentation for stats that would be immediately important in the VAB info window or the PAW. So I created it. OneDrive link. I'll add concept writing for configuration options for planets later, but these options near-entirely borrow from how Kopernicus' HazardousBody module works. This module can already assign heat zones to planets via: altitude + latitude + longitude curves, grayscale texture (heat map), biome filters.
  8. Firstly, I'll just say I've barely been playing KSP over a year now and I'm a swift learner. I absolutely love this game. I feel like Squad hooked us up with an unlimited supply of super-powered LEGOs or something! The freedoms... It's incredibly entertaining... but today I wish to personally introduce RNG to my kraken-fist! Okay, so here's the breakdown: My ultimate goal is to vacation the surviv-- uh, I mean Kerbals of my space program to Laythe. Naturally, there's a few things we'll need to truly enjoy ourselves on Laythe... You know, boats, jets, spider-bots and submersibles... the usual. However, for ease of transit and a larger margin of error, I decided that a Minmus refueling station would be, not only necessary, but PERFECT for such a feat. Not only does the super-low gravity prove simple to beat, but Minmus is also the furthest satellite from Kerbin, naturally nullifying a great deal of the deltaV required to escape Kerbin's gravity. That's going to come in handy with this career later, as well, considering my plans of sending many heavy toys to Laythe to play with. Jebs and Vals, I assure you I have done similar Minmus bases before, many times in past, now-deleted game saves. Never ONCE was I disappointed until this very evening. After starting a new career and establishing a communications constellation around both Kerbin and then Minmus, spending a few hours in the SPH designing a beautifully mobile and minimalistic Minmus refueling base, then building the launcher for it, it was finally time to send a probe to survey the minty planet. I didn't. Instead, I tested out the full potential of the refueler, from launch to landing to ensure a later success. After a near-perfect flight, I landed the base safe and sound, ultimately deciding it was no test flight at all. No time later, that surveyor launch was underway, and without failings of any kind (other than my inefficient piloting.) Soaring over the north pole of Minmus, my capture burn was a success, so I deployed the probe's scanners in haste, ready to move on with the next phase of the operation. I could always move the refueler to the nearest ore concentration, if necessary. And RNG kicked me right where the sun don't shine. Minmus was practically dried up. No more than 4% ore content at the hottest concentration, and that makes mining ore ridiculously lengthy, no matter how many BadS, 5-star engineers you have aboard. I'll time-warp through a day of mining, sure. No problem. Warping through years of mining? Forget it. It's one thing to have to stop the drills so the ISRU can catch up... it's a whole 'nother headache to stop the ISRU and wait for ore. Good thing I have so much experience in starting careers from scratch, because this will be the fastest-deleted game save I've ever started... having only spent about 6 hours in total, from beginning launch to surveying the prune that is Minmus. Hopefully the career I just started will be more like what I'm used to seeing-- averaging around 12% ore concentration, and generally in the Flats areas, where landing is even easier... Good luck to you, my fellow kerbonauts! May the odds be ever in your "flavor."
  9. I'm on Linux: $ uname -a Linux metric 4.8.0-41-generic #44-Ubuntu SMP Fri Mar 3 15:27:17 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux This behaviour occurs from both the 32- and 64-bit launchers. The game is stock, from Steam, with no modifications at all. The game starts, some logs are generated, but the output is a black screen. Not even the loading screen appears. The program hangs like this until either terminated, or after a minute or two at which point it silently dies on its own. Unity Log $ cat ~/.config/unity3d/Squad/Kerbal\ Space\ Program/Player.log ../common/pipes.cpp (769) : Assertion Failed: fatal stalled cross-thread pipe ../common/pipes.cpp (769) : Fatal assert failed: ../common/pipes.cpp, line 769. Application exiting. Assert( Assertion Failed: fatal stalled cross-thread pipe ):../common/pipes.cpp:769 _ExitOnFatalAssert crash_20170319164726_2.dmp[6854]: Uploading dump (out-of-process) /tmp/dumps/crash_20170319164726_2.dmp crash_20170319164726_2.dmp[6854]: Finished uploading minidump (out-of-process): success = no crash_20170319164726_2.dmp[6854]: error: libcurl.so: cannot open shared object file: No such file or directory crash_20170319164726_2.dmp[6854]: file ''/tmp/dumps/crash_20170319164726_2.dmp'', upload no: ''libcurl.so: cannot open shared object file: No such file or directory'' _polygon_offset GL_EXT_subtexture GL_EXT_texture_object GL_EXT_vertex_array GL_EXT_compiled_vertex_array GL_EXT_texture GL_EXT_texture3D GL_IBM_rasterpos_clip GL_ARB_point_parameters GL_EXT_draw_range_elements GL_EXT_packed_pixels GL_EXT_point_parameters GL_EXT_rescale_normal GL_EXT_separate_specular_color GL_EXT_texture_edge_clamp GL_SGIS_generate_mipmap GL_SGIS_texture_border_clamp GL_SGIS_texture_edge_clamp GL_SGIS_texture_lod GL_ARB_framebuffer_sRGB GL_ARB_multitexture GL_EXT_framebuffer_sRGB GL_IBM_multimode_draw_arrays GL_IBM_texture_mirrored_repeat GL_ARB_texture_cube_map GL_ARB_texture_env_add GL_ARB_transpose_matrix GL_EXT_blend_func_separate GL_EXT_fog_coord GL_EXT_multi_draw_arrays GL_EXT_secondary_color GL_EXT_texture_env_add GL_EXT_texture_filter_anisotropic GL_EXT_texture_lod_bias GL_INGR_blend_func_separate GL_NV_blend_square GL_NV_light_max_exponent GL_NV_texgen_reflection GL_NV_texture_env_combine4 GL_S3_s3tc GL_SUN_multi_draw_arrays GL_ARB_texture_border_clamp GL_ARB_texture_compression GL_EXT_framebuffer_object GL_EXT_texture_compression_s3tc GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_MESA_window_pos GL_NV_packed_depth_stencil GL_NV_texture_rectangle GL_ARB_depth_texture GL_ARB_occlusion_query GL_ARB_shadow GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_mirrored_repeat GL_ARB_window_pos GL_ATI_fragment_shader GL_EXT_stencil_two_side GL_EXT_texture_cube_map GL_NV_depth_clamp GL_NV_fog_distance GL_APPLE_packed_pixels GL_APPLE_vertex_array_object GL_ARB_draw_buffers GL_ARB_fragment_program GL_ARB_fragment_shader GL_ARB_shader_objects GL_ARB_vertex_program GL_ARB_vertex_shader GL_ATI_draw_buffers GL_ATI_texture_env_combine3 GL_ATI_texture_float GL_EXT_depth_bounds_test GL_EXT_shadow_funcs GL_EXT_stencil_wrap GL_MESA_pack_invert GL_NV_primitive_restart GL_ARB_depth_clamp GL_ARB_fragment_program_shadow GL_ARB_half_float_pixel GL_ARB_occlusion_query2 GL_ARB_point_sprite GL_ARB_shading_language_100 GL_ARB_sync GL_ARB_texture_non_power_of_two GL_ARB_vertex_buffer_object GL_ATI_blend_equation_separate GL_EXT_blend_equation_separate GL_OES_read_format GL_ARB_color_buffer_float GL_ARB_pixel_buffer_object GL_ARB_texture_compression_rgtc GL_ARB_texture_float GL_ARB_texture_rectangle GL_ATI_texture_compression_3dc GL_EXT_packed_float GL_EXT_pixel_buffer_object GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_rgtc GL_EXT_texture_mirror_clamp GL_EXT_texture_rectangle GL_EXT_texture_sRGB GL_EXT_texture_shared_exponent GL_ARB_framebuffer_object GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXT_packed_depth_stencil GL_ARB_vertex_array_object GL_ATI_separate_stencil GL_ATI_texture_mirror_once GL_EXT_draw_buffers2 GL_EXT_draw_instanced GL_EXT_gpu_program_parameters GL_EXT_texture_array GL_EXT_texture_compression_latc GL_EXT_texture_integer GL_EXT_texture_sRGB_decode GL_EXT_timer_query GL_OES_EGL_image GL_AMD_performance_monitor GL_ARB_copy_buffer GL_ARB_depth_buffer_float GL_ARB_draw_instanced GL_ARB_half_float_vertex GL_ARB_instanced_arrays GL_ARB_map_buffer_range GL_ARB_texture_rg GL_ARB_texture_swizzle GL_ARB_vertex_array_bgra GL_EXT_texture_swizzle GL_EXT_vertex_array_bgra GL_NV_conditional_render GL_AMD_conservative_depth GL_AMD_draw_buffers_blend GL_AMD_seamless_cubemap_per_texture GL_AMD_shader_stencil_export GL_ARB_ES2_compatibility GL_ARB_blend_func_extended GL_ARB_debug_output GL_ARB_draw_buffers_blend GL_ARB_draw_elements_base_vertex GL_ARB_explicit_attrib_location GL_ARB_fragment_coord_conventions GL_ARB_provoking_vertex GL_ARB_sample_shading GL_ARB_sampler_objects GL_ARB_seamless_cube_map GL_ARB_shader_stencil_export GL_ARB_shader_texture_lod GL_ARB_texture_cube_map_array GL_ARB_texture_gather GL_ARB_texture_multisample GL_ARB_texture_query_lod GL_ARB_texture_rgb10_a2ui GL_ARB_uniform_buffer_object GL_ARB_vertex_type_2_10_10_10_rev GL_ATI_meminfo GL_EXT_provoking_vertex GL_EXT_texture_snorm GL_MESA_texture_signed_rgba GL_NV_texture_barrier GL_ARB_get_program_binary GL_ARB_robustness GL_ARB_separate_shader_objects GL_ARB_shader_bit_encoding GL_ARB_shader_precision GL_ARB_texture_compression_bptc GL_ARB_timer_query GL_ARB_transform_feedback2 GL_ARB_transform_feedback3 GL_NV_vdpau_interop GL_ANGLE_texture_compression_dxt3 GL_ANGLE_texture_compression_dxt5 GL_ARB_base_instance GL_ARB_compressed_texture_pixel_storage GL_ARB_conservative_depth GL_ARB_internalformat_query GL_ARB_map_buffer_alignment GL_ARB_shading_language_420pack GL_ARB_shading_language_packing GL_ARB_texture_storage GL_ARB_transform_feedback_instanced GL_EXT_framebuffer_multisample_blit_scaled GL_EXT_transform_feedback GL_AMD_shader_trinary_minmax GL_ARB_ES3_compatibility GL_ARB_arrays_of_arrays GL_ARB_clear_buffer_object GL_ARB_copy_image GL_ARB_explicit_uniform_location GL_ARB_framebuffer_no_attachments GL_ARB_invalidate_subdata GL_ARB_program_interface_query GL_ARB_robust_buffer_access_behavior GL_ARB_stencil_texturing GL_ARB_texture_query_levels GL_ARB_texture_storage_multisample GL_ARB_texture_view GL_ARB_vertex_attrib_binding GL_KHR_debug GL_AMD_pinned_memory GL_ARB_buffer_storage GL_ARB_internalformat_query2 GL_ARB_multi_bind GL_ARB_seamless_cubemap_per_texture GL_ARB_texture_mirror_clamp_to_edge GL_ARB_texture_stencil8 GL_ARB_vertex_type_10f_11f_11f_rev GL_EXT_shader_integer_mix GL_NVX_gpu_memory_info GL_ARB_clip_control GL_ARB_conditional_render_inverted GL_ARB_derivative_control GL_ARB_get_texture_sub_image GL_ARB_pipeline_statistics_query GL_ARB_shader_texture_image_samples GL_ARB_texture_barrier GL_EXT_polygon_offset_clamp GL_KHR_context_flush_control GL_KHR_robust_buffer_access_behavior GLX Extensions: GLX_ARB_create_context GLX_ARB_create_context_profile GLX_ARB_create_context_robustness GLX_ARB_fbconfig_float GLX_ARB_framebuffer_sRGB GLX_ARB_get_proc_address GLX_ARB_multisample GLX_EXT_import_context GLX_EXT_visual_info GLX_EXT_visual_rating GLX_EXT_fbconfig_packed_float GLX_EXT_framebuffer_sRGB GLX_EXT_create_context_es2_profile GLX_EXT_create_context_es_profile GLX_MESA_copy_sub_buffer GLX_MESA_multithread_makecurrent GLX_MESA_query_renderer GLX_MESA_swap_control GLX_OML_swap_method GLX_OML_sync_control GLX_SGI_make_current_read GLX_SGI_swap_control GLX_SGI_video_sync GLX_SGIS_multisample GLX_SGIX_fbconfig GLX_SGIX_pbuffer GLX_SGIX_visual_select_group GLX_EXT_texture_from_pixmap GLX_INTEL_swap_event Setting maxVSyncInterval to 4 GL: Detected 1024 MB VRAM AudioManager: Using PulseAudio: Default Output Device Begin MonoManager ReloadAssembly Platform assembly: /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/UnityEngine.dll (this message is harmless) Loading /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/UnityEngine.dll into Unity Child Domain Platform assembly: /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/Assembly-CSharp-firstpass.dll (this message is harmless) Loading /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/Assembly-CSharp-firstpass.dll into Unity Child Domain Platform assembly: /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/Assembly-CSharp.dll (this message is harmless) Loading /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/Assembly-CSharp.dll into Unity Child Domain Platform assembly: /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/Assembly-UnityScript-firstpass.dll (this message is harmless) Loading /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/Assembly-UnityScript-firstpass.dll into Unity Child Domain Platform assembly: /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/Assembly-UnityScript.dll (this message is harmless) Loading /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/Assembly-UnityScript.dll into Unity Child Domain Platform assembly: /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/UnityEngine.UI.dll (this message is harmless) Loading /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/UnityEngine.UI.dll into Unity Child Domain Platform assembly: /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/UnityEngine.Networking.dll (this message is harmless) Loading /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/UnityEngine.Networking.dll into Unity Child Domain Platform assembly: /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/Mono.Cecil.dll (this message is harmless) Loading /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/Mono.Cecil.dll into Unity Child Domain Platform assembly: /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/KSPAssets.dll (this message is harmless) Loading /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/KSPAssets.dll into Unity Child Domain Platform assembly: /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/TrackIRUnity.dll (this message is harmless) Loading /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/TrackIRUnity.dll into Unity Child Domain Platform assembly: /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/xmldiffpatch.dll (this message is harmless) Loading /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/xmldiffpatch.dll into Unity Child Domain Platform assembly: /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/XmlDiffPatch.View.dll (this message is harmless) Loading /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/XmlDiffPatch.View.dll into Unity Child Domain - Completed reload, in 0.074 seconds Platform assembly: /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/System.Core.dll (this message is harmless) Platform assembly: /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/System.dll (this message is harmless) Platform assembly: /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/Boo.Lang.dll (this message is harmless) Platform assembly: /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/System.Xml.dll (this message is harmless) Default vsync count 0 requesting resize 1680 x 1050 Selecting FBConfig GLX_FBCONFIG_ID=159 GLX_BUFFER_SIZE=32 GLX_DOUBLEBUFFER=1 GLX_RED_SIZE=8 GLX_GREEN_SIZE=8 GLX_BLUE_SIZE=8 GLX_ALPHA_SIZE=8 GLX_DEPTH_SIZE=24 GLX_STENCIL_SIZE=8 GLX_SAMPLES_ARB=2 GLX_SAMPLE_BUFFERS_ARB=1 GLX_STEREO=0 GLX_CONFIG_CAVEAT=NONE requesting fullscreen 1680 x 1050 at 0 Hz Desktop is 3280 x 1200 @ 60 Hz Using libudev for joystick management Importing game controller configs UnloadTime: 3.440000 ms Release Build (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) [KSP Version]: (LinuxPlayer) ==================================== (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) [Input Devices]: (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) [Input Devices]: (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) Launcher Settings File exists (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) Launcher disabled? False (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) Launcher after checking file: False (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) ******* Log Initiated for Kerbal Space Program - (LinuxPlayer) ******* (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) Changing real window size to 1680 x 1050 Ignoring window size change to 1680x1050 : waiting for fullscreen at 1680x1050 Changing real window size to 1680 x 1050 Changing real window size to 1680 x 1050 Changing real window size to 1680 x 1050 Changing real window size to 1680 x 1050 Changing real window size to 1680 x 1050 Changing real window size to 1680 x 1050 PhysicsGlobals: Loading database (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) ActionCanvas MASK: 3458764513820540928 (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) AppCanvas MASK: 3458764513820540928 (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) MainCanvas MASK: 3458764513820540928 (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) Load(Assembly): Squad/Plugins/KSPSteamCtrlr (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) AssemblyLoader: Loading assembly at /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/GameData/Squad/Plugins/KSPSteamCtrlr.dll (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) Load(Assembly): Squad/Plugins/Steamworks.NET (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) AssemblyLoader: Loading assembly at /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/GameData/Squad/Plugins/Steamworks.NET.dll (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) AssemblyLoader: Loading assemblies (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) Non platform assembly: /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/GameData/Squad/Plugins/KSPSteamCtrlr.dll (this message is harmless) Non platform assembly: /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/GameData/Squad/Plugins/Steamworks.NET.dll (this message is harmless) VesselModules: Found VesselModule of type CommNetVessel with order 999 (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) VesselModules: Found VesselModule of type FlightIntegrator with order 0 (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) VesselModules: Found 2 VesselModule types (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) ************************************************************************ Environment Info Unix 7FFFFFFFFFFFFFFF Args: KSP.x86_64 Mod DLLs found: Stock assembly: Assembly-CSharp v1.0.0.0 Stock assembly: KSPSteamCtrlr v0.0.1.35 Stock assembly: Steamworks.NET v9.0.0.0 / v9.0.0 Folders and files in GameData: Stock folder: Squad .DS_Store ************************************************************************ (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) [AddonLoader]: Instantiating addon 'KSPSteamController' from assembly 'KSPSteamCtrlr' (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) KSP Log $ cat ~/.local/share/Steam/steamapps/common/Kerbal\ Space\ Program/KSP.log [LOG 16:44:25.580] ******* Log Initiated for Kerbal Space Program - (LinuxPlayer) ******* Kerbal Space Program - (LinuxPlayer) OS: Linux 4.8 Ubuntu 16.10 64bit CPU: Intel(R) Xeon(R) CPU X5450 @ 3.00GHz (8) RAM: 30914 GPU: Gallium 0.4 on AMD CAPE VERDE (DRM 2.46.0 / 4.8.0-41-generic, LLVM 3.8.1) (1024MB) SM: 30 (OpenGL 3.0 [3.0 Mesa 12.0.6]) RT Formats: ARGB32, Depth, ARGBHalf, Shadowmap, RGB565, ARGB4444, ARGB1555, Default, ARGB2101010, DefaultHDR, ARGBFloat, RGFloat, RGHalf, RFloat, RHalf, R8 Log started: Sun, Mar 19, 2017 16:44:25 Launcher Output $ ~/.local/share/Steam/steamapps/common/Kerbal\ Space\ Program/KSP.x86_64 Found path: /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP.x86_64 Mono path[0] = '/home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed' Mono path[1] = '/home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Mono' Mono config path = '/home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Mono/etc' displaymanager : xrandr version warning. 1.5 client has 6 screens displaymanager screen (0)(DisplayPort-0): 1680 x 1050 displaymanager screen (1)(DVI-0): 1600 x 1200 Using libudev for joystick management Importing game controller configs Terminated
  10. So here's the rub: I have a copy of the newest KSP update (1.1.2) and I put Mechjeb onto it. So far, worked like a charm. Fired it up today, and the takeoff works fine, but when it gets near it's apoapsis the craft does several things. 1: Creates the node for the maneuver. 2: Doesn't line up for the maneuver. 3: Spins out of control, like the wheel has just been allowed to go free. 4: Fails to throttle up. 5: Continues counting past the maneuver. 6: Hits the ground in what the scientists refer to as a "Gravity's poodle" move. I've tried this with every craft I made as well as the stock ones, and I get the same result. I've turned on RCS, played with corrective steering, all of it. I don't know why it just began to glitch out. Please help!
  11. Mechjeb is being a total jerk to me. It fails to comprehend targets, it won't do anything at all for ascent guidance except autostage, and rendezvous planning also doesn't work. It basaically just has a big catastrophic failure. Here's a list of plugins I use: Mechjeb Hyperedit DynamicTextureLoader BetterTimeWarp That's it. Someone help, please!
  • Create New...