Project Space Shuttle Vessel

amalahama

Member
Joined
Feb 13, 2008
Messages
38
Reaction score
5
Points
8
Absolutely!! There is no many coders out there able to (or eager to) deal with the complexity of Space Shuttle systems, you would add way more value as coder than as modeller (whose 3D models I already consider ok-ish).

No further comments with regards to your three main focus areas.

On the bright side, although SSU/SSV cockpit looks outdated and wrongly scaled (feels tiny really), labels are way more readable than in Flightgear.

Best Regards
 

Urwumpe

Not funny anymore
Addon Developer
Donator
Joined
Feb 6, 2008
Messages
36,997
Reaction score
1,678
Points
203
Location
Langendernbach
The 3D model isn't what scares me (yes, it's not easy), I'm more concerned about GPCs, IDPs, ADCs, MDUs, DEUs, DDUs, DUs, basically all the unseen parts that drive the displays, lights, talkbacks, etc.
On the graphics side, the only "concerns" are interior and panel/switch lighting (which is sort of out of my hands as it depend a lot on the graphics engines), the mechanical tapes (for altitude, velocity, etc) in the MCDS version, and ejection seats. All of these are +/- far in the future, so I'm currently loosing sleep with other things. Meanwhile there will be the occasional "incremental update" to improve what exists, but after 2+ years of graphics work, the 3 main focus areas are 1) code, 2) code, and 3) code.

Yes, those are complicated. But maybe you can find a way to simplify things more than I can, because I am already too deep into the FCOS flow charts to really find a good abstraction.
 

GLS

Well-known member
Orbiter Contributor
Addon Developer
Joined
Mar 22, 2008
Messages
5,150
Reaction score
1,856
Points
188
Website
github.com
Yes, those are complicated. But maybe you can find a way to simplify things more than I can, because I am already too deep into the FCOS flow charts to really find a good abstraction.
It will have to be done with incremental changes, and the occasional "kick forward" that breaks compatibility. The C&W and "SM hack" are testing the limits of current GPC/IDP I/O, so improving relationship that is rising to the top of the TODO list. For now, moving "regular I/O" signals to the MDMs is the priority, as it decreases the number of "software class calling the subsystem class" cases and brings closer the separation of the GPCs from the simulation, currently predicted for sometime after the return of Halley's comet.
 

amalahama

Member
Joined
Feb 13, 2008
Messages
38
Reaction score
5
Points
8
Out of curiosity @GLS , how do you come to know so much about the shuttle? Pure hobby or did you have previous contact with the program? Do you work in a space-related job?

Best regards
 

GLS

Well-known member
Orbiter Contributor
Addon Developer
Joined
Mar 22, 2008
Messages
5,150
Reaction score
1,856
Points
188
Website
github.com
Out of curiosity @GLS , how do you come to know so much about the shuttle? Pure hobby or did you have previous contact with the program? Do you work in a space-related job?

Best regards
Hobby. The joke I usually make is: "it was either this or drugs" . :ROFLMAO:
 

Wolf

Donator
Donator
Joined
Feb 10, 2008
Messages
1,091
Reaction score
10
Points
38
Location
Milan
Well, accomplishing such a gigantic endeavour with such little manpower ( AFAIK SSV is a one man show) probably requires some "external help" hence drugs are not ruled out I guess :LOL:
 

GLS

Well-known member
Orbiter Contributor
Addon Developer
Joined
Mar 22, 2008
Messages
5,150
Reaction score
1,856
Points
188
Website
github.com
Well, accomplishing such a gigantic endeavour with such little manpower ( AFAIK SSV is a one man show) probably requires some "external help" hence drugs are not ruled out I guess :LOL:
Only plain water.
 

GLS

Well-known member
Orbiter Contributor
Addon Developer
Joined
Mar 22, 2008
Messages
5,150
Reaction score
1,856
Points
188
Website
github.com
It's been a while without an update, so here is one!
Since the last release, work has been mostly about finishing the C&W work, both in the software and hardware sides, and also adding new thumbwheels and pushwheels.
Untitled.png
The fault message line is a bit hard to read in MOGE (no problem in D3D9, as it is visible above). I tried to improve that, but scaling that color combination just doesn't give good results.
Panel R13U should be fully functional, although only an handful of sensors exist at the moment. In the GPCs, that are also only a few fault messages, but these should already be enough for people to start hating the sound of the Master Alarm and Systems Management tone. :ROFLMAO:

