sal_vager

Yes, the aero FX slider will do that, it'll look rougher but it will contribute less to slowdown of the game. It's possible you're running KSP with the incorrect physics values, KSP comes with a Physics.cfg in the game folder but if this is deleted it will be replaced by the game, unfortunately with older (and incorrect) values. Also if KSP is run from a shortcut outside of the game folder it will look for the Physics.cfg where the shortcut is, you can check the shortcuts properties to see if the path to the KSP.exe is in the target box, if it is not there it needs to be added. Running KSP on the desktop can also cause problems, due to how Windows behaves with programs that were not installed, just unzipped. If KSP is on the desktop please copy it to C:\Games and run the copy.

All Unity3D engine command line arguments are here by the way.

In other news, Ubuntu has created their own official personal package archive (PPA) for the latest proprietary graphics drivers, currently only Nvidia drivers are available but AMD will soon follow. This PPA supersedes the Edgers PPA, it should be compatible with all Ubuntu based distros and is preferred over manual driver installation.

Hi Nakara, please try replacing your physics.cfg with the one here, and if you use links to start the game try starting KSP using the KSP.x86 or KSP.x86_64 instead.

I may know why it wasn't seen in the bios/uefi, if it's like mine it will display the boot device priority, usually with the CD/DVD drive first, then the HDD, maybe also with a network boot option. There should be another option to change the order of HDD's, allowing you to put a different HDD first as the boot device. Though if the HDD is also seen as a DVD in the bios it probably won't be listed there, I was thinking that if it was set as the boot HDD then it might be seen as a HDD instead of a DVD.

It looks like this might be a regression, there was a similar issue with Maverick for a while and Unity hacked together a workaround to deal with it, until they could get Apple to fix Maverick's OpenGL ARB VBO implementation. As far as I know, that never happened. With the release of Yosemite we have seen a lot of issues with KSP on OSX here on the Squad forums, weird stuff such as graphical corruption, excessive memory use and of course many players suffering from frequent crashing, this goes far beyond what Windows, Linux or even OSX Maverick users have experienced. This thread discusses the Maverick issue on Yosemite, unfortunately they also say it is still present in Unity5. This is just a guess as I have not found anything from Unity themselves on this, but the Maverick workaround may not work on Yosemite, and I doubt Apple have fixed something that may only affect one customer if it's not affecting normal use, even a customer as big as Unity. I don't know if this regression has been reported to the Unity issue tracker yet as it will only show me "bugs we have successfully reproduced", maybe you have to be a registered Pro user as I don't even see a button to submit new issues.

This looks like the wheels are in radial mode, it's R to switch between radial and mirror modes, with mirror mode being better suited for the SPH. F toggles between absolute and local co-ordinates for rotation and offset. Though once you place symmetrical parts in one mode (or one symmetry level) all child parts inherit that mode, unless you place a part singularly.

