Project Soyuz 7K-T Custom

diogom

Well-known member
Joined
Aug 2, 2010
Messages
1,229
Reaction score
151
Points
78
Shipedit.exe can also calculate normals.
For some reason that wasn't working, though I gave up on it before trying the "missing normals only" option for the mesh group. It's been working pretty well for the VC though.
 

diogom

Well-known member
Joined
Aug 2, 2010
Messages
1,229
Reaction score
151
Points
78
And the docking rework is done, the full sequence is now simulated, requiring the SSVP to be powered for all mechanical actions:

Manual extension of the docking probe rod before docking will automatically trigger the head latches extension (animated) at the end, and if the hooks are open, the docking system is ready for use, indicated by a KSU signal.

Upon contact and soft-dock (signalled by the KSU), the rod retraction is commanded manually, which brings the two spacecraft closer. The hooks closing is automatically triggered, forming the airtight seal, followed by the latches retraction to break the first mechanical link, and the rod retracts to the final position, establishing hard-dock (signalled by the KSU).

KSU Undocking command from hard-dock will start the hooks opening, after which the Soyuz will undock, providing indication on the electroluminescent display.

Durations for each of the mechanical actions are adjusted to reflect the values given on the Soyuz-TM manual: 6 minutes for the probe rod, 2 for the latches and 3 for the hooks.

1652833151801.png

I think in the future it might be doable to visually simulate an out of alignment docking (but still within limits, up to 10 degrees in roll and 7 degrees in pitch/yaw). I'm already getting the relative orientation to the target through Igla right up to docking, and the docking code should allow for setting the initial docking orientation at a given angle, and progressively align in all axes as the probe retracts.
 

diogom

Well-known member
Joined
Aug 2, 2010
Messages
1,229
Reaction score
151
Points
78
Been preparing some more Navigation Display functionality, so a new world map was in order. Based on the available description and Soyuz-35, worked this up:

1654400405914.png

1654400437282.png

Base land mask from http://www.shadedrelief.com/natural3/index.html. Including the location of ground stations, Comrade A. Voltov wasn't available, so a few might be off.

A short break follows, but after that it's time to bring it to Orbiter and get to work on the globe animations.
 

diogom

Well-known member
Joined
Aug 2, 2010
Messages
1,229
Reaction score
151
Points
78
INK is done for now. Hopefully it adds to the immersion I'm aiming for.
Pending is the daylight/shade indicator, haven't been able to get a good grip on how it worked (or even looked tbh).

Short overview of the feature set, mesh still needs normal adjusting:

First, inputing the current orbital period and adjusting the globe's initial position, switch to З/ON ("zemlya" or earth), followed by the landing angle function: a certain angle is input, and when switching the instrument mode to МП, the globe advances the orbital track by that angle. This is used to estimate the landing location if a de-orbit burn were to happen in that moment, being the angle travelled between the de-orbit burn and landing. This angle was passed on from ground control for each de-orbit opportunity, along with the orbit number. Finally, the orbit counter incrementing as the orbit progresses.

Finishing touches remain to save all this to the scenario file, so resetting all this isn't necessary for in-orbit scenarios/saves. However, for launch it will require an initial setup/tuning, and should be activated only after reaching orbit, not at the launch site.
 

Soyuz_TpK

New member
Joined
Jun 10, 2022
Messages
4
Reaction score
1
Points
3
Location
Hamburg
Hi all. Please help. How do I install it? I downloaded all the add-ons, but there is still nothing but land when I start it up.
 

Soyuz_TpK

