sal_vager

Course, there's always moar wheels!

@Kerbal101, if you have not already can you please report this on the tracker with your findings regarding tolerances.

Something to bare in mind regarding braking, these gear are usually attached behind the CoM, with a single unbraked LY-05 in front. When you're braking in a car or on a motorbike it's your front brakes that do the most work, as the vehicles inertia causes the vehicle to tilt forwards and push down on the front wheel(s) you can apply more braking force without losing grip, but the rear wheels will have a lot less weight on them, this is the number one cause for locking up the rear wheel on a bike, too much force too soon on the back brake when stopping. Braking with the rear wheels only can be done, but takes longer unless you want to risk locking up the wheels, as there's less pressure on them against the road they will have less grip. It's like this with the LY-01's behind the CoM, applying the brakes causes the craft to nose down a bit, putting more force on the (useless for stopping) LY-05, and a little less on the 01's, so it takes longer to stop. Bigger brakes won't help much, as what you need are braked wheels in front of the CoM, you can see this yourself with any of the retractable gear, just disable the brakes on the front wheels and your stopping distance will increase, a lot. Also, moved to Suggestions. Edit: Derp, breaking not braking :/ Btw, max take of weight of a Cessna 185 is 1,506 kg, no where near 6 tons, so I wouldn't expect the gear to be that strong.

You should be able to Control+A in the text box then delete all the contents, including the quote.

It should work, it's working here on Xubuntu 16.04, though some window managers have trouble with Unity requesting bad sizes and crashing X when KSP starts, and as you didn't mention it I assume that didn't occur with XWayland.

Some posts repeatedly asking for updates have had to be removed, please be patient, modders have lives too.

Are you plugging the controller in after KSP starts? It's unable to save the bindings if the controller has not been added to the settings.cfg, so please try restarting KSP with the controller attached.

Okay, if you could take a look here and find your logs from KSP that might help.

Hi @miceliux, according to the Unity3D roadmap there has been no progress so far on supporting alternative display managers, "Standalone: Support for alternative display managers Wayland and Mir on desktop Linux." probably also includes XWayland as it is an X server running as a Wayland client, and its status is grey (not started), though it was the focus of a hackweek in May, that is different to mainline development. Until we hear otherwise we have to assume only X11 is supported at this time. Your logs look normal except for multiple attempts to change the screen resolution to 1920 x 1016, then resorting to 1920 x 1080, I assume due to your taskbar(s) leaving less vertical space for the KSP window. You might have to run KSP in a true X11 environment for the time being.

Hi @LandscapeJohn, which version of Sierra are you using? There are reports of Unity3D failing to work on the developer releases of Sierra. More details here.

No, not that at all, hold on I'll take a screenshot. Edit. It's just easier to see it. That's the most common cause of failure to set up controllers, the other one is from plugging in the stick after KSP starts, KSP has to have the controller in the settings.cfg file before bindings will be saved.

Hi @Ben The Starsailorman, don't use the secondary inputs for controller axis, they will not work as they are only for digital input, use the pitch, roll and yaw axis bindings instead.

Pushed to dev discussion.

Not at all, you can either install over the top of your existing install, use the patch to update your current install, or install the game again and copy your saves from one to the other.

We'll need your logs guys.

Hi @nonni15, there's a few things that can cause this, if you are still warping even at 5x the stage lock will remain on, if your craft has run out of electricity and you don't have a Kerbal you won;t have control so it'll be on as well. You can see your electric in the resource app, top right of the screen. If it's not those then please take a look here, we'll need your game logs.

The patcher is no longer in use, please go to your Squad store account downloads page and download the patch for your version of KSP (windows only) or the full game, thank you.

It's not possible to guarantee that a copy of KSP that was updated to 1.2 using the patcher (which should not be working) will work without problems from updating in that manner, so please if you do run into any issues I ask that you redownload KSP from your Squad store account page.

Dude, without your logs we're blind here, your game will have a KSP.log and an output_log.txt, they will really help.

Great news @Kyrt Malthorn, glad I could help!

Are you noticing any issues in any other programs? Also, according to this site your CPU is rated to handle a maximum of 105°, it may be worth checking for airflow and dust build-up as the reported temperature may be lower at the sensor than the core of the CPU.

Hi @IceBadger, that's on purpose so funds values that are too large for the tumblers can be displayed, the 'empty' space will display an appropriate modifier. For example:

Hi @PGTART, if you could take a look here and rustle up your game logs and system specs we coul dtry to figure out what's wrong.

Amalgamated, please only press submit once in future.

Hi @cpc20, they should work fine, please see here as we'll need more info from you if the issue persists.