Well, this is new. Receiving unhandled NULL exception Obtained 49 stack frames. #0 0x00000099b24d50 in strlen #1 0x000000001bf045 in ReadFontFiles() #2 0x000000001bf46d in DynamicFontData::GetFaceForFontRef(FontRef&, std::vector<PPtr<Font>, stl_allocator<PPtr<Font>, (MemLabelIdentifier)26, 16> >&) #3 0x000000001bf562 in DynamicFontData::GetFaceForCharacterIfAvailableInFont(FontRef&, std::vector<PPtr<Font>, stl_allocator<PPtr<Font>, (MemLabelIdentifier)26, 16> >&, unsigned int) #4 0x000000001bf6c6 in DynamicFontData::GetFaceForCharacter(std::vector<UnityStr, stl_allocator<UnityStr, (MemLabelIdentifier)26, 16> >&, std::vector<PPtr<Font>, stl_allocator<PPtr<Font>, (MemLabelIdentifier)26, 16> >&, unsigned int, unsigned int) #5 0x000000001bfcac in Font::GetCharacterBitmap(unsigned int&, unsigned int&, unsigned int&, RectT<float>&, float&, unsigned int, int, unsigned int) #6 0x000000001c395a in Font::AddCharacterToTexture(unsigned int, int, unsigned int) #7 0x000000001c49c3 in Font::CacheFontForText(unsigned short*, int, int, unsigned int, std::vector<TextFormatChange, std::allocator<TextFormatChange> >) #8 0x000000002abdf7 in NativeTextGenerator::Setup() #9 0x000000002aa1fe in TextMeshGenerator2::Generate() #10 0x000000002a9f25 in TextMeshGenerator2::Get(UTF16String const&, Font*, TextAnchor, TextAlignment, float, float, float, bool, bool, ColorRGBA32, int, int) #11 0x000000002a81a1 in IMGUI::GetGenerator(RectT<float> const&, GUIContent const&, Font&, TextAnchor, bool, bool, ColorRGBA32, int, int, ImagePosition) #12 0x000000002a0f8f in GUIStyle::DrawContent(GUIState&, RectT<float> const&, GUIContent&, GUIStyleState const*) const #13 0x000000002a0226 in GUIStyle::Draw(GUIState&, RectT<float> const&, GUIContent&, bool, bool, bool, bool) const #14 0x0000000029d14a in IMGUI::GUILabel(GUIState&, RectT<float> const&, GUIContent&, GUIStyle&) #15 0x00000000453233 in GUI_CUSTOM_INTERNAL_CALL_DoLabel(RectT<float> const&, MonoObject*, void*) #16 0x0000001b8c933d in (wrapper managed-to-native) UnityEngine.GUI:INTERNAL_CALL_DoLabel (UnityEngine.Rect&,UnityEngine.GUIContent,intptr) + 0x2d (0x1b8c9310 0x1b8c935b) [0x6d05e00 - Unity Root Domain] #17 0x0000001b8c92f8 in UnityEngine.GUI:DoLabel (UnityEngine.Rect,UnityEngine.GUIContent,intptr) + 0x18 (0x1b8c92e0 0x1b8c92fd) [0x6d05e00 - Unity Root Domain] #18 0x0000001b8c92ce in UnityEngine.GUI:Label (UnityEngine.Rect,UnityEngine.GUIContent,UnityEngine.GUIStyle) + 0x36 (0x1b8c9298 0x1b8c92d3) [0x6d05e00 - Unity Root Domain] #19 0x0000001b8c9282 in UnityEngine.GUI:Label (UnityEngine.Rect,string,UnityEngine.GUIStyle) + 0x42 (0x1b8c9240 0x1b8c9287) [0x6d05e00 - Unity Root Domain] #20 0x00000055203ae3 in ScreenMessages:DrawGUI () + 0x4c3 (0x55203620 0x55203f33) [0x6d05e00 - Unity Root Domain] #21 0x0000005520360a in ScreenMessages:OnGUI () + 0x52 (0x552035b8 0x5520360f) [0x6d05e00 - Unity Root Domain] #22 0x000000062e0c89 in (wrapper runtime-invoke) object:runtime_invoke_void__this__ (object,intptr,intptr,intptr) + 0x41 (0x62e0c48 0x62e0cdd) [0x6d05e00 - Unity Root Domain] #23 0x000000013b8a16 in mono_jit_runtime_invoke #24 0x000000014ec4b7 in mono_runtime_invoke #25 0x0000000024a98f in scripting_method_invoke(ScriptingMethodMono, MonoObject*, ScriptingArguments&, MonoException**) #26 0x000000003540f4 in ScriptingInvocationNoArgs::Invoke(MonoException**) #27 0x0000000034475c in MonoBehaviour::DoGUI(MonoBehaviour::GUILayoutType, int) #28 0x0000000029a162 in _ZL18MonoBehaviourDoGUIPvN13MonoBehaviour13GUILayoutTypeEi #29 0x00000000299a79 in GUIManager::DoGUIEvent(InputEvent&, bool) #30 0x000000002993e7 in GUIManager::Repaint() #31 0x000000002f194a in PlayerRender(bool) #32 0x000000002f2457 in PlayerLoop(bool, bool, IHookEvent*) #33 0x0000000065e65c in -[PlayerAppDelegate UpdatePlayer] #34 0x0000009a168bab in __NSFireTimer #35 0x0000009be842a6 in __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ #36 0x0000009be83c37 in __CFRunLoopDoTimer #37 0x0000009be62cd0 in __CFRunLoopRun #38 0x0000009be621dc in CFRunLoopRunSpecific #39 0x0000009be62088 in CFRunLoopRunInMode #40 0x00000091ac2543 in RunCurrentEventLoopInMode #41 0x00000091ac98ab in ReceiveNextEventCommon #42 0x00000091ac971a in BlockUntilNextEventMatchingListInMode #43 0x0000009ab08ee8 in _DPSNextEvent #44 0x0000009ab08752 in -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] #45 0x0000009ab04ac1 in -[NSApplication run] #46 0x0000009ad95ac5 in NSApplicationMain #47 0x0000000065e3ab in PlayerMain(int, char const**) #48 0x00000000003095 in start I think it's saying you have a corrupt font, I have no idea how to fix that so all I can do is point you to OSX support threads, hopefully fixing the fonts will fix KSP. It's something to try at least.

