OHM Mir Space Station v.1.3

Also I saw at least 2 different pictures of Kvant tug so I made something average. I hope in some day I'll find some photo of this tug.

I just went on to Astronautix looking for some pictures of the tug, and I can see what you mean. This is what I always thought it looked like:

http://en.wikipedia.org/wiki/Image:Kvant_module_and_FSM_drawing.png

Also seen here:

http://www.astronautix.com/graphics/k/kvantsm1.jpg
http://www.astronautix.com/graphics/k/kvantsm2.jpg
http://www.astronautix.com/graphics/k/kvant.jpg

And these pictures seem to be similar to the model included in the add-on:

http://www.astronautix.com/graphics/k/kvantbig.gif
http://www.astronautix.com/graphics/k/kvantdwg.gif

My best guess is that in the bottom two pictures, the faring between the Kvant 1 module and the tug is omitted for some reason. Does anyone else have some more information on this?

Actually I try to make Travers, but it was so heavy (too many polygons) so i decided make it later, maybe using texture with alpha-channel.

Kind of what I thought.
 
I assume he trying to say some launch scenarios is incompatible with Proton v2.0.
 
Got a problem. I don't know why Orbiter is shutting down when I'm trying to start the Kvant launch. On Core module weren't shutting down. I installed Orlan spacesuit but it's doing it even on core module launch. I've got Orbiter 2010P1 and Proton LV v2.2
 
Got a problem. I don't know why Orbiter is shutting down when I'm trying to start the Kvant launch. On Core module weren't shutting down. I installed Orlan spacesuit but it's doing it even on core module launch. I've got Orbiter 2010P1 and Proton LV v2.2

You need to install [ame="http://www.orbithangar.com/searchid.php?ID=4555"]Mir v1.3 Scenarios Patch[/ame] to update the scenario for Kvant launch.
 
for me, only the core module and kvant work. the others cause a ctd.
the log says no errors, it just stops at;
Module Orlan.dll ............. [Build ******, API 060425]

i installed the orlan addon, and after that the scenario patch and it still doesn't work.
anyone an idea how to fix this?
 
for some reason, if i remove lc81 from the scenario file, it works perfectly. except for the proton launcher that lies flat on the ground with its engine's roaring.
 
okay I removed the orlan part's from the scenario's now it doesn't give any error in the log but it's still giving a ctd (strangely, the core module and kvant (1) work both launch and orbital scenario) maybe it has something to do with it being an orbiter 2006 add-on, even though it did work on my previous obiter installation. (also 2010-p1)
 
I got it to work on Orbiter '10 also. Don't forget to download the updated scenarios...

I recently ran them again (within 3-4 months). Can you post you orbiter log immediately after the CTD?
 
launch scenario

**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 5.14563e-007 sec
Found 0 joystick(s)
Devices enumerated: 9
Devices accepted: 7
==> RGB Emulation
==> Direct3D HAL
==> Direct3D T&L HAL
==> Direct3D HAL (NVIDIA GeForce 9400)
==> Direct3D T&L HAL (NVIDIA GeForce 9400)
==> Direct3D HAL (NVIDIA GeForce 9400) #2
==> Direct3D T&L HAL (NVIDIA GeForce 9400) #2
Module AtlantisConfig.dll .... [Build 100830, API 100830]
Module AtmConfig.dll ......... [Build 100830, API 100830]
Module DGConfigurator.dll .... [Build 100830, API 100830]
Module EnergyConfigurator.dll [Build ******, API 060425]
Module ProjectOutpostsConfig.dll [Build 120604, API 100830]
Module OrbiterSound.dll ...... [Build ******, API 060425]
---------------------------------------------------------------
>>> WARNING: Obsolete API function used: oapiRegisterMFDMode
At least one active module is accessing an obsolete interface function.
Addons which rely on obsolete functions may not be compatible with
future versions of Orbiter.
---------------------------------------------------------------
Module transx.dll ............ [Build 100824, API 100823]
Module LuaMFD.dll ............ [Build 100830, API 100830]
Module CustomMFD.dll ......... [Build 100830, API 100830]
Module ScnEditor.dll ......... [Build 100830, API 100830]
Module Rcontrol.dll .......... [Build 100830, API 100830]
Module FlightData.dll ........ [Build 100830, API 100830]
Module Framerate.dll ......... [Build 100830, API 100830]
Module ExtMFD.dll ............ [Build 100830, API 100830]
Module ITSArrayMFD.dll ....... [Build ******, API 060425]
Module UnivPTG.dll ........... [Build 110305, API 100830]
Module RPOP.dll .............. [Build 111124, API 100830]
Module GPCMFD.dll ............ [Build 111222, API 100830]
Module ScriptMFD.dll ......... [Build 100830, API 100830]
Module SoyuzGuidanceMFD.dll .. [Build 120225, API 100830]
Module videnie.dll ........... [Build 110912, API 100830]
Module LaunchMFD.dll ......... [Build 120519, API 100830]
Module Telescope.dll ......... [Build 110413, API 100830]