New member
Joined
Jun 10, 2022
Messages
4
Reaction score
1
Points
3
Location
Hamburg
Can you post the contents of your orbiter.log?
**** Orbiter.log
000000.000: Build Aug 28 2016 [v.160828]
000000.000: Timer precision: 1e-007 sec
000000.000: Found 0 joystick(s)
000000.000: Devices enumerated: 6
000000.000: Devices accepted: 5
000000.000: [ ] RGB Emulation (SW)
000000.000: [ ] Direct3D HAL (HW)
000000.000: [x] Direct3D T&L HAL (HW)
000000.000: [ ] Direct3D HAL (Intel(R) HD Graphics) (HW)
000000.000: [x] Direct3D T&L HAL (Intel(R) HD Graphics) (HW)
000000.000: Module AtlantisConfig.dll .... [Build 160828, API 160828]
000000.000: Module AtmConfig.dll ......... [Build 160828, API 160828]
000000.000: Module DGConfigurator.dll .... [Build 160828, API 160828]
000000.000:
000000.000: **** Creating simulation session
000000.000: DirectDraw interface OK
000000.000: Direct3D interface OK
000000.000: Graphics: Viewport: Window 1274 x 771 x 32
000000.000: Graphics: Hardware T&L capability: Yes
000000.000: Graphics: Z-buffer depth: 32 bit
000000.000: Graphics: Active lights supported: 8
000000.000: Loading 15382 records from star database
000000.000: ---------------------------------------------------------------
000000.000: >>> ERROR: DDraw error DDERR_BLTFASTCANTCLIP
000000.000: >>> [OrbiterGraphics::clbkBlt | .\OGraphics.cpp | 1633]
000000.000: ---------------------------------------------------------------
============================ ERROR: ===========================
While initialising solar system Spaceports\Sol:
>> File not found: .\Config\Spaceports\Sol.cfg
[Orbiter::CreateRenderWindow | .\Orbiter.cpp | 756]
===============================================================
000000.000: >>> TERMINATING <<<
 

diogom

Well-known member
Joined
Aug 2, 2010
Messages
1,229
Reaction score
151
Points
78
Was this the "7k-T docked to Salyut 4" scenario, "Soyuz 18-1 launch", or "Soyuz 18-1 post launch"?
 

Soyuz_TpK

New member
Joined
Jun 10, 2022
Messages
4
Reaction score
1
Points
3
Location
Hamburg
When running the "7k-T docked to Salyut 4" script, there are no objects other than the ground, and when running the "Soyuz 18-1 launch", or "Soyuz 18-1 post launch" scripts, an error like above appears. I don't understand anything, orbiter is clean, only with the addon that you said.
 

diogom

Well-known member
Joined
Aug 2, 2010
Messages
1,229
Reaction score
151
Points
78
Hm. For "Soyuz 18-1 post launch", I think I have a solution for the crash, I've reproduced it as well by not installing anything else. Has to do I think with igel's addons using a separate solar system. Try replacing it with the attached file, I'll update it for future releases.

Just to confirm, you installed "7k_T_dll_11052022"?

I just tried a clean install of O2016 and 7k and both non-launch scenarios load fine, in both stock and D3D9. Not sure what could be going wrong. Could you post the log after closing "7k-T docked to Salyut 4" with no objects?
 

Attachments

  • Soyuz 18-1 post launch.zip
    724 bytes · Views: 5

The Orbiterfan

New member
Joined
May 26, 2021
Messages
8
Reaction score
4
Points
3
Location
mumbai
Showed like this in the end

WARNING: --------------------------
> On simulation shutdown 2 graphics objects were not released
> [CD3DFramework7::DestroyObjects | .\D3d7frame.cpp | 86]
---------------------------------------------------------------
============================ ERROR: ===========================
Destroy framework objects failed
[OrbiterGraphics::Exit3DEnvironment | .\OGraphics.cpp | 1138]
===============================================================
000003.131: **** Closing simulation session

Could it be because I don't have a graphics card?

Edit, the code, actually was recognised as a script by the forum website. ans the ':D' as a smiley
 

N_Molson

Addon Developer
Addon Developer
Donator
Joined
Mar 5, 2010
Messages
8,786
Reaction score
2,474
Points
203
Location
Toulouse
Could it be because I don't have a graphics card?

Can you post your config ? In Windows search bar type "System" then it should display system information and you have a handy "Copy" button. Then Control-V here.
 

Soyuz_TpK

New member
Joined
Jun 10, 2022
Messages
4
Reaction score
1
Points
3
Location
Hamburg
Hm. For "Soyuz 18-1 post launch", I think I have a solution for the crash, I've reproduced it as well by not installing anything else. Has to do I think with igel's addons using a separate solar system. Try replacing it with the attached file, I'll update it for future releases.

Just to confirm, you installed "7k_T_dll_11052022"?

