Pulse Wave Analyzer Hotfix soon, please?

I am still finding cores with my PWS...
But, definately fewer than before. One technique I'm using is to fly with the astroid field just above me. When my path happens to cross with a core it lights up as expected. I change it up every so often and meander aimlessly through the rocks, often finding ones I missed on the first pass. Also what I noticed is that when you find a core, more often than not, there's another close by.
The hotspots definitely have live areas and dead areas. If you find a few in succession, check the area thoroughly and conversely, if you have had no hits for ages, then you're in a dead zone so move on.
It's a bit like fishing.
Someone in this thread mentioned wasting limpets. Generally, if you think a rock might be a core, 90% of the time it isn't.
When you find one it's unmistakable. With experience the maybes won't fool you.
To me it's as if the range of the PWS has been drastically reduced. Remember how, because they are so bright and glow so long, with an A rated scanner, you could pick them out from miles away?
Now you only spot those that are along your track.
I was filling my 224 ton python in 1h20m, give or take, now it would take in excess 03h30.

Personally I think that this change is intentional and not a bug at all.

Sorry for the long post...I don't have a banana for you.
 
I wonder whether the state of confirmed is coming from the devs or just triggered by numbers of confirming players. Is this somewhere documented?

edit:
Never mind, it's explained in the FAQ. It's the latter, confirmed by enough players (10 independent reproductions).
Ultimately, therefore, "intended behaviour" and "confirmed" are not contradictory. Without further comments from the developers the whole affair is still open.

Which in turn also means that those who seriously believe that the developers would be forced to repair it just because its set to confirmed now, are actually the ridiculous ones here.

But someone seems to have mentioned, that the devs have 'acknowledged' it (somewhere in a dev post). Good luck then with insisting on a fix. History has shown that it can easily last 12 month or more until a seemingly trivial fix is ready - if at all. Most of the long-time players certainly still remember the beige planets drama. This case was also very soon 'acknowledged'.

This confirms that you clearly are talking of things you don't know at all, or don't understand.

The issue is in "acknowleged" state on the issue tracker. Read again the FAQ.
 
I think there are one or 2 votes missing to confirm it .... there are 3 duplicates, so it is possible that players have voted on the 2 that are closed by duplication.
Look https://issues.frontierstore.net/issue-detail/19374

I see it as Acknowleged

Immagine.jpg
 
Frillop's stubborn and increasingly silly denials aside (it's really dead easy to confirm the issue. Fly into a hotspot (or anything else, for that matter), fire the PWA and make sure nothing glows, then sit for five minutes and fire it again and marvel at the previously dark rocks suddenly glowing), I was wondering if it has something to do with the recent fix for the ridiculous exploit of using the same SSD roid over and over again.

My thinking is this: Core roids staying empty for is it 6 hours or 6 days is a thing and has been for some time. This obviously requires the servers to keep track of which Cores have been mined and not so they don't re-spawn on a re-log which, given the relative rarity of Cores (which is as it should be, I hasten to add), wasn't really that much of a load on the server hamsters.

Now imagine that they implemented the same functionality for the much more frequent SSD glowing roids, and now you have to wait for the servers to check ALL of the potentially glowing roids as to whether they should glow or not in your instance before you get a reliable response from your PWA.

I don't know. I'm just spitballing here.

I'm just annoyed that I can't just say "not glowing, moving on" anymore. I don't honestly care if they're harder to find, as a matter of fact they should be, in my opinion, but I'd like to know that a negative response from my PWA means that there's nothing there, rather than "nothing there right now, but there might be if you look again in 10 minutes").

It'd be like my plasmas only firing every third button press and me never knowing if they were ACTUALLY firing or not.
 
Yeah, I see it now. You can't see it directly if you just follow the link. You have to go to the status overview or leave the mouse over it. I admit, I never cared much about the issue tracker, because for me it is nothing else than hiding all the bug reports from the public. However, it gets silly the moment you read an 'obligation' out of 'acknowledged' to fix the bug as soon as possible. You are dreaming if you really believe that. But we will see how long it will take until something happens...

I don't read an obligation, I read the acknowledgment from FD that something IS wrong, and they're looking into it and it will be fixed when it will be fixed, don't care. That was the point in the OP post, and the whole thread. The point you still seem to miss. There's only one thing you actually can add to this thread if you wish to sound less ridiculous: apologize.

Not for being wrong (there's nothing bad in being wrong), but for your attitude. You clearly 1) Bragged all along the thread without having a look at the issue 2) Bragged all along the thread missing very basic knowledge of the PWA module spec and scanning behavior 3) Insulted the whole people involved in thread, repeatedly.

Not to mention the ridiculous and unreasonable attempt to climb the mirror now.

Now, if you wish to contribute seriously to the thread (for example, we still don't know if you're actually affected by the issue or not, and that would be interesting) that's really fine. Otherwise, you can go back mining your VOs with your superbe skills and actually do what you suggested some posts ago, stopping wasting your time here.
 
I do hope they fix the issue soon and to be clear, the behaviour of the PWS has definitely changed, I'm by no means a novice miner and my yields are nowhere what they were. Anybody that says there's nothing wrong with the PWS obviously doesn't spend as much time in the fields as I do.
 
Ok, got it. So you want it more convenient/faster whatever. Just be in for appropriate price adjustments once the mainstream starts farming VO cores. Better think twice than sorry...
Oh c'mon, don't be such a humourless liverwurst. I'm just someone who doesn't give a damn about other people's opinions (especially when it comes to majorities), and success seems to confirm my actions surprisingly often
That's all I can do for you. And good luck with your broken PWA campaign. 😁
My conclusion: It's not the PWA that sucks nor the devs. You can guess who does...

And by the way: I gained 30t in 17 minutes. With a peak price of 1.6 Mio (not right now, I know) this makes 48 Mio in 17 minutes. But yeah, the PWA sucks, because... people's opinion! 🤣
I give up. Why does everyone ignore the 2 short videos I made last night (#31) and instead repeat the same nonsense over and over again? Is the truth now formed by majority? Is everything okay with you?

just quoting only the first few post, enjoy
 
Last edited:
Where am I bragging? Is it that:




Fact, plain and simple. With video evidence (note the in-game timestamp). So where else do you want to fantasize bragging into?

The rest are at best some sharp comments that arise in a heated discussion, as it usually looks like when a single person stands up against the views of an angry mob. You can try it at times, if you have the balls to do so.

There was no angry mob, there isn't even now. There's only you, and your unreasonable attitude.

Having a discussion being in minority it's not always bravery. Often is blind stubbornness, you know?
 
Thank the gods for that, maybe we can actually get on with a workaround in the meantime without stroppy knickers sticking his oar in

Dunno if someone already tried to swap the PWA module position... but I'm afraid it won't do much

Edit: maybe also downgrading the PWA is worth a try
 
Back
Top Bottom