[Nix]

I can verify this even with Blaise's Derelict, with the mission with the gorgon cannon, it never fires.  Any capship with beams refuses to fire on corvettes and other ships.  Antifighter beams work ok but that's it.  
Retail FS2 campaign, same thing, capship beams just dont fire on other large ships

[phatosealpha]

Things I've noticed:

In their finest hour, the Sathanas doesn't fire on the big C.  The collosus, on the other hand, has no trouble at all opening fire on the Ravana that jumps in.

None of the other GTVA ships in the mission use their beams - the two cains do fire theirs, and the lillith is as trigger happy as ever.

[Nuke]

its mostly a matter of beems having a range disperportional to ship size. beam cannons on the back of my 11km long ssj dante cannot hit a ship flying above the forward arms. when looking at a big ship you kinda over estimate the distances between them. pit a ravana and a hecate in a broadside to brodside beam fest at maximum effective beam range, and you couldnt fit any other destroyer between them.

[FireCrack]

^Too bad thered only be one beam firing in that case (i think)

Anyways, in their finest hour i never had any of the GTVA ships but the C use their beams, so is this normal or was i using a fubar build?

[WMCoolmon]

The turrets don't seem to be working properly, still.

[Pnakotus]

In another example of horrible FREDDING, the caps in 'Their Finest Hour' don't use beams.  Because, you know, they're only saving the human race, why worry?  

Say it with me - 'The Freespace campaign is perfect how it is'.  

[FireCrack]

I once saved the colossus and capella by only disabling the beam turret on that lilith, it slid right past the collossus and to the capela star where it presumably interfered with the subspace wave...


Sathanii 43: Danm lilith n00b!!!

[Nuke]

hey, armor makes sence now

[Gregster2k]

Whatever happened to the idea of using an SCP approved standard mission for testing every possible thing........... >_> .....

......we really need to decide on ONE mission that really pushes the SCP's code to the limits in all aspects (graphical, SEXp, everything).........but i digress. I haven't had much trouble (YET) with this build.

For now.

[Nix]

For the past few builds, I've been getting some very strange activity when using Direct 3D.  I'll post these in mantis if you wish.  Put simply, I've described a problem somewhere else where my texture memory would drop to 0, then the game would start to freeze up.  Well, it's now doing the same thing even with a boatload of available texture memory.  I've been using the same exact flags as I have been on previous builds, using a fairly fresh install of FS2, have all my mods seperated into thier own folders, and have a fresh re-installation of my video drivers.

[Trivial Psychic]

Originally posted by redmenace
I got this with TBP 3.2 Beta on startup

Assert: si->data != NULL
File: e:\cvs\fs2_open\code\sound\ds.cpp
Line: 930

Any new developpments on this?  Getting a fully OGG-supportive build that works with TBP is crucial to testing for said team.  This one works with all oggs, but the crashing prevents its effective use.

[redmenace]

yes please fix the tech room bugs and the other issues. I will give you whatever support you need.

[Solatar]

Any chance of a FRED build that won't yell at me for using armor?

[phreak]

Originally posted by WMCoolmon
Well, if I rewrite the turret code, it'll be more neatly coded but probably behave differently and break backwards compatibility.

Although I'm not 100% sure that'd fix it.

The problem is that some turrets acquire targets just fine; others simply don't. I set up a debugger display to show me what all the turrets on a given ship were doing, on two Deimos Corvettes attacking a Hathepsut, none of the turrets were firing.

That being said, maybe it's something related to the big only flag or enemy mask...

i think i fixed the turret problems.  check the aiturret.cpp diffs

http://fs2source.warpcore.org/cgi-bin/cvsweb/cvsweb.cgi/fs2_open/code/ai/aiturret.cpp

[WMCoolmon]

I'll test it when I get the chance.

[phatosealpha]

Please try it out soon.  The beam bug is literally the only thing making me use 3.65 instead of your recent builds, and being able to have proper missile lock-on recticle support at 2048 would be a great boon

[Goober5000]

I don't think the beam bug is related to the turret code, WMC.  I noticed it when playing Derelict before all your stuff got committed.

It happened on several missions, but the most noticeable was one of the last few missions when you're guarding the GTVX Gorgon Cannon.  It fires in 3.6.5, but it stops firing in later builds.  I'm guessing the bug was added very soon after 3.6.5 was released.

[Alpha0]

Would it be possible to determine which is the first released build that carries this bug? If yes, we could at least check CVS changes around the date of bug's introduction and see if it is possible to find out its exact causes.

[Trivial Psychic]

Originally posted by Goober5000
It happened on several missions, but the most noticeable was one of the last few missions when you're guarding the GTVX Gorgon Cannon.  It fires in 3.6.5, but it stops firing in later builds.  I'm guessing the bug was added very soon after 3.6.5 was released.

Ah... so I'm not crazy after-all.

[DaBrain]

I can hardly test TBP with any build... Most of the newer builds just crash.

Looks like I have to get back to build testing.

Perhaps we even need another code freeze until the bug is fixed...