Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: GruntOfAction on July 01, 2008, 05:30:05 pm
-
First problem is this:
(http://i247.photobucket.com/albums/gg147/GruntOfAction/Shipisgone.jpg)
Where is my ship at? I try dragging a ship off the side to where it usually is, but it will not go there...
Then when I am at weapons selection, alot of the weapons have doubles of them but will have a D at the end of them (example "Lazor 1" and "Lazor 1d"
Whats wrong with my game???
EDIT:Alright using the Freespace 1 port allows me to see the ships for selection..
But now when I tried to do campaign it kicked me out with this error:
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:
------------------------------------------------------------------
------------------------------------------------------------------
-
In the campaign room select the FS1 campaign. Trying to run the FS2 Campaign on the port will always crash the game.
-
the "D" after a weapon names means it used for dogfight. Usually you don't see them when playing solo mission (else it isn't a fs2 original campaign).
-
the "D" after a weapon names means it used for dogfight. Usually you don't see them when playing solo mission (else it isn't a fs2 original campaign).
That explains things a little, it seems he has created a multiplayer pilot and tried to join a nonexistent game??? Which is why his ship cannot be selected, only the host can select the ships you will dogfight!
*EDIT* Spellcheck, Spellcheck, Spellcheck................I must remember to spell check!
-
I was wondering why he had, say, an Ares "available" at the very beginning.
-
the "D" after a weapon names means it used for dogfight. Usually you don't see them when playing solo mission (else it isn't a fs2 original campaign).
That explains things a little, it seems he has created a multiplayer pilot and tried to join a nonexistent game??? Which is why his ship cannot be selected, only the host can select the ships you will dogfight!
*EDIT* Spellcheck, Spellcheck, Spellcheck................I must remember to spell check!
Actually, that was in Single Player, under the tech room with the mission simulator..that happens when I select Massive Battle 1 and 2..
Also on random missions astroids are not appearing, some shivan ships (manticores, ect) are showing up grey and from a distance are not fully rendered, they appear as little spikey looking things..
-
We really need to remove Massive Battle 1 and 2. They weren't ever finished and shouldn't have been in the multiplayer pack anyway.
-
Actually, that was in Single Player, under the tech room with the mission simulator..that happens when I select Massive Battle 1 and 2..
May I ask why you were playing those? You could have just picked a campaign and start playing it.
Also on random missions astroids are not appearing, some shivan ships (manticores, ect) are showing up grey and from a distance are not fully rendered, they appear as little spikey looking things..
If you take a look at the Launcher, you'll see a tab called Features. Open it and tick on at least the following options: Enable specular, Enable glowmaps, Enable jpg/tga textures (if you're using the 3.6.9 build) and Use models for ship selection.
-
In order to see the ships at the bottom, you must make your ship part of a wing in FRED.
-
Another little "cheat": i had also this problem. Press the "reset" button and all fixes.
-
We really need to remove Massive Battle 1 and 2. They weren't ever finished and shouldn't have been in the multiplayer pack anyway.
I gather there was no real point in those 2 missions ?
-
From the look of it they were test missions that got stuck in the VP by accident.