[Wanderer]

Hmm. i had some problems with that c20050520.zip, it loaded all fine and the weapons loadout looked very good but:
 - Vasudan vessels used old thruster effects
 - Vasudan afterburner trail thingyes didn't start where they should have
 - Multipart turrets didn't bother to turn (with Stratcoms Sparta) if turrets even fired at all.

I moved back to old 3.6.5 build and all these problems disappeared.

BTW. How can i stop the reciting in the Tech Room?

[StratComm]

You mean Microsoft Sam?  In the launcher, go to the "voice" tab and deactivate the simulated voice in the techroom.

[WMCoolmon]

Unfortunately, p4 builds have started to CTD for me, so I can't test it out.

Can you describe unselectable? I haven't touched the pilot screen or code at all in awhile, certainly not in the time between these two builds.

[Mongoose]

At least for me, the "undetectability" meant that my pilot didn't appear at all on the selection screen.  It was as though it didn't exist, even though the pilot files were still in the correct folder.  This was as of the 4/15 P4 build.

[Solatar]

You can press enter and it'll let you pass, though if you try to go into the mission simulator there are no missions present. Crashing ensues.

[Mongoose]

I've just been trying to play Fall of Epsilon Pegasi with the 4/20 build, and I receive a CTD whenever the first mission starts loading.  I was able to load the second mission, so I restarted the campaign to see if that would resolve things; now I can't even play it.  I've also experienced crashes in other missions, both when the mission is loading and upon hitting "Commit" (that one required a Ctrl+Alt+Del).  I don't know if it's related to the new mv_music.vp you released or not, although I do know that it seemed to crash at different points depending on whether or not I used the mod folder (the one I was using  contained the FS2 cutscenes and Fall of Epsilon Pegasi files; the SCP VPs are in the main FS2 folder).

[WMCoolmon]

Do debug builds clear anything up?

[WMCoolmon]

Okay, new build. Originally wasn't going to post it, but since I have the EXEs compiled and spent several hours tonight poking through the code, I figured I'd post it.

Umm:
- Made engine washes dynamically allocated
- Unnoticeably faster engine wash indexing
- Unnoticeably faster image drawing
- Figured out an easy fix for that lab problem people have been complaining about.
- Minor fix to lab window caption code, as well as some changes to make less chance of skinning bugs arising (Mainly forcing all top-level objects to have different names, although I need to add checking at every level)
- Fixed spelling of "mulitplicative" in armor.tbl
- Minor changes throughout the code to prepare to get rid of the ships.tbl limits
- Disabled parsing of $Player Ship Precedence, since nothing else in the code references it.
- Updated code to latest CVS code, so turrets should be working now (according to phreak)

http://fs2source.warpcore.org/exes/latest/C20050423.zip

Mostly I'm interested in the reliability factor of this build - does it crash more?

Added to the website.//redmenace

[KyJelly]

Got this when trying to run the P4 verion of 4/23 build:

Error: trying to set invalid bitmap as render target
File:.\graphics\grd3dbmpman.cpp
Line: 652

Call stack:
------------------------------------------------------------------
------------------------------------------------------------------
 regular version does not give this

[WMCoolmon]

When/where?

[KyJelly]

when loading the game from the launcher. the screen goes black then i hear a low pitch beep then it crashes with that error.

[Mongoose]

This latest build helped solve a problem that's been bugging me for the last week or so.  I loaded up a mission with it, and just like the past few builds have, it crashed around the third loading bar.  I had had problems related to not hearing music in-mission in a recent build, with or without the mv_music.vp.  When I started using your recent update to this VP, that's when the crashes started.  I had tried removing the VP file earlier, but I still experienced crashes; this time, when I got rid of it, the build ran fine, and I could still here the original low-quality music in-mission.  Looks like the problem is related to that VP file, not the builds.

I did experience one trivial problem with this build; the cursor is distorted, and a strange orange box appears around it.  This only happens in OGL; it still works fine in D3D.  Here's a screenshot:



Obviously, this isn't a big issue, but it does look weird. If it helps, I'm using a Radeon X300 with what I believe are the 4.12 Catalyst drivers.

P.S.  Good work on the lab; it's nice to finally be able to see all of the ship classes.

[StratComm]

I have already mantised this, sort of.  That's where it goes though, moreso than here anyway.

[Cobra]

hey, wmc, where's the new table?

[WMCoolmon]

