Author Topic: Bridge Commander crashes (Read 1082 times)

Zippy91 · « **on:** December 01, 2018, 04:11:46 PM »

Hey all,

We all know Bridge Commander crashes. Alot. But for me right now it doesn't take much for it to crash and it's barely playable. I only installed it today and got KM along with a couple of extra mods, I got the log script that was recommended on this forum and for some reason it says Breen ships are missing, which I have no clue why because I haven't put anything in that requires Breen ships. The log is pasted at the bottom but it's a long one.

Is there any other way to fix this? All I want out of my game is the ability to add ships, random encounters and to travel anywhere.

Oh also for some reason, I can't select an Era, only Dominion war is available so that means I can't fly anything like a TOS ship as my butt gets kicked from anything that's not TOS era in random encounters.

I fear this isn't the same error each time, but I haven't done that much modding to it outside of KM so I don't understand why it's acting like this.

Spoiler: show

Zippy91 · « **Reply #1 on:** December 01, 2018, 04:26:01 PM »

Update, just tried again to see if it was the same error, I can't see anything that stands out. This time I was about to warp from the Sol system to the Banzai system.

Spoiler: show

Zippy91 · « **Reply #2 on:** December 01, 2018, 05:09:31 PM »

Update 2: Just tried it for a third time and I crashed shortly after I enabled Random Battles. I think this is where the cause is, could someone confirm this for me in the two logs I posted previously, in all instances I have run Random Battles.

If this is the cause can someone tell me how I can fix it as I love random encounters.

Blackrook32 · « **Reply #3 on:** December 01, 2018, 08:33:13 PM »

Quote from: Zippy91 on December 01, 2018, 05:09:31 PM

Update 2: Just tried it for a third time and I crashed shortly after I enabled Random Battles. I think this is where the cause is, could someone confirm this for me in the two logs I posted previously, in all instances I have run Random Battles.

If this is the cause can someone tell me how I can fix it as I love random encounters.

From what I could read, You got a couple of things going on.

In my experience, KM is very sensitive to added modded scripts. Using Random Battles with Galaxy Chart's Random defense force (RDF) caused a conflict. Use or activate one of the other, not both. If you favor the Random Battles, then GC's (RDF) mutator should not be selected.

The DJEnterprise G has a bugged MVAM launching script. When you tried to integrate the ship, that caused a cascade crash. Try using this...

DJEnterpriseGMVAM

Code: [Select]

### Okay, Chances are if you're reading this then you're interested in making an MVAM ship. So I will lay out what to do
### in some easy steps. Good luck, and remember to be patient and read thoroughly :)

### 1) First off, you need ships. Sorry, but I don't have the ability to split up an existing ship for you, so you'll
###    either have to make them yourself or have someone else do it. You will need the full (combined) ship plus the
###    seperated models.
#
### 2) You may want to adjust the hardpoints to each of the ship files. Remember that if one subsystem name equals the
###    subsystem name on the combined ship, then it's damage amount will be transfered to the other. If you,
###    for example, don't want the shields status of the combined ship to be transfered over to the seperated ship, you
###    just simply name it something other then what it's called on the combined ship.
#
### 3) Now you need a plugin file. Copy one of the plugin files that came with the Mvam Infinite (either GalaxyMvam.py or
###    PrometheusMvam.py) and paste it into the same directory as you copied it from(scripts/Custom/Autoload/Mvam). Rename
###    your new plugin file to whatever you want (I suggest: ShipnameMvam.py). Please don't overwrite anyone's mod, or my
###    own... also keep in mind that you NEVER put anything but the plugin file into the scripts/Custom/Autoload/Mvam
###    directory.
#
### 4) Modify the plugin file for your ships. Change only the lines below a "###TO CHANGE:". Always keep names in order
###    (IE: combined ship, seperated ship #1, seperated ship #2, seperated ship #3, etc).
#
### 5) Package all the files needed into a zip file, keeping things in the proper directory's. Remember to include the
###    plugin file, ship models, ship hardpoints, misc sound files you used, and anything else. DON'T include ANY
###    of the Mvam Infinite files (which means you shouldn't modify them AT ALL). I may want to release patches to this
###    if needed later on, and i don't want to have to contend with alternate versions floating around. If you want
###    something changed, email me at sneaker98@hotmail.com and let me know about what you would like modified). Also,
###    if you require assistance with the plugin or anything else, email me and I'll see what I can do.
#
### Readme Note: If you don't credit me in your readme, I will take action. You are modifying the code that I created in
###              my own spare time. This literally took months to get working and I don't expect to be overlooked. Also,
###              notify the users that they require the Mvam Infinite in order for your mod plugin to work.
#
### Final Note: Eventually, I may make a pretty GUI for all this... still not sure if I'll ever get the time.

