Problem with Captain April's Canon Nemesis Enterprise and Valdore HP pack

[GreatBarrier86]

Cool. I dont understand why no one else has reported this problem.

[Captain_April]

well, maybe its an issue with the torpedo...maybe I'll try dling that ship, and see if that creates the same issue.

well, I installed the PDW Excelsior, it does use the same torpedoes, but the tracking on them is much less than that of my Sovereign, just from using them ingame, but I do like it a lot (the torps, not the ship...I'll take a Sov or Defiant or Intrepid or Connie any day before an excelsior).  anyway, about the sounds, no changes whatsoever...I do not know how your problem was created...maybe something else uses it?

I dont understand why no one else has reported this problem.

Neither do I.  Maybe if we had a more complete list of the MODS you've installed, expand the search.

[Kirk]

Just for the record, sounds can be defined to many names (ex, Lint's defiant defines 1 sound with 3 different names) so the same sound can be used for different weapons without problems.

[GreatBarrier86]

Ok. This install has the following on it.

KM 1.0
DS9FX
PDW Excelsior
DJ Galaxy Pack
Cap April's hardpoint pack.

--Installed in that order too

That's it.

[Kirk]

Alright, I am going to make that install on my computer (I hope you patched BC before you installed KM though.)

Edit: Which variants/patches of April's hps?

Edit 2: Why isn't this in Tech Support?

Edit 3: Why did you install ds9fx over KM 1.0? Ds9fx is in KM 1.0, and I can only think of a few things that I would actually want from ds9fx in KM 1.0 and it wouldn't require a full install of ds9fx, only picking out the necessary files.

Edit 4: So far, the PDW excelsior quantums work fine. I have not yet install the hp fixes as you have not told me which ones.

[GreatBarrier86]

1. I did install the patch first. I forgot to mention it.
2. Bc this is a mod problem. Not a game problem.
3. Good question....lol. Guess i didnt think of it .
4. The only hardpoint fixes i am talking about is the patch is this http://bridgecommander.filefront.com/file/Canon_Nemesis_Enterprise_and_Valdore_patch;92816

[Kirk]

So you only installed the patch?

[GreatBarrier86]

For the hardpoint?

I installed the two links in my original message,

[Kirk]

Ah, now I see. Ok, I will download those and test them.

Edit: Was able to recreate problem, now looking for solution.

[GreatBarrier86]

Oh thank god someone was able to

YAY!!

[Captain_April]

Just for the record, sounds can be defined to many names (ex, Lint's defiant defines 1 sound with 3 different names) so the same sound can be used for different weapons without problems.

I am well aware of that, you just assign a sound identity to a variable, the game can't tell that they're the same sound, but back on topic:

GreatBarrier86: Oh thank god someone was able to

YAY!!

Exactly how if feel :hurr

[ACES_HIGH]

2. Bc this is a mod problem. Not a game problem.

This is the description for the Tech Support Forum:

BC Technical Support
You can find help on Mod installation issues, problems with BC installations and settings, program errors, and general computer problems related to BC here.

[GreatBarrier86]

2. Bc this is a mod problem. Not a game problem.

This is the description for the Tech Support Forum:

BC Technical Support
You can find help on Mod installation issues, problems with BC installations and settings, program errors, and general computer problems related to BC here.

Please review the following. http://bc-central.net/forums/index.php/topic,4304.0.html

The last post in the thread states that since it is a mod problem and not a game problem, it is "fine in this forum."

While it is not the same issue, the fact that these are both modding issues would suggest that perhaps this is an appropriate forum for this discussion.


So kirk, any news??????

[Starforce2]

In my opinion, this is still a form of debugging. Since you installed a mod and didn't have sounds working, which is what I gather from the first posts of this thread, it should be moved to tech support, so that's where it is going.

[Kirk]

No news yet, I haven't had a chance to look it over.

[MLeo]

That thread about Max, not related to BC, except that you could make models for BC in it, but that's only a small, unrelated feature (didn't even see it either).

So this thread, which is about a problem with a mod, ought to have been here in Tech Support.

Anyway, on to the real problem...
Missing sounds in general usually means a faulty encode, BC is kinda picky (tough it depends on the sound settings, EAX or not, most people don't have EAX).

Missing sounds on torpedo/pulse launch usually mean a missing sound, or a faulty sound plugin, or a wrong sound name used in the projectile.


In this case it's a wrong sound name (or missing Sound plugin), put this in scripts/Custom/Autoload

[Kirk]

Wrong torpedo MLeo, that would fix a problem with the photons, but it is the quantums that have an issue. I've gone over the projectile files, the hp, and the sound def and can't find a problem. I also looked at the encoding of the sound file itself and nothing stood out at me as being blatantly wrong. If applicable, how did you (April) encode the file?

Edit: Re-encoding the file to a known usable format did not fix it. I must be missing something in the scripts.

Edit 2: Found the fracking problem! BC has no problems with you defining a sound file with 2 names, but when you define two sounds, even the same sounds, but in different files, to the same name, neither will play. KM already defined this sound and adding another sound def for the sound, with the same name, only fracked things up. Delete scripts\Custom\Autoload\RapidQuantum_sound_def.py and .pyc and you should be all set.

[MLeo]

Actually, they ought to overwrite eachother (when it comes to Foundation).

But it might be a BC mechanic that does this.


[EDIT] Still, there was a missing sound definition!

[GreatBarrier86]

I deleted that py and pyc file and it worked. SWEET...YAY

Thanks guys.

So for us laymen, what was the problem?

[Kirk]

Problem was that two exact same sound definitions canceled each other out, why, I don't know.