Hard Light Productions Forums
Hosted Projects - Standalone => The Babylon Project => Topic started by: dragon1 on August 22, 2005, 01:44:16 pm
-
Hi All!
I just downloaded version 3.2. Excellent update.
Just three quick questions...
1) The Drakh cruiser doesn't fire its main guns on custom missions, only the AAA guns. Are they switched off? Is there a way to activate them?
2) The Shadow battlecrab turret subsystem seems a little weak. Is there a way to beef it up or make the turret invulnerable to damage? Its pretty bad when one Sharlin can take out two Shadow ships.
3) The B5 station received a weapons upgrade during season 2, does anyone know what weapons should go into which hardpoints for the upgrade? I remember Ivonova mentioning pulse cannons and mine launchers but not much else.
Thanks for all of your hard work and effort.
-
The Drakh cruiser should fire all weapons:wtf:
The shadows problem will be address in the next release.
-
Yes, the Dk Cruiser doesn't fire it's main cannons, although the AAA neutrons work fine... :confused:
I pitted it against other ships, ordered to attack them: beam-free-all and nothing...
it was destroyed as it didn't use the main cannons... :wtf:
-
I`m not tring to be funny but.
I pitted the Drakh cruiser against the Dilgar cruiser (Drakh ordered to attack only).. Beam free all to both ships and the Drakh cruiser made mincemeat out of the Dilgar cruiser...
In the event editor I set beam free all to ( has time elapsed ) I set the time to 2 seconds..
I don`t know if the value will make a difference in the initial orders, I set this to 89.
Hope this will shead some light on your problem. :)
(edit)
Oh and :welcome:
-
I have now tried the manual event editor and the default beam-free-all switch in the mission editor. Still no go on the Drakh heavy guns. Also changing the target priority to 89 was unsuccessful. Any other thoughts?
-
Well if those beams don't fire then they don't fire. There's nothing much you can do with just FRED.
Ofcourse you could use the fire beam operator, but theres no reason for it to work when beam-free-all doesn't.
Seems like the model is somehow, you know, screwed... :sigh:
-
What scp build are you using?
-
I've fiddled with the DK Cruiser a bit, and, to me it seems as if it does fire it's main weaponry. At least, when one is against two Brakiri Avoiki classes, a Sharlin, an Omega and a Hyperion it is capable of damaging most of them, almost killing both Aviokis and (sometimes) killed one of them. It usually destroys the Hyperion cruiser too.
I havn't noticed a problem. Doesn't mean there isn't one, but, I have seen the DK cruiser fire, what I presume is it's main anti-cap beams.
Unless the blue ones are the anti-fighter ones... And, if so, they're pretty tough for anti-fighter beams... :p
-
My cruiser fires its main cannons aswell as all the others.
(http://www.3dactionplanet.com/hlp/hosted/babylon/gallery/d_firing.jpg)
-
Okay, I was wrong. The model is fine.
Seems like something else is somehow, you know, screwed up. :wtf:
See if there is any beams assigned in the main turrets. And try to change to another beam weapon to see if that works.
And then there is the remote chance of corrupt file of somekind in somewhere and sometime etc.
-
1) I dunno. Maybe the ship you're trying to fire at is protected or beam-protected or too small to be targetted by the main beams. Maybe it's a one off FRED screw up that'll magically get fixed if you rebuild the mission from scratch.
2) Yes the Battlecrab's mouth is too weak. It might be fixed in the beta test new tables in the beta testing forum.
3) http://www.babtech-onthe.net/b5/ . You may or may not find weapons in the core that match those configurations. It's probably easier to wait for us to produce a new model with the S2 defence grid.
-
There must be something wrong with the Dk Cruisers main neutron guns (the ones on the turrets without -base)...:sigh:
They don't fire when beam freed...
I've tried several times using beam-free-all
at the mission specs, as well as beam freeing in the events editor...:doubt:
And using the fire beam event caused a CTD...:doubt:
I've put DK Cruiser against a Sekhmet, which is a large ship. The ships were facing each other a distance 6km...
Even when they were flying around each other only the AAA neutrons were fired at the Deathwalkers and me
( :p I was invulnerable).
The ships were positioned at the same "altitude"...
I tried adding other weapons to those turrets...
but... no effect...:eek2:
Pulse weapons as well as Mimbari neutrons didn't fire...:doubt:
Every other capship I tested that way fired it's weapons normally, without any troubles... :wtf:
What can cause something like that?!:confused:
-
Uhm... most capital ship beam weapons have range of 4500-5500 meters. Placing a ship more than 5500 meters away makes it effectively out of range. I encountered no problems whatsoever when I tweaked those drakh beams for 3.3 beta.
-
And if they're circling one another then the enemy ship is out of the Drakh Cruiser's main beam firing arc. Put the enemy ship 3k away from the Drakh Cruiser. Give both ships stand still orders to face one another. See what happens.
-
Originally posted by aipz
I tried adding other weapons to those turrets...
but... no effect...:eek2:
Pulse weapons as well as Mimbari neutrons didn't fire...:doubt:
Every other capship I tested that way fired it's weapons normally, without any troubles... :wtf:
What can cause something like that?!:confused:
I strongly suspect that the ships .pof might be corrupt somehow. You should try replacing it. Someone could perhaps send it to you, I cant since I'm still at work. It's not a big file so it shouldn't be a problem...
Just to be safe, try to equip the Drakh beam in to some other ship. That way we can make sure that it is model problem, and not table related...
-
Ordering the ships to stand still and placing them 3 km from each other didn't solve anything...:doubt:
The Sekhmet shot but Dk Cruiser did nothing... :doubt:
Previously, as I tested, the ships flew 2-4 km at collisiion course and should fire their main weaponry without any troubles...
So it wasn't definetly the case with running in circles...;)
I've put the Drakh heavy neutrons on the Sekhmet instead its X-rays and they fired normally so it's definetly not the issue with weapons themselves...:) :doubt:
EDIT: Forcing Dk Cruiser to fire using fire beam event always causes CTD!
The FRED didn't show any errors and I checked if the event is correctly filled...:doubt:
-
Originally posted by aipz
What can cause something like that?!:confused:
Which build are you using ? The one that came with TBP, or one out of the "Recent builds" SCP forum ?
-
D:\Games\The Babylon Project\fs2_open_r.exe -spec -glow -nomotiondebris -2d_poof -nobeampierce -dualscanlines -ship_choice_3d -targetinfo -orbradar -3dwarp -tbpwarpeffects -snd_preload -ambient_factor 60
The build included in 3.2 release, nothing else...
-
I just switched the Drakh guns to the Sharlin and they worked fine. It must be the DK Cruiser not the weapons themselves. I seem to be having the same problem as aipz.
-
Then the problem is almost certainly in the model... Or what say our shipbuilders?
Trying a new .pof would be worthwhile... Placing it in the data\models directory should do it. As I understand the game uses it over the one in the .vp file...
Unfortunatley I don't have that file handy. I don't have TBP installed currently 'cos I just reinstalled Windows, and I won't be installing TBP 'cos I will be installing new Windows in a day or two... :shaking:
-
You could try deleting the dkcruiser.ibx in your \data\cache folder, so it will create a new ibx file from the pof.
-
Originally posted by Col. Fishguts
You could try deleting the dkcruiser.ibx in your \data\cache folder, so it will create a new ibx file from the pof.
Just tried that. Still a no go.
-
i have this problem as well, think i posted a while back, i have never got the main beams to fire, even when i tried replacing the weapon with something else even a none-beam weapon, i am using the build that came with 3.2. So i think i somehow must have a bit of a corrupt download, but i dnt want to redownload the whole base file it for one model, because i can't get broadband where i live, so i will wait for the nxt release.
-
Just like Dragon said... it also didn't work for me...The ibx file didn't had any effect...:sigh:
-
Ok download my Drakh cruiser pof and place it in your data/models folder,if you havn't got those folders, create it. I know this works,if it doesn't then you must try another scp build as some of them had issues with beam weapons,some fired,some didn't.
Drakh Cruiser (http://home.austarnet.com.au/sigma958/drakhcruiser.pof)
-
Hmmm, It seems i`ve been using an inferno build that works fine, but when I tried the fs2open_r build that came with the release the game crashed on the mission loading screen.. I won`t go as far to say its just the build causing the problem, but it may be a little of both the model and the build... Everything else seems to works fine with the install build..
I`m going to extract the Drakh cruiser from the vp and take a closer look at it.
Could it be the FOV on the main beam turrets is to narrow?
I`m thinking the FOV has no bearing, but i`ll try anything once. But that wouldn`t make the game crash, to my knollage.
(edit) Ok FOV on turrets 01a and 02a is 40 and 60 on the rest of the single part turrets. 40 is a little narrow, but it would still fire.. And the B5 team had good reasons for setting it at that value, probably to keep it from firing through it self, thats good enough reason for me :nod:
-
If you're trying new builds delete your .ibx files from the cache folder just to be on the safe side. Also as Sigma said, certain builds did have issues firing beams. It took us quite a while to find a good build to release with 3.2. Well actually karajorma found it :D
-
Thanks Sigma, download tht pof, seems to of sorted my problems it now fires YAY!!
-
?
Really!?
Wow that was wierd.
-
Ahhh...Help!!!
I downloaded the Dkcruiser.pof and put it into Data/Models (I created a new directory for 'models'). Now when I open FRED and try to access the model, the program crashes with;
[AppName: fred2_open_r.exe AppVer: 1.0.0.1 ModName: fred2_open_r.exe ModVer: 1.0.0.1 Offset: 001048b3]
Sorry about being such a pain in the ass.
-
No no IP... That's weird :wtf:
Went too complex now... I may know all about FRED, but when those error messages come up with all the numbers I lose touch with my conscious mind...
-
Does FRED work if you remove the model again? What if you delete the relevent IPX too?
-
FRED works once the model is gone. I tried deleting the IPX file. Still a no go. The old model is still there, but with the persisting problem.
-
Still no go...:doubt:
Deleting the Ibx also didn't help...
I didn't have any troubles with FRED after I extracted the model to data/models...;)
For me nothing has changed...:doubt:
Really weird issue...:wtf:
-
I deleted the new POF file and re-downloaded it.
Now FRED works again, but the damn DK Cruiser just won't fire. I am where aipz is at again.
-
Hey aipz if you're not careful you'll deplete HLP's supply of smileys.
They'r a depletable resource you know... :dizzy:
-
Don't worry never used them all...;)
I wanted only to add a bit of expression to my posts...:nervous:
EDIT Guess I'll just wait to TBP 3.3, as my knowledge to solve such problem is limited...
-
Well I'm clean out of ideas aswell.:confused:
-
I just tried again and found something interesting. The hardpoints on the DK Cruiser tend to flicker when the ship comes into range to fire. I don't know what this means, but perhaps others have seen this.
-
That's a clipping problem. Not relevant to the problem at hand. Nor can it be fixed in it's own right.
-
What Build are the people using, for whom the Drakh Cruiser works fine?
-
I'm using Taylors build 20050807 and it works fine.
-
I just downloaded v.3.3 from the website. How do I find out what 'build' I am using?
-
In the launcher, at the top next to the browse button. The bit after the final \
-
Try the newest build posted by Sigma957
it worked for me it's 20050828
-
Ok, stupid question, but where do I download the newest build from?
-
duh, never mind!
I just found it.