#required import. Don't touch this...
import App


###TO CHANGE: what ships are in this? start with the full ship, then the ones that seperate
MvamShips = ["DJEnterpriseG", "DJEnterpriseGSaucer", "DJEnterpriseGDrive", "DJEnterpriseGThunderbird"]


#this is to make things less confusing... don't touch this!
MvamDirections = []
MvamDistances = []
MvamReinDirections = []
MvamReinDistances = []
for i in range (len(MvamShips) - 1):
	MvamDirections.append(App.TGPoint3())
	MvamDistances.append(App.TGPoint3())
	MvamReinDirections.append(App.TGPoint3())
	MvamReinDistances.append(App.TGPoint3())


###TO CHANGE: these are all the buttons used. Keep them in the order that you named them first (ie: saucer sep for the
############# saucer, then stardrive, etc). Note: For the reintegration button, make sure you have "$Rein" at the VERY
############# end, so I know what it is. Dont worry, that part wont show in game.
IconNames = ["Saucer Detatchment", "Stardrive Detatchment", "Aux Thunderbird Detatch", "Reintegrate$Rein"]


###TO CHANGE: This is the hardest part. You need to find the offset of the new ship models as opposed to the
############# original integrated model. Using MPE greatly assists in this, you can use it to compare a point on the
############# combined model to a point on the seperated one. Use PrometheusMvam.py to give you an idea of how this
############# works, as the MvamGalaxy models were positioned all around the same central point entirely for the purpose
############# of seperating (doing this isn't recommended as it makes ships turn very oddly). So this is what you do:
############# 1) Open up two instances of MPE. One for the combined ship, and the other to see a seperated ship.
#############    REMEMBER: MPE's model scale needs to be set to 0.01. To check this, go to Edit -> Options. The model
#############    scale is shown in the third text box.
############# 2) You need to pick a point that you can see on both the combined ship and the seperated ship. For
#############    example, I used the top of the bridge on the prometheus to find the offset for the saucer section, since
#############    I can clearly see it on both models
############# 3) For each XYZ point you're given after selecting the point on both ships, subtract the value on the
#############    combined ship from the value on the seperated ship. IE: If you're given (3.5, 4.0, 4.1) on the
#############    combined ship and (2.0, 2.5, 2.3) on the seperated ship, you'd do: 3.5 - 2.0 for the X, 4.0 - 2.5 for
#############    the Y, and 4.1 - 2.3 for the Z.
############# 4) Repeat for each seperated ship, using a different point each time of course. Remember to record the
#############    results of your calculations and put them below. Be as accurate as possible, as you can see I have done.
MvamDistances[0].SetXYZ(0.0, 0.828989, 0.144821)
MvamDistances[1].SetXYZ(0.0, -0.503057, 0.053076)
MvamDistances[2].SetXYZ(0.0, -0.512189, -0.20303)


###TO CHANGE: This is the direction you want the seperated ship to go during the seperation sequence. It's all X, Y, Z.
############# Remember, its in the order you name them. 0 = the first ship, 1 = the second ship, etc etc. Now, the first
############# number is to the left (so a negative number would send a ship to the right.. you get the idea), the second
############# number is to go forward, and the last number is to go up. So a 0.0, 1.0, 1.0 would send a ship on a heading
############# of forward and up, or about a positive 45 degree pitch (i use the word pitch lightly, it doesnt twist or turn
############# the model whatsoever, it's just the direction it moves)
MvamDirections[0].SetXYZ(0.0, 1.0, 0.0)
MvamDirections[1].SetXYZ(0.0, 1.0, -0.25)
MvamDirections[2].SetXYZ(0.0, 1.0, -0.5)


###TO CHANGE: This is the speed you want each ship to go. 1.0 is about 600 km/h on the speed display ingame for the
############# prometheus. Remember, its in the same order as the ships.. ie [ship1, ship2, ship3, ship4]
MvamSpeeds = [0.8, 0.8, 0.8]