I've also resumed work in the CCTV, but there is a lot of code reorganization left to do, as the initial implementation was pretty much a test of the concept.

Other new features and improvements, both small and large, are also in development, so stick around. 😉
 

Marg

Active member
Joined
Mar 20, 2008
Messages
459
Reaction score
63
Points
28
I have spent so much time in SSV that it is hard to write everything down. I've tried OPS105, OPS201, OPS 202, OPS 302, etc...

1) At first I was trying IUS deployment, long time trial and errors. I put TDRS good model on the stack. I know some things are not implemented yet, but I did everything to make aft ring to go up (60 degrees). After a long research I luckily came across ultra old thread, where "latch release" on A6 panel was mentioned. Then I succeeded.
Only IUS ASE is quite basic, low poly model. I replaced it with "mine". I do not remember where I got "my" ASE, but I think I took JacquesMomo\Papy's one, and heavily modified, adding many details (Gattispilot as well did a lot here). In High-RES photos IUS ASE's are quite complex structures. As I understand SSV's model defines group numbers, which will "turn" along with IUS ASE's aft frame. One thing tough - I noticed that forward frame's LOAD LEVELERS are hanging in payload bay. They are not a part of neither ASE, but of a shuttle mesh itself. Is it supposed to be this way? And - they are quite detailed, unlike default SSV's ASE.
2) RMS operations - a lot trial and error. Powering up - turning central switch to the PORT position was obvious, DEPLOY as well.... but only after a while I realized those 2 "RELEASE" switches are working too (SHOULDER BRACE + release below that). And then DIRECT +\- switch.
3) External tanks have sometimes visible shading "seam" (normal doubling?) on the front side. I just rotated (in MeshWizard) LOX and HOX tanks around 30 degrees so that it is hidden under cable trays. But UV mapping is unchanged and intertank (which I did not rotate) has some shift ( I noticed when burnt texture appeared).
4) Upon reentry APU often does not give hydraulic pressure, I noticed it (seeing on the screen) after crashing a couple of times in the Pacific 1000 km short of Edwards AFB. Haven't understood what is missing though, tried to activate APU's in reverse (from post MECO checklist).
 

GLS

Well-known member
Orbiter Contributor
Addon Developer
Joined
Mar 22, 2008
Messages
5,150
Reaction score
1,856
Points
188
Website
github.com
1) At first I was trying IUS deployment, long time trial and errors. I put TDRS good model on the stack. I know some things are not implemented yet, but I did everything to make aft ring to go up (60 degrees). After a long research I luckily came across ultra old thread, where "latch release" on A6 panel was mentioned. Then I succeeded.
The electrical and data parts of the IUS aren't implemented, so only the deploy switches work. I still have to write in the manual some basic deploy info on the IUS, but there is a checklist somewhere online. Quickly:
  • there are 2 PRLAs holding the fwd end of the IUS, so they need to be deployed first.
  • Drive Enable - Intermediate
  • Motion - Up (wait for stop at 29º)
  • Umbilicals - Enable and Release
  • Motion - Up (wait for stop at 58º)
  • Pyro Bus - On
  • IUS Deployment - Enable and Deploy


Only IUS ASE is quite basic, low poly model. I replaced it with "mine". I do not remember where I got "my" ASE, but I think I took JacquesMomo\Papy's one, and heavily modified, adding many details (Gattispilot as well did a lot here). In High-RES photos IUS ASE's are quite complex structures. As I understand SSV's model defines group numbers, which will "turn" along with IUS ASE's aft frame. One thing tough - I noticed that forward frame's LOAD LEVELERS are hanging in payload bay. They are not a part of neither ASE, but of a shuttle mesh itself. Is it supposed to be this way? And - they are quite detailed, unlike default SSV's ASE.
Then it won't work.... I'd rather make one from scratch than taking one from an unknown source. Anyway, except for the occasional part here and there, graphics are not the current priority, so further work in the IUS ASE will probably only happen when I make the other IUS variants.
The IUS ASE meshes, and CISS and others, are handled as being part of the OV and separate not vessels.


