Cassiopee not showing up in-game

RangerPL

Addon Consumer
Joined
May 25, 2008
Messages
345
Reaction score
0
Points
16
Location
Soviet bunker on Pluto
I have a pretty big problem with the Cassiopee space station module from Mustard's site: it does not appear in Orbiter. The docking ports are all correctly place; but the mesh just isn't there. The odd thing is that it worked perfectly fine yesterday, and it started malfunctioning today.

I did not run any software that might have wiped anything from the disk in the meantime. I also reinstalled the Cassiopee several times to no effect. I think that this is something obvious that I missed, as I am a noob at rooting out problems :(
 
I often have the same problem with modules from mustard's site.

Could you post your "orbiter.log"?

I solved the problem this way:
Search for "Cassiopee.cfg" in your "config" and "config/vessels" folders.
If the file is empty, copy the text from
a normal (not empty) "Cassiopee.cfg" into the empty "Cassiopee.cfg".

If this does not help there must be a problem with an other Addon (probably CamShake, if you have it, try it out with all modules disabled).

:cheers:
 
My orbiter.log shows nothing wrong:
Code:
**** Orbiter.log
Build Sep 29 2006 [v.060929]
Found 1 joystick(s)
Module AtlantisConfig.dll [API v.060425]
Module DGConfig.dll [API v.060425]
Module EnergyConfigurator.dll [API v.060425]
Module AttitudeMFD.dll [API v.060425]
Module ExtMFD.dll [API v.060425]
Module Framerate.dll [API v.050206]
Module GPCMFD.dll [API v.060425]
Module OrbiterSound.dll [API v.060425]
Module Rcontrol.dll [API v.050206]
Module RendezvousMFD.dll [API v.050206]
Module ScnEditor.dll [API v.060425]
Module NotesMFD.dll [API v.060425]
Module HUDdataMFD.dll [API v.060425]
Module InterMFD51.dll [API v.060425]

That's all that there's in it. I installed UMmu support for the ISS recently, but that can't be it, because I un-installed it and installed it again to no effect. (I use JoneSoft Generic Mod Enabler)

And yeah, the add-ons from Mustard's page are great for stationbuilding, but they have their problems. *sigh*
 
I know this is basically completely unrelated from Orbiter, but I've noticed with Star Trek Bridge Commander the identical thing starting happen. I've also noticed a lot more people complaining here lately about meshes just disappearing even though they worked before. Ya wild thought I know, but who knows? There could be some virus or spyware connection!
 
Video drivers?

Did you do a Windoze update recently or change your video card drivers or hardware?
Try another 3D mode and see if it still does it.
 
I've also noticed a lot more people complaining here lately about meshes just disappearing even though they worked before. Ya wild thought I know, but who knows? There could be some virus or spyware connection!
I had recently a mesh that disappeared randomly. For instance, spawning the vessel with the scenario editor was working fine but after saving then reloading the scenario, no more mesh (and scenario was not saved correctly).

It was just a problem on the mesh file itself, an empty group declared (no vertice just the texture material and the geom flags but no other data).

Cassiopee is one of my older addons, it was originaly an addon for orbiter 2005 and a spacecraft2 vessel if I remember well. I suggest to convert it to spacecraft3.
 
Ok, I will use a different add-on for my station.

Maybe describing the what I did to get the cassiope in my scenario will be better:

I'm building a space station, so I copy+pasted the Cassiopee into my scenario manually and attached it to the XR5 using the UCD/UCDCarrier combo. I launched my XR5 and completed the mission, docking the Cassiopee to my station and returning to base. After that I turned off my computer and did not do anything orbiter-related until today, when I realized that the Cassiopee mesh is invisible. The saseva is also invisible. Everything on the Cassiopee works perfectly, even the docking is correct with two exceptions:
-RCS is unusable
-Mesh is invisible

The vessel is there; it can even be attached to the UCD. It's just invisible and unusable other than that.
 
Unfortunatley I dont have the archive at home and can't download (mustard's site seems to be offline as dansteph's :blink: )

Well, I can't remmeber how I did Cassiopee but try something like that:
Open your scenario file and modify the cassiopee definition.
Cassiopee: Spacecraft/spacecraft3
...
END
do the same for saseva:
saseva:Spacecraft/spacecraft3
...
END

EDIT: Don't do that, Cassiopee is already a spacecraft3 vessel, I really don't know why the mesh is dissappearing :huh:

I can't reproduce the problem at home, it works as intended.
 
Last edited:
Hey, that actually works! :speakcool:
For now at least, though the saseva CTDs when I try to switch to it. No biggie though, as I'm only really using the Cassiopee on my station.

Thanks!:cheers:
PS: Mustard's site is back.
 
I noticed that it was in the scenario as "Cassiopee:cassiopee" not "cassiopee:spacecraft/spacecraft3"

I often have the same problem with modules from mustard's site.

Could you post your "orbiter.log"?

I solved the problem this way:
Search for "Cassiopee.cfg" in your "config" and "config/vessels" folders.
If the file is empty, copy the text from
a normal (not empty) "Cassiopee.cfg" into the empty "Cassiopee.cfg".

If this does not help there must be a problem with an other Addon (probably CamShake, if you have it, try it out with all modules disabled).

:cheers:

EDIT: I used Astrosammy's way. None of the vessels from Mustard's that I have (PMA, Cassiopee, Ariane, CTV/ATV) that are designed for Orbiter 2005 have complete .cfgs.
 
Last edited:
Okay, now I'm having problems with the Solaris solar arrays I got from Mustard's site. I need to put two of them in my scenario.

I tried to put two into my scenario, the way they are added in the startup scenarios that they come with:
Code:
solaris:Solaris
  STATUS Orbiting Earth
  RPOS 4516389.98 3918530.89 2723372.90
  RVEL -4560.024 913.571 6248.380
  AROT 102.37 -1.65 -134.68
  ATTACHED 1:6,XR5-UCD
  NAVFREQ 0 0
  CONFIGURATION 1
  CURRENT_PAYLOAD 0
  SEQ 0 -2 0.000000
  SEQ 1 -2 0.000000
  SEQ 2 -2 0.000000
END
solaris:Solaris
  STATUS Orbiting Earth
  RPOS 4516363.73 3918573.93 2723349.87
  RVEL -4560.022 913.569 6248.378
  AROT -145.71 -30.42 23.22
  NAVFREQ 0 0
  CONFIGURATION 1
  CURRENT_PAYLOAD 0
  SEQ 0 -2 0.000000
  SEQ 1 -2 0.000000
  SEQ 2 -2 0.000000
END

This causes a CTD with the following Orbiter.log:

Code:
**** Orbiter.log
Build Sep 29 2006 [v.060929]
Found 1 joystick(s)
Module AtlantisConfig.dll [API v.060425]
Module DGConfig.dll [API v.060425]
Module EnergyConfigurator.dll [API v.060425]
Module AttitudeMFD.dll [API v.060425]
Module ExtMFD.dll [API v.060425]
Module Framerate.dll [API v.050206]
Module GPCMFD.dll [API v.060425]
Module OrbiterSound.dll [API v.060425]
Module Rcontrol.dll [API v.050206]
Module RendezvousMFD.dll [API v.050206]
Module ScnEditor.dll [API v.060425]
Module NotesMFD.dll [API v.060425]
Module HUDdataMFD.dll [API v.060425]
Module InterMFD51.dll [API v.060425]

**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Zbuffer: 16 bit
Render device: Fullscreen 1280 x 1024
Device has no hardware T&L capability
Joystick throttle: Z-AXIS
Joystick throttle control detected
Module Sun.dll [API v.050206]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Mercury.dll [API v.050206]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
Module Venus.dll [API v.050206]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
Module Earth.dll [API v.050206]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
Module Moon.dll [API v.041022]
ELP82: Precision 1e-005, Terms 116/829
Module Mars.dll [API v.060425]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
Module Phobos.dll [API v.060425]
Module Deimos.dll [API v.060425]
Module Galsat.dll [API v.041022]
Module Jupiter.dll [API v.050206]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
Module Io.dll [API v.041022]
Module Europa.dll [API v.041022]
Module Ganymede.dll [API v.041022]
Module Callisto.dll [API v.041022]
Module Satsat.dll [API v.050206]
Module Saturn.dll [API v.060425]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
Module Mimas.dll [API v.050206]
SATSAT Mimas: Terms 113
Module Enceladus.dll [API v.050206]
SATSAT Enceladus: Terms 33
Module Tethys.dll [API v.050206]
SATSAT Tethys: Terms 101
Module Dione.dll [API v.050206]
SATSAT Dione: Terms 59
Module Rhea.dll [API v.050206]
SATSAT Rhea: Terms 68
Module Titan.dll [API v.050206]
SATSAT Titan: Terms 100
Module Hyperion.dll [API v.050206]
SATSAT Hyperion: Terms 595
Module Iapetus.dll [API v.050206]
SATSAT Iapetus: Terms 605
Module Uranus.dll [API v.050206]
VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
Module Miranda.dll [API v.060425]
Module Ariel.dll [API v.060425]
Module Umbriel.dll [API v.060425]
Module Titania.dll [API v.060425]
Module Oberon.dll [API v.060425]
Module Neptune.dll [API v.050206]
VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
Module Triton.dll [API v.060425]
Finished initialising world
Module EnergyTower.dll [API v.060425]
Module Mir2.dll [API v.060425]
Module Spacecraft3.dll [API v.060425]
Module URMS.dll [API v.060425]
Module XR5Vanguard.dll [API v.060425]
Module UCargoDeck.dll [API v.060425]
Module Spacecraft2.dll [API v.050206]

(note, it says nothing went wrong)

I tried to duplicate the Solaris .cfg files and use the following formula:
Code:
solaris:Spacecraft/Spacecraft3
  STATUS Orbiting Earth
  RPOS 4516389.98 3918530.89 2723372.90
  RVEL -4560.024 913.571 6248.380
  AROT 102.37 -1.65 -134.68
  ATTACHED 1:6,XR5-UCD
  NAVFREQ 0 0
  CONFIGURATION 1
  CURRENT_PAYLOAD 0
  SEQ 0 -2 0.000000
  SEQ 1 -2 0.000000
  SEQ 2 -2 0.000000
END
solaris:Spacecraft/Spacecraft3
  STATUS Orbiting Earth
  RPOS 4516363.73 3918573.93 2723349.87
  RVEL -4560.022 913.569 6248.378
  AROT -145.71 -30.42 23.22
  NAVFREQ 0 0
  CONFIGURATION 1
  CURRENT_PAYLOAD 0
  SEQ 0 -2 0.000000
  SEQ 1 -2 0.000000
  SEQ 2 -2 0.000000
END
This works fine, but the docking ports do not work. I.e. I simply can't dock them using the dragonfly, RMS or the scenario editor.

Please help me.
 
You can't use the same name twice in one scenery; you have to re-name one of the Solaris descriptions "Solaris2" to distinquish between the two; i.e

solaris:Spacecraft/Spacecraft3
STATUS Orbiting Earth
RPOS 4516389.98 3918530.89 2723372.90
RVEL -4560.024 913.571 6248.380
AROT 102.37 -1.65 -134.68
ATTACHED 1:6,XR5-UCD
NAVFREQ 0 0
CONFIGURATION 1
CURRENT_PAYLOAD 0
SEQ 0 -2 0.000000
SEQ 1 -2 0.000000
SEQ 2 -2 0.000000
END
solaris2:Spacecraft/Spacecraft3
STATUS Orbiting Earth
RPOS 4516363.73 3918573.93 2723349.87
RVEL -4560.022 913.569 6248.378
AROT -145.71 -30.42 23.22
NAVFREQ 0 0
CONFIGURATION 1
CURRENT_PAYLOAD 0
SEQ 0 -2 0.000000
SEQ 1 -2 0.000000
SEQ 2 -2 0.000000
END
 
You can't use the same name twice in one scenery; you have to re-name one of the Solaris descriptions "Solaris2" to distinquish between the two; i.e

solaris:Spacecraft/Spacecraft3
STATUS Orbiting Earth
RPOS 4516389.98 3918530.89 2723372.90
RVEL -4560.024 913.571 6248.380
AROT 102.37 -1.65 -134.68
ATTACHED 1:6,XR5-UCD
NAVFREQ 0 0
CONFIGURATION 1
CURRENT_PAYLOAD 0
SEQ 0 -2 0.000000
SEQ 1 -2 0.000000
SEQ 2 -2 0.000000
END
solaris2:Spacecraft/Spacecraft3
STATUS Orbiting Earth
RPOS 4516363.73 3918573.93 2723349.87
RVEL -4560.022 913.569 6248.378
AROT -145.71 -30.42 23.22
NAVFREQ 0 0
CONFIGURATION 1
CURRENT_PAYLOAD 0
SEQ 0 -2 0.000000
SEQ 1 -2 0.000000
SEQ 2 -2 0.000000
END

This will require a second .ini file.
Copy the Solaris.ini file from the config/spacecraft folder.
rename the copied file to match the name of the craft in the .scn file.
 
Back
Top