Cannot exit VAB after 1.0.5 installed

[mdailey403]

I tried to play after 1.0.5 was installed and I am not able to leave the VAB. I cannot exit to Space Center and I cannot exit to Launch. I am unable to leave the VAB whether I have a ship active or if it is blank after clicking on New. Why does this game always break on me?!!!!

[Mikster]

Yes, i have this bug to, i also cannot launch either, which kinda spoils the whole point of the game

[Speadge]

can you guys post a list of mods that could be a Problem since the update? Did you try it without modding?

[9bananas]

got the same issue, also since 1.0.5 update. i'm running 64-bit version, but i've been searching around for a while and am 70%+ sure that it's not related to 64-bit unity (it's pretty damn stable for me, haven't had a crash for a month or so). when checking the dbug console i found out that i'm getting null reference exception errors. i have no craft files, happens immediatley when i start the game. glad to see i'm not the only one -.-'

[razanon]

same happens to me, ksp x64 without mods, WORKS ok. installed compatible mods via ckan, WORKS ok, im pretty sure its a 1.05 not supported mod

[9bananas]

UPDATE: got it working with a bunch of mods, strictly using mods that are definitely 1.0.5 compatible (via ckan). was using quite some 1.0.4 mods before, although i read the devs blog before the update and i remember them stating, that the update shouldn't break stuff.

i'm not going to disable my mods one by one to see which one is causing the issue...the install in question has 55+ mods...it takes like full 5min to even get to the main menu...not gonna do that all day long -.-

i'm on a new install now with fewer mods, and it's working just fine.

soooo.....oh well...i'll just wait for the updates...

[razanon]

UPDATE: got it working with a bunch of mods, strictly using mods that are definitely 1.0.5 compatible (via ckan). was using quite some 1.0.4 mods before, although i read the devs blog before the update and i remember them stating, that the update shouldn't break stuff.

i'm not going to disable my mods one by one to see which one is causing the issue...the install in question has 55+ mods...it takes like full 5min to even get to the main menu...not gonna do that all day long -.-

i'm on a new install now with fewer mods, and it's working just fine.

soooo.....oh well...i'll just wait for the updates...

as my frend said, installing CKAN compatible mods, grants fully VAB functionality.

i had all my stuff installed when 1.05 came up, and cant enter VAB. uninstalling all, vanilla x64 ksp, works fine. COMPATIBLE CKAN MODS, works fine. so thats the clue, im pretty sure its only one md having that problem, but same as my friend bananas, i havent time to test one by one all incompatible mods, so, for me, its ok.

[9bananas]

yeah, right? i'm like...whatever...i still miss a couple mods, but nothing i can't live without

also, i'm using the 32bit version for. i was too lazy to install all the graphics mods, so i don't really need 64bit for now^^

[SnakyLeVrai]

This is probably caused by Action Groups Extended, I've experienced the same thing. This issue has been addressed; kudos to M. Diazo. New 1.0.5 compatible version here -> http://forum.kerbalspaceprogram.com/threads/74195-1-0-4-(Jul09-15)-Action-Groups-Extended-250-Action-Groups-in-flight-editing-Now-kOS-RemoteTech

Edited November 12, 2015 by SnakyLeVrai
typos