###TO CHANGE: This is the reintegrating distance. Basically, this where each ship starts off at the beginning
############# of the reintegration custscene. I found the values for the Prometheus models by doing the following, NOTE,
############# You need to have the seperation sequence working properly to get this to work properly as well:
############# 1) Get the XYZ world location of the seperated ships before they start moving. Use the "PreSeperate" def
#############    below to get these values. The following bits of code can get you started:
#############    Get a ship by name: pShip1 = App.ShipClass_GetObject (pSet, "DJEnterpriseGSaucer")
#############    Print location: print 'X=', pShip1.GetWorldLocation().GetX(), 'Y=', pShip1.GetWorldLocation().GetY(), etc
############# 2) Get the world location of the seperated ships AFTER they've done the cutscene. Use the "PostSeperate" def
#############    below to get these XYZ values.
############# 3) Go ingame and perform the seperation sequence so that the XYZ values of step 1 and 2 are output to the
#############    console. Write down these values.
############# 4) Subtract the XYZ values you got in the second step from the XYZ values you got in the first. Write down
#############    the numbers you get as a result.
############# 5) Flip the sign (+/-) of the new value's Y number. Ie: If you got Y=4.56345, it's now Y=-4.56345.
############# 6) Add these new XYZ values (there were 3 sets of them for the prometheus) to the values in MvamDistances.
#############    This is because you want the ship to reintegrate to the spot it would be on the combined ship. Write down
#############    the result of this calculation into the variables below, keeping the order of the ships like you should
#############    have been doing throughout this plugin.
MvamReinDistances[0].SetXYZ(0.0, 3.0, 2.95)
MvamReinDistances[1].SetXYZ(0.0, -0.05, 1.35)
MvamReinDistances[2].SetXYZ(0.0, 4.9, 0.05)


###TO CHANGE: This is the reintegration heading. If you used the 6 step guide in MvamReinDistances, you would simply
############# take the value in MvamDirections two steps above; switch the +/- sign on the Z value for each; and put it
############# in the appropriate spot below. Remember to keep the proper order of the ships.
MvamReinDirections[0].SetXYZ(0.0, 1.0, 0.0)
MvamReinDirections[1].SetXYZ(0.0, 1.0, 0.25)
MvamReinDirections[2].SetXYZ(0.0, 1.0, 0.5)


###TO CHANGE: This is how fast each ship is going during the reintegration sequence. If you used the 6 step guide in
############# MvamReinDistances, you simple use the same speed values you used in MvamSpeeds three steps above.
MvamReinSpeeds = [0.8, 0.8, 0.8]


###TO CHANGE: this is the name of your music! It's the file in sfx/music. REMEMBER to include this file in your plugin if
############# you've used your own.
MusicName = "DJEnterpriseG"


###TO CHANGE: this is the name of the seperating sound. it's the file in sfx/Explosions. REMEMBER to include this file
############# if it's different then what I have. Leave blank ("") if you don't want a sound
SoundName = "MvamPromSfx"


###TO CHANGE: this is the name of the bridge sound during seperation. it's the file in sfx/. REMEMBER to include this
############# file too, if you decide to have one. Leave blank ("") if you don't want a sound
BridgeSoundName = "MvamPromBridge"


###TO CHANGE: this is the sound when the ships reintegrate. I allowed two different sounds just in case, and keep in mind
############# that the file for this is in sfx/Explosions. REMEMBER to include this file too, if you decide to have one.
############# Leave blank ("") if you don't want a sound.
ReinSoundName = "MvamPromReinSfx"


###TO CHANGE: this is the name of the bridge sound during reintegration. it's the file in sfx/. REMEMBER to include this
############# file too, if you decide to have one. Leave blank ("") if you don't want a sound
BridgeReinSoundName = "MvamPromBridgeRein"


###TO CHANGE: this is the name of the ai you want to use. Unless you want it doing something REAL special, use what i have.
############# Remember to include the ai file if you use something different then what i have. For reference, the MvamAI
############# is just a basic attack plus collision avoidance. IF you make your own AI (and want computer controlled
############# ships to seperate as well), then base it on the MvamAI so it'll go through certain scripts that detect when
############# the ai ship should seperate
MvamAiName = "Custom.Sneaker.Mvam.MvamAI"


###TO CHANGE: if you want your integrated ship to have the ability to seperate when it's under computer control, set it
############# to 1. If not, set it to 0.
AiSepAbility = 1


