s.orbis.zone
Sure, one can make almost any build work in PVE.Yeah, don't worry too much about it.
I think the power priorities don't get exported correctly from Inara, I haven't set the priorities in game like they are shown in Coriolis. I've had that issue with EDSY in the past, too. I didn't bother to check the priorities when exporting last night.
The way I traditionally organize my power groups is like this: I distribute the core functions across 1 and 2. 1 is always the thrusters and FSD, 2 is often the rest. 3 is everything deployeable and / or needed in combat, 4 is all things shields, and 5 is all the stuff I don't need in normal space or only need in SC. It's fine and works for me.
See above.
it works fine and doesn't matter. Edit: If anything, I might be most susceptable to the argument that a C5 Bi-Weave works as well with the added benefit of upping the cargo capacity.
First, I don't have prismatics, so there's that. Second, ramming is my (in this case) 7th hardpoint, so I've made my peace with always going for optimum raw strength and absolute protection vs. protection through resistances. It's fine either way, and my way helps with the ramming hardpoint. And again, in PvE it doesn't matter, above a certain threshold a ship like this is unkillable either way unless you aggro a whole instance of a dozen or more ships, changing this or that to optimize is basically "funny number goes up (or down)". I don't do PvP, but I am very sure this build is gank proof as in: Fast and robust enough to escape.
Appreciated.
Well not to backpedal to much, but it's pretty gank proof for your average ganker (who is usually pretty bad). For organized dedicated ones in a group, maybe probably not so much. I have a similarly built/protected but slower Viper IV that escaped the odd gank with no problem.
well my Mandalay isn't a dedicated combat ship, much less so for PvP. If it was it wouldn't have cargo, a scoop, collectors, or a vehicle hangar. It's an armed multirole mission runner, and such a ship will never be proof against the most dedicated PVPer or murder hobo (or both).I understand. When I am in a combat ship, I fight even against uneven odds. I simply want to practice, I don't care if I die.
But I don't want to give gankers the satisfaction, even though rebuys are inconsequential
I’m also running a 6C BiWeave (Reinforced and Fast Charge) and am not seeing any issues with the 5A Charge Enhanced PD … I pretty much fly with 2-pips in everything and it all just seems to work …Yeah, don't worry too much about it.
I think the power priorities don't get exported correctly from Inara, I haven't set the priorities in game like they are shown in Coriolis. I've had that issue with EDSY in the past, too. I didn't bother to check the priorities when exporting last night.
The way I traditionally organize my power groups is like this: I distribute the core functions across 1 and 2. 1 is always the thrusters and FSD, 2 is often the rest. 3 is everything deployeable and / or needed in combat, 4 is all things shields, and 5 is all the stuff I don't need in normal space or only need in SC. It's fine and works for me.
See above.
it works fine and doesn't matter. Edit: If anything, I might be most susceptable to the argument that a C5 Bi-Weave works as well with the added benefit of upping the cargo capacity
First, I don't have prismatics, so there's that. Second, ramming is my (in this case) 7th hardpoint, so I've made my peace with always going for optimum raw strength and absolute protection vs. protection through resistances. It's fine either way, and my way helps with the ramming hardpoint. And again, in PvE it doesn't matter, above a certain threshold a ship like this is unkillable either way unless you aggro a whole instance of a dozen or more ships, changing this or that to optimize is basically "funny number goes up (or down)". I don't do PvP, but I am very sure this build is gank proof as in: Fast and robust enough to escape.
Appreciated.
I’m out on an exobio shakedown trip and very happy with the 5D G3 Dirty ones I’m running. It’s way faster than my DBX so need to be aware of how much throttle you give it when you’re down low.
s.orbis.zone
Exploration build focused on self-sufficiency. No downgrade on thrusters but running with a size 3 power distributor and an overcharged size 4 powerplant.
Carries 2 SRVs, AFMU, repair limpet controller and a reinforced size 3 shield generator. Range is at 75ly unladen.
Coriolis EDCD Edition
A ship builder, outfitting and comparison tool for Elite Dangerous
I hate switching the vehicle bay on and off all the time, so I didn't bother with that. So that's very much on purpose. Since I'm exploring with my carrier around most of the time, I was actually thinking about taking only one SRV though.
I hate switching the vehicle bay on and off all the time, so I didn't bother with that. So that's very much on purpose. Since I'm exploring with my carrier around most of the time, I was actually thinking about taking only one SRV though.
Thanks for the distributor hint! I'll try and see how much of a difference it makes. Not sure why I didn't have that idea myself.
Yeah.
Yeah.
Also tried the distributor in coriolis. about 0.10ly more. I think I won't make that engineering tour anytime soon.
Yeah, I know, but that's still not what I want. Things need to be functional and not switch off under certain circumstances. The difference would be about 0.4ly and that's also not worth it in my book. I need my ship to be robust and functional somehow.
If you put the vehicle hanger at priority 4 or 5 it will shutdown automatically and power itself back on when you are landed and the thrusters are powered off.I hate switching the vehicle bay on and off all the time, so I didn't bother with that. So that's very much on purpose. Since I'm exploring with my carrier around most of the time, I was actually thinking about taking only one SRV though.
Thanks for the distributor hint! I'll try and see how much of a difference it makes. Not sure why I didn't have that idea myself.
That was already suggested and my answer is right above your post.
