Dre4dW0rm

Worked for me. Thanks a lot.

I report the same problem. CKAN download is broken.

I really want the wings to be procedureal at least, the current selection of components for wings is pathetic to say the least.

Do we have any info on whether KSP2 design will be based on all parts being procedurally generated ? This is very serious limitation of the first KSP, and so far, every mod trying to make it work could only do that partially and at a cost.

I will wait for official SQUAD confirmation that the site is back to ORIGINAL. If it's been hacked it's quite likely the hackers will mine the login details and more.

Hi I just tried to go into the store and see if there's an update to ksp and got the same as above with my IP address though!!! Can I get some explanation as to the reason behind the ban? Last time I was on www.kerbalspaceprogram.com was some 5 months ago! And why is there no link to customer support contact or something, so that we can get assistance ?

You're right, not T2s fault, I think it was just my anger talking, after like 10th lock up. Everytime it happens, I lose the current mission, as well as another 10 min for restart. I hope it gets fixed, but I think I will have to live with it for a lot longer, due to mod incompatibility the next version will bring again. I really wished squad was more open about the changes, and which ones will or will not break the mods, so far it was very erratic since 0.22.

Thanks I will try that. It's a shame the moment T2 takes over the game breaks in such simple way. 1.4.5 will break many mods again.

This is 1.4.4 related issue only, it never happened on 1.4.3 or any prior version. When I play and go to VAB or SPH, then press ESC instead of Quit button, the game shows the Save/Load/Settings/Quit menu on the screen, which is OK. Now, pressing ESC while the menu is displayed will hide the menu, but will not return the game to its normal state. Some controls are enabled, but quit doesn't work in SPH or VAB anymore, the right mouse click doesn't rotate, the Build/Actions/Crew assignment buttons are disabled, the Switch editor type does nothing, I can't pick any new parts, save the craft or do anything. Pressing ESC again does NOT bring the menu back, the game is locked, but it's not hanging. The highlight still works when moving mouse cursor over the craft, or any UI controls, but they just don't react. The only way I can quit the game is via ALT+F4 and/or Alt+Tab and Close. I tested it on plain vanilla 1.4.4, as well as modded one, and they behave the same. It never happened on 1.4.3 before, or any other prior version, and I played the game since 0.22 or something.

I've never done it myself, but I think it's just a matter of re-upload with updated meta. Here's the guide: https://github.com/KSP-CKAN/CKAN/wiki/Adding-a-mod-to-the-CKAN

CKAN download is broken, the uploaded file is corrupted.

Grow up!

Why so aggressive?

Why can't people just switch to the built in toolbar? It seems silly to keep this one up, and an unnecessary work for blizzy to keep it up 2 date.

What do you mean, 7.4.2 is marked as 1.2.1 compatible, and yet FS1Pro definitely crashes the game the moment it's attached to the root via any part or directly.

Found it on SpaceDock in the changelog https://spacedock.info/mod/48/Editor Extensions Redux/download/3.2.14

3.3.7 no longer works in the KSP 1.1.3. The X/C functionality is back to stock, and there's no button in the toolbar.

It's not working, the patcher is connecting to the domain of my e-mail address. Squad has probably NEVER tested it outside of their own site. How poor, this is like 1000 times simpler app to make than the game itself, and they can't even get this right. I'm just so fed up with all the issues, a never ending story.

You do realize that couple means two, right? It's been 3+ weeks now since the announcement of the experimental phase, and no update so far. I assume things have gone so badly, that I will probably get to play No Man's Sky before 1.1 comes out.

[quote name='ModZero']I, in turn, would fire immediately a developer who thinks the same restrictions should apply to computer games and storm surge protection barrier driver software. EDIT: and beyond that hyperbole (I would just rant at them, I'm not the kind of a person who would fire someone for such a weak reason), I wish people had more respect for people who worked hard and brought us a successful piece of software. And IT in general could use a lot more of respect towards coworkers, by the way. Starting with an idea that a good developer never says something like "Sorry mate but this is BS."[/QUOTE] Because of thinking like this the gaming industry goes down the drain pipe in terms of quality of product and delivery for the past few years. I had way too much experience with behaviour like this, which is very expensive. The game is out of BETA now, so the erratic and random rules don't apply anymore. I stopped playing KSP only because it break saves or crafts with every release in one way or another, and I don't have that much time to keep starting over and over again. Yes, I could keep playing the old version, but it doesn't make sense. I want the latest and more stable version, but I can't actually play it. The idea was good, but execution is poorly managed, even though the game works in general. I would really like if the devs read forums at least once, gather all the real issues and missing features people were reporting all this time, and implement them once and for all - but it's been few years and it didn't happen, so I lost hope. [COLOR="silver"][SIZE=1]- - - Updated - - -[/SIZE][/COLOR] [quote name='Coyote27']Personally I don't expect any more massive changes that make craft behave differently like the aero/heat updates. The aero is probably right where we want it, and the heat seems to be getting where we want it too, so if those change in the future it probably won't be by very much. What I would expect in the near future are some new parts that might suddenly feel essential, and brand new systems like the communication relays which won't really break anything but would add a new mechanic that could change how future craft are designed. I imagine that there's a lot coming that I or the rest of you really have no clue about so far though.[/QUOTE] Well, next version is about to bring the new Unity, with PhysX support and more, so I believe almost everything will break.

Sorry mate but this is BS. Good developer always thinks about backward compatibility, ESPECIALLY when a new version comes as a micro number 1.0.4-1.0.5. If this breaks things, then the devs simply do horrible job, or don't care. I myself am in this industry for 20 years now, and I would fire developer for doing this immediately.

I have a big problem with this mod. First time I used it, it caused the NaN on my funds when recovering the vessel. This was always caused by NaN on the PCSA or PCSTs. Second, I'm unable to edit PCSA or PCST as control surfaces anymore, not sure why is it, but it worked for the first time, and now it doesn't. All I get is Show data and next config, which BTW does nothing. Currently B9PW seems broken beyond usable.

The NaN error is still there. I'm using the very latest from GitHub 3.0.1, as the CKAN is 3.0 only. I found the source of the NaN I think. It happens with procedural parts. It looks like it can't calculate something and blows up with NaN. I created a jet with procedural wings, went on for takeoff, there was some science on the airfield, so I did it, and came back - recover, only to get the NaN error as a result. I scrolled through the list of all the recovered parts, and all procedural wings had the NaN value, which caused all my funds to go NaN too.

I'm getting weird problem in 1.0.4 ksp, the button keeps on multiplying, every time I enter VAB or SPH I get a new button (dysfunctional though) on the right side of the toolbar.

Well, if you're checking for IP after connection has been made it's too late. Either you have to bind to 127.0.0.1 to make it local only, and not to 'any' local port, or you have to validate a lot more than just the IP. Also, I think you don't really have to worry much about the security in this case anyway, as majority of the use cases are in LAN only, and if there's an intruder/malware/spyware/trojan already in LAN, then it's also too late, and your software sec is the least concern for the victim.