###TO CHANGE: name the following def's EXACTLY what the seperated mvam ships are called. You need to have as many def's
############# as you have ships seperating (we aren't counting the integrated ship).
def DJEnterpriseGSaucer(pObject, pEvent):


	# get the player
	pGame = App.Game_GetCurrentGame()
	pPlayer = pGame.GetPlayer()
	snkMvamModule = __import__ (__name__)
	# check if its our full ship
	if (pPlayer.GetScript() == "ships." + snkMvamModule.ReturnMvamShips()[0]):
		import Custom.Sneaker.Mvam.Seperation


###TO CHANGE: change the last word in quotes in the next line to the name of the def. (ie: "MvamGalaxySaucer")
		Custom.Sneaker.Mvam.Seperation.Seperation(snkMvamModule, "DJEnterpriseGSaucer")


	pObject.CallNextHandler(pEvent)


###TO CHANGE: dont forget to change this name too.
def DJEnterpriseGDrive(pObject, pEvent):


	# get the base variables
	pGame = App.Game_GetCurrentGame()
	pPlayer = pGame.GetPlayer()
	snkMvamModule = __import__ (__name__)
	# check if its our full ship
	if (pPlayer.GetScript() == "ships." + snkMvamModule.ReturnMvamShips()[0]):
		import Custom.Sneaker.Mvam.Seperation


###TO CHANGE: change the last word in quotes in the next line to the name of the def
		Custom.Sneaker.Mvam.Seperation.Seperation(snkMvamModule, "DJEnterpriseGDrive")


	pObject.CallNextHandler(pEvent)


###TO CHANGE: dont forget to change this name too.
def DJEnterpriseGThunderbird(pObject, pEvent):


	# get the base variables
	pGame = App.Game_GetCurrentGame()
	pPlayer = pGame.GetPlayer()
	snkMvamModule = __import__ (__name__)
	# check if its our full ship
	if (pPlayer.GetScript() == "ships." + snkMvamModule.ReturnMvamShips()[0]):
		import Custom.Sneaker.Mvam.Seperation


###TO CHANGE: change the last word in quotes in the next line to the name of the def
		Custom.Sneaker.Mvam.Seperation.Seperation(snkMvamModule, "DJEnterpriseGThunderbird")


	pObject.CallNextHandler(pEvent)


###OPTIONAL CHANGE: This is the reintegrate sequence. You really don't need to touch this
def Reintegrate(pObject, pEvent):
	#get the base variables
	pGame = App.Game_GetCurrentGame()
	pPlayer = pGame.GetPlayer()
	pSet = pPlayer.GetContainingSet()
	snkMvamModule = __import__ (__name__)
	#check to see if all the ships are still around in the set. start a counter
	intCounter = 0
	for i in range((len(snkMvamModule.ReturnMvamShips())) - 1):
		if (App.ShipClass_GetObject(pSet, snkMvamModule.ReturnMvamShips()[i + 1]) == None):
			#make sure we're not skipping the player ship
			if (pPlayer.GetScript() != "ships." + snkMvamModule.ReturnMvamShips()[i + 1]):
				#NOW it's bad. something isnt right, so notify the counter
				intCounter = intCounter + 1
	#alright, if this is a legit reintegrate, intCounter will equal 0
	if (intCounter == 0):
		import Custom.Sneaker.Mvam.Reintegration
		Custom.Sneaker.Mvam.Reintegration.Reintegration(snkMvamModule)
	pObject.CallNextHandler(pEvent)


