Pulse Wave scanner issues after update 12
- Thread starter Urbanski101
- Start date
How does this bug affect people?
Well, I've been mining at a Tritium double hotspot overlap four times. On three occasions, I had this bug. It took me nearly 2 hours to laser mine a full T10 load (256t) of Tritium and around 200 limpets, and I am chasing occasional shadows only to find nothing. Furthermore, suppose I target anything on an asteroid. In that case, I get no targeting reticle - which makes targeting surface and subsurface deposits (which you accidentally come across on asteroids that do not shine) extremely difficult. For example - I should have a targeting icon for the prospector limpet, but I do not. You can see that it is targeted. This is the same for deposits.
Mining Targeting Bug by Anthony Sheehy, on Flickr
On the only occasion that this bug did not occur, it took me an hour to fill the hold, I slung half my limpets, and I'm always within a couple of asteroids of subsurface deposits (which I'm getting very good at extracting!) Plus, I nabbed a core presenting 14t of Void Opals.
I did not do anything unique or different on the day it did work. So it makes it a struggle to do what we do, mainly if you depend on doing this in the black for a carrier.
Dear @sallymorganmoore thank you so much for being there when we call you. Can you check that this is on the radar for us, please?
Well, I've been mining at a Tritium double hotspot overlap four times. On three occasions, I had this bug. It took me nearly 2 hours to laser mine a full T10 load (256t) of Tritium and around 200 limpets, and I am chasing occasional shadows only to find nothing. Furthermore, suppose I target anything on an asteroid. In that case, I get no targeting reticle - which makes targeting surface and subsurface deposits (which you accidentally come across on asteroids that do not shine) extremely difficult. For example - I should have a targeting icon for the prospector limpet, but I do not. You can see that it is targeted. This is the same for deposits.
Mining Targeting Bug by Anthony Sheehy, on FlickrOn the only occasion that this bug did not occur, it took me an hour to fill the hold, I slung half my limpets, and I'm always within a couple of asteroids of subsurface deposits (which I'm getting very good at extracting!) Plus, I nabbed a core presenting 14t of Void Opals.
I did not do anything unique or different on the day it did work. So it makes it a struggle to do what we do, mainly if you depend on doing this in the black for a carrier.
Dear @sallymorganmoore thank you so much for being there when we call you. Can you check that this is on the radar for us, please?
Last edited:
For miners this is almost a game-breaking bug. My Squad and some invited Cmdrs where on a deep-space-mining operation when during update 12 this occured. That was at first big confusion and then a disapointment as we had to abort the operation.How does this bug affect people?
Well, I've been mining at a Tritium double hotspot overlap four times. On three occasions, I had this bug. It took me nearly 2 hours to laser mine a full T10 load (256t) of Tritium and around 200 limpets, and I am chasing occasional shadows only to find nothing. Furthermore, suppose I target anything on an asteroid. In that case, I get no targeting reticle - which makes targeting surface and subsurface deposits (which you accidentally come across on asteroids that do not shine) extremely difficult to see or target. For example - I should have a targeting icon for the prospector limpet, but I do not. You can see that it is targeted. This is the same for deposits.
On the only occasion that this bug did not occur, it took me an hour to fill the hold, I slung half my limpets, and I'm within a couple of asteroids of subsurface deposits (which I'm getting very good at extracting!) Plus, I nabbed a core presenting 14t of Void Opals.
I did not do anything unique or different on the day it did work. So it makes it a struggle to do what we do, mainly if you depend on doing this in the black for a carrier.
Dear @sallymorganmoore thank you so much for being there when we call you. Can you check that this is on the radar for us, please?
OK follow up... and predicably its not working as intended.
A double alexandrite pristine as yet undiscovered until I mapped the entire system.
No alexandrite at all.. just bauxite roids with lepidolite and uranite sub surface.
Couldn't find any cores at all. Eventually found a core after 20 mins searching, So their here. Just very elusive so ties in with hotspots not influencing deepcore yield at all.
So it's disappointing.
Hotspots are still working for ore that's anything but core related.
On a good note. The scanner appears to work...leastways it highlights high yield roids. But finding cores is still hit n miss regardless of the hotspot denoted.
These were virtually on top of one another so ideal double.
This needs to be addressed. Namely that deep core mining has no buff since nerf. Which seems obvious but harsh.
I'd have thought a double would increase the chances of finding one by 2. Surely?
(Quick note. Yes l was aware of metal rich metallic etc)
Last edited:
Good to know the PWS is working for you.
I still haven't been mining since I reported this so I can't comment. I'm hoping new nvidia drivers might be the answer as it was for some.
As for the hotspots baring no relation to what is actually found, not sure how long that has been an issue but it feels like a long time. In my last mining sessions at a Musgravite hotspot I found 0 Musgravite cores, but lots of the other cores present in the ring.
Again, I don't expect either issue to be addressed by FD, it's just another couple of bugs in a long list of issues that appear to be not important enough to fix.
Another update.
Found a pristine icy ring with void opal and ltd hotspots.
Omg!!
What a difference.
The cores are just a few kms apart. Easily found if you use the planet as forwards.
Seems pristine icy are more lucrative for deep core than metal rich.
I'll report back about rocky soon as I find a decent one.
Found a pristine icy ring with void opal and ltd hotspots.
Omg!!
What a difference.
The cores are just a few kms apart. Easily found if you use the planet as forwards.
Seems pristine icy are more lucrative for deep core than metal rich.
I'll report back about rocky soon as I find a decent one.
You can switch back to Horizons to mine as workaround.
The issue posted earlier in the thread has now moved to voting - which means it is acknowledged as a bug and now needs everyone to pile in and click that vote button!
Until the voting triangle gets a small green tick in the upper right corner, the issue isn’t acknowledged by FDev.
Voting still helps with the report’s visibility though
Yes, I confirmed the issue a while ago and voted (thankfully the Issue tracker is behaving at the moment).
It's a long way to go before it's officially acknowledged by FD (as @Arioch mentioned), then has enough votes to be viewed as important and then finally be investigated and fixed. I can't see that happening any time soon...but I'm cynical.
I tagged our friendly neighbourhood spiderman... er... @sallymorganmoore so maybe she might be able to give a little weight to it. She's good at that.
Are you sure in Horizons it works as before U12? Did not test this yet, as my keybindings are always gone to dust when switching between ody and horizons. IF in horizons this works, i am willing to accept the keybind problem.
It shouldnt break the bindings. IIRC it was fixed some updates ago.
But, if you want to be absolutely sure, you should use named-custom-binds for both Horizons and Odyssey
StrontiumDog how-to is for Horizons, but it is still valid for Odyssey which need to bear the 4.0 version number while the bindings for Horizons are 3.0 version number as in the guide
lost your binds? want hasstle free backed up binds look no further
keybindings can reset if you visit the control section without one of your usual devices used to play the game ie hotas , xbox pad etc not plugged in or at that present moment is undetected by windows as it thinks your just using keyboard and mouse it simply rewrites your binds for you...
Edit: Even before fixing the binds, switching from EDO to Horizons then back to EDO (while using named custom binds as above) would work nicely with the sole exception for on-foot section reverting back to default KBM at the switch to EDO, so i had to go into config and select my named-custom-binds from the drop down.
But, as i said, they seem to have fixed that and lately i didnt had to reselect my on-foot binds.
But, as i said, they seem to have fixed that and lately i didnt had to reselect my on-foot binds.
Thanks. I will try this later. Did not know FDev eventualy fixed this.
PSA reminder alexandrite Is core rocks ONLY its not sub surface item... bring your core rock breaking explosives not the missile in EDH...
Last edited:
Extra As announced in June 2020 by Fdev Overlap generation boost was nuked all round when tritium was added...
A double overlap degrades rapidly as does the hot spot the greater you get from the hot pot centre after you have passed the kill of percentage the over lap fails to increase anything, This made only triple overlaps have a bonus effect higher than the centre of a single hot spot..
This is why all FC had an efficiency boost to use half the tritium to do 500Ly jump...
A double overlap degrades rapidly as does the hot spot the greater you get from the hot pot centre after you have passed the kill of percentage the over lap fails to increase anything, This made only triple overlaps have a bonus effect higher than the centre of a single hot spot..
This is why all FC had an efficiency boost to use half the tritium to do 500Ly jump...
Ok, i tested the horizons thing. Indeed the bug is not present in Horizons. And Keybindings also stay as they are. Northpin and Gábor were right.
Last edited:
Also noticing this issue now, U12, Odyssey, PC.
Voted on the issue tracker here: https://issues.frontierstore.net/issue-detail/50436
Voted on the issue tracker here: https://issues.frontierstore.net/issue-detail/50436