AMSO version 1.18 published

[jarmonik]

Now to say, the development will be frozen until we know what will happen with the new version of Orbiter. Actually, speaking of AMSO, the backward compatibility of the future new version of Orbiter is really catastrophic. The tests we made with recent Orbiter beta versions do CTD for almost 80% of AMSO scenarios, even before the scenario is fully loaded.

If I remember this correctly this problem has allready existed longer than a years. But all that could be caused by some small bug hiding somewhere. So there is no need to lose hopes yet.

If Martin could reproduce the CTD in a debug environment, that might give some ideas where the bug is hiding.


-----Posted Added-----


BTW, what will happen if you build AMSO using OrbiterSDK 08 instead of 06 ?

 

[Missioncmdr]

The new rover looks great, but I think I should read the manual the next time before I try it. Do you plan making the assembly of the rover a player task? The final outfitting of the rover consists of many items just appearing out of nowhere, I doubt you planned this to be final after adding many great animations.

And what about the MESA pallets?

http://www.myspacemuseum.com/mesa.htm

I think an animated MESA would work well with the rover missions. After the initial rover deployement, you could drive it around the back of the LM to the front of the MESA (as was done during the missions). Then, you could retrieve the various rover parts in a similar fashion to how the other items (like the flag and ALSEP) are retrieved and attach them to the rover.

Of course, the H-series and J-series MESAs were quite different in that the H-series MESA was smaller and more simpler. The only question is how much detail would be necessary.

Of course, these are all only suggestions and ACSoft should do whatever he sees fit. AMSO is still awesome and the new rover has an amazing amount of detail.

 

[Moonwalker]

BTW, what will happen if you build AMSO using OrbiterSDK 08 instead of 06 ?

That's what I would like to ask too.

Most addons, if not all addons, have to/should be compiled using the latest OrbiterSDK anyway once the new Orbiter version is released. But maybe some configs of the new Orbiter version will be different too, so most scenario files also require updates I fear...

BTW, any information when the new Orbiter version is going to be released?

 

[ACSoft]

I think that is only understandable, but maybe you can get this problem solved before the new version of Orbiter is released, by just giving detailed feedback to Martin. I think you just use what the API gives you and do not use direct meddling into the core of Orbiter (As far as I don't see you do something impossible with the API), so your feedback might be useful finding out what the correct behavior of the API functions should be.

I exclusively use the API and I have contacted Martin several times about these backward compatibility problems. Martin is the only guy well placed to efficiently use AMSO as a "Test addon" for backward compatibility of his Orbiter new version and perform the necessary investigations. On my side, I am almost "totally blind". Of course, I already told Martin that I am at his disposal to collaborate with him for this task, if he decide to do it.

Martin told me that he might do this, but only when the new features codes and new structures of Orbiter will be more or less stabilized, which seem to me totally logical. So, actually, I am waiting and hoping this will happen.

The new rover looks great, but I think I should read the manual the next time before I try it. Do you plan making the assembly of the rover a player task? The final outfitting of the rover consists of many items just appearing out of nowhere, I doubt you planned this to be final after adding many great animations.

And what about the MESA pallets?

Making the final assembly of the rover as a player task is something who might appear in the future. The code has been designed with this in mind. But, unfortunately, they are some missing API to do it well and in the easy way. Think about the fact that now, for example, you can return inside the LM all around it, as far as you are inside the proper distance intervall and not only on the foot of the ladder.

ACS


-----Posted Added-----

That's what I would like to ask too.

Most addons, if not all addons, have to/should be compiled using the latest OrbiterSDK anyway once the new Orbiter version is released. But maybe some configs of the new Orbiter version will be different too, so most scenario files also require updates I fear...

I didn't waited your advise to try this, but it maked no difference, almost with the version I used to try this. Like I said in my previous answer, only Martin can efficiently track these problems. What I can do, is to help him doing this, which, of course, I will do, for example by compiling AMSO with whatever SDK Martin would like to see AMSO compiled with, even a special one, with more powerful debug functionalities.

BTW, any information when the new Orbiter version is going to be released?

This is a question you should ask to Martin, not me !

ACS

 

[Urwumpe]

Think about the fact that now, for example, you can return inside the LM all around it, as far as you are inside the proper distance intervall and not only on the foot of the ladder.

Yes, but thanks to CTRL+J, it is now less annoying as in the past, as you can use this menu for finding out which action J will cause at this distance.

 

[Apollofan]

I am sitting here with tears in my eyes....excellent work!!!