I just tried a clean install of O2016 and 7k and both non-launch scenarios load fine, in both stock and D3D9. Not sure what could be going wrong. Could you post the log after closing "7k-T docked to Salyut 4" with no objects?
Unfortunately also no objects other than land (here is a log.

**** Orbiter.log
000000.000: Build Aug 28 2016 [v.160828]
000000.000: Timer precision: 1e-007 sec
000000.000: Found 0 joystick(s)
000000.000: Devices enumerated: 6
000000.000: Devices accepted: 5
000000.000: [ ] RGB Emulation (SW)
000000.000: [ ] Direct3D HAL (HW)
000000.000: [x] Direct3D T&L HAL (HW)
000000.000: [ ] Direct3D HAL (Intel(R) HD Graphics) (HW)
000000.000: [x] Direct3D T&L HAL (Intel(R) HD Graphics) (HW)
000000.000: Module AtlantisConfig.dll .... [Build 160828, API 160828]
000000.000: Module AtmConfig.dll ......... [Build 160828, API 160828]
000000.000: Module DGConfigurator.dll .... [Build 160828, API 160828]
000000.000:
000000.000: **** Creating simulation session
000000.000: DirectDraw interface OK
000000.000: Direct3D interface OK
000000.000: Graphics: Viewport: Window 1274 x 771 x 32
000000.000: Graphics: Hardware T&L capability: Yes
000000.000: Graphics: Z-buffer depth: 32 bit
000000.000: Graphics: Active lights supported: 8
000000.000: Loading 15382 records from star database
000000.000: ---------------------------------------------------------------
000000.000: >>> ERROR: DDraw error DDERR_BLTFASTCANTCLIP
000000.000: >>> [OrbiterGraphics::clbkBlt | .\OGraphics.cpp | 1633]
000000.000: ---------------------------------------------------------------
000000.000: Module Sun.dll ............... [Build 160828, API 160828]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
000000.000: Module Mercury.dll ........... [Build 160828, API 160828]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
000000.000: Module Venus.dll ............. [Build 160828, API 160828]
000000.000: Module VenusAtm2006.dll ...... [Build 160828, API 160828]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
000000.000: Module Earth.dll ............. [Build 160828, API 160828]
000000.000: Module EarthAtmJ71G.dll ...... [Build 160828, API 160828]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
000000.000: Module Moon.dll .............. [Build 160828, API 160828]
ELP82: Precision 1e-005, Terms 116/829
000000.000: Module Mars.dll .............. [Build 160828, API 160828]
000000.000: Module MarsAtm2006.dll ....... [Build 160828, API 160828]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
000000.000: Module Phobos.dll ............ [Build ******, API 060425]
000000.000: Module Deimos.dll ............ [Build ******, API 060425]
000000.000: Module Galsat.dll ............ [Build 160828, API 160828]
000000.000: Module Jupiter.dll ........... [Build 160828, API 160828]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
000000.000: Module Io.dll ................ [Build 160828, API 160828]
000000.000: Module Europa.dll ............ [Build 160828, API 160828]
000000.000: Module Ganymede.dll .......... [Build 160828, API 160828]
000000.000: Module Callisto.dll .......... [Build 160828, API 160828]
000000.000: Module Satsat.dll ............ [Build 160828, API 160828]
000000.000: Module Saturn.dll ............ [Build 160828, API 160828]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
000000.000: Module Mimas.dll ............. [Build 160828, API 160828]
SATSAT Mimas: Terms 113
000000.000: Module Enceladus.dll ......... [Build 160828, API 160828]
SATSAT Enceladus: Terms 33
000000.000: Module Tethys.dll ............ [Build 160828, API 160828]
SATSAT Tethys: Terms 101
000000.000: Module Dione.dll ............. [Build 160828, API 160828]
SATSAT Dione: Terms 59
000000.000: Module Rhea.dll .............. [Build 160828, API 160828]
SATSAT Rhea: Terms 68
000000.000: Module Titan.dll ............. [Build 160828, API 160828]
SATSAT Titan: Terms 100
000000.000: Module Iapetus.dll ........... [Build 160828, API 160828]
SATSAT Iapetus: Terms 605
000000.000: Module Uranus.dll ............ [Build 160828, API 160828]
VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
000000.000: Module Miranda.dll ........... [Build ******, API 060425]
000000.000: Module Ariel.dll ............. [Build ******, API 060425]
000000.000: Module Umbriel.dll ........... [Build ******, API 060425]
000000.000: Module Titania.dll ........... [Build ******, API 060425]
000000.000: Module Oberon.dll ............ [Build ******, API 060425]
000000.000: Module Neptune.dll ........... [Build 160828, API 160828]
VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
000000.000: Finished initialising world
============================ ERROR: ===========================
Could not load vessel module: Soyuz_7k\Salyut4
[Vessel::LoadModule | .\Vessel.cpp | 5747]
===============================================================
============================ ERROR: ===========================
Could not load vessel module: Soyuz_7k\Soyuz7k_T
[Vessel::LoadModule | .\Vessel.cpp | 5747]
===============================================================
000000.000: Finished initialising status
000000.000: Finished initialising camera
000000.000: Finished setting up render state
000000.000: Finished initialising panels
000035.812: **** Closing simulation session
 

Urwumpe

Not funny anymore
Addon Developer
Donator
Joined
Feb 6, 2008
Messages
36,752
Reaction score
1,416
Points
203
Location
Langendernbach
Showed like this in the end

WARNING: --------------------------

---------------------------------------------------------------
============================ ERROR: ===========================
Destroy framework objects failed
[OrbiterGraphics::Exit3DEnvironment | .\OGraphics.cpp | 1138]
===============================================================
000003.131: **** Closing simulation session

Could it be because I don't have a graphics card?

Edit, the code, actually was recognised as a script by the forum website. ans the ':D' as a smiley

Can be possible, but I think, the first hard error to happen is more important there:

File not found: .\Config\Spaceports\Sol.cfg

Can you check that your Orbiter installation is fine and the missing files installed properly?
 

diogom

Well-known member
Joined
Aug 2, 2010
Messages
1,229
Reaction score
151
Points
78
Very strange. There's a lot I don't know still, so it's not unlikely there's some detail with graphics in the code I don't know about. I'm assuming here that everything else with (stock) Orbiter is working fine?

Edit:
File not found: .\Config\Spaceports\Sol.cfg

This one should be related to igel's addons missing. After the addon migration to OF, I seem to only be able to get Vostok 1.3 and Soyuz 1.2, so I'm not entirely sure launch scenarios will be possible for new users for now (Spaceports 1.5 missing).

000000.000: >>> ERROR: DDraw error DDERR_BLTFASTCANTCLIP
000000.000: >>> [OrbiterGraphics::clbkBlt | .\OGraphics.cpp | 1633]

This one looks concerning but I'm seeing it too with the scenario loading fine.
 
Last edited:

gamer19

Well-known member
Joined
Jul 16, 2016
Messages
108
Reaction score
175
Points
58
crash (with launch scenario)

000000.000: ---------------------------------------------------------------
000000.000: >>> WARNING: Obsolete API function used: VESSEL::SetBankMomentScale
000000.000: At least one active module is accessing an obsolete interface function.
000000.000: Addons which rely on obsolete functions may not be compatible with
000000.000: future versions of Orbiter.
000000.000: ---------------------------------------------------------------
000000.000: Finished initialising status
000000.000: Finished initialising camera
000000.000: Finished setting up render state
D3D9: ERROR: Base Object 0x23BCCC0 = 'Baikonur_1' not cataloged
D3D9: ERROR: Base Object 0x23BD030 = 'Baikonur_2' not cataloged
D3D9: ERROR: Base Object 0x23BD840 = 'Baikonur-51' not cataloged
D3D9: ERROR: Base Object 0x23A1440 = 'Baikonur_51' not cataloged
D3D9: ERROR: Base Object 0x23A17B0 = 'Baikonur-70' not cataloged
D3D9: ERROR: Base Object 0x23A1B20 = 'Baikonur_70' not cataloged
D3D9: ERROR: Base Object 0x23A1E90 = 'Baikonur-23' not cataloged
D3D9: ERROR: Base Object 0x23ACC80 = 'Baikonur_23' not cataloged
D3D9: ERROR: Base Object 0x23ACFF0 = 'Baikonur-24' not cataloged
D3D9: ERROR: Base Object 0x23AD360 = 'Baikonur_24' not cataloged
D3D9: ERROR: Base Object 0x23AD6D0 = 'Baikonur_81' not cataloged
D3D9: ERROR: Base Object 0x23A9468 = 'Baikonur-31' not cataloged
D3D9: ERROR: Base Object 0x23A97D8 = 'Baikonur_31' not cataloged
D3D9: ERROR: Base Object 0x23CCFD0 = 'Baikonur_112' not cataloged
D3D9: ERROR: Base Object 0x23CD340 = 'Baikonur' not cataloged
D3D9: ERROR: Base Object 0x23CD6B0 = 'Arkalyk' not cataloged
D3D9: ERROR: Base Object 0x23DA8C0 = 'Dzezkazgan' not cataloged
D3D9: ERROR: Base Object 0x23DAC48 = 'Clavius Base' not cataloged
D3D9: ERROR: Base Object 0x1DAC0790 = 'Preary Base' not cataloged
000000.000: D3D9: [Scene Initialized]
000000.000: ---------------------------------------------------------------
000000.000: >>> WARNING: Obsolete API function used: oapiGetAtmPressureDensity
000000.000: At least one active module is accessing an obsolete interface function.
000000.000: Addons which rely on obsolete functions may not be compatible with
000000.000: future versions of Orbiter.
000000.000: ---------------------------------------------------------------




edit:
ok so I believe it's Baikonur objects related, other two scenarios loads just fine :unsure:
and it never looked better :love:


orbiter_2022_06_13_23_56_27_191.jpg
 
Last edited:

diogom

Well-known member
Joined
Aug 2, 2010
Messages
1,229
Reaction score
151
Points
78
crash (with launch scenario)

000000.000: ---------------------------------------------------------------
000000.000: >>> WARNING: Obsolete API function used: VESSEL::SetBankMomentScale
000000.000: At least one active module is accessing an obsolete interface function.
000000.000: Addons which rely on obsolete functions may not be compatible with
000000.000: future versions of Orbiter.
000000.000: ---------------------------------------------------------------
000000.000: Finished initialising status
000000.000: Finished initialising camera
000000.000: Finished setting up render state
D3D9: ERROR: Base Object 0x23BCCC0 = 'Baikonur_1' not cataloged
D3D9: ERROR: Base Object 0x23BD030 = 'Baikonur_2' not cataloged
D3D9: ERROR: Base Object 0x23BD840 = 'Baikonur-51' not cataloged
D3D9: ERROR: Base Object 0x23A1440 = 'Baikonur_51' not cataloged
D3D9: ERROR: Base Object 0x23A17B0 = 'Baikonur-70' not cataloged
D3D9: ERROR: Base Object 0x23A1B20 = 'Baikonur_70' not cataloged
D3D9: ERROR: Base Object 0x23A1E90 = 'Baikonur-23' not cataloged
D3D9: ERROR: Base Object 0x23ACC80 = 'Baikonur_23' not cataloged
D3D9: ERROR: Base Object 0x23ACFF0 = 'Baikonur-24' not cataloged
D3D9: ERROR: Base Object 0x23AD360 = 'Baikonur_24' not cataloged
D3D9: ERROR: Base Object 0x23AD6D0 = 'Baikonur_81' not cataloged
D3D9: ERROR: Base Object 0x23A9468 = 'Baikonur-31' not cataloged
D3D9: ERROR: Base Object 0x23A97D8 = 'Baikonur_31' not cataloged
D3D9: ERROR: Base Object 0x23CCFD0 = 'Baikonur_112' not cataloged
D3D9: ERROR: Base Object 0x23CD340 = 'Baikonur' not cataloged
D3D9: ERROR: Base Object 0x23CD6B0 = 'Arkalyk' not cataloged
D3D9: ERROR: Base Object 0x23DA8C0 = 'Dzezkazgan' not cataloged
D3D9: ERROR: Base Object 0x23DAC48 = 'Clavius Base' not cataloged
D3D9: ERROR: Base Object 0x1DAC0790 = 'Preary Base' not cataloged
000000.000: D3D9: [Scene Initialized]
000000.000: ---------------------------------------------------------------
000000.000: >>> WARNING: Obsolete API function used: oapiGetAtmPressureDensity
000000.000: At least one active module is accessing an obsolete interface function.
000000.000: Addons which rely on obsolete functions may not be compatible with
000000.000: future versions of Orbiter.
000000.000: ---------------------------------------------------------------

Soyuz rocket version 1.2 or 1.3?
 

gamer19

Well-known member
Joined
Jul 16, 2016
Messages
108
Reaction score
175
Points
58
Soyuz rocket version 1.2 or 1.3?
1.3
I downloaded 1.2 too, just for the case.... but wasn't thinking about it too much I guess
cause I always prefer to have latest versions of mods
should I go with 1.2 ?
 
Top