nukeboyt

Yes. I've brought my saves over. The only problems I ever had were associated with IR and tweakscale. For unknown reasons, one of my sips designed in windows, would improperly sized stock parts when brought over. It wasn't a big deal recreating the ship. Since I only play sandbox, I cannot say whether or not there are problems with a career mode game.

Many thanks, Sal. You're always very helpful.

How do you monitor FPS under Linux? Back under Windows, I could get it from Nvidia gforce experience. But how do I determine FPS in Linux?

I had a similar situation where the textures were not decompressing. When I switched from Kubuntu to Mint the problem went away.

After you've left the Kerbin Sphere of Influence (SOI) and while you are still a long way away from the target planet, experiment with very short (momentary) burns in EACH of the 6 main directions (Prograde, Retrograde, Normal, Antinormal, Radial, Antiradial). As you do each burn, watch the periapsys (or closest approach) and how it changes with each burn. (Mouse over in map view, then left-click to keep it up). You will find that each burn will either make the periapsis GROW (get further away) or SHRINK (get closer). Do longer burns on the ones that SHRINK the periapsis (or closest approach) and stop burning when the value quits SHRINKING. Then repeat for the other directions. You will soon learn that one direction will have a much bigger effect than all the others. When you have an encounter, use the TAB key to focus the view on the planet in question. You should be able to see the periapsis of your upcoming encounter. Continue to use the method above to get the periapsis down to the value you want. I suggest that you learn first on planets or moons with atmospheres. Because these can help you slow down by aerobreaking. For example, at jool, I set my periapsis to about 120K and it will slow me down enough to get into orbit. Setting the periapsis too low, will result in having to land (or crash). For planets / moons without atmospheres, you will have to just bring more fuel

Agreed. If someone wanted to replicate the issue on THEIR machine, what steps would be necessary? (Assume that I have a COMPLETELY STOCK installation, but with MecJeb as the ONLY MOD. How could I duplicate your problem on my machine?)

Great job! Thanks

Thank you for taking on the maintenance of this mod. It has always been one of my favorites, and you're doing a great job.

I love recommending KSP to my friends and coworkers. I was just wondering if there are any plans to issue an updated demo. The version based on 18.3 is quite dated, and no longer provides the best "taste" of the game's flavor (IMHO).

Agreed. Being as your're a video maker (and a good one at that), I was wondering if you got a pre-release version?

I moved a craft from original KSP installation on windows (first picture) into a new install on linux. I used the latest versions of Tweakscale and Infernal Robotics. Now some of the stock parts seem to all be at 400% (2nd and 3rd pictures) Does anyone have ideas on how I can fix this craft without rebuilding it from scratch?

It isn't abandoned. In one of his other mod threads, the developer Alesustas said: "Sorry folks, but I have a lot of RL work right now, and seems like I'll be busy at least till mid-December. I will return back to continue my work on projects when i will have more free time."

The best solution for me was to install an extra hard drive. After first disconnecting the Windows drive, I then installed Kubuntu and got everything running. Then I reconnected the windows drive. Now all I have to do is tap to enter Bios on start-up and choose which hard disk to boot from. This way I didn't have to worry about any boot-loader conflicts.

Almost everything on the panel in front of the pilot's chair have some function or other. On the right, most of them do also. Several are reserved and only have a function if MecJeb is installed. There really isn't any better (or more fun) way to find out the functions of the buttons than to just experiment! In my opinion, Alexustas' IVA's are simply the best in the game. I'd love to see some additonal integration (like Docking Port Alignment Indicator) but I still think this is great

After all weekend of trials and errors (lots of errors), I found the solution that works. The main problem was that, because the QNIX monitor isn't directly supported, the NVIDIA configuration utility could not create an xorg.conf file that would work. Also complicating maters was that almost all online references assume that NVIDIA has "Twinview", which as far as I can tell, is not a select-able option in the 331 drivers. Here's what allows me to have Full resolution on both monitors. _________________ # nvidia-settings: X configuration file generated by nvidia-settings # nvidia-settings: version 331.20 (buildd@roseapple) Mon Feb 3 15:07:22 UTC 2014 Section "ServerLayout" Identifier "Layout0" Screen 0 "Screen0" 0 0 InputDevice "Keyboard0" "CoreKeyboard" InputDevice "Mouse0" "CorePointer" Option "Xinerama" "0" EndSection Section "Files" EndSection Section "InputDevice" # generated from default Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/psaux" Option "Emulate3Buttons" "no" Option "ZAxisMapping" "4 5" EndSection Section "InputDevice" # generated from default Identifier "Keyboard0" Driver "kbd" EndSection Section "Monitor" # HorizSync source: xconfig, VertRefresh source: xconfig Identifier "Monitor0" VendorName "Unknown" ModelName "DFP-0" HorizSync 88.8 - 160 VertRefresh 59.5 - 120 # ModeLine "2560x1440R" 241.500 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync # ModeLine "nvidia-auto-select" 241.500 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync ModeLine "2560x1440" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync ModeLine "2560x1440_60" 312.25 2560 2752 3024 3488 1440 1443 1448 1493 -hsync +vsync Option "DPMS" Option "DPMS" EndSection Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" BoardName "GeForce GTX 680" BusID "PCI:1:0:0" EndSection Section "Screen" Identifier "Screen0" Device "Device0" Monitor "Monitor0" DefaultDepth 24 Option "UseEDID" "False" Option "UseEDIDDPI" "False" Option "UseEDIDFreqs" "False" Option "ExactModeTimingsDVI" "True" Option "ModeValidation" "AllowNonEdidModes, AllowNon60hzmodesDFPModes, NoEDIDDFPMaxSizeCheck, NoVertRefreshCheck, NoHorizSyncCheck, NoDFPNativeResolutionCheck, NoMaxSizeCheck, NoMaxPClkCheck, NoEDIDModes" Option "NoBandWidthTest" "true" Option "Stereo" "0" Option "nvidiaXineramaInfoOrder" "DFP-0" Option "metamodes" "DVI-I-1: 2560x1440 +0+0, DVI-D-0: 1680x1050_60 +2560+195" Option "SLI" "Off" Option "MultiGPU" "Off" Option "BaseMosaic" "off" SubSection "Display" Depth 24 EndSubSection EndSection

