Furious1964

I'm not that savvy with coding, so I'm going to have to live with it as my test with 32Bit crashed after installing 41 Mods...that's half of the mods I wanted to install. Sorry to be a complete pain, bother and jacktard to everyone. I have no choice BUT to use 64Bit. I don't know if the option to use OpenGl has changed or not and I don't know if it will crash because of the amount of mods used.

What I meant to say is that, yes, the warning should be once. But couldn't there have been an option to disable that from happening when the game is restarted? I'm currently testing the mods I have one at a time to see if they work and I keep getting the Nyan Cat and warning. Yes, it is cute and funny...the first time around. Sorry if I'm being a pest and a complete tard, but once is enough. And does anyone know the MEM limits for OpenGL?

First of all, I appreciate what the modders are doing and that their work is free. I have no problem with that. I have a problem with not being given a choice. If a person wants to use 64Bit, then it should be his choice and he should get one warning. After that, if anything goes wrong, he has no reason to complain because he was warned. Secondly, I just started to get the latest version of KSP and all of my mods (was still playing 0.24.5) because they were updated. Thirdly, I'm not too savvy with Linus and have no external drives for a back-up of Windows 7. I read the Linux instructions, but I see no need for an extra expense just for a game. Lastly, I have tried OpenGl in 0.24.5, but had serious graphical glitches. So there's absolutely no need to wag you finger at me, Sir. As I said: I appreciate what the modders are doing, but users SHOULD be given a choice and one warning.

Already have that and installing it now, But I was experiencing tons of MEM crashes with 32Bit and I had ATM in 0.24.5 and earlier. That's why I use 64Bit as I search out my problem and found out the limits of 32 and 64Bit. Will see if it crashes if I run it with all the mods AND on 32Bit.

I know that, but the mods I use push it over that limit. That's why I use 64Bit. As for Dual Booting, I don't have Linux and wouldn't want to screw up my system already if something goes wrong.

Is there a version of this that doesn't have the annoying 64Bit warning and Nyan Cat? I DON'T need this! I have to use 64Bit because of all the mods I use. If I were to use the 32Bit version, the game would constantly crash because it ran out of memory...even though my system has 16GB RAM and my next upgrades will push it to 64GB. If you wanted to warn people of the problems with 64Bit, then do it in a pop-up window with a check box saying "Do not show again. Use at your own risk".

Does this support 0.25?

Is there any way to move the MechJeb Sidebar Tab down? It's obstructing the menus in the upper right corner.

If that is the link to the untested 64bit version, then I'll test it after work.

I hope this gets looked into as it just might be.

-redacted- Figured out the problem, I had to attach something to the rocket in order to see it.

For some strange reason, Kerbal Engineer isn't showing up in the toolbar. And ideas?

I used to have a lot of crashes with or without using ATM. I tried several things, but nothing helped. Then I looked at the output log of a crash and found a lot of the errors were due to modstatistic being installed. I deleted that and associated the shortcut to the launcher and now I haven't had any crashes since. Will test ATM on my game later.

Oh, so the detector is rover based and not sat based. Was putting it on a rocket. But the readouts are in a pop up window or something. And do I need MKS and/or SCANsat?

OK, but when a probe is in orbit with the scanner, does it map in on the planet or do I get a pop up window?

So I tried this with the new .dll and it still explodes when anything is detached. Any idea on what's causing it? I know the Majiir is busy with that Kerbal Cup thing, but is anyone else working on this?

What other mods do I need to get this to work? The standalone version doesn't work, can't be assigned to an action group and it doesn't display anything.

I have the latest Firespitter (633) and KSP 0.24.2 and I'm still getting an incompatibility warning for Firespitter. Is this a false positive? Is this updated yet?

Hopefully, this will be updated soon. Waiting patiently. Any ETA for this?

But it functioned perfectly in 0.23.5. Was Real Chute already in your code?

Is smart auto staging also research able? When 0.24.0 came out, I made a new game and everything researched.

I've been testing it out and I get those errors in the debug console too. Nothing I do gets this to work right and I end up having to manually do the stuff Mechjeb is supposed to do. The Floating Kerbal Is now long dead.

I've set up every node with MechJeb, had enough of everything, but this mod doesn't execute anything beyond Guidance Assistant. When it tries to make an intercept course with anything, it just flies off into deep space. And no, I'm not asking for anyone to tell me how to do things, what I'm saying is that the functions of MechJeb are not working.