Problem STS-133 Exp Pack

[rluettge]

I have installed thre STS-133 Exp Pack and as requested the HTV by Donamy was loaded before the STS-133 pack.
I receive the following errors in Orbiter log file. Can somebody help me out here ? Thanks and apologize if I have overlooked something.

...
Module ISS20A.dll [API v.060425]
**** WARNING: Mesh not found: .\Meshes\.msh
**** WARNING: Mesh not found: .\Meshes\.msh
**** WARNING: Mesh not found: .\Meshes\.msh
>>> ERROR: Missing texture: Stationdynamic.dds
>>> [C:\Source\Orbiter\Texture.cpp / 781]
Module SSRMS.dll [API v.060425]
Module ProgressM1.dll [API v.060425]
Module ATV.dll [API v.060425]
Module SoyuzTMA.dll [API v.060425]
Module Colombus.dll [API v.060425]
>>> ERROR: Missing texture: pma.dds
>>> [C:\Source\Orbiter\Texture.cpp / 781]

 

[lmlimo]

STS-133 Exp Pack - same problem

Am experiencing exact same problem. All the other STS scenarios work ok however. Have tried installing the previous STS-133 packages in order of release with the same result.

 

[David413]

A little more info would be helpful

Okay, to begin with, have you installed the main STS Expansion package (or special edition, depending on your preference), and have you followed the instructions in the Setup documentation that came with the basic Expansion pack? It details the additional third-party add-ons necessary for a full expansion package setup (which your error message posted implies that you didn't load all of the required additional packages).

The main Expansion packs are listed in the Orbithangar descriptions for the STS-133 expansion packages.

Without further information, I can't really detail what additional problems you may be having.

Dave

 

[cymrych]

Hi Dave,

I also received this exact error log, verbatim.

I can't speak for the fellas who posted above, but I know for quite certain that I have installed everything listed in the various pdfs in the order indicated, from a clean install of 06Sp1 on down the list.

The weird thing is that the mesh iss20A is present in the install. The only thing I can think of is if the dll has a typo in the mesh name it's trying to call, like iss20a instead of iss20A or something similar.

Thanks for your great work and help! Cheers

---------- Post added at 07:29 AM ---------- Previous post was at 07:10 AM ----------

Correction: It's clearly not something in the dll (as I should have known!), because the STS-131 missions, also utilizing ISS20A, all load perfectly. However, both FD1 and FD3 for STS-133 result in this same error log. For the life of me I don't know why though.

---------- Post added at 07:59 AM ---------- Previous post was at 07:29 AM ----------

The third time's the charm.

You guys must have done the same as I did, downloaded the expansion and STS-133, with the idea of getting STS-132 later on once the real-life STS-133 mission was over.

Go to the hangar and grab STS-132 and install. Then the STS-133 scenarios should load up. I've haven't quite figured out what meshes from 132 the 133 scenarios are trying to call up yet, but clearly that's what we were missing.

Dave, if you get a moment, you might want to make a note of this either on the hangar download page for STS-133 or in it's documentation for future Discovery pilots.

Cheers!

 

[David413]

Thank You

Thanks for taking the time to check this out; I'll update the OH descriptions to include your suggestion.

Thanks again,

Dave

 

[rluettge]

Thanks guys, problem fixed with the STS132 package.

 

[lmlimo]

STS-133 Expansion Pack

David,

Again, incredible work you have done over the years with the STS packages. Glad to see there is apparently a solution, as I followed the setup docs with pencil and checklist in hand, in addition to re-downloading fresh copies of all the required addons. Will try the fix later on today on my home machine and report any additional problems if observed.

Gary