**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Graphics: Viewport: Window 1914 x 1055 x 32
Graphics: Hardware T&L capability: Yes
Graphics: Z-buffer depth: 32 bit
Graphics: Active lights supported: 8
Loading 103976 records from star database
Module Sun.dll ............... [Build 100830, API 100830]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Earth.dll ............. [Build 100830, API 100830]
Module EarthAtmJ71G.dll ...... [Build 100830, API 100830]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
Module Moon.dll .............. [Build 100830, API 100830]
ELP82: Precision 1e-005, Terms 116/829
Finished initialising world
Module Spacecraft3.dll ....... [Build ******, API 060425]
---------------------------------------------------------------
>>> WARNING: Obsolete API function used: VESSEL::SetBankMomentScale
At least one active module is accessing an obsolete interface function.
Addons which rely on obsolete functions may not be compatible with
future versions of Orbiter.
---------------------------------------------------------------
Module Fairing.dll ........... [Build 100901, API 100830]
Module P3.dll ................ [Build 100901, API 100830]
Module Skirt.dll ............. [Build 100901, API 100830]
Module P2.dll ................ [Build 100901, API 100830]
Module P1.dll ................ [Build 100901, API 100830]
Module LC81.dll .............. [Build 100901, API 100830]

orbit scenario


==> Direct3D T&L HAL
==> Direct3D HAL (NVIDIA GeForce 9400)
==> Direct3D T&L HAL (NVIDIA GeForce 9400)
==> Direct3D HAL (NVIDIA GeForce 9400) #2
==> Direct3D T&L HAL (NVIDIA GeForce 9400) #2
Module AtlantisConfig.dll .... [Build 100830, API 100830]
Module AtmConfig.dll ......... [Build 100830, API 100830]
Module DGConfigurator.dll .... [Build 100830, API 100830]
Module EnergyConfigurator.dll [Build ******, API 060425]
Module ProjectOutpostsConfig.dll [Build 120604, API 100830]
Module OrbiterSound.dll ...... [Build ******, API 060425]
---------------------------------------------------------------
>>> WARNING: Obsolete API function used: oapiRegisterMFDMode
At least one active module is accessing an obsolete interface function.
Addons which rely on obsolete functions may not be compatible with
future versions of Orbiter.
---------------------------------------------------------------
Module transx.dll ............ [Build 100824, API 100823]
Module LuaMFD.dll ............ [Build 100830, API 100830]
Module CustomMFD.dll ......... [Build 100830, API 100830]
Module ScnEditor.dll ......... [Build 100830, API 100830]
Module Rcontrol.dll .......... [Build 100830, API 100830]
Module FlightData.dll ........ [Build 100830, API 100830]
Module Framerate.dll ......... [Build 100830, API 100830]
Module ExtMFD.dll ............ [Build 100830, API 100830]
Module ITSArrayMFD.dll ....... [Build ******, API 060425]
Module UnivPTG.dll ........... [Build 110305, API 100830]
Module RPOP.dll .............. [Build 111124, API 100830]
Module GPCMFD.dll ............ [Build 111222, API 100830]
Module ScriptMFD.dll ......... [Build 100830, API 100830]
Module SoyuzGuidanceMFD.dll .. [Build 120225, API 100830]
Module videnie.dll ........... [Build 110912, API 100830]
Module LaunchMFD.dll ......... [Build 120519, API 100830]
Module Telescope.dll ......... [Build 110413, API 100830]

