Problem AMSO Lunar Rover Crash

Hi Guys,

Please also test with the following modules set:

http://www.acsoft.ch/tmp/Test2-Modules.zip

With this set, guilty preloading is just moved elsewhere into the code of the main Apollo vessel module. It seem to also solve the CTD problem. Again, don't ask me why !!!

This is a better solution, if it work for everybody.

I recommend to play the following scenario for testing the FIRST set:

AMSO\AS-512\Apollo 17 step 4.scn

It is the extraction of the LM which will create the LM vessel and therefore execute the LRV meshes preloading.

Otherwise, for both set of modules, the main test scenario is obviously:

AMSO\Miscellaneous\Apollo 16 LRV deployment.scn

Thanks in forward for your tests & reports.

ACS
 
Thanks ACS! It works PERFECTLY with those new modules!:thumbup:
Mantis,

You mean with both set Test-Modules AND Test2-Modules ?

ACS
 
Actually, I just tried the second set. I assumed that they superceded the first set. Should I try it with the first set as well?
No, you don't need.

This is the set I prefer to adopt for the official patch, as it do not introduce a small hang up during the LM extraction.

ACS
 
No, you don't need.

This is the set I prefer to adopt for the official patch, as it do not introduce a small hang up during the LM extraction.

ACS

Thanks for all your help! I'm going to re-fly the "J Missions" now that I can use the rover. As I said, this is my favorite addon of all. :tiphat:
 
Thanks for all your help! I'm going to re-fly the "J Missions" now that I can use the rover. As I said, this is my favorite addon of all. :tiphat:
Would be nice if you can fly one of them the next few comings days and report here that, hopefully, you didn't encounter any other CTD or other major problems.

As I said, the modification I made is not a real correction, but an empirical change, which apparently overturn the problem. Therefore, I hope it is not just that the problem was displaced elsewhere by this modification.

In this meaning, I will wait almost until Sunday evening before to publish the new patch.

ACS
 
Would be nice if you can fly one of them the next few comings days and report here that, hopefully, you didn't encounter any other CTD or other major problems.

As I said, the modification I made is not a real correction, but an empirical change, which apparently overturn the problem. Therefore, I hope it is not just that the problem was displaced elsewhere by this modification.

In this meaning, I will wait almost until Sunday evening before to publish the new patch.

ACS

Certainly, I'd be happy to do that!

:thumbup:
 
Xyon
Thanks for the .dll information, when I checked vc++2008 wasn't on computer. It is now.

ACSoft
Tried both test modules and rover still crash's. Even tried on another vista machine and same result. I also tried AMOS 1.19 with Orbiter 2006p1 and in this case the rover deploys and missions can be completed. Thanks again for your efforts.
 
Ok ACS, I flew the entire Apollo 15 mission from launch to landing with no trouble at all. I really like the way the rover works - makes it much easier to get around on the moon!
 
Test2 also fixed my CTD on the Rover(didnt try test1). Using 2010P1 with Vista x64. Thanks!
 
ACSoft

Just tried Orbiter 2010P1 using zip & msi versions, with and without your Test2. Lunar rover still crash's. Am I doing right by unzipping test2 into Orbiter base. Also Compatibility wizard keeps poping up, so I've tried the options in that. I've no idea what to do next.
 
ACSoft, am I doing right by unzipping test2 into Orbiter base.
No !!! It's wrong !!!

This archive contain a set of module dll, BUT WITHOUT PATH. The way you have done has unzipped the set into the root directory of Orbiter.

You must put this set into:

OrbiterRoot\Modules\AMSO\

Try it and report if it solve also the problem for you.

Thanks in forward,

ACS
 
ACSoft

Happy Days!Wonderful! Brilliant!Spot On! It Works
Many Thanks Orbitnovice
 
WOW!!! After a few busy days I've caught up with the thread, DLed and tried Test2 in my working install (100606 on Windows7 Home Premium...haven't got the P1 version yet.), and ...it works!

ACSoft, Many, many Thanks! It's thrilling to get in the rover and drive around, so much better than walking/hopping.:) Again, thanks.

And Orbitnovice, thank you as well. I was kinda wondering where to extract it to as well!





:hail::probe:
 
Thanks Guys !

I am happy it seem to work now for everybody !

I suspect that maybe this CTD is linked with ATI graphic driver (who apparently use msvcr80.dll library). Those who suffered of this CTD, could-you report if your PC is equipped with ATI hardware ? This would be interesting to know.

ACS
 
Thanks Guys !

I am happy it seem to work now for everybody !

I suspect that maybe this CTD is linked with ATI graphic driver (who apparently use msvcr80.dll library). Those who suffered of this CTD, could-you report if your PC is equipped with ATI hardware ? This would be interesting to know.

ACS

Hello ACS...I do indeed have an ATI Radeon Mobility adapter in all of my computers. My main notebook has an ATI Radeon Mobility 5870 with 1 GB of dedicated RAM and my secondary notebook has an ATI Radeon 4350.
 
Last edited:
ACS

Thanks Guys !

I am happy it seem to work now for everybody !

I suspect that maybe this CTD is linked with ATI graphic driver (who apparently use msvcr80.dll library). Those who suffered of this CTD, could-you report if your PC is equipped with ATI hardware ? This would be interesting to know.

ACS


No sir, Im using an Nvidia Geforce 9600GT. It always crashed on LRV in 2010 until that latest patch (test2). Sure is nice exploring the Moon in style now :thumbup: :hail: :probe:
 
Interesting ! So we know it do not depend of a specific graphic hardware.

Turbo, do-you remember if you crashed also inside the famous msvcr80.dll library ?

ACS
 
Back
Top