2) RMS operations - a lot trial and error. Powering up - turning central switch to the PORT position was obvious, DEPLOY as well.... but only after a while I realized those 2 "RELEASE" switches are working too (SHOULDER BRACE + release below that). And then DIRECT +\- switch.
The bottom panel pretty much handles the MPM on both sides, and the top panel handles the RMS. There is no GPC yet to handle the RMS, so there are bits and parts that don't work, but the "basics" should work. The PDRS checklists should have good info on how to deploy and stow the RMS.


3) External tanks have sometimes visible shading "seam" (normal doubling?) on the front side. I just rotated (in MeshWizard) LOX and HOX tanks around 30 degrees so that it is hidden under cable trays. But UV mapping is unchanged and intertank (which I did not rotate) has some shift ( I noticed when burnt texture appeared).
I know about that seam, and others, (they exist because of the uv mapping) and I know how to fix them, but the current priority is code so we'll just have to live with it for a few weeks/months.


4) Upon reentry APU often does not give hydraulic pressure, I noticed it (seeing on the screen) after crashing a couple of times in the Pacific 1000 km short of Edwards AFB. Haven't understood what is missing though, tried to activate APU's in reverse (from post MECO checklist).
Are you sure the APUs are working? Again, checklists are your friends, and the Entry checklist has the APU start proceedures.
 

Marg

