![]() Auxiliaries do not, and they also don't have many pads either so they will take a while to launch. I don't know if the raptor has those because it has the massive grid of launch pads, but other ships should. The "point" allegedly of carriers is that they have launch tubes, which allows them to poo poo out their entire fighter complement very quickly, though they still take ages to recover them. It is a powerful visual metaphor for my posting. I don't see why you wouldn't just take a handful of auxiliaries instead for repair/rearm and let your fighters run on their own instead of directly attaching them to any capitals. Carriers are so slow and their autonomous fleet behavior so fiddly that they just drag things down without adding any value in my experience.Įven the raptor with its absurd 90+ medium turrets is kind of eh in direct combat because the AI doesn't do a great job bringing all of those guns to bear against stations and other capital ships. In fact it's easier to manage their behavior if they aren't. If it's your fighters actually doing the killing it doesn't necessarily matter if they're attached to a carrier or not. And after you get a wharf they are super easy to outfit.Īnd strangely they don't take that many losses.ĭepends on what you mean precisely. There are a ton of little deficiencies in fleet AI both in and out of sector that make the experience rough and clunky.īut carrier gently caress things up much better than anything else. Now, if patches are available and merged into 2.6.34 - why isn't (un)docking simply working / fully supported in the latest version of Natty (which to my humble understanding has surpassed kernel version 2.6.The real annoyance comes if you find yourself having to babysit a capital ship and its 10's of fighter craft while you're trying to work on something elsewhere. May be more then one, such as on a ThinkPad X40 with ThinkPad X4 Dock. This is due to the ACPI dock drivers only registering theįirst logical Dock port they encounter and in some rare cases there In some cases you may not get any events on ![]() There are some issues though: No event on undock. You can monitor this by running # udevadm monitor and when you dock or press the undock button you should see a flurry of events. With recent distributions, docking and undocking should function out of the box. seconds, indicating that the system itself hasn't "crashed" but is still (somewhat ?) The screen goes blank (with backlight remaining on), ![]() when pressing the blue undock button on the docking station: IBM Thinkpad X41 & docking station > no joy :-(. And the lights on the dock never change to indicate it Pressing the undock button on a " ThinkPad X4 Dock" with a ThinkPad X40 does notĬause any udev events. I don't want to tinker around with bash scripts if avoidable. I've read briefly about hal and udev, and can imagine that they are somewhat related to this, see links below. This issue is VERY important to me and I would be MOST grateful to anyone being able to sieve through the following links (some of which are actually quite recent) and translate their meaning into reliable and concrete simple (?) steps. ![]() Given that it still doesn't work (effective April 2012), my hope is fading that it will start working all of a sudden with Precise Pangolin at the end of the month. I'd like to start using my docking station again however, it still doesn't work as it should, see the following bug descriptions (with special focus on Thinkpad X41 & the X4 Dock).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |