Here you'll get the current version and patches of IMS. Updates will be posted in this first post.

RC1 is out! Everybody, get something to drink!!

get RC1 here

Current coding priorities, in this order:

-get my life back



=======Update============
(no particular order yet)
-dual mode for thermal engines
-gyros
-multiple directions for radiators
-configurable maximum acceleration
-touchdown points
-payload system
-IMS editor (scenario editor derivative)
-Orbiter Sound support
-Graphics Client support


Done:

-composite modules rework (0.8.2)
-gear shifting for drives (0.8.1)
-booster MFC (0.8.1)
-button to delete docking ports x through y (0.8)
-autosave (0.8)
-save finalised vessels to config files (0.8)
-save state for panels (0.8)
-transport seal (0.7.9)
-external cooling (0.7.8)
- CoG rework (0.7.5)
-external power (0.7.4)
-marking overheated radiators on schematic (0.7.2)
-marking radiators belonging to selected module on schematic (0.7.2)
-failure modes (0.7)
-ability to take generators offline completely (0.7)
-finish engineering panel (0.6)
-transfer of propellant and consumables (0.5.7)
-finish Pilot panel (0.5.7)
-wasteheat managment (0.5)
-rough energy management (0.4)
-support for energy sources other than solar panels (0.4)
-Reworked RCS assignment (0.3)
-Get rid of dynamic heating code (0.3)
-made fuel capacity a general parameter (0.3)
-support for general purpose modules with an animation (0.3)
-support for life support and storage modules (0.3)
-support for multiple exhausts per engine (0.2.4)
-support for antenna modules (0.2.4)
-support for airlock modules (0.2.1)
-support crew transfer through permanent docking ports (0.2.1)
-add airlocks for permanent docking ports (0.2)
-add non-permanent docking ports as construction helpers (0.2)
-Remove all unnecessary stuff from the control module (0.2)
-support for modules that provide additional docking ports (0.1.1)
-Fix engine assignment (0.1)
-add exhaust definitions for thrusters (0.1)
-Get rid of VC and make a fully compatible 2010 panel instead (0.0.8)
-adapt code to VESSEL3 class for Orbiter2010 (0.0.8)
-Get rid of CTD at scenario load (0.0.7)

Fixed the CTD at scenario load, so now you can play around a bit more and don't have to rebuild your vessel from scratch every time.

I also noticed that you can't attach files to posts in social groups. That means you won't be able to attach meshes and config files either. Does anyone here have a bit of webspace we can use? Shouldn't need much. I attached the patch above to the public dev thread which is good enough for now, but not an option in the long run.

Small update on progress:

Implementing the Panel proves to take an unexpected amount of time. Major reason is the lack of documentation on the new panel architecture. I followed the tutorial in the API doc, thinking that if I do it the old way it won't be too hard to then upgrade it to the new one, but it turns out that I have to completely rewrite most parts of the panel code to adapt it to Orbiter 2010. I still hope that I can call the panels done after this weekend and release a new patch, since I really can't afford to spend much more time on panels, but I'm not quite sure yet.

On the other hand, there hasn't been a single confirmed Bug yet, which is really weird. I remember that there was quite a few of them left over last time when I was the tester, mostly connected to the heating and power code, but I can't exactly remember what they were. Testers, if you figure out some bugs while I finish these pesky panels, that would be really great, because then I can get around to fixing them immediately when I finish.

bit of bad news, now that I finally got the hang of how panels work in Orbiter 2010, it turns out that the old drawing methods of the displays won't work at all anymore. I had hoped that I could do a temporary version that still uses the old GDI calls and turn my attention to more pressing matters, but it looks like I have to do the whole thing now. Could well set me back another week...

A bit of better news, bringing the panel to a functional level didn't take as long as I feared. I have to give martin credit to design the sketchpad interface in a way that makes it really simple to port code from the old GDI drawing. Once you figured it out, that is...

Anyways, before a new patch goes up I want to get all the original meshes together again, and implement the one or other usefull thing. Like tank capacity based on volume, and support for more fuel types. This shouldn't take too long... then again, I think that every time when I lay hands on that code.

New version's up. Most work involved porting everything from Orbiter 2006 to Orbiter 2010 Panel architecture and sketchpad, but there's some bugfixes too, and the new feature to define an exhaust point for thrusters (RCS blocks not yet supported). See config writer's guide, moduletype engine for details. Also, LH2 is now an officially supported fuel type.

Making a module add a docking port to the IMS vessel was easy, making the freakin' thing stay in the same place not so much. Fortunately I had most kinks of the cog shifting code worked out from the exhausts, so now I got to the bottom of the matter a bit quicker.

Check config writers guide for how to add docking ports to your modules!

Preparing for airlock implementation, which requires quite some changes to the code (the UMMU-handling is currently absolutely static). It's as good a time as any to tear all the unnecessary integrated stuff out of the control module, like deployable docking port, integrated RCS and radiator.
It'll make the code a lot cleaner and it'll be so much easier to create new command modules, and the bloody docking port won't be able to wreack havoc with my airlocks...

In essence that means that my code won't be in working condition for the next few days, don't expect any updates soon.

Next update will probably take a bit longer. There's several issues with the docking port adaptation, many of which are fixed by now, but a few still remain. Looks like my system wasn't as foolproof as I thought...

i have something to say here i put IMS 0.1 on my Orbiter and when i spawn the Command Module my orbiter Crashes

have you installed the 0.1.1 patch? also, please post bug reports in the bug reports section. In this case, best together with your orbiter.log.

oki doki ive installed the patch ill post in bug reports now

Updated link for 0.1 base package, this time with the textures in the right place. Sorry for the inconvieniance.

Link updated again, this time for a package that has been tested on a clean install. Shouldn't be anything missing anymore now.

I thought I'd certainly have the new version up today, but I'm not so sure anymore. Basically all is done that I wanted to do for this one, but I am fighting with what might be an Orbiter bug. Plus, I'm fighting with DanStep's unfathomable use of directional vectors...

I still hope I get this baby up before going to sleep.

I'm about to go to bed, but here's a new version. So many things have changed that it deserved it's own itteration, so this is now officially 0.2. It's probably full of new bugs, have fun finding them!

I've made it to the Moon using IMS, so it's sertified as spaceworthy in my book now

Nice little contraption. Mind if I post this in the orbiter screenshot thread for a bit of awareness-building for the project?
Of course, you can just post it there yourself. You built this thing, after all.

That's a curious RCS setup. Does IMS handle pitching correctly with this configuration?

You are free to use this picture as you like, it's you who made it possible
This kind of RCS setup works fine. But it gave weird results with only two opposing RCS modules attached. I'll make some testing later.

Blast! somewhere there's a major memory leak in connection with having no crew aboard. No idea what's going on, but completely unrelated pointers suddenly point to random places when I EVA the last one

On the plus side, airlock modules with door animations otherwise are working. Now I have to stuff that leak and get the code for vessel to vessel transfers going, and we're all set for 0.2.1.