###OPTIONAL CHANGE: If you set AiSepAbility to equal 1 then you might want to have a specific condition on when the AI
################### seperates. Returning 1 means it seperates, returning 0 means it doesn't.
def CheckSeperate (pShip):
	#grab base values for use later
	pGame = App.Game_GetCurrentGame()
	pEpisode = pGame.GetCurrentEpisode()
	pMission = pEpisode.GetCurrentMission()
	pSet = pShip.GetContainingSet()
	pEnemies = pMission.GetEnemyGroup()
	pFriendlies = pMission.GetFriendlyGroup()
	snkAiRanSep = App.g_kSystemWrapper.GetRandomNumber(5)

	#is the ship an enemy?
	if (pEnemies.IsNameInGroup(pShip.GetName())):
		#seperate if we're outnumbered 3 to 1
		if ((pFriendlies.GetNumActiveObjects() >= (pEnemies.GetNumActiveObjects() * 3)) and (snkAiRanSep == 4)):
			return 1
		#seperate if 50% damaged and outnumbered 2 to 1
		if ((pShip.GetHull().GetConditionPercentage() <= 0.5) and (pFriendlies.GetNumActiveObjects() >= (pEnemies.GetNumActiveObjects() * 2)) and (snkAiRanSep == 4)):
			return 1
	#the ship is a friendly or neutral
	else:
		#seperate if we're outnumbered 3 to 1
		if (pEnemies.GetNumActiveObjects() >= (pFriendlies.GetNumActiveObjects() * 3) and (snkAiRanSep == 4)):
			return 1
		#seperate if 50% damaged and outnumbered 2 to 1
		if ((pShip.GetHull().GetConditionPercentage() <= 0.5) and (pEnemies.GetNumActiveObjects() >= (pFriendlies.GetNumActiveObjects() * 2)) and (snkAiRanSep == 4)):
			return 1
	return 0


###OPTIONAL CHANGE: The next four def's are for before and after both the seperation and reintegration sequences,
################### respectively. I really can't think of what someone would want to do with them as of this second, but
################### it's my job to keep it as dynamic as possible. Oh, The def names say where each one is called,
################### really. ALWAYS return 0. If you don't want the AI to use the changes, you might want to have a check
################### for it (eg: if (pPlayer.GetName() == "Player"): )

#pShip is the integrated ship just before ANYTHING is done
def PreScripts(pAction, pShip):
	#these are the base values... very useful. they are commented out since I dont use them right now
	#pGame = App.Game_GetCurrentGame()
	#pEpisode = pGame.GetCurrentEpisode()
	#pMission = pEpisode.GetCurrentMission()
	#pSet = pShip.GetContainingSet()

	return 0


#pShip is the seperated ship just before the seperation cutscene
def PreSeperate(pAction, pShip):
	#these are the base values... very useful. they are commented out since I dont need them right now
	#pGame = App.Game_GetCurrentGame()
	#pEpisode = pGame.GetCurrentEpisode()
	#pMission = pEpisode.GetCurrentMission()
	#pSet = pShip.GetContainingSet()

	return 0

#pShip is the seperated ship just after the seperation cutscene
def PostSeperate(pAction, pShip):
	#these are the base values... very useful. they are commented out since I dont need them right now
	#pGame = App.Game_GetCurrentGame()
	#pEpisode = pGame.GetCurrentEpisode()
	#pMission = pEpisode.GetCurrentMission()
	#pSet = pShip.GetContainingSet()

	return 0

#pShip is the seperated ship just before the reintegration cutscene
def PreReintegrate(pAction, pShip):
	#these are the base values... very useful. they are commented out since I dont need them right now
	#pGame = App.Game_GetCurrentGame()
	#pEpisode = pGame.GetCurrentEpisode()
	#pMission = pEpisode.GetCurrentMission()
	#pSet = pShip.GetContainingSet()

	return 0

#pShip is integrated ship just after the reintegration cutscene
def PostReintegrate(pAction, pShip):
	#these are the base values... very useful. they are commented out since I dont need them right now
	#pGame = App.Game_GetCurrentGame()
	#pEpisode = pGame.GetCurrentEpisode()
	#pMission = pEpisode.GetCurrentMission()
	#pSet = pShip.GetContainingSet()

	return 0


###OPTIONAL CHANGE: I REALLY don't recommend modifying the following, they are for the cutscene. VERY touchy... I
################### can with all honesty say that I don't know for sure what they all do. Changing one changes the others
################### and it just gets so damned complicated. I used the warp-in camera position with a few modifications.
################### The best advice I can give is to try to think of the values as a "range" in which the camera could be.
################### The more of a "range" you have, the less likely you'll get a repeated camera movement.

def ReturnCameraValues ():
	#this is as far as I can tell mostly useless
	AwayDistance1 = -1.0
	AwayDistance2 = 100000.0

	#this is the true viewing distance from the ship. probably the most useful. Also, it controls which SIDE of the
	#ship you're going to view. As far as I can tell, it looks like: if both numbers are negative, it's going to view
	#from behind; and if both numbers are positive it'll view from the front
	ForwardOffset = 4.0
	SideOffset = 4.0

	#NOTE: The next two sets of numbers need the lowest value on the top and the highest on the bottom.
	###### The game WILL freeze if you do this wrong, trust me.
	#something to do with where the camera rotates around the ship (horizontal values... more or less)
	RangeAngle1 = 130.0
	RangeAngle2 = 410.0

	#looks to be how far the camera can go up and down while "rotating" around the ship (vertical values... more or less)
	RangeAngle3 = -45.0
	RangeAngle4 = 45.0

	return [AwayDistance1, ForwardOffset, SideOffset, RangeAngle1, RangeAngle2, RangeAngle3, RangeAngle4, AwayDistance2]

