Iron Hill Project Thread

This was my first chance to run Orbiter since the landing, and now I'm getting a CTD. I did have SSK installed but tried to download it again. No luck with the CTD, but everything was working when in orbit. Error messages at the end of the attached log, but I don't know how to quickly fix this. What download did I miss?

Rick
 

Attachments

We have arrived safely back at Iron Hill:)
I'd like to spend the next couple of days getting the tables and lights set up.
Rick, you haven't gotten to do anything on Mercury yet, so I'd like you to set up the tables. We need two in the wardroom placed end to end, and one each in the science lab and the rover workshop.

Felipi, when Rick is done, your job will be to use the beam lights to outline a landing pad for the Arrow.

No pressure on either of these--just whenever you are ready;)

Oh, and I disabled Orulex, because it seemed to be causing trouble for both of you. Man, I'm going to miss that view:(
 
Last edited:
For me it's NOT a problem, because I updated it to the latest version that is working with Orbiter 2010...
 
Good:thumbup:
Rick, can you do the same?

I'm sure I can get this working, but I have never used Orulex. I installed Orulex Land Gen v1.2 and activated the module. Using the previous scenario state that TMac provided at the distant base (before driving back), I was able to load the program. What I get is a view from the TMac MMU at the base with the usual heads up display markings and normal program status information on the screen, but the view is completely black. I assume I should be seeing something.

I don't know what Felipi calls the latest version that is working with Orbiter 2010, but all I see at Orbiter Hanger is Orulex 1.2. Exactly what do I need to make this work and do I have to load something else? Do I need some kind of mesh for Mercury and where do I get it? Appreciate any assistance.

Rick
 
Some possible answers:
1) Orulex takes a while to load. There should be a status indicator on the screen telling you the progress of the loading. Maybe just wait a few minutes?
2) Your monitor?
3) Try the most recent scenario (where we have returned to Iron Hill), and see if it looks any different.
4) Try this: load the older scenario (where we're still at Scopas), move my UMMU outside, and tell me what you see...
 
Some possible answers:
1) Orulex takes a while to load. There should be a status indicator on the screen telling you the progress of the loading. Maybe just wait a few minutes?
2) Your monitor?
3) Try the most recent scenario (where we have returned to Iron Hill), and see if it looks any different.
4) Try this: load the older scenario (where we're still at Scopas), move my UMMU outside, and tell me what you see...

Ok, had more time to play with this tonight. The Orulex test scenarios work fine, including the one on the Mercury plains. If I load the last posted scenario, the view is black, but if I put a suit on and walk forward, I go through the wall and can see the hills of Mercury (although the light levels are very low). If I load the scenario where Tmac just finished the base, I get the black view but if I switch to external view, I can see our ship and the local hills with a very low sun. Are the base interiors pitch black? How do I turn on the lights or otherwise do anything? With the scenario I started with (Tmac at the other base) I just see a narrow strip of sky (I have sky objects turned on in planetarium view). All the views from ships and from mmus on Earth look fine. Orulex is definitely processing as soon as I unpause the scenario at the beginning. The mmu demo of a base also looks fine. What do you guys see when one of these scenarios starts up? (Note when I say black view, I mean I can still see the Hud and the normal game data on the screen, but the view itself is black)

Rick
 
Some possible answers:
1) Orulex takes a while to load. There should be a status indicator on the screen telling you the progress of the loading. Maybe just wait a few minutes?
2) Your monitor?
3) Try the most recent scenario (where we have returned to Iron Hill), and see if it looks any different.
4) Try this: load the older scenario (where we're still at Scopas), move my UMMU outside, and tell me what you see...

I dont claim to be an authority on Orulex, but Im pretty sure several minutes is too long to load. Maybe theres some sort of issue with syncing terrain? Although you can have identical craters by inputting the same data into World studio, orulex generates terrain with fractal functions when it doesnt have heightmaps to work with, and thus might be giving each one of you a different set of terrain? If its really giving you headaches, my best reccomendation would be to shut down collisions and work from there
 
Wait...I know what's going on...and you're going to laugh your :censored: off:lol:
You are very close to the black door of the module, so that it's filling your view! If you load the Scopas scenario and back up a bit, you'll see what I mean;)
 
Wait...I know what's going on...and you're going to laugh your :censored: off:lol:
You are very close to the black door of the module, so that it's filling your view! If you load the Scopas scenario and back up a bit, you'll see what I mean;)

Thanks, guys, I fixed it! I'm laughing, but not because of the door (although that gave me a hint). I discovered the ambient light parameter and found that it was set too low, even though everything had looked fine up to now. I changed it from 10 to 100 and now I can see everything and Mercury looks great. I think Orulex should be fine, so we can continue to use it. I will work on setting up tables this weekend. :thumbup:

Rick
 
Okay:yes:
Pass the scenario to Felipi when you're done. He'll work on arranging the beam lights for the Arrow landing area.

And after you save the scenario, don't forget to go in and delete AFCMODE from all the unpacked modules;)
 
Okay:yes:
Pass the scenario to Felipi when you're done. He'll work on arranging the beam lights for the Arrow landing area.

And after you save the scenario, don't forget to go in and delete AFCMODE from all the unpacked modules;)

Ok, scenario attached. Tables set up per instructions and I deleted the AFCMODE as required. Good luck Felipi!

Rick
 

Attachments

Back
Top