[ItsMike]

Hello everyone,

First of all I gotta say that fs open rocks ! keep up the good work.

I just finished the FS1 campaign with the fsport, I ran into some small problems but I managed to finish the campaign.
Now I tried the FS2 campaign, but sadly I ran into a problem.
I've created a new pilot and when I started the first training mission I noticed I didn't have any weapons at all, so I've thought it's just a bug with the training (like fs port had with one training mission).
After skipping the three training missions this error message poped up:

Error: Invalid weapon name.

In sexpression: ( when
   ( true )
   ( good-secondary-time
      "Friendly"
      100
      "Cyclops"
      "Belisarius"
   )
)
(Error appears to be: Cyclops)
File:J:\src\cvs\fs2_open_3_6_9.final\code\Mission\MissionParse.cpp
Line: 5798
[This filename points to the location of a file on the computer that built this executable]

Call stack:
------------------------------------------------------------------
------------------------------------------------------------------

Error: Invalid subsystem name.

In sexpression: ( when
   ( true )
   ( send-message
      "Psamtik"
      "High"
      "FIRE!"
   )
   ( fire-beam
      "Psamtik"
      "turret03"
      "Belisarius"
      "turret13"
   )
)
(Error appears to be: turret03)
File:J:\src\cvs\fs2_open_3_6_9.final\code\Mission\MissionParse.cpp
Line: 5798
[This filename points to the location of a file on the computer that built this executable]

Call stack:
------------------------------------------------------------------
------------------------------------------------------------------

Error: Invalid ship class name.

In sexpression: ( when
   ( true )
   ( tech-add-ships "GTCv Deimos" )
)
(Error appears to be: GTCv Deimos)
File:J:\src\cvs\fs2_open_3_6_9.final\code\Mission\MissionParse.cpp
Line: 5798
[This filename points to the location of a file on the computer that built this executable]

Call stack:
------------------------------------------------------------------
------------------------------------------------------------------

Error: Ship class "GTCv Deimos" invalid
File:J:\src\cvs\fs2_open_3_6_9.final\code\Parse\SEXP.CPP
Line: 10013
[This filename points to the location of a file on the computer that built this executable]

Call stack:
------------------------------------------------------------------
------------------------------------------------------------------

And so, after pressing "Ok" to debug on all these error messages I got my self into the first mission but again, I didn't have any weapons on my ship.


Did I forget to install anything ? How do I get it working ?

Thanks in advance,
Mike.

[Colonol Dekker]

Select Mediavps as a mod in the Launcher when playing the FS2 campaign. actually, create a new pilot too. I try and keep a seperate pilot for each mod i run.


Also


And ...Dekker away!

[ItsMike]

Wow, thanks for the quick reply.

I've selected mediavps as mod folder in the launcher, and made a new pilot but I'm still getting the same error message.
Oh, and yes I've chose the FS2 campaign in the campaign room in case anyone wonders.

[FUBAR-BDHR]

Did you select the main fs2 campaign in the campaign room?

[colecampbell666]

1. In the Launcher, select and run a debug build until it crashes.
2. Post \data\fs2_open.log.
3. ??????
4. Profit!

[Colonol Dekker]

Hmmm. . . . . . Log solves all problems.

[ItsMike]

This time in debug mode it crashed just when I went into the briefing room.

log attached.

[attachment deleted by Tolwyn]

[Zacam]

Put all your FSPort stuff into a folder labled FSPort.

Code: [Select]

Searching root pack 'D:\games\freespace2\fsport-fs1_training.vp'
Searching root pack 'D:\games\freespace2\fsport-glow.vp'
Searching root pack 'D:\games\freespace2\fsport-hi_res.vp'
Searching root pack 'D:\games\freespace2\fsport-missions.vp'
Searching root pack 'D:\games\freespace2\fsport-shine.vp'
Searching root pack 'D:\games\freespace2\fsport3_0_4.vp'

And delete these:

Code: [Select]

Searching root pack 'D:\games\freespace2\mp-710_adveffects.vp'
Searching root pack 'D:\games\freespace2\mp-710_effects.vp'
Searching root pack 'D:\games\freespace2\mp-710_models.vp'
Searching root pack 'D:\games\freespace2\mv_adveffects.vp'
Searching root pack 'D:\games\freespace2\mv_core.vp'
Searching root pack 'D:\games\freespace2\mv_effects.vp'
Searching root pack 'D:\games\freespace2\mv_models.vp'
Searching root pack 'D:\games\freespace2\mv_music.vp'
Searching root pack 'D:\games\freespace2\mv_textures.vp'

And what is this and why is it there? :

Code: [Select]

Searching root pack 'D:\games\freespace2\data\cbanim.vp'

Also:

Code: [Select]

nitializing Direct3D graphics device at 1280x1024 with 32-bit color...
  Direct3D Adapter        : NVIDIA GeForce 8800 GTS
  Direct3D Driver Version : 6.14.11.7813

  Using PURE D3D Device
  Alpha texture format = ARGB, 4:4:4:4
  Non-alpha texture format = ARGB, 1:5:5:5
  Max texture units: 8
  Max texture size: 8192x8192
  Can use compressed textures: YES
  Texture compression available: YES
... Direct3D init is complete!
Switch to OpenGL.

[ItsMike]

Oh sweet, that did it.
I kinda thought all mod files had to be at the root dir, guess not huh

And wow OpenGL menus are soo much better.

Thanks everyone.

Oh and btw about data\cbanim.vp'. It's is for fsport, I was too lazy to download all the files for it and I own a copy of FS1, so the fsport readme said to copy that file there.

[Jeff Vader]

I kinda thought all mod files had to be at the root dir, guess not huh

You might want to read Karajorma's FreeSpace FAQ. Even though a tad bit outdated, it still has numerous instructions that still are valid. Such as the fact that each and every mod must have its own subfolder. If you have all mod vps in \freespace2\, the one that is first alphabetically will always be read before the others and it will most certainly **** up all the other mods.

[Aardwolf]

One thing to note, the mvps installed with Turey's Installer come with a readme which says to put everything loose in the FS2 dir... which is bad.

[Jeff Vader]

I've notified him of that issue previously, but apparently it is the fault of whoever cooked up the release in the first place. Basically the user should just ignore that particular readme (as illogical as it may sound) and have faith in the Installer.