Core mining bug?

Urbanski101

Urbanski101
I had a very weird episode core mining just now.

Seismic charges were exploding on contact with the asteroid even when aimed right at the fissure, then when it did work and the charge attached even placing a minimum charge on a high fissure would push the explosion meter all the way into the red.

I was in a wing so would that cause those sorts of problems?

I've done a lot of core mining so I do know how it works and this felt very off / bugged. I've had to log for now but I will try again later.

I won't raise it as a bug until I've had the chance to replicate it or had feedback on here that it's a known issue or I'm going mad....

Thanks
 

Northpin

Northpin
Urbanski101 said:
I had a very weird episode core mining just now.

Seismic charges were exploding on contact with the asteroid even when aimed right at the fissure, then when it did work and the charge attached even placing a minimum charge on a high fissure would push the explosion meter all the way into the red.

I was in a wing so would that cause those sorts of problems?

I've done a lot of core mining so I do know how it works and this felt very off / bugged. I've had to log for now but I will try again later.

I won't raise it as a bug until I've had the chance to replicate it or had feedback on here that it's a known issue or I'm going mad....

Thanks
Click to expand...

Yea, there are issues with wing mining
IIRC, To work around them, the one that fired the prospector has to place the charges
 

Urbanski101

Urbanski101
Northpin said:
Yea, there are issues with wing mining
IIRC, To work around them, the one that fired the prospector has to place the charges
Click to expand...
Thanks, though we were mining independently of each other some 50km apart but in a wing so I was placing the prospector and the charges...weird bug.
 

GraphiteGB

GraphiteGB
Northpin said:
oh well... my bad then...

but then, why bother with wing mining?
Click to expand...
It was giving a temp boost to the output of the prospectors when winged ...
Don't know if this exploit stilll works that way but using a fighter bay did the same in the past as the rocks items spawned from the mining was based in how many allied ships were in the instance mining...
 

Urbanski101

Urbanski101
GraphiteGB said:
It was giving a temp boost to the output of the prospectors when winged ...
Don't know if this exploit stilll works that way but using a fighter bay did the same in the past as the rocks items spawned from the mining was based in how many allied ships were in the instance mining...
Click to expand...
As I don't wing up very often I've never heard of this and running an exploit was the furthest thing from our minds, we just wanted to get a session of gaming in ED together. However the number of bugs present now means we have an ever shrinking pool of things we can actually do. Can't mine together, can't run missions together (or at all as it turns out)...next time I don't think we'll bother with a wing or indeed with ED...probably just play something else.
 

Ian Doncaster

Ian Doncaster
Urbanski101 said:
So it seems I can't confirm the bug on the tracker as even when I'm logged in it won't let me leave a comment on a bug report....bug tracker is bugged....I just can't....words fail me.
Click to expand...
There's a sometimes-hidden 30-character minimum on both the message and the reproduction details when confirming a bug.

You also need to ensure that Javascript is sufficiently enabled to allow not just Javascript for the bug tracker itself but also recaptcha to load.

You also may want to clear temporary files if you've previously browsed the tracker as I've been seeing weird caching behaviour on the bug tracker since last weekend's update to it.

If you haven't recently sacrificed a chicken, next full moon is in about 8 days.

Certain semi-common punctuation characters like '#', ';' or '<' are not allowed in messages. It should tell you if you use one, but sticking to numbers, letters and spaces for safety may help.
 

Bigmaec

Bigmaec
Ian Doncaster said:
There's a sometimes-hidden 30-character minimum on both the message and the reproduction details when confirming a bug.

You also need to ensure that Javascript is sufficiently enabled to allow not just Javascript for the bug tracker itself but also recaptcha to load.

You also may want to clear temporary files if you've previously browsed the tracker as I've been seeing weird caching behaviour on the bug tracker since last weekend's update to it.

If you haven't recently sacrificed a chicken, next full moon is in about 8 days.

Certain semi-common punctuation characters like '#', ';' or '<' are not allowed in messages. It should tell you if you use one, but sticking to numbers, letters and spaces for safety may help.
Click to expand...
Don't forget the dust on the router...
 

Urbanski101

Urbanski101
Ian Doncaster said:
There's a sometimes-hidden 30-character minimum on both the message and the reproduction details when confirming a bug.

You also need to ensure that Javascript is sufficiently enabled to allow not just Javascript for the bug tracker itself but also recaptcha to load.

You also may want to clear temporary files if you've previously browsed the tracker as I've been seeing weird caching behaviour on the bug tracker since last weekend's update to it.

If you haven't recently sacrificed a chicken, next full moon is in about 8 days.

Certain semi-common punctuation characters like '#', ';' or '<' are not allowed in messages. It should tell you if you use one, but sticking to numbers, letters and spaces for safety may help.
Click to expand...
Thanks for the info Ian...very well informed and helpful as ever.

You know what, I'm going to leave it, I've had my fill of FD bugs right now and I think I need to step away from ED before I have a high velocity, blunt object into PC monitor incident. ;)

Cheers
 
You must log in or register to reply here.
Back
Top Bottom