Lag from high parts count. Can't click SAS presets.

[Arugela]

I don't know if this is something solvable outside of removing parts or waiting for an update to improve performance.

But when the game gets too laggy you can only highlight the prograde marker and other SAS presettings. Could this be called a bug. Is it something they could eventually program around to make it more likely to work in high stress situation? Currently I can generally get it to get the red highlight. But if you click it never takes the commands or changes green after clicking in very laggy situations. It stop responding to seemingly left click commands for some reason. this actually happens on several things on the interface. The only usable things are generally keyboard commands. Which all work well but are delayed from lag.

Actually, testing this, It seems to only be the navball... So maybe it is something that could be considered a bug. Even the button on the navbal to make it slide down or up and be visible works. It's only the buttons inside the navball that are hidden when it is closed that are affected from what I can tell.

It's not the mouse itself as I can use all other mouse features like zoom and rotate with right mouse. I can also click everything and it works, albeit slowly from lag. This is something I have actually noticed for a long time. It is the single biggest problem I get when making really really large ships.(which I do almost exclusively) Although I haven't consciously tested it until now. Clicking presets for SAS is the single most important thing in large ships I build. It is the larges problem I encounter from interface like issues out of all bugs in the game. It is a certainty after so much lag is reached.

I've basically just clicked everything else in the game on the interface and the only things affected are literally the RCS, SAS, and preset buttons. The presets gain a highlight from hover but cannot be turned green to change them.. The RCS and SAS don't havea highlight from what I can tell and also can't be manually clicked to change them. I have to use keyboard shortcuts. This unfortunately leaves the SAS presets out of actions(Stability assist, prograde, retrograde, etc).

The surface to orbit window even works. And it works faster than almost anything else in the entire interface. So it's just those 3 things. The two buttons and the SAS preset buttons.

I'm using linux x64 with 64 bit KSP via steam.

Fedora 22 x64

Gnome desktop as is default with Fedora 22

8 gigs ram (1600)

560ti 384 core 1gig Vid card.

256 SSD main drive. (game is on this as is other game software related to KSP and steam.)

750 Raid 10(not relevant really to the game.)

Phenom II 1100t (running default settings with the ability to overclock itself to 3.7 as are the settings in the default auto OC features.)

GB-970A-D3 Rev1.0 mobo. (I think it's on firmware version 12. I could be wrong though.)

Here is my craft file if you want to reproduce this level of lag. (1600 parts)

http://www./download/fn5cltcahfltj4b/The_Orion_Basic_wBooster%284%29.craft<- Canpt type a period after this postions without it defaulting back to the end of the hyperlinked text(That is positions below this hyperlink in black).(this is a new error withing this error report.) I also can't hit enter after a hyperlink on this forum and start typing without it being like this. Even after several lines. These are two potential differnent bugs I just ran into. The latter I run into alot. The former is new with the period button.(.)<- period button. This is why there is no period at the end of the below black lettered sentence.

This happens on all large ships for me.<- It has magically stopped. Leaving info for posterity and error correcting. Previously if I typed a period it would be at the end of .craft(.)<-"position noted" if I tried to put the period after the work me at the end of the first sentence in this paragraph.

Edited October 7, 2015 by Arugela

[sal_vager]

The entire UI including the HUD is being replaced for 1.1, there's no information on specifics such as this, so please wait until the release.

Until then you can try updating your graphics drivers, reducing your mouse polling rate and reducing your part count.

[Arugela]

What is the mouse polling rate? And should I increase it or decrease it.

And it only fails to work for the indicated navbal buttons. It might be something weirder. Something that might pass on to the next interface. Everything else I can use all mouse features with even in massive lag.

[Padishar]

It sounds very much like the code that detects the clicks on those UI elements is checking to see if the mouse button is currently down rather than how the key bindings generally work which tests if the key has gone down since the previous frame. Do they work if you hold the mouse button down for a long time?

The mouse polling rate is the number of mouse position updates that KSP gets sent per second. On some systems this defaults to 1000 which seems to cause various nasty problems. Setting it to 125 can give much better behavior. See this thread for info about how to view and change this setting in Linux.

Edited October 6, 2015 by Padishar

[Arugela]

Holding it down does not work from what I have tried. And I have tried a lot of times! 8) will look at the thread you posted.

Any idea how to change the mouse polling in fedora. The stuff from the ubuntu instructions don't work in fedora. I can't find anything on it either.

cat /sys/module/usbhid/parameters/mousepoll

0

This didn't work though:

echo 8 > /sys/module/usbhid/parameters/mousepoll

bash: /sys/module/usbhid/parameters/mousepoll: Permission denied

sudo echo 8 > /sys/module/usbhid/parameters/mousepoll

bash: /sys/module/usbhid/parameters/mousepoll: Permission denied

Edited October 6, 2015 by Arugela

[sal_vager]

Try this for Fedora Arugela.

[Arugela]

Yep, it is now clickable. I thought by reading that stuff originally it was a different issue. Interesting. I think that is why I miss a lot of linux fixes.

Any idea what the best value would be for linux. One thread said 2 and another 10. Is one of them better from peoples experience or another value possibly?

Edit: OK, it worked on the runway but stopped when I fired my engines and increased the lag! 8) I have it set at 10 atm. Definitely an improvement though!

And I can oddly set it to Stability assist now after it's more laggy. But I can't set back to prograde or other options.

Edit2: found a workaround. Cut engines real quick and change then put them back on. Seems to work now! 8) This on top of the mouse changes seems to have fixed the issue. And if that doesn't work I can also push the button on my mouse to make increase DPI and it seems to work when other things dont.

Edited October 8, 2015 by Arugela