###OPTIONAL CHANGE: How long would you like the seperation cutscene to play? Remember, 1.0 is about a half a second
def ReturnCameraSepLength ():
	return 7.0

###OPTIONAL CHANGE: How long would you like the reintegration cutscene to play? Remember that changing this value will
################### affect how your ships come together in the reintegration cutscene, since they aren't timed to exactly
################### how long the cutscene plays.
def ReturnCameraReinLength ():
	return 7.0


### DON'T TOUCH ANYTHING PAST HERE. THEY RETURN VALUES TO THE MVAM PROGRAM. MODIFY AT YOUR OWN RISK ###
def LoadDynamicMusic ():
	#load in the sound
	import DynamicMusic
	App.g_kMusicManager.LoadMusic("sfx/Music/" + MusicName + ".mp3", MusicName, 2.0)
	DynamicMusic.dsMusicTypes[MusicName] = MusicName
	return
def ReturnMvamShips ():
	return MvamShips
def ReturnMvamDirections ():
	return MvamDirections
def ReturnMvamDistances ():
	return MvamDistances
def ReturnMvamSpeeds ():
	return MvamSpeeds
def ReturnMvamReinDirections ():
	return MvamReinDirections
def ReturnMvamReinDistances ():
	return MvamReinDistances
def ReturnMvamReinSpeeds ():
	return MvamReinSpeeds
def ReturnMusicName ():
	return MusicName
def ReturnSoundName ():
	return SoundName
def ReturnBridgeSoundName ():
	return BridgeSoundName
def ReturnReinSoundName ():
	return ReinSoundName
def ReturnBridgeReinSoundName ():
	return BridgeReinSoundName
def ReturnMvamAiName ():
	return MvamAiName
def ReturnAiSepAbility ():
	return AiSepAbility
def ReturnIconNames ():
	return IconNames
def ReturnModuleName ():
	return __name__

King Class Scout · « **Reply #4 on:** December 02, 2018, 05:25:02 AM »

hmm, some things to note, there. think I've had similar problems with some of DJ's other MVAM capable ships.

"Galaxy charts" is notoriously twitchy. as for eras, you have to literally make an era plugin for yourself. SFRD was working on a separate Race Def for use with TOS ships.

Zippy91 · « **Reply #5 on:** December 02, 2018, 06:39:02 AM »

Okay this has helped my head somewhat!

Funny thing is that I think the Enterprise G came with KM as I didn't install that ship myself, I'm not interested in that ship!

In fact, is there a way I can just take this ship out as I'm not interested in the Enterprise G?

Seems crazy that something that comes with the KM mod also causes it to crash!

Zippy91 · « **Reply #6 on:** December 02, 2018, 06:40:10 AM »

Quote from: King Class Scout on December 02, 2018, 05:25:02 AM

hmm, some things to note, there. think I've had similar problems with some of DJ's other MVAM capable ships.

"Galaxy charts" is notoriously twitchy. as for eras, you have to literally make an era plugin for yourself. SFRD was working on a separate Race Def for use with TOS ships.

Is there a tutorial or a guide into making an era plugin?

King Class Scout · « **Reply #7 on:** December 02, 2018, 05:26:46 PM »

go over the paperwork that comes with galaxy charts, as I think there's a howto in there. I'll have a look myself, as I'm not sure after just getting back into it after 6 years idle.

Blackrook32 · « **Reply #8 on:** December 03, 2018, 12:02:12 PM »

Quote from: Zippy91 on December 02, 2018, 06:39:02 AM

Okay this has helped my head somewhat!

Funny thing is that I think the Enterprise G came with KM as I didn't install that ship myself, I'm not interested in that ship!

In fact, is there a way I can just take this ship out as I'm not interested in the Enterprise G?

Seems crazy that something that comes with the KM mod also causes it to crash!