Well this adds a lot to a two year old thread, try starting a new one. Closing!

2.3 Forbidden messages Messages that inquire about release dates for future versions of KSP.

You could see if this still works. Slumpie's stock scaling bug fix.

Can you put the file on dropbox please ?

Maybe the player.log has some clues. Console might be Finder, and the files may be hidden.

Very interesting, but easily worked around by using parts such as winglets, SAS with reaction wheels or engines with gimbals to stabilize your rocket. If you want to report this as a bug please see the bug reporting guide

Just install 0.13.3 and go to the Mun and back

Squad isn't providing 1.0.3 anymore, just 1.0.4 and the previous stable version 0.90.0, so be leery. You can get KSP from the Squad store, GoG.com, GreenManGaming (Steam key), Humble store (also Steam key) or Steam. I do not recommend you use Amazon.

Sorry no, aside from completely reinstalling Windows, I don't know what is causing your issue but a blue screen is indicative of serious problems with your operating system. The minidump tells me nothing however it's a "system_service_exception". You can find more on stop errors here, you could then see if there's any fixes on Microsoft Answers. There's a hotfix for Windows 7, you don't say what you're using however. Also you should ask on the Unity forums in case others have run into this with other Unity games. A simple workaround would be to (A) don't plug in the webcam, or ( plug it in ahead of time. KSP doesn't use your webcam in any way by the way, though this doesn't rule out the Unity engine polling for webcams, and while there is support for TrackIR it's off by default if no TrackIR device is present.

Well done Maestro22, I didn't know that option was hidden, I even have it on Linux with the Nvidia driver, it's called "Image Quality" for me Marking as solved!

Actually I think that's what Claws fix does as well, it's just automatic.

Hmmm, well, it should work if it's a standard Ubuntu install (or one of the Ubuntu variants) and the graphics driver from the repository, Steam is in the repo as well. Ckan can cause issues with KSP if ckan isn't in the KSP folder, as it doesn't set the path to the binary file, so KSP ends up looking for cfg's on the desktop or wherever. If you have not yet installed the gfx driver and you're using Ubuntu 15.04 64bit, try these in the terminal. For Nvidia: sudo apt-get install nvidia-346 For AMD: sudo apt-get install fglrx Reboot so the gfx driver starts up (it's easiest this way) Then: sudo apt-get install steam-launcher Then start the KSP.x86_64 directly.

Glad it worked as if it hadn't I'd have been stumped It's not the memory used, though I first thought that to be the case, it's actually the hooks (Wikipedia) it puts into running processes that the software needs in order to work, it makes things unstable.

Hi Stir_Fry_Beans, I don't see errors in your log, but your pics look like the anti-aliasing bug. Please try disabling anti-aliasing in the KSP settings then start the game again. I'd suggest updating your graphics driver, but apparently that isn't something you can do on a Mac.

Oh I thought I got them working, must only have worked for me as they were in my cache after trying to fix them. Hmm, if you can show craft turning south when they have parts on the north side, that would be interesting.

Yeah it's a known issue, there's lots of threads on this one Claw has made a fix which you can find in his sticky at the top of this section which deals with this issue for now, and 1.1 will see completely replaced wheel code, but there are no plans for any interim patches.

Don't overlook RCS for flight control, it's surprisingly effective now.