Active member
Joined
Mar 20, 2008
Messages
459
Reaction score
63
Points
28
SSV is huge project no doubt, customization options are already huge (transferred quite easily some my painted ET's to new textures).
I forgot to ask about roll to heads up manouevre. When I created 1988-89 mission using STS-120 as a base (I think), it still rolled to heads up. I could not find any options to set it ON\OFF. Or it is better to take appropriate early mission as a base.
 

GLS

Well-known member
Orbiter Contributor
Addon Developer
Joined
Mar 22, 2008
Messages
5,150
Reaction score
1,856
Points
188
Website
github.com
SSV is huge project no doubt, customization options are already huge (transferred quite easily some my painted ET's to new textures).
I forgot to ask about roll to heads up manouevre. When I created 1988-89 mission using STS-120 as a base (I think), it still rolled to heads up. I could not find any options to set it ON\OFF. Or it is better to take appropriate early mission as a base.
Eventually it will be simplified, but for now:
There is an file (I-LOAD List.xls) in the Doc folder with a list of the I-LOADs (which I just realized is incomplete) and their units and basic descriptions (for most of them).
The most changed parameters will eventually have a "pretty edit" capability in other tabs of the Mission Editor, so the user "doesn't get their hands dirty".

For the second stage roll angle there are 2 parameters (actually 3):
PHI_CMD​
rad​
commanded roll angle​
PHI_2STG​
rad​
desired roll command for second stage​
V_RHO_PHI​
fps​
switch velocity for roll command​
PHI_CMD is the initial 2nd stage roll angle, so 180º or PI radians. This should never change.
V_RHO_PHI is the relative velocity at which PHI_CMD is replaced with PHI_2STG.
So to roll heads up, PHI_2STG should be 0, and to stay heads down it should be 3.141593.
 

GLS

Well-known member
Orbiter Contributor
Addon Developer
Joined
Mar 22, 2008
Messages
5,150
Reaction score
1,856
Points
188
Website
github.com

EarthMoon

The Earth and the Moon
Joined
Jul 12, 2022
Messages
11
Reaction score
1
Points
3
Location
Germany
Website
earthmoon.glitch.me
I installed SSV and when I launch one scenario, it just places an "invisible" object in eastern pacific where the cam can move around.

Orbiter 2016

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 (NVIDIA Quadro NVS 450) (HW)
000000.000: [x] Direct3D T&L HAL (NVIDIA Quadro NVS 450) (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: Module XRSound.dll ........... [Build 200703, API 160828]
000000.000: Module Orb2CelMFD.dll ........ [Build ******, API 060425]
000000.000: ---------------------------------------------------------------
000000.000: >>> WARNING: Obsolete API function used: oapiRegisterMFDMode
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: Module ScnEditor.dll ......... [Build 160828, API 160828]
000000.000: Module transx.dll ............ [Build 160216, API 160214]
000000.000:
000000.000: **** Creating simulation session
000000.000: DirectDraw interface OK
000000.000: Direct3D interface OK
000000.000: Graphics: Viewport: Window 1194 x 721 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: SSV_LCC
[Vessel::LoadModule | .\Vessel.cpp | 5747]
===============================================================
============================ ERROR: ===========================
Could not load vessel module: SSV_LC39
[Vessel::LoadModule | .\Vessel.cpp | 5747]
===============================================================
============================ ERROR: ===========================
Could not load vessel module: SSV_MLP
[Vessel::LoadModule | .\Vessel.cpp | 5747]
===============================================================
============================ ERROR: ===========================
Could not load vessel module: SSV_OV
[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
000000.000: XRSound 2.00 (Build Date: Jul 3 2020) initialized using sound driver DirectSound8; irrKlang version = 1.6.0. XRSound UpdateInterval = 0.050 (20.0 updates per second)
000012.546: XRSound 2.00 (Build Date: Jul 3 2020) terminating.
000012.546: **** Closing simulation session
000012.546:
000012.546: **** Creating simulation session
000012.546: DirectDraw interface OK
000012.546: Direct3D interface OK
000012.546: Graphics: Viewport: Window 1194 x 721 x 32
000012.546: Graphics: Hardware T&L capability: Yes
000012.546: Graphics: Z-buffer depth: 32 bit
000012.546: Graphics: Active lights supported: 8
000012.546: Loading 15382 records from star database
000012.546: ---------------------------------------------------------------
000012.546: >>> ERROR: DDraw error DDERR_BLTFASTCANTCLIP
000012.546: >>> [OrbiterGraphics::clbkBlt | .\OGraphics.cpp | 1633]
000012.546: ---------------------------------------------------------------
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: SSV_LCC
[Vessel::LoadModule | .\Vessel.cpp | 5747]
===============================================================
============================ ERROR: ===========================
Could not load vessel module: SSV_LC39
[Vessel::LoadModule | .\Vessel.cpp | 5747]
===============================================================
============================ ERROR: ===========================
Could not load vessel module: SSV_MLP
[Vessel::LoadModule | .\Vessel.cpp | 5747]
===============================================================
============================ ERROR: ===========================
Could not load vessel module: SSV_OV
[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
000000.000: XRSound 2.00 (Build Date: Jul 3 2020) initialized using sound driver DirectSound8; irrKlang version = 1.6.0. XRSound UpdateInterval = 0.050 (20.0 updates per second)
000033.686: XRSound 2.00 (Build Date: Jul 3 2020) terminating.
000033.686: **** Closing simulation session

I don't get a "Critical error ocurred. See orbiter.log" error, It just loads an "invsible" object.

A short (01:05) video clip (inside a .zip; .mp4 upload not supported):
 

Attachments

  • SSV-invisible.mp4.zip
    33.9 MB · Views: 3

GLS

Well-known member
Orbiter Contributor
Addon Developer
Joined
Mar 22, 2008
Messages
5,150
Reaction score
1,856
Points
188
Website
github.com
Hi there @EarthMoon !
It looks like you are missing OrbiterSound (link in the readme file and manual), or the bridge module to emulate OS with XRSound, although I don't think that would explain everything... are you sure the vessel cfg and dll files exist?
Is this with SSV v1.2?
 

EarthMoon

The Earth and the Moon
Joined
Jul 12, 2022
Messages
11
Reaction score
1
Points
3
Location
Germany
Website
earthmoon.glitch.me
Yes, it's v1.2

There is no \modules\ folder in the .zip file. That's why, because the orbiter.log says "Could not load vessel module: SSV_###".

no_modules_folder.png
 

GLS

Well-known member
Orbiter Contributor
Addon Developer
Joined
Mar 22, 2008
Messages
5,150
Reaction score
1,856
Points
188
Website
github.com

EarthMoon

The Earth and the Moon
Joined
Jul 12, 2022
Messages
11
Reaction score
1
Points
3
Location
Germany
Website
earthmoon.glitch.me
I downloaded now the correct file, but the orbiter.log continues saying "ERROR: Could not load vessel module: SSV_*", but the modules exist.

I'm using Orbiter 2016 (160828), SSV 1.2

could-not-load-vessel-module.jpg
All SSV_*.dll files in Orbiter2016\Modules and all SSV errors in orbiter.log

I think the SSV_*.dll files are compiled wrong or have syntax errors.
 
Top