Problem Trouble getting Vinka's spacecraft working

[Phaedrus]

I can't seem to wrap my head around what Vinka's spacecraft module needs to work.

I've got the ini file and the cfg file set up, copied from another ship that works fine, but Orbiter crashes when I add the ship using the scenario editor. The last two entrys in the orbiter.log file is

**** WARNING: Mesh not found: .\Meshes\.msh
**** WARNING: Mesh not found: .\Meshes\.msh

I've checked a zillion times, and the mesh IS there. It works fine if the "module = spacecraft" line is removed from the cfg file, but then I can't have the animations I am aiming for. Also, if I edit the ship into the scenario file, it loads up fine. The original ship can be added using the scenario editor, and there are virtually no changes to the ini or cfg files, only the mesh name. It is making me crazy!

Can anyone point me toward a resource that explains exactly what Vinka's spacecraft dlls need, and how to troubleshoot this?

 

[Woo482]

Mind showing us your .ini ? it'll make it easier for us to help find and fix your problem :thumbup:
and to the forum !

 

[MeDiCS]

AFAIK, Spacecraft3 vessels can't be spawned by the scenario editor. Don't know why thou'.

Oh, and !!!

 

[Woo482]

Actually, they can just a real pain to get it working

 

[DaveS]

Actually, they can just a real pain to get it working

Pain? What pain? It is as simple as copying the Spacecraft3.cfg over to the Vessels subfolder. Nothing more. Very easy can be done under a minute, even manually.

 

[Phaedrus]

Thanks for the quick response!

The INI file:

; === Galapagos Space Station, Nuclear Reactor ===

[CONFIG]
MESHNAME="GS_trussreactor"

SIZE=22.5
EMPTY_MASS=40000
FUEL_MASS=0
MAIN_THRUST=0
RETRO_THRUST=0
HOVER_THRUST=0
ATTITUDE_THRUST=0
ISP=0
TRIM=0.0
PMI=(3.6,3.6,7.2)

FOCUS=-1
VISIBLE=1
CAMERA=(0.00,0.00,0.00)

;------------ DOCKING POINTS DESCRIPTION SECTION ------------

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

[DOCK_1]
POS=(0,0,-5)
DIR=(0,0,-1)
ROT=(0,1,0)

;------------ ANIMATIONS SECTION ------------

[ANIM_SEQ_0]
KEY=G
DURATION=10
REPEAT=1

[ANIM_COMP_0]
SEQ=0
GROUPS=1,4,6,8
RANGE=(0.0,1.0)
TYPE=ROTATE
ROT_PNT=(0,0,0)
ROT_AXIS=(0,0,1)
ANGLE=360

This is an EXACT copy of a working ini, with only the name of the mesh changed. All the values are wrong, but I figure I'll fix them once I get it working at all.

The CFG file:

; === Galapagos Space Station, Nuclear Reactor ===

MeshName = GS_trussreactor
Module = Spacecraft2

Not much to it. I've tried it with spacecraft and spacecraft3 as well.

Thanks!

---------- Post added 03-07-10 at 12:21 AM ---------- Previous post was 03-06-10 at 11:57 PM ----------

Now my mind is totally blown.

I just noticed that it works if, in the scenario editor, I give the vessel the EXACT name as the ini (or mesh, or cfg, they're all the same). I can add other vessels with names different from the ini name ... does this have something to do with the ClassName? I am so confused.

 

[Notebook]

I think the problem is here in your .ini file.

[CONFIG]
MESHNAME="GS_trussreactor"

There should be a 'spacecraft\' before the filename of your mesh. You have to give it the path to the mesh.

Could be wrong of course, hopefully others will confirm.

N.

 

[Donamy]

That's only if the mesh is in the meshes/spacecraft folder.

 

[Phaedrus]

I'm missing something fundamental, aren't I?

DaveS, my spacecraft3.cfg file is indeed in the Vessels subfolder (as is spacedraft.cfg and spacecraft2.cfg). I still can't spawn more than one, and that one has to have exactly the right name. Is that a normal limitation of the scenario editor?

 

[Donamy]

In dealing with SC3 vehicles, it may be.

 

[PhantomCruiser]

It can be a little convoluted. But I'd wound up adding an SC3 vessel (a Space1999 Eagle), then closed out of Orbiter using CTRL+Q. Then edited the current state scenario changing the name of the Eagle to my daughters name. Then loaded the current state, added another Eagle (lather, rinse, repeat). After a few times I'd figured out how to add craft by hand using notepad. I had 7 Eagles named after my daughter, neices and nephews.
It's not an ideal solution, but it worked...