Trouble with Moon Level 9 textures and AMSO

Saturn V

Addon Developer
Addon Developer
Donator
Joined
Mar 24, 2008
Messages
548
Reaction score
2
Points
0
Location
West Hell
Hi all,

Been away for awhile and had to start all over (all of my files and customized installations are gone).

My question is this:

I installed the most recent Moon Level 9 textures (mcwoggs?) and while AMSO runs fine otherwise, as soon as the LM descent engine fires into the initial braking phase (during PDI), the LM winks out of sight. The camera tracks where the lander should be, but there's nothing there. Changing FOV doesn't help and if I exit and restart the current scenario, everything loads, but I've got a black screen except for the AMSO info in the corners.

If I use the older set of Moon Level 9 textures (KB9LAD?), everything works as expected.

Is there a known incompatibility issue with the newer textures? BTW: everything is installed correctly...I'm not a total noob! ;)

Also, is there anyway to correct the little pixelated "box" around a vessel at higher screen resolution? I'm on a new PC with a widescreen monitor and cant practically run lower than 1440 X 900.

Any help is much appreciated...


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


WHOA! Don't everybody jump in at once! :tounge:

Seriously though, the Moon textures isn't that big a deal, but the "pixel box" thing is driving me buggy. Anybody got a fix?
 
Welcome back!

I'm using the Level 9 textures by McWoggs and have been since before the start of "you know what". All of A12 was done using them. I have never experienced what you are seeing.

:cheers:


P.S. Partial noob, perhaps? :P
 
Also, is there anyway to correct the little pixelated "box" around a vessel at higher screen resolution? I'm on a new PC with a widescreen monitor and cant practically run lower than 1440 X 900.

Wasn't that problem related to exhaust textures and using AA (anti-aliasing) while running Orbiter?
 
In my case the textures played no role at all - in a thread in the old Orbiter forum I found a thread discussing an issue similar to the issue you have. It could be traced back to two missing .dll files in a Windows folder... in my case only one of these files was missing - after I put the missing file where it belonged there was no more issue at all.

In case you still have an issue, please post and I will look up and post detail information.

b.
 
Back
Top