BIG SHOUT OUT
RUTHENIUM and ARSENIC at B1 if anyone is at wp8 now.
Just found zirconium as well.
AND cadmium
This place is a gold mine
I found a cannister of tea, does that help
BIG SHOUT OUT
RUTHENIUM and ARSENIC at B1 if anyone is at wp8 now.
Just found zirconium as well.
AND cadmium
This place is a gold mine
I found a cannister of tea, does that help![]()
I found a cannister of tea, does that help![]()
It's nothing more than a minor irritation to anyone other than long distance explorers so very low priority to the devs. There just might be a fix in the next major release but don't bet on it - and any fix will likely be cancelled out by the new bugs they introduce and haven't noticed because they just don't bother to test anything from an explorer's perspectiveWhat really is getting my goat is the silence from FD on this. We have seen it happen so many times. It's really screwing up our expedition. Why can't they just give us a status report on their findings?
This bug is nasty, completely random, and can happen at any time anywhere without warning
Which will be why it's so difficult to fix. If you couldn't reproduce it slowly driving over the same spot the Frontier developers must be having a real headache with it!
I can't help thinking though that this is related to the bug of ships stopping in mid air near a planet and why they shouldn't ever boost below 2K, and it must somehow be related to there being plenty of other people in the same area. I'm thinking that it might be about the timing of collision detection somehow. Timing errors with parallel processes or threads are the most difficult to track down. Quite often you can try to put in loads of debugging information and because it slows everything down it makes the bug even less likely to happen.
I'm sure it is very hard to track down and properly fix. But it is quite easy to alleviate if there is the will. A simple bit of logic along the lines of "don't allocate more than 50% damage from landscape hits within any one second period" would instantly resolve this issue. Sure, it would mean that idiots who drove off mile high cliffs might not get their just deserts but that's almost certainly the lesser of the two evils (and those idiots would likely have multiple hits over several seconds so would rightly die anyway).Which will be why it's so difficult to fix. If you couldn't reproduce it slowly driving over the same spot the Frontier developers must be having a real headache with it!
I can't help thinking though that this is related to the bug of ships stopping in mid air near a planet and why they shouldn't ever boost below 2K, and it must somehow be related to there being plenty of other people in the same area. I'm thinking that it might be about the timing of collision detection somehow. Timing errors with parallel processes or threads are the most difficult to track down. Quite often you can try to put in loads of debugging information and because it slows everything down it makes the bug even less likely to happen.
I found a cannister of tea, does that help![]()
I am at WP 8 happy to join. Let me know if there is anything I can do to help. I'll be combing the forums to find out how this expedition is going forward. I see there is a private group or two? I had jumped into open as I want to be part of this but I am still wary of drunk players and pirates![]()
- - - - - Additional Content Posted / Auto Merge - - - - -
Shhhhhhhhhhhhhh don't tell the othersI was at +2777, two sys beyond a whole bunch of tagged sys and there was no other way up ; but i didn't take the time to search all the area for a higher reachable system n_n' Well, I guess I'll have to check that one, and come back once I have J3 too
Keep me updated on your new record!
It says "Where are you? We need to receive or confirm some distances from the system you are right now." and then there's a text box where I can enter...something. But what? I figure I need to enter some distances to some systems, but formatted in what way? Sorry for being a pain.![]()