Jump to content

Ulrick_Zebulon

Members
  • Posts

    9
  • Joined

  • Last visited

Reputation

0 Neutral

Profile Information

  • About me
    Curious George

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Kim Kaster, thanks for the post. Got questions. What exactly did you do? When Ksp locks up does the below change? If KSP locks up do you change back to what's below? Found in /home/(user name)/.config/unity3d/squad/Kerbalspaceprogram/prefs <unity_prefs version_major="1" version_minor="1"> <pref name="Screenmanager Is Fullscreen mode" type="int">1</pref> <pref name="Screenmanager Resolution Height" type="int">1080</pref> <pref name="Screenmanager Resolution Width" type="int">1920</pref> <pref name="UnityGraphicsQuality" type="int">5</pref> <pref name="UnitySelectMonitor" type="int">-1</pref> </unity_prefs> I solved the problem by not moving the KSP window, and doing everything else on the second monitor. Ksp has worked fine since although I have had to adapt to doing things differently. With this said the above prefs file works, I think. Did not know it existed tell you pointed out.
  2. Although there is much discussion I have had difficulty finding work on this subject I have found the following: Scientists have been researching atmosphere breathing engines in non oxygen atmosphere since before 1958. the following link is a PDF file titled Atmosphere Breathing Engines In Astronautics by S.W. Greenwood and D.S. Carton https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=2&ved=0ahUKEwi05vvkk_POAhUL54MKHQwICCIQFggkMAE&url=http%3A%2F%2Frepository.tudelft.nl%2Fassets%2Fuuid%3A9b471a04-c479-4ab6-8939-24e910fce6f7%2FCoA_Note_No._88.pdf&usg=AFQjCNFU5u1pXHDjAUQpcd3keEr3381vRA&sig2=tmF9_1VT_p4QlvbsEjVATQ Another link i found titled WSPC Develops Martian Jet Engine http://www.wickmanspacecraft.com/marsjet.html I think atmosphere breathing engines in non oxygen atmosphere is quite feasible especially considering some atmospheres like Jupiter, and Saturn have atmospheres that are combustible (hydrogen). Instead of fuel all you need is an oxidizer. I look forward to any mods on this. I found Fireheart318 It's Just Air mod on Curse but there is no download link. Picture looks like a J-X4 Whiplash engine that has been modified. I miss the Kethane mod and would like to see something replace it. Although it's not working completely as I like I have been messing around with the J-90 Goliath's .cfg file with much success as part of an Eve return mission. I just changedcheckForOxygen to False, added an oxidizer, and deleted IntakeAir. It works. Although I would like to assume Eve's atmosphere is combustible considering it has Explodium Sea's and only an oxidizer is required I looked up Saturn's moon Titan which has lakes of methane and found that it's atmosphere is 98.4% nitrogen and only 1.4% methane, and 0.1-.02% hydrogen. Comparing this to Earths 20.95% oxygen atmosphere and I have a hard time justifying using Eve's atmosphere as a fuel source. In conclusion even if you have to provide both a fuel and an oxidizer, turbine engines are far more efficient then rocket engines. Real scientists are working on the subject of atmosphere breathing engines in non oxygen atmosphere and I don't see any reason why it shouldn't be part of Kerbal Space Program.
  3. Still ran into problems. This is how I got to work on Ubuntu. Thanks for all the above help. 1) Download Blender 2.76b from Ubuntu SoftWare 2) Download io_object_mu from github https://github.com/taniwha/io_object_mu 3) Found Blender addons at (folders where locked) Computer/usr/share/blender/scripts/addons 4) If locked open terminal gksudo nautilus sudo apt install gksu (if not installed) gksudo nautilus special folder window will open, goto folder unlock in Properties/Permissions Change Owner to yourself, Access: Create and delete files Now you can copy/paste io_object_mu-master folder into addons 5) Start Blender File - User Preferences - Add-ons - Import-Export:Mu model format (KSP) Check box and Save User Settings 6) Now you can import KSP Mu(.mu) Thanks again for all the help.
  4. sal_vager, thanks so much for your input on this subject. I tried the following based on Psycho_zs. sh -c 'sleep 1 ; echo 15 > "/proc/$(pgrep KSP.x86_64)/oom_adj"' & exec Desktop/KSP_linux/KSP.x86_64 ... and I got the following: ulrick@thor:~$ sh -c 'sleep 1 ; echo 15 > "/proc/$(pgrep KSP.x86_64)/oom_adj"' &[1] 6293 ulrick@thor:~$ exec Desktop/KSP_linux/KSP.x86_64 ...sh: 1: cannot create /proc//oom_adj: Directory nonexistent "Stops with blinking box. When I press return I get the following and then terminal immediately quits. Could only capture using SimpleScreenRecorder." Set current directory to /home/ulrick Found path: /home/ulrick/Desktop/KSP_linux/KSP.x86_64 Mono path[0] = '/home/ulrick/Desktop/KSP_Data/Managed' Mono path[1] = '/home/ulrick/Desktop/KSP_Data/Mono' Mono config path = '/home/ulrick/Desktop/KSP_Data/Mono/ect' displaymanager : xrandr version warning. 1.5 client has 4 screens displaymanager screen (0)(DVI-I-1): 1920 x 1080 displaymanager screen (0)(HDMI-0): 1920 x 1080 Using libudev for joystick management Importing game controller configs Furthermore; SimpleScreenRecorder was glitching out with the screen pixilated, blocky, and or terminal was at 50% opacity. Fortuneatly I could find a frame that was readable. This has me concerned about how other programs function when this problem occures. Since I have demonstrated to myself that this problem is randomly repeatable (happening 5 times after 3 to 7 game starts and always the instant I try to move the KSP window) I have decided to change how I play the game. I plan on playing KSP on my primary screen (full screen) and 'never move it' while having my toolbar and other programs running on my secondary screen and see how that goes. When I have some spare time I will try the Unity3D command line arguments you recommended. If anything I might learn something. Thanks again
  5. To better help find where the problem lies I did the following: On a spare hard drive I did a fresh install of Ubuntu 16.04. Update Installed the Nvidia GeForce driver. Installed KSP 1-1-2 (no mods) Thats it, nothing else. I then started Launcher.x86_64. When done pressed play, KSP started just fine. Went to setup, moved window to secondary screen, maxed out settings,set to full screen, and played one mission. Exited KSP and restart computer. Started KSP using KSP.x86_64 Always starts in primary screen (left) After loading I went to settings, unset full screen, moved screen to secondary (right), accept and played one mission. Exited KSP and restart computer. Repeat On the 7th startup upon unsetting full screen, placed pointer as always on top bar of screen to move. The instant I clicked my mouse the KSP screen disappeared leaving only the top bar with the x (close) – (minimize) symbols and Kerbal Space Program. The square (full screen) was also missing. At this point there is no way to play KSP. Once the bar is closed it will never be seen again nor can you ever start KSP even on relaod. I made a copy of the logs as I played. They seemed to be identical up to the point of crash. Here is the last several lines before crash. [WRN 14:12:08.560] [HighLogic]: =========================== Scene Change : From MAINMENU to SETTINGS ===================== [WRN 14:12:08.572] The referenced script on this Behaviour is missing! [LOG 14:12:08.657] UICanvasPrefabSpawner SettingsSpawner spawning Settings [LOG 14:12:08.702] UIMasterController: ShowUI [ERR 14:12:08.852] SettingControl 'Show Version Number in Game': Cannot find GameSetting field named 'SHOW_VERSION_NUMBER' [LOG 14:12:08.873] [ApplicationLauncher] OnSceneLoadedGUIReady: scene SETTINGS ShouldBeVisible() False ShouldBeOnTop() False iIsPositionedAtTop True [LOG 14:12:15.554] Launcher here(in write): False [LOG 14:12:15.738] [MessageSystem] Reposition 6.737286 12858 On the previous play through (didn’t crash) it looked like this: [LOG 14:00:24.721] [ApplicationLauncher] OnSceneLoadedGUIReady: scene SETTINGS ShouldBeVisible() False ShouldBeOnTop() False iIsPositionedAtTop True [LOG 14:00:30.628] Launcher here(in write): False [LOG 14:00:30.813] [MessageSystem] Reposition 5.962694 12952 [LOG 14:00:38.128] Launcher here(in write): False [LOG 14:00:38.249] [MessageSystem] Reposition 12.03396 13317 [LOG 14:00:39.094] Launcher here(in write): False [LOG 14:00:39.095] UIMasterController: HideUI [WRN 14:00:39.096] [HighLogic]: =========================== Scene Change : From SETTINGS to MAINMENU ===================== The only difference is in the last line Reposition coordinates which I assume is the mouse location. The only other oddities I ran into was on my second mission when I activated a TR-18A Stack Decoupler at splash down for a contract the game crashed but restarted just fine. Also I get the following after initial install of Ubuntu: [ 3.318837] nouveau 0000:01:00.0:gr: failed to load fecs.inst I have to hard reset then all works fine. Tried to find out what this is but no luck and updates did not install. I seriously doubt that either is the cause of the problem but I could be wrong. Hopefully someone out there can make sense of this and find a solution. Thanks
  6. Secret Hamster - My problem starts when I try to move the KSP window then it is exactly as you describe. The only way I know how to fix the problem is a fresh install of Ubuntu. Then I can play for several sessions before it starts over again. Am in the process of cleaning up a spare hard drive to see if this is repeatable.
  7. The driver I am using is from Nvidia.com. When I try to update I get; nvidia-361 is already the newest version (361.42-0ubuntu2). Strange because when I check Nvidia says 361.45.11 is the newest version. Tried sudo apt-get purge nvidia-* Then reinstalled using the following; sudo add-apt-repository ppa:xorg-edgers/ppa -y sudo apt-get update sudo apt-get install nvidia-361 lspci -vnn | grep -i VGA -A 12 restart then glxinfo | grep OpenGL | grep renderer Still get; nvidia-361 is already the newest version (361.42-0ubuntu2) and KSP still will not start even if I delete and reload.
  8. Hello Got a problem with KSP 1.1.2 Just started playing again and running into a catastrophic failure while starting up KSP. I’m running Ubuntu 16.04 with a GeForce GTX 970 with dual monitors with a fresh OS install. Rather then steam I do a direct download of KSP. What happens is KSP starts up fine. I then go to settings and change screen from full to window so I can move from my left to my right monitor then make full screen again. Randomly on moving KSP crashes and will not restart even after reloading KSP. ( I like KSP to run on my right screen while having my left for toolbar and running other stuff like simple screen recorder and audacity). This happened last week and in order to fix the problem I did a fresh OS install. Now it has happened again after about a dozen sessions and would rather not have to rebuild my computer on a weekly basis to play KSP. I have tried all the recommendations from the scg_scg thead on same topic but none have worked. He is using steam and I am not. I have tried every permutation of the following I could think of but none have worked. -force-glcore33 -force-gfx-direct -force-glcore LIBGL_DRI3_DISABLE=1 %command%_64 -force-glcore33 Got only “no such job” or “command not found” The only time I got any real results was by adding (Desktop/KSP_linux/KSP.x86_64) before the above arguments but still didn’t fix the problem. Desktop/KSP_linux/KSP.x86_64 -force-gfx-direct This gave me the following. Set current directory to /home/ulrick Found path: /home/ulrick/Desktop/KSP_linux/KSP.x86_64 Mono path[0] = '/home/ulrick/Desktop/KSP_linux/KSP_Data/Managed' Mono path[1] = '/home/ulrick/Desktop/KSP_linux/KSP_Data/Mono' Mono config path = '/home/ulrick/Desktop/KSP_linux/KSP_Data/Mono/etc' displaymanager : xrandr version warning. 1.5 client has 4 screens displaymanager screen (0)(DVI-I-1): 1920 x 1080 displaymanager screen (1)(HDMI-0): 1920 x 1080 Using libudev for joystick management Importing game controller configs I admit I am a bit of a noob at this. Could someone give me a full command line that might fix this so I don’t have to rebuild my computer again.
×
×
  • Create New...