Soyuz 7K-TM

[4throck]

Nice mesh Castor !

I wouldn't worry much about the launcher meshes until a complete Soyuz spacecraft add-on is released. Launch is important, but not crucial for a first release, in my opinion.
It's normal to have small scale incompatibilities between meshes from different sources.

On my end, I've finally got all mesh groups listed so that I can at least make the solar panels scale horizontally! LOL, it seems trivial but it took a lot of work.

 

[4throck]

Just to say that I've finally added RCS to the reentry module. It's very nice to watch in action from the external view.
Also, I've configured the thermal blankets to be jettisoned from the Service module at the same time as the cabling. I guess it's more accurate that way.

Small but steady progress

 

[4throck]

My time and attention span are moving on from this (right now I'm back to messing with the Space:1999 stuff) so I'll share with you my progress so far.

Here's a test version of my implementation featuring the Soyuz 7K-T-AF:
http://www.easy-share.com/1912891762/7k_orbiter.rar

The file has all the textures and meshes, because I needed to do some changes to add the parachute and remove antenas for the launch situation.

This is a basic implementation with approximate parameters and functionality. Soyuz is a spacecraft3.dll vessel with each module as a payload. Animations, RCS and mesh positions are not completely correct.

If you want it finished please help correct all the problems that exist and post the updated config files here. I don't think there is a problem in using this thread as it is quiet now.

 

[castorp]

nicely done, 4throck! many thanks!!

 

[diogom]

The addon is really nice, although I found a little problem. I don't know if it happens with anyone else, but a few seconds after I jettison the periscope on the SA, I get a CTD. Anyone knows what the problem is?

 

[4throck]

Strange... did you check the Orbiter log ?
The way everything is put together if there's a problem like a missing file, for example, you will get an immediate CTD.

Do you get the same effect if you don't eject it? Perhaps it has something to do with surface bases. Were you over any base (or close enough for Orbiter to load surface tiles for example ? )

 

[diogom]

**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 2.79365e-007 sec
Found 0 joystick(s)
Devices enumerated: 6
Devices accepted: 5
==> RGB Emulation
==> Direct3D HAL
==> Direct3D T&L HAL
==> Direct3D HAL (NVIDIA GeForce Go 7400 )
==> Direct3D T&L HAL (NVIDIA GeForce Go 7400 )
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 transx.dll ............ [Build 100824, API 100823]
Module ScnEditor.dll ......... [Build 100830, API 100830]
Module Rcontrol.dll .......... [Build 100830, 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 LuaMFD.dll ............ [Build 100830, API 100830]
Module LuaConsole.dll ........ [Build 100830, API 100830]
Module ExtMFD.dll ............ [Build 100830, API 100830]
Module ScriptMFD.dll ......... [Build 100830, API 100830]
Module ScreenCapture.dll ..... [Build ******, API 060425]
Module CameraMFD.dll [API v.060425]
**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Graphics: Viewport: Fullscreen 1024 x 768 x 16
Graphics: Hardware T&L capability: Yes
Graphics: Z-buffer depth: 16 bit
Graphics: Active lights supported: 8
Loading 8816 records from star database
Module Sun.dll ............... [Build 100830, API 100830]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Mercury.dll ........... [Build 100830, API 100830]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
Module Venus.dll ............. [Build 100830, API 100830]
Module VenusAtm2006.dll ...... [Build 100830, API 100830]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
Module Earth.dll ............. [Build 100830, API 100830]
Module EarthAtmJ71G.dll ...... [Build 100830, API 100830]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
BaseObject: Parse error
Module Moon.dll .............. [Build 100830, API 100830]
ELP82: Precision 1e-005, Terms 116/829
Module Mars.dll .............. [Build 100830, API 100830]
Module MarsAtm2006.dll ....... [Build 100830, API 100830]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
Module Phobos.dll ............ [Build ******, API 060425]
Module Deimos.dll ............ [Build ******, API 060425]
Module Galsat.dll ............ [Build 100217, API 100215]
Module Jupiter.dll ........... [Build 100830, API 100830]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
Module Io.dll ................ [Build 100217, API 100215]
Module Europa.dll ............ [Build 100217, API 100215]
Module Ganymede.dll .......... [Build 100217, API 100215]
Module Callisto.dll .......... [Build 100217, API 100215]
Module Satsat.dll ............ [Build 100215, API 100212]
Module Saturn.dll ............ [Build 100830, API 100830]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
Module Mimas.dll ............. [Build 100215, API 100212]
SATSAT Mimas: Terms 113
Module Enceladus.dll ......... [Build 100215, API 100212]
SATSAT Enceladus: Terms 33
Module Tethys.dll ............ [Build 100215, API 100212]
SATSAT Tethys: Terms 101
Module Dione.dll ............. [Build 100215, API 100212]
SATSAT Dione: Terms 59
Module Rhea.dll .............. [Build 100215, API 100212]
SATSAT Rhea: Terms 68
Module Titan.dll ............. [Build 100215, API 100212]
SATSAT Titan: Terms 100
Module Iapetus.dll ........... [Build 100215, API 100212]
SATSAT Iapetus: Terms 605
Module Uranus.dll ............ [Build 100830, API 100830]
VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
Module Miranda.dll ........... [Build ******, API 060425]
Module Ariel.dll ............. [Build ******, API 060425]
Module Umbriel.dll ........... [Build ******, API 060425]
Module Titania.dll ........... [Build ******, API 060425]
Module Oberon.dll ............ [Build ******, API 060425]
Module Neptune.dll ........... [Build 100830, API 100830]
VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
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.
---------------------------------------------------------------
Finished initialising status
Finished initialising camera
Finished initialising panels
Finished setting up render state
---------------------------------------------------------------
>>> WARNING: Obsolete API function used: oapiGetStationCount
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.
---------------------------------------------------------------
**** WARNING: Mesh file name not provided

This is the Orbiter log. I wasn't above any surface base, and not close to any (in the middle of the Ocean), but I don´t get a CTD when I don't jettison the periscope.

EDIT: I don´t know if it's important, but instead of crashing right to the desktop, the screen turns black and white and that Windows message "orbiter.exe has encountered a problem and needs to close... Send error report/Don't send" appears

 

[4throck]

Perhaps I forgot to include some mesh :facepalm:
Let me check that

 

[4throck]

Real world is keeping me from Orbiter I'll try to solve the problem as soon as possible...

 

[4throck]

Ok, I forgot to include some config files for the jetissoned spacecraft parts.
Here's an updated version:

http://www.easy-share.com/1913044357/7k_orbiter.rar

 

[jedimaster1214]

in T-AF_PAO_servicemodule.ini

change this:

[DOCK_0]
POS = (0,0,-0.78)
DIR = (0,0,+1)
ROT = (0,1,0)

To this:

[DOCK_0]
POS = (0,0,4.5)
DIR = (0,0,1)
ROT = (0,1,0)

It places the docking port on its appropriate place on the orbital module.

Also, the meshes are out of place and need to be moved from inside the folder, and directly into the meshes folder...

 

[diogom]

:thumbup:Thanks a lot, 4throck, that solved the problem.

As for you correction jedimaster1214, there seems to be a problem. I did everything you said in your post, but the PAO, while docked, stays a little bit too far from the SA and BO.

 

[jedimaster1214]

well, i guess this only works pre-jettison.
i'll help with the spacecraft3.ini's and see what i can get out of them to make it look better...

 

[4throck]

Thanks for helping :thumbup: !

I know there's something wrong with the docking port positions / mesh offsets, and to solve it it's just a matter of trial and error... I changed the values dozens of times and still couldn't get them right.

The values must be set for the payload meshes (before jetisson) and the docking ports on both the parent and children (jettisoned) vessels...

Sorry about the mesh paths. I tried to keep the same structure as in Castor's release but it ended up being more confusing that way.

 

[jedimaster1214]

ok, if you decide to update the meshes, DONT center the mesh on the origin. having them offset is easier because they are in the correct places relative to the other pieces..

----------------EDIT-------------------------

Ok i watched how it jettisons IN orbiter, and realized that you only need ONE docking port as the main port i described a few posts earlier. You would actually need a few attachment points.

With my idea, you also don't need to switch focus in order to jettison everything.

I have a diagram to explain how i think it would work easier.

I'll upload my idea later when i get around to it....

 

[4throck]

As long as it works any arrangement is good.

My solution is not the best, but it was the easiest I found to fit all the Soyuz versions (non docking, docking, male/female, Zond, etc).

This one (T-AF) is just the easiest to implement, but I have configs for all the others. I didn't share those just to avoid the confusion of having half a dozen half working Soyuz !

I didn't change the meshes. In fact, we shouldn't, because they are Castor's work. And they all have common origin coordinates.

 

[diogom]

Do you have Config files for Soyuz 1? If you do, could you post them here?

Also, I added the Soyuz's Re-Entry Module some engine exhaust to make it look like the real one, they aren't very well placed, since I'm new to configurating vessels, but if you'd like, I could post the updated config file.

 

[diogom]

Here is the updated SA config, with landing thrusters exhaust.

 

[4throck]

I've been busy with real life stuff, so I haven't had the time to test your config. I'll do it when possible. Thanks anyway!:thumbup:

As for Soyuz 1 (and other versions) what I have might not be up to date with the current (T-AF) configs and mesh structure. Nevertheless I'll zip what I have and make it available here.

 

[4throck]

Just to let you know that I'm working on Soyuz again.

I have included the SA landing thrusters exhaust thumbup and I'm again trying to place the reentry module in the right place. I'll then make the configs available here, with all versions sharing the same structure, meshes and similar configs.