The problem with the Enterprise-G, by using Galaxy Chart's Random defense force (RDF) it will choose any allied ship in your install. Since the Enterprise-G had a buggy MVAM file, that what caused the crash; when the AI tried to use the function.

Deleting the 1701-G is up to you.

Also, on the Galaxy Charts Era's selection, that was always in beta; meaning, it was automatically set for the TNG era. You could not have changed to another era, even if you tried.

Zippy91 · « **Reply #9 on:** December 03, 2018, 02:19:14 PM »

In that case then is it worth to "rebuild" my mod collection from the ground up instead of using KM? Just adding mods and ships that I like?

If so, how can I get the "Automatic Test Mode" from Kobayashi Maru as I am a big fan of the Edit mode and like making screenshots out of it.

Morgan · « **Reply #10 on:** December 04, 2018, 12:25:15 AM »

Quote from: Zippy91 on December 03, 2018, 02:19:14 PM

In that case then is it worth to "rebuild" my mod collection from the ground up instead of using KM? Just adding mods and ships that I like?

That's purely at your discretion. Most people use KM because it's an "all-in-one" deal and you don't have to deal with knowing which order mods need to be installed, what scripts work with what, etc. If you do go with your own install, you'll want to make sure you do the major mods in the following order:

1.) BC clean install

2.) BC 1.1 Patch

3.) Foundation

4.) NanoFX 2

5.) Core Ejection

6.) MVAM

7.) QB Autostart

8.) Bridge Plugin

9.) Galaxy Charts

10.) DS9FX

11.) Delta Quadrant Pack

From there you can install ships, bridges, solar systems, and QB AutoStart scripts in any order you choose (unless of course their readme's say otherwise). I also recommend a console tracker that will automatically dump BC's console into a text file, so that way you have an easy way to locate potential problems.

You should still be able to get into Edit Mode by just doing edit() in the console if I'm not mistaken, but I can count on one hand the number of times I've used it so someone correct me if I'm wrong. I'm not sure about Automatic Test Mode - frankly I don't even know what it does so I never gave it much thought.

King Class Scout · « **Reply #11 on:** December 04, 2018, 06:44:29 AM »

there's a mutator switch for automatic test mode. it adds a line to the game's shortcut and enables some stuff along with Console Commands. the game gains a God Mode (which I use for weapons testing, more often than not), among other things.

I agree with adding the DQP, which I have separately. I've had some trouble, though, with galaxy charts conking stuff out like the blinkers on some ships. still trying to figure out which of my ships is calling for a couple nonexistent torpedo scripts (which can cause a cascade lockup with my error reporting/logging script)

and, yes, edit() mode is how we got new systems with SFRD. unfortunately, tiq never passed on more than how to activate it before HE passed on.

Zippy91 · « **Reply #12 on:** December 04, 2018, 11:43:05 AM »

This is great stuff!! Thank you for that, I'm rebuilding my game following this as we speak, only one problem so far and that's to do with the DQP mod, only place I can find it is a site called lonebullet and the zip file only includes the credits and nothing else.

Blackrook32 · « **Reply #13 on:** December 10, 2018, 02:54:12 PM »

Quote from: Zippy91 on December 04, 2018, 11:43:05 AM

This is great stuff!! Thank you for that, I'm rebuilding my game following this as we speak, only one problem so far and that's to do with the DQP mod, only place I can find it is a site called lonebullet and the zip file only includes the credits and nothing else.

The FULL DQP mod is in our BCC archives.

* JL Studios Delta Quadrant Pack v.1.0:
http://www.bc-central.net/forums/index.php?action=downloads;sa=view;down=31

News:

Author Topic: Bridge Commander crashes (Read 1082 times)

Zippy91

Bridge Commander crashes

Zippy91

Re: Bridge Commander crashes

Zippy91

Re: Bridge Commander crashes

Blackrook32

Re: Bridge Commander crashes

King Class Scout

Re: Bridge Commander crashes

Zippy91

Re: Bridge Commander crashes

Zippy91

Re: Bridge Commander crashes

King Class Scout

Re: Bridge Commander crashes

Blackrook32

Re: Bridge Commander crashes

Zippy91

Re: Bridge Commander crashes

Morgan

Re: Bridge Commander crashes

King Class Scout

Re: Bridge Commander crashes

Zippy91

Re: Bridge Commander crashes

Blackrook32

Re: Bridge Commander crashes