I see we've been officially annexed into shipyards.
Sweet acceptance.
You might be happy to hear that with any Kirin that has the OSE Combat Computers installed, her turrets will at least try to shoot down missiles of all sorts automagically - from auto-locking on them to firing
Curious about the first Kirin versus Juggernaut battle ...
L
(Who might, when own meta-oxp is finally done, well buy himself one of the bigcargoed plus multiturreted Kirin's)
slow but deadly accurate (as accurate as the Dragon or Neo-caduceus).
Excuse the question, sir, what does it means "deadly accurate" ? That it shots always in the center of the crosshair ? Or that it lets you do very small position change in order to get the target exactly where the laser will hit ?
And could this technology be transferred to such a tin can like a TIE fighter ?
Thank you in advance.
Cmdr. Saint, Golden Gladstone with 4 leaves Clovers of the Most Noble Order or The B.D.c.
As Wyvern informed me after I'd build the first (and as it turned out) fairly flawed) Caduceus. Hence the reason why the neo-caduceus is the oxp to get.
Aligning the exit point of the laser (plist) with the model (dat) and with the player view point (plist) radically enhances the accuracy of a ships weapons.
For optimum accuracy a ship model should be centred in xyz. That way when you set the view point and the laser exit point (at 0 y and eather 0z (for side lasers) and 0x for front and back) there's nothing to interfere with the angle at which the laser appears to be firing.
Basically your setting everything up directly down the line ship, laser and sight.
Technically it could be done for any ship but your lasers might end up coming out in a weird place and not necessarily where you may want them. Hence the reason the kirins lasers are mounted "high". It's worth having the accuracy, and it's just a creative challenge to adapt the texture to account for this.
You might be happy to hear that with any Kirin that has the OSE Combat Computers installed, her turrets will at least try to shoot down missiles of all sorts automagically - from auto-locking on them to firing
Because of my woefully low-spec, ancient computer, OSE bogs down framerates to the point that the sim is technically unplayable. As you put it on another thread,
Also OSE really needs at least a 2+GHz dualcore and 3+GB RAM system to run properly!
Not doable, unless a rich uncle dies or I somehow win a lottery. There's this curse called a recession going on, and I have higher priorities than a new box right now. So no OSE for this space ace.
There's a lot of oxps that I ultimately had to ditch, Assassins being one of them.
That said, the combo of target autolock, missile analyzer, bounty scanner and AMS + missile sniping turrets in trunk offers the same function as your combat computer. The only thing missing is an autofire of the ECM, which would be cool to have.
Last edited by Cmdr Wyvern on Wed Aug 05, 2009 3:05 am, edited 1 time in total.
Running Oolite buttery smooth & rock stable w/ tons of eyecandy oxps on:
ASUS Prime X370-A
Ryzen 5 1500X
16GB DDR4 3200MHZ
128GB NVMe M.2 SSD (Boot drive)
1TB Hybrid HDD (For software and games)
EVGA GTX-1070 SC
1080P Samsung large screen monitor
Cmdr Wyvern, when OSE is done and I find the time, I might just do a separate CombatComputers.oxp ... and perhaps also a PlayerStations.oxp for those who don't want to or can't play full OSE.
I have been asked for this already, so why not. Or perhaps, if someone else took out these functions and made a separate oxp of them - that would be even better
Meanwhile, in the wiki's OXP_List page, the 'Kirin' entry shows as 'Y' in the compatibility column.
Would one of the Wiki Gods wish to step up and fix that ?
And while I'm here... just read this forum thread and its sibling for 'Kirin Sport' (the 'Sport' is correctly labeled as 'Problematic' within 'OXP_List'). From the little I could understand there, the issues of both OXPs have to do with shaders mgm't. While I might have figured this out completely wrong, I'd like to ask anyway...:
Since I'm playing Oolite only in a lowly netbook which does NOT allow 'Shader Effects', would that mean that the bugs in either OXP would not bother to bite me ? Or would it be that the issues go deeper than that ?
Of course, I could just try either one and see for myself... but really hope some kind soul would step in and save me from a possible dead-end setup and experimentation.
From the little I could understand there, the issues of both OXPs have to do with shaders mgm't. While I might have figured this out completely wrong, I'd like to ask anyway...:
Since I'm playing Oolite only in a lowly netbook which does NOT allow 'Shader Effects', would that mean that the bugs in either OXP would not bother to bite me ? Or would it be that the issues go deeper than that ?
Of course, I could just try either one and see for myself... but really hope some kind soul would step in and save me from a possible dead-end setup and experimentation.
Well, they don't give me any trouble on this cruddy old IBM x40 (i855GM has all the 3d capabilities of a one-eye goose with glaucoma), which is as shader-free as your setup.
Well, they don't give me any trouble on this cruddy old IBM x40 (i855GM has all the 3d capabilities of a one-eye goose with glaucoma), which is as shader-free as your setup.
Consider that an endorsement, I suppose.
Thx fronclynne, that's good news. On this side there's an Asus EEE 901 w/ GMA950.
I'll be adding one of the Kirin OXPs soon then, and try a branching story from my current Caduceus saga. I like these overpowered beasts... some sort of subconscious compensation I guess.
[offtopic]
Oh, and since we're at it - just tried the DeepspaceShips OXPs. I was a bit cautious, since someone said they'd eat up a bit more CPU cycles... I didn't notice any significant increase in CPU percentage or heat, and it does add very nice textures to most ships. I can swear it also generally 'beautified' the game screens overall, although I can't really pinpoint any objective differences.
If you haven't tried it yet, might be a good addition to your in-game experience.
<EDIT>*
