FlyingPete

Agreed. If 64-bit is required for stable operation, the developers should just commit to that. And announce it properly rather than just focus on shiny new features.

The question remains though: what is the "write to location(hex code) caused an access violation" error all about? What causes it?

I stick with 32-bit windows because I also have several old games which are problematic on 64. Like I said, if 32-bit isn't enough, why is it officially supported. Either the developers should ensure it will be stable, or else commit and say that 64-bit is required. My system meets the required specs, so I expect it to work- albeit with detail settings etc turned down which goes without saying. I'm reluctant to simply throw hardware at the problem- KSP still seems to leak memory and I'm unconvinced that adding more wouldn't simply delay the problem. I don't even have that many ships/parts in orbit- I never get far enough without a random crash. Monitoring RAM/CPU usage on the other screen, it's usually above halfway on both but never maxing out, so I'm not convinced that "add more boosters" would fix it. How about running a dual-boot setup with 64-bit linux and running ksp in that? Then I can keep Windows for compatiblity and make use of the extra RAM in Linux. Then we'd see if the issue goes away.

Latest crash file from today:

I get on better with a gamepad rather than a joystick. The two sticks can be used for all three rotation axes plus fore/aft translation, with the d-pad for the other two. I put pitch/yaw on the left stick as this works better for rockets and in space. I'd like to try using a flight yoke and pedals along with a separate stick for translation. Could take some skill to coordinate all six axes at once though!

I've seen (and since attempted to copy) a design where a SRB is used as a strong and non-bendy structural member as well as an engine. Fire it at altitude (as the jet engines start to expire) to cover the gap before nukes become effective.

The best way I've found on Minmus is to have two wheels, segway-style. Have landing struts for parking and a SAS gyro for stability. The extra load on two wheels gives better traction. RCS is a must though.

Any developments on this?

Well if KSP requires 64-bit windows to run, why is the 32-bit even available? It always used to work fine until 1.0 came out- if not for the outdated aerodynamic model I'd probably have gone back to 0.90 by now.

Here's my PC specs: Processor: Intel Core2 Quad Q6700 2.66GHz Installed memory: 4.00GB (3.25 usable) 32-bit Windows 7 Graphics card: Nvidia GeForce GT730 KSP was running without issues on this system from 0.18 up to 0.90. Here's the contents of output_log.txt:

I think a reasonable compromise would be to have a stack of disposable first stages kept in Eve orbit. The reusable upper stage collects one before descending to the surface. Top-up with fuel refined locally, then drop the lower stage during ascent. You'd need to periodically ship a supply of lower stages from Kerbin, but all the important bits would be in the reusable upper stage.

Just re-read this starting right back at Eve: Order Zero. Spotted a few plot intricacies around the Kerbulans which I missed before! Excellent writing and looking forward to the conclusion!

I always tend towards "Minmal"

Tried increasing the virtual address space to 3gb as suggested... no effect. Business as usual with this 'access violation' issue and the increased space doesn't seem to be recognised by KSP.

I've built a fuel truck before that has a grabber claw at one end. On Minmus you can land things with reasonable precision, so it should only be a short run from mining base to a landed ship. Make the core of the truck an orange tank or one of the Kerbodyne tanks if you really wanted to. Certainly easier to handle than a train of several tanks.

Still having problems with the same issue as previously. The game repeatedly crashed to desktop (sometimes while not doing anything particularly taxing) which is making it virtually unplayable- I can't even design a spacecraft properly since the game keeps crashing. It's always with the same issue in the error text file "Write to location (hex number here) caused an access violation." Sometimes there is an error window up on the desktop, sometimes it just quits without explanation. This is a completely stock game, no mods whatsoever. I have the maximum 4Gb of RAM installed on a 32-bit windows, so that shouldn't be the issue. Here's the four crash files in the space of the last hour or so:

I think the Duna record is going to take some beating- especially with a height above ground of 47m!

So Kulebron's efforts with a near-explosive heat shield make 12,965m the new Kerbin record. Any takers for the other planets? Eve and Jool should be interesting..

Perhaps refuel at Gilly and make your orbital change at Gilly's apoapsis. Then hope you can ge out of the atmosphere and make a low orbit to rendezvous with the main ship afterwards.

Eve should be fun to explore. How about an kerbed atmo-dipper that will dive into the upper atmosphere and return to orbit? Plus an unkerbed probe or two to land on the surface. Gilly's gravity is so low you can almost treat it as an asteroid and park the whole ship there-dig some ore for the return trip. You could have the mining equipment as a separate section and leave it behind (no sense hauling it back to Kerbin) for later use by future expeditions.

Getting your spacecraft into the relevant orbit is allowed by any means you like as that's not relevant to the challenge. Heat shields (or anything else used as ablative armour) and staging are also fine unless said staging is used for nefarious purposes like providing significant thrust through decoupler spam. You could throw an asteroid at a planet an use that if you wanted to. Ballistic trajectories and aerodynamic craft are treated equally. Looks like the Kerbin record is currently held by vyznev at 19,965m according to the video.

I don't mean re-entry as in slowing down to <1000m/s, rather an orbit or flyby with a Pe inside the atmosphere, and coasting through and back out into space. Obviously slowing right down and getting back to space without engine firing isn't possible- you need to carry enough speed through to get back into space.

Well on Kerbin for example, getting 5m below 70km and coasting back out again would count, and the record would then be set at 69.995km. There's no set target, but the lower the better!

The concept is simple. Re-entry from orbit, get as close to the ground as possible and return to space. No engine firing allowed while in atmo. So this will take efficient aerodynamics to get back into space, and good cooling design to prevent from being cooked. Any kind of ship design is allowed as long as engines are off once you enter the atmosphere. Separate limbo categories for: Planet Record Gained By Duna 888m Kulebron Laythe Kerbin 12,965m Kulebron Eve Jool

The Mun can be useful if it happens to be in the right place at the right time. Otherwise, it's not really worth the hassle. Far better to mine the Mun or Minmus, launch empty and fuel up there. Sometimes Eve or Kerbin itself can be of use for a slingshot to elsewhere.