Thank you. I'll give that a look.

Long time KSP player / forum member but brand new to Linux, just a couple of weeks ago. I posted a help request on a couple of Ubuntu (Kubuntu) forums, and so far gotten no replies, So I will ask here, on the hopes that some "KSP-playing-Linux-Expert" might have a solution. The problem is that I want to run dual monitors with the Nvidia proprietary drivers. I currently have a QNIX 2650x1440 and an Acer 1680x1050. They work simultaneously when using the Nouveau (default) driver. But since I"ve installed the Nvidia 331 recommended driver, I can only get one to function at any given time. I've tried several configurations of the Xorg.conf file, but to no avail. Each time I attempt to add a second monitor (Monitor1) one of the two goes into it's "resolution not supported" mode, which on the QNIX, means cycling through several colors. I haven't found any way to manually set a resolution from within the xorg.conf file itself. I should mention that I have two GTX 680's. I've tried connecting both monitors to one card, and one on each card and the results are always the same. Any suggestions are welcome. I really don't want to have to return to Windows to have dual monitors. Thanks _____________________________________________________ Here's an example of an xorg.conf file that works for the QNIX: # nvidia-settings: X configuration file generated by nvidia-settings # nvidia-settings: version 331.20 (buildd@roseapple) Mon Feb 3 15:07:22 UTC 2014 Section "ServerLayout" Identifier "Layout0" Screen 0 "Screen0" 0 0 InputDevice "Keyboard0" "CoreKeyboard" InputDevice "Mouse0" "CorePointer" Option "Xinerama" "0" EndSection Section "Files" EndSection Section "InputDevice" # generated from default Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/psaux" Option "Emulate3Buttons" "no" Option "ZAxisMapping" "4 5" EndSection Section "InputDevice" # generated from default Identifier "Keyboard0" Driver "kbd" EndSection Section "Monitor" # HorizSync source: xconfig, VertRefresh source: xconfig Identifier "Monitor0" VendorName "Unknown" ModelName "DFP-0" HorizSync 88.8 - 88.8 VertRefresh 59.5 ModeLine "nvidia-auto-select" 241.500 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync Option "DPMS" EndSection Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" BoardName "GeForce GTX 680" BusID "PCI:1:0:0" EndSection Section "Screen" Identifier "Screen0" Device "Device0" Monitor "Monitor0" DefaultDepth 24 Option "Stereo" "0" Option "nvidiaXineramaInfoOrder" "DFP-0" Option "metamodes" "nvidia-auto-select +0+0" Option "SLI" "Off" Option "MultiGPU" "Off" Option "BaseMosaic" "off" SubSection "Display" Depth 24 EndSubSection EndSection

My QNIX 2560 x 1440 monitor quits working when I install the Nvidia drivers. I searched around and found some settings for the xorg.conf that allowed it to work. Life was good until I tried to add a second monitor with different resolution. I failed to make a copy of the xorg.conf file and ended up unable to boot to either monitor. I could have corrected it with my live usb-stick, but I decided to move on to Ubuntu

I started out with Kubuntu and after a week, I'm now experimenting with Ubuntu. I plan on giving a lot of the flavors a try. After only an hour or so with Ubuntu, I miss the Kommand-line option on the right-click, and the ability to have the window buttons on the right. KSP is still phenomenal though. Primary reason for switching was that I really dorked-up my xorg.conf so bad I couldn't boot.

I had an old harddrive from a computer I no longer used, so I decided last week to give Linux a try. This is the how-to that helped me along. All I can say is ***WOW***. I've been able to load all of the memory-hog mods that I've only been able to play one-at-a-time. And without texture compression!! If you are comfortable with installing new OS's I ***highly recommend*** giving it a shot. Have a great day. Also, disconnected my Windows HD completely during the installation because I'm not interested in dual boot. Instead, I now use bios to determine which HD to boot from

I found this helpful.

Perfectly legitimate question. The answer is of course, that people want to let the author know that his/her work is appreciated and missed. I cannot speak for any mod author, but if I had taken some time off, and was questioning whether or not it was worth the effort to continue, it would make a difference to me whether or not the "fans" showed an interest. And keeping threads near the front, while perhaps not the best way, is one way to show the author that you're interested.

If anyone wonders why this mod is anxiously anticipated, they must not be familiar with Alesuxtas' work. His previous mods are, probably the best when it comes to detail and functionality of the IVA. The internal controls of ALCOR make IVA-only missions not only possible but fun and exciting. The heads-up display of ERS is fantastic. The idea behind PRC is ingenious. I'm sure KONQUEST will be worth the wait. To see why we wait, go check out the mods I've mentioned. Sorry no links yet, gotta rush. Check out Alexustas' signature.

No, you're not the only one. But I could live with it and just stay away from the coastlines