**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Graphics: Viewport: Window 1914 x 1055 x 32
Graphics: Hardware T&L capability: Yes
Graphics: Z-buffer depth: 32 bit
Graphics: Active lights supported: 8
Loading 103976 records from star database
Module Sun.dll ............... [Build 100830, API 100830]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Earth.dll ............. [Build 100830, API 100830]
Module EarthAtmJ71G.dll ...... [Build 100830, API 100830]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
Module Moon.dll .............. [Build 100830, API 100830]
ELP82: Precision 1e-005, Terms 116/829
Finished initialising world
Module Spacecraft3.dll ....... [Build ******, API 060425]
---------------------------------------------------------------
>>> WARNING: Obsolete API function used: VESSEL::SetBankMomentScale
At least one active module is accessing an obsolete interface function.
Addons which rely on obsolete functions may not be compatible with
future versions of Orbiter.
---------------------------------------------------------------

---------- Post added at 10:38 AM ---------- Previous post was at 10:38 AM ----------

this is from the Kristall scenario's btw.
 
Hmmm, that's peculiar.

I'm grasping at straws here, but try turning the local light sources off. I seem to remember that sometimes it can cause trouble.

My windows computer is broken at the moment, and I'm using Linux for the time being. I'll see if I can hijack my kids computer and see if I can run these missions, or get a similar CTD.
 
when i load the scenario, the loading stops at kristall/cone.dds, freeze's for 2 seconds and i get a program stopped working error.
 
I decided to take these missions for another go; missions 1 and 2 work with no issues but from the Kvant 2 launch and beyond I'm getting an "Orbiter has stopped working..." message.

The loading stops on KmlWriter; the previous scenarios also have that same line in the scenario and they run fine. The log looks clear, so I'm puzzled. And for grins, the STS-71 rendezvous is A-OK.

Code:
**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 6.41343e-007 sec
Found 1 joystick(s)
Devices enumerated: 6
Devices accepted: 5
==> RGB Emulation
==> Direct3D HAL
==> Direct3D T&L HAL
==> Direct3D HAL (AMD Radeon HD 6310 Graphics)
==> Direct3D T&L HAL (AMD Radeon HD 6310 Graphics)
Module AtlantisConfig.dll .... [Build 100830, API 100830]
Module AtmConfig.dll ......... [Build 100830, API 100830]
Module DGConfigurator.dll .... [Build 100830, API 100830]
Module OrbiterSound.dll ...... [Build 121120, API 100830]
Module ScnEditor.dll ......... [Build 100830, API 100830]
Error loading module Modules\Plugin\AeroBrakeMFD.dll (code 126)
Error loading module Modules\Plugin\BaseSyncMFD.dll (code 126)
Error loading module Modules\Plugin\Glideslope.dll (code 126)
Error loading module Modules\Plugin\LightingMFD.dll (code 126)
Module AutoFCS.dll ........... [Build ******, API 050206]
Module CSSC_Spawner.dll ...... [Build 120331, API 100830]
Error loading module Modules\Plugin\ReleaseMFD-Mouse.dll (code 126)
Error loading module Modules\Plugin\GS2.dll (code 126)

**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Graphics: Viewport: Fullscreen 1600 x 900 x 32
Graphics: Hardware T&L capability: Yes
Graphics: Z-buffer depth: 32 bit
Graphics: Active lights supported: 8
Loading 15382 records from star database
Joystick throttle: Z-AXIS
Joystick throttle control detected
Module Sun.dll ............... [Build 100830, API 100830]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Earth.dll ............. [Build 100830, API 100830]
Module EarthAtmJ71G.dll ...... [Build 100830, API 100830]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
Module Moon.dll .............. [Build 100830, API 100830]
ELP82: Precision 1e-005, Terms 116/829
Finished initialising world
Module Spacecraft3.dll ....... [Build ******, API 060425]
---------------------------------------------------------------
>>> WARNING: Obsolete API function used: VESSEL::SetBankMomentScale
At least one active module is accessing an obsolete interface function.
Addons which rely on obsolete functions may not be compatible with
future versions of Orbiter.
---------------------------------------------------------------
Module Fairing.dll ........... [Build 100901, API 100830]
Module P3.dll ................ [Build 100901, API 100830]
Module Skirt.dll ............. [Build 100901, API 100830]
Module P2.dll ................ [Build 100901, API 100830]
Module P1.dll ................ [Build 100901, API 100830]
Module LC81.dll .............. [Build 100901, API 100830]
 
