dreadx

I did have 1 radiation incident in the first day of playing (Kendrick was in medbay at the time and not radiated). After that, no more. So I don't think radiation is causing this. Could he have a trauma from the time Engineering got invaded by intruders and he got shot? Nav-computer and Bridge are not a problem when down to 50% but comlink lets you loose Fleet C&C!

quote: Originally posted by SC: Solutions are for problems. I see NO problems. OK, so Kendrick is not a problem. Can I just call him a "Pain in the @ss" then? And while we 're at it. Can we compare Kendricks DNA with that of Resnig?

Yes, all the artifacts are on board. I suspect it started around the time that the special cargo items came into play but I'm not sure cause that was a long time ago.

LOL, that's uncle Douglas Adams at his best (hm, except for the spermwhale maybe) As for SC's question. Yes, I speak a little bit French because they forced me to learn it for 4 years in school. Was never any good at it though.

My ships name is in dutch and it is a polite greeting (like goodday). It's also the dutch name for the morningstar (wooden stick with chain attached and a very spiky ball on the end) Guess it's irony

Ready to support and serve, sir! Sir, number One, sir!

So there's no real solution? The CE needs his "on-station" time to build up AI. Well, let's hope the CE quits degrading systems (first com and after a couple of days he took interest in the bridge in my case) once his AI is high enough (Kendrick is at 81% now but I'm still hoping) I'm trusting in JAC to do the realy important repairs. Hmm, seems that putting all SE's in the medibay also does the trick. As long as Kendrick hasn't somebody around to do the repairs he stops fiddeling, being afraid that he has to pick up the toolbox himself. [ 07-05-2003, 05:37 PM: Message edited by: dreadx ]

Check for diplomats in the sector you're in. If they enter your sector and then get whacked by merc's, you get the blame (and -5000 ep).

PerTrak? Isn't that the system in the operationsroom, between Mr Coffee and the machine that does "ping"? You know, the one that Resnig should operate when dispatching "his" marines.He did confiscate the manual, but we all know he can't read it.

LOL especially about the spelling and the "head in the sand"

I will modify as I go by using this threat as a sig test. I dropped the "War is not about who is right, but about who is left" in favor of "It's the propellant charge that makes a bullet lethal" because the latter has more Balor spirit.

Ready to support and serve, sir! Pugwash's maps are better and easier to understand than some maps I've come across in the military. Never mind the nice S-curves, the maps don't need them. Great job.

As for the repairs. I've experienced that when the estimated repair time is less then 1 minute the system-engineer will work exactly 0 minutes on that system (no repair). Don't know if this still holds up after installing the patch though. And don't worry about the 99%. The system is just as good and it adds character to your ship.

I did my homework already (reading the Insurgents home-pages) and have decided that I would like to be a part of the Balor fleet. What's next?

I also apologize for intruding into this roll call, but I would like to join this fleet. Could someone please point me in the right direction?

yes, experienced the slow down to turtle-speed more than once, especially when there are a lot of white missile markers in my TACSCAN! I just ride it out and wonder if I feel lucky enough to go downstaires, refill my coffee-cup and be back in the driverseat before the gamespeed returns to normal. This behaviour leads to two things: 1. Coffee spillage from my kitchen to my pc. 2. The first thing you see when walking through the door is the last thing you see of your beautifull CC. I now learned the aprox amount of white dots I "need" in my tacscan before I can have a descend coffee-refilling-moment.

LOL. Talkin about volatile mixtures!! Both before and after you drink it.

Here, here.

Hi there, I see you are fighting the internal battle. Each time there is a system-failure we must find some-one to blaim it on. Generally, Kendrick is to blame, cause he must make sure that every system is at 100% all the time. Well, if you wouldn't use your CC. You would have no systemfailures. If your flight-officer would know as much of the bridge-systems as Kendrick, he wouldn't press the wrong buttons and blow up fuses (causing it to go to 50%). But seriously. I've worked on board of a Royal Dutch Frigat as DWEO (Deputy Weapons Engineering Officer) for 3,5 years and had roughly the same job as Kendrick. I know the ins and outs of systems breaking down and repairing them. No matter how much you know of your systems there's always something you dont know. Murphy's Law! So far, I think the damage done to the CC is pretty accurate. We had a Autopilot which, for no perticular reason, went hard to port. Once in a while. Although it still worked, it wasn't an ideal situation (Autopilot 50%) especially when sailing close to other ships. We checked the complete system, couldn't find anything wrong, did some minor repairs (which had nothing to do with the steering order) and reported the system back at 100%. 30 hours later, the autopilot went hard port again. (fault still present: Autopilot 50%). After checking everything again and replacing some choice components, the system worked once again like a charm. Autopilot 100%. After a week, the same problem occured!! Now what? To cut a long story short. During major overhaul there were modifications to the bridge-panel. A few extra holes had to be drilled. The metal shavings, from drilling that holes, fell down into a connectionbox and would (under very special circumstances) cause a circuit to short out. This resulted in a logical "1" in one of the lines and the computer interpurted this as "hard to port". What I want to say is: Each minute your systems work is a good minute. But faillure is only one minute away. Don't get irritated, repair as best you can and get on with the fight. A damaged system adds character to your vessel!

Starstations shoot at missiles. I've witnessed this when I pointed my mkIII at an incomming target. Both the station and and the enemy-cruiser were in my bridgeviewer. I switched to TacOps and saw the cruiser being pounded by the starstation. Shields and half his hull gone, he finally emerged from hyperspace and launched a missile at the station. All the turrets of the station targetted the missile (5000 hull) and were ripping it to bits while it closed the distance (it still found its target, though). The cruiser (at +/- 1300 hull) was no longer receiving any damage. It bought itself time to launch more missile and continue its attack (and was "save" doing so as long as there was at least one missile between him and the station). Now, I don't know about you but I would not like my turrets to behave in this way. I already have EMD and Cloaking to deal with incomming missiles and I need my turrets to deal with the missile-platform before it can launch more "I don't like you-messages with a hot tail".

It's a old threat but I couldn't resist to add some comments. On sound in space. There is "sound" in space! If you are close to an exploding spacecraft, you will see an expanding cloud of debris. These particles (like dust) will have a significant speed (and are not slowed down in vacuum), but are not fast or energetic enough to trigger the shields. When the particles slam into your hull by the trillions, they create small shockwaves through your ship. Your hull starts vibrating and part of that vibration is transferred to the air inside your ship. In there, the sudden particle-hailstorm will sound like an explosion or a short thunderclap. On newtonian physics: They do not apply at high speeds. On gravity: It's just another field-force we have yet to master. If we haven't found out how it works by 3000AD. We never will.