If you're talking about armor.tbl, look on the first page of this thread, I posted an example there. I still haven't gotten around to completely testing it, although I do know it seems to parse with my current codebase.

[Cobra]

i thought you updated the table when you updated the build. sorry.

[Mongoose]

Originally posted by StratComm
I have already mantised this, sort of.  That's where it goes though, moreso than here anyway.

I just Mantised it myself.  I figured it was high time to get over my apprehension at using it.

[FireCrack]

I dont mean to pry, but artent the armour indexies a tad redundant. Wouldnt

Code: [Select]

#Armor Type
$Name: Happy Armor factors
$Type: multiplicative
;;This means that all values in the table will be the product of the damage times the number entered

;;Lasers Projectiles Fireballs Missiles
$0: (0.2 1.0 1.3 1.0 ) ;;Mirror armor
$1: (1.2 0.5 1.5 1.0 ) ;;Hardened armor
#End


#Armor Type
$Name: Happy Armor bonuses
$Type: additive
;;This means that all values in the table will be added to the damage entered

;;Lasers Projectiles Fireballs Missiles
$0: (-20.0 0.0 0.0 10.0 ) ;;Mirror armor
$1: (0.0 0.0 0.0 0.0 ) ;;Hardened armor
#End


Ships.tbl

Code: [Select]


$Name: MirrorShip
...
$Armor Type: Happy Armor factors   ;;Factor things first
$Armor Type: Happy Armor bonuses ;;Then add the bonuses (so bonuses will not be scaled)
$Armor Index: 0 ;;Use the mirror armor row

$Name: HardenedShip
...
$Armor Type: Happy Armor factors   ;;Factor things first
$Armor Type: Happy Armor bonuses ;;Then add the bonuses (so bonuses will not be scaled)
$Armor Index: 1 ;;Use the hardened armor row



be the same as

Code: [Select]

#Armor Type
$Name: Happy Armor factors
$Type: multiplicative
;;This means that all values in the table will be the product of the damage times the number entered

;;Lasers Projectiles Fireballs Missiles
$0: (0.2 1.0 1.3 1.0 ) ;;Mirror armor
#End


#Armor Type
$Name: Happy Armor bonuses
$Type: additive
;;This means that all values in the table will be added to the damage entered

;;Lasers Projectiles Fireballs Missiles
$0: (-20.0 0.0 0.0 10.0 ) ;;Mirror armor
#End


#Armor Type
$Name: Happy Armor hardened factors
$Type: multiplicative
;;This means that all values in the table will be the product of the damage times the number entered

;;Lasers Projectiles Fireballs Missiles
$0: (1.2 0.5 1.5 1.0 ) ;;Hardened armor
#End


#Armor Type
$Name: Happy Armor hardened bonuses
$Type: additive
;;This means that all values in the table will be added to the damage entered

;;Lasers Projectiles Fireballs Missiles
$0: (0.0 0.0 0.0 0.0 ) ;;Hardened armor
#End


Ships.tbl

Code: [Select]


$Name: MirrorShip
...
$Armor Type: Happy Armor factors   ;;Factor things first
$Armor Type: Happy Armor bonuses ;;Then add the bonuses (so bonuses will not be scaled)
$Armor Index: 0 ;;Use the mirror armor row

$Name: HardenedShip
...
$Armor Type: Happy Armor hardened  factors ;;Factor things first
$Armor Type: Happy Armor hardened bonuses ;;Then add the bonuses (so bonuses will not be scaled)
$Armor Index: 0 ;;Use the hardened armor row

[WMCoolmon]

Yeah, but if you want the same type of damage for all weapons it's a bit more convenient.

That way may be a bit easier for people to understand though.

[FireCrack]

Hmm, i just had a n idea somthing along the lines of this...

If you cant tell each subarmour acts in the original armour in the order they are listed so youds only need to reference one armour in ships. Usefull for complex armour types.

Code: [Select]

#Armor Type
$Name: Happy Armor factors
$Subarmour: multiplicative
;;This means that all values in the table will be the product of the damage times the number entered

;;Lasers Projectiles Fireballs Missiles
$0: (0.2 1.0 1.3 1.0 ) ;;Mirror armor

$Subarmour: additive
;;This means that all values in the table will be added to the damage entered

;;Lasers Projectiles Fireballs Missiles
$0: (-20.0 0.0 0.0 10.0 ) ;;Mirror armor

#End