Greetings all, new here.
I just rediscovered Orbiter, and reluctantly updated from my 2005 install to 2006 p1 because I somehow lost my Orbitersound 2.5 package. Now that I've re-familiarized myself with Orbiter I've become re-interested with Mir and obtained this addon, only to find that most of the 'required addons' are no longer available. Since I'm only interested in replacing the default station with one from this pack can I simply copy the mesh and texture files to my orbiter install and create a new scenario ?
 
Mir Station itself works fine in Orbiter 2006p1, and even in Orbiter 2010. I suppose since your using 2006p1 most of the required addons would work as is(provided you installed them first:lol:), though some may have problems in Orbiter 2010, and Thorton's Proton 1.0 is no longer available since it was replaced by a newer version. Spacecraft3, although not called out in the required addon list, is required though. Spacecraft3 works as intended in Orbiter 2006p1, and much the same in Orbiter 2010, so I believe you'll have no problems with it.

Good news is, since you're after a replacement for the default Mir, you don't have to worry about the other required addons except Spacecraft3. I don't believe you want to try building Mir like it was done way back when. You are going to have to do more than just copying over a few meshes and texture files to use this Mir in place of the default one, but in the end it's a bit of scenario editing. You have two options to get to that part:

Option 1) Simply take all the extracted files and folders from the .rar this came in and copy it into your Orbiter install. So long as you preserved the folders while extracting, this is the easy and painless way to install this Mir. Skip past Option 2 if you want to find out what is next, or keep reading.

Option 2) Figure out what files you need, and then copy only those out of the extracted folder. You must first figure out which assembled Mir you want and open it's .ini file; since you most likely want Mir in it's Amazing Final Form, pick Mir_VI.ini and open it in Notepad. Inside we find Mir uses a exhaust texture, Mir_Station/exhaust_crcs, and a mesh named Mir_Station/Mir_VI. Notice the "Mir_Station\" bit? It indicate that the files are in a folder named Mir_Station, inside the folder Orbiter will look in for the mesh or texture. So now we have three files to copy over, and we will stick them in the following locations in our Orbiter install:

Mir_VI.ini goes into Spacecraft folder inside the Config folder(Spacecraft3 should have created this folder for you, if not, you likely didn't install it yet.)

exhaust_crcs.dds goes into the folder Mir Station inside the Textures folder( you'll have to make the Mir_Station folder yourself)

Mir_VI.msh goes into the folder Mir_Station in the Meshes folder

We're not done yet though. You might have noticed there's a bunch of other texture files along with exhaust_crcs.dd, and we are going to need a bunch of them. But which ones though? To find out, we open up Mir_VI.msh in Notepad. Don't worry that Notepad doesn't seem to be the right tool for opening 3d files, just take it from me that it works. Inside you'll find a numerical representation of the mesh, laid out in masses of numbers. We will pass this by and move to the very bottom of the file, where we will see this:

Code:
TEXTURES 20
Mir_Station\Core_6.dds
Mir_Station\spectrN.dds
Mir_Station\core_2.dds
Mir_Station\Dockring.dds
Mir_Station\core_1_1.dds
Mir_Station\Solar1.dds
Mir_Station\Solar_4.dds
Mir_Station\spectr.dds
Mir_Station\kvant_1.dds
Mir_Station\Side1.dds
Mir_Station\rad.dds
Mir_Station\Side.dds
Mir_Station\dock.dds
Mir_Station\Solar_2.dds
Mir_Station\Solar_3.dds
Mir_Station\doc.dds
Mir_Station\grapple.dds
Mir_Station\ODSSM.dds
Mir_Station\point.dds
Mir_Station\core_5.dds

It's the textures the mesh Mir_VI.msh uses. Copy them into the folder Mir_Station inside the Textures folder and now you have what you need.

Having done either Option 1 or 2, what's next?


Next is to actually get a Mir from this addon in a scenario to replace the default one, and this means editing a scenario file. If you took option two, you only have Mir in it's Final Ultimate Form(Mir_VI), so we have to find a scenario file from with that particular Mir. If you took Option 1 any Mir would work, but let's use Mir_VI anyway. So we'll first look in the Scenarios folder, then the Mir Space Station folder. Inside is three folders: Launch Scenarios, Mir Configurations, and Misc. Since I'm your guide, I'll pick Mir Configurations for you, and once there we see a bunch of scenarios. Using what I remember about the Mir, I know Priroda was the last module added to Mir, and it's also the last scenario file. Opening it in Notepad, we look to see what ships are here, and find this in the relevant section:

Code:
BEGIN_SHIPS
[B]Mir_VI[/B]:spacecraft\spacecraft3
  STATUS Orbiting Earth
  RPOS 5751919.43 3197208.99 -1534320.11
  RVEL 3941.948 -6451.150 1364.056
  AROT -80.67 -32.91 98.49
  VROT -0.07 -0.00 -0.00
  PRPLEVEL 0:0.849
  [U]DOCKINFO 0:0,TM-23 3:0,Cosmonaut1[/U]
  NAVFREQ 0 0
  RCS 1
  CTRL_SURFACE 1
  CONFIGURATION 1
  CURRENT_PAYLOAD 0
  SEQ 0 -2 0.318200
  SEQ 1 -2 0.151500
  SEQ 2 -2 0.000700
END
TM-23:soyuztma
  STATUS Orbiting Earth
  RPOS 5751925.77 3197199.34 -1534318.53
  RVEL 3941.948 -6451.150 1364.056
  AROT 99.33 32.91 81.51
  VROT 0.07 -0.00 0.00
  RCSMODE 2
  PRPLEVEL 0:0.615
  DOCKINFO 0:0,Mir_VI
  NAVFREQ 0 0
  XPDR 0
  CONFIGURATION 0
  PANELS 1.000
END
Cosmonaut1:orlan
  STATUS Orbiting Earth
  RPOS 5751932.53 3197210.01 -1534322.05
  RVEL 3941.948 -6451.150 1364.056
  AROT -80.67 -32.91 98.49
  VROT -0.07 -0.00 -0.00
  RCSMODE 2
  PRPLEVEL 0:0.840
  DOCKINFO 0:3,Mir_VI
  NAVFREQ 130 130
END
END_SHIPS

Yay, Mir_VI(bold) is in this scenario, maeaning we found Mir in it's Ultimate Super Form. We also see a few other ships, and since we don't have them installed, we simply can't copy them over and expect them to work. However, they are docked to Mir, as shown with the underlining in Mir's Ship entry. Not a big crisis, as we can deal with this easily later. Anyway, we want to have this Mir replace the default one, so we ought to find a scenario with the default Mir. I'll use the scenario file inside the Checklists folder called "Mission 2- ISS to Mir". Now we'll find Mir in there, in the ships part of the file. It should look like this(minus the underlining, I'll explain why that's there in a moment):

Code:
Mir:Mir
[U]  STATUS Orbiting Earth
  RPOS -2351755.31 -379917.64 -6234978.51
  RVEL 7235.564 -160.954 -2708.618
  AROT 1.60 -46.80 88.82[/U]
  IDS 0:540 100 1:542 100 2:544 100
  XPDR 482
END

Here is Mir_VI again for comparison(again, the purpose of underling will be shown in a moment):

Code:
Mir_VI:spacecraft\spacecraft3
[U]  STATUS Orbiting Earth
  RPOS 5751919.43 3197208.99 -1534320.11
  RVEL 3941.948 -6451.150 1364.056
  AROT -80.67 -32.91 98.49
  VROT -0.07 -0.00 -0.00[/U]
  PRPLEVEL 0:0.849
  DOCKINFO 0:0,TM-23 3:0,Cosmonaut1
  NAVFREQ 0 0
  RCS 1
  CTRL_SURFACE 1
  CONFIGURATION 1
  CURRENT_PAYLOAD 0
  SEQ 0 -2 0.318200
  SEQ 1 -2 0.151500
  SEQ 2 -2 0.000700
END

We want Mir_VI to replace the default Mir, and now we must take a few steps. Ready?

Step 1) Copy Mir_VI into Mission 2-ISS to Mir somewhere between BEGIN_SHIPS and END_SHIPS, but not between another ship and it's END line. If we save hit save right now, we would have two Mir upon loading this scenario in Orbiter, that is if would crash. Let's fix that.

Step 2) Take aim at the following line in Mir_VI:
Code:
  DOCKINFO 0:0,TM-23 3:0,Cosmonaut1
Then delete it.

Now we have two Mirs, one default and one Thorton. If we saved this scenario right now, we would see in Orbiter that the two Mirs are in completely different orbits. Let change that too. Remember the underlining from before? I'll show it again:

Code:
Mir:Mir
[U]  STATUS Orbiting Earth
  RPOS -2351755.31 -379917.64 -6234978.51
  RVEL 7235.564 -160.954 -2708.618
  AROT 1.60 -46.80 88.82[/U]
  IDS 0:540 100 1:542 100 2:544 100
  XPDR 482
END

Code:
Mir_VI:spacecraft\spacecraft3
[U]  STATUS Orbiting Earth
  RPOS 5751919.43 3197208.99 -1534320.11
  RVEL 3941.948 -6451.150 1364.056
  AROT -80.67 -32.91 98.49
  VROT -0.07 -0.00 -0.00[/U]
  PRPLEVEL 0:0.849
  NAVFREQ 0 0
  RCS 1
  CTRL_SURFACE 1
  CONFIGURATION 1
  CURRENT_PAYLOAD 0
  SEQ 0 -2 0.318200
  SEQ 1 -2 0.151500
  SEQ 2 -2 0.000700
END

The underlining is the part that tells the ship where it is, in what orientation, relative velocity etc. The STATUS line will also say what planet the vessel is orbiting, or if it it is landed on a planet. Since we want Mir_VI to be in the same orbit as default Mir, we do step 3.

Step 3) Copy from default Mir's STATUS line down to the one that says VROT, and paste it over Mir_VI's corresponding lines. Now we have Mir_VI right where default Mir is, and thus the next step is:

Step 4) Delete default Mir from the scenario. We don't need it anymore, having replaced it with Mir_VI. Now we arrive at the penultimate step.

Step 5) Save the scenario file as "Mission 2- ISS to Thorton's Mir", or whatever you fancy. I wouldn't want you to overwrite the one default one, but you can overwrite it if you wish.

Step 6) Load the scenario, hope that neither of us missed something important, and fly to your new Mir. Good luck!
 
Last edited:
Thank you orbitingpluto, I'm on the path of option 2 tho I did it before reading your post. I renamed the original Mir so I could fall back to it if needed and replaced it with the Mir_IV mesh, and copied over the entire texture folder keeping the dir structure and it worked fine. I don't have animations and such but it looks incredible. I didn't even need to edit the scenarios at all, Orbiter doesn't seem to notice the original mesh has been replaced but I'll move/edit the .ini file when I get home tonight.

I did notice something strange tho, the scale seems a bit off. The station (by my guess) is about 30% too small. Is that something that can be set in the ini file ?
 
Docking troubles

Hi! I love the addon, but there is a problem:
I run Orbiter 2010 P1, so the orlan and the soyuz tm will not work and cause a CTD. So, I went into the .scn file for the complete Mir ("7. Mir - Priroda.scn") and inserted a Soyuz-TM from your ISS 3.? addon, docked to port 1. It showed up just fine at the back port of Mir, but when I try to put it on a port with a DOCKINFO number higher than 3, I get a CTD. What is there that can be done? Also, what is the port number of the central docking port (the only free port on the core module)?
 
Back
Top