what card, what version of nvidia drivers?
Pulse Wave scanner issues after update 12
- Thread starter Urbanski101
- Start date
what card, what version of nvidia drivers?
Made no difference here,
BUT - I find the problem is weirdly intermittent, and variable in nature. Sometimes all seem fine, other times I'm finding unhighligted rocks have deposits (sub or surface), I'm frequently getting the disappearing signals (glow that vanishes on approach), and regularly getting phantom signals (where the rock turns out to be completely unremarkable, despite glowing), and those annoying partial reflection type glows that don't seem to relate to anything nearby.
It's not always distance-from-drop-in dependent either.
I figured this came in with Odyssey. PWS was always a bit too jank and haphazard for my tastes, but it seems to have gotten worse.
It's the way they're doing it with something like spawning light sources and things. Things shine onto other things, it's weird. I'm guessing the lighting system changes in Odyssey made purpose-built mechanisms behave differently. Like the chrome paintjobs. PWS should work more like night vision does. Just be some kind of 2d overlay connected to your cockpit viewport. Even if it was kind of slapped-on, sort lo-fi or a bit pixelly or something, as long as it was done right, it would fit right in with the rest of Elite's 70s low design/heavy industry tech aesthetic.
It's the way they're doing it with something like spawning light sources and things. Things shine onto other things, it's weird. I'm guessing the lighting system changes in Odyssey made purpose-built mechanisms behave differently. Like the chrome paintjobs. PWS should work more like night vision does. Just be some kind of 2d overlay connected to your cockpit viewport. Even if it was kind of slapped-on, sort lo-fi or a bit pixelly or something, as long as it was done right, it would fit right in with the rest of Elite's 70s low design/heavy industry tech aesthetic.
Before U12 it was fine in ody
RTX 3060Ti
Version 516.59
There's another update coming through now but I'm out of the mining cycle now. Just mined 600MCr for an expedition and I'm off into the black.
Good luck exploring o7
I'm also out of the mining loop for now. I tend to mine for a few sessions then move on to do something different.
Can anyone else confirm if the driver update works for them?
I've just updated the GeForce Game Ready Driver to 516.59, no change, the bug still exists.
Okay - so this morning I pull into an icy ring and I notice that I have the problem. Finding lots of un-marked subsurface and surface opportunities.
Is this specific to icy rings, and not metallic rings where last week it was perfectly fine?
I'm out of town until the end of next week, otherwise I'd be testing this out.
Is this specific to icy rings, and not metallic rings where last week it was perfectly fine?
I'm out of town until the end of next week, otherwise I'd be testing this out.
My screenshots from page 2 were from a Rocky Ring - the bug happened consistently in that ring.
Sadly not - I've been getting it on & off all week in a pristine metallic ring.
So I am having this same issue on my main PC BUT I have ran into something very odd. I also play elite on my Steam Deck using the valve Proton layer and the Pulse Wave works just fine on there. Outside of having a layer that translates all commands for linux I am working on narrowing down the game settings to see if one of them is causing the issue. Ill post an update later if I find a setting causing issues OR if the translation layer is what is causing the fix.
running on steamdeck means some really low settings - it would be interesting if you manage to pinpoint the setting that "fixes" the issue - if any, and not the translation layer as the bug-fixer
Update to this: I have solved my issue on my PC and have my PWA working on both of my system.
I matched all of my game settings but none of these worked. Tried changing some settings in the AMD software as well but did not help. I ended up uninstalling and reinstalling the whole game and now the PWA works. I did notice during the initial start that it creates a "Graphics Card Profile" that says it creates on startup but also updates after graphics card driver updates..... I just updated my drivers this morning and I know that it did not go through an "update" for this profile this morning and I have a feeling that may be what was causing the issues for me. I am not aware of a way to force the game to update the games GPU profile (btw this is different than the profile for the game in the graphics software) outside of reinstalling and it doing it on the initial boot.
You would be surprised about that. My steam deck runs settings of about a 50/50 mix of medium to high settings and it runs just fine, avg 60fps (screen is only 60hz so im perfectly content with 60fps). I am planning to test out how high I can take my settings before suffering performance loss but have not done this yet.
There is an option in-game to run the shader generation each time rather than just on changes.
Edit: Scrap that - I remembered there being one, but it was not there when I looked.
Last edited:
Ugh - this is a nightmare. It was working perfectly for me yesterday and I had a taste of what Tritium mining should be. Shedding limpets by the truckload. Today, nyada. Laser mining only sucks. My only saving grace was that I only needed 160t to fill the tank.
Out in the black in a system I've just mapped. Apart from systems discovery and planet A the rest were not discovered 4 of which had rings some metallic, one that's rocky and another that's ice.
I jumped into all of em.
All exitibiting the same bug namely that u can see reflections of the core roid but its not there all I can see is its light shining onto nearby roids.
I do find cores but 10s of kms apart and as l always use the planet as a direction, I'm not going in circles.
Contributed to ongoing report.
I jumped into all of em.
All exitibiting the same bug namely that u can see reflections of the core roid but its not there all I can see is its light shining onto nearby roids.
I do find cores but 10s of kms apart and as l always use the planet as a direction, I'm not going in circles.
Contributed to ongoing report.
Also
1) not finding any subsurface roids at all. Mined over 200t in 4 rings (running tests) painite alexandrite, ltds, monazite, plus others and all the roids I found were just surface or core (rarely) Or laser.
2) after locating a core and blowing it up with "in the blue" shown as optimal, as it detonates up pops a message always saying depleted yield (in red) and l get between 9 to 13.
Plus a dozen or so more from abrasive surface. So about 25 to 30 in all.
Seems odd that given the charges set are optimal according to after l set last charge, that it's always flashing up as low yield. So is this a bug too?
1) not finding any subsurface roids at all. Mined over 200t in 4 rings (running tests) painite alexandrite, ltds, monazite, plus others and all the roids I found were just surface or core (rarely) Or laser.
2) after locating a core and blowing it up with "in the blue" shown as optimal, as it detonates up pops a message always saying depleted yield (in red) and l get between 9 to 13.
Plus a dozen or so more from abrasive surface. So about 25 to 30 in all.
Seems odd that given the charges set are optimal according to after l set last charge, that it's always flashing up as low yield. So is this a bug too?
To 1)
I did find subsurface deposits randomly on not glowing asteroids. But you can only see them in the contact panel or when searching directly on the asteroids surface. They are not marked with the blue icon as before U12. And on the core asteroids there are also subsurface deposits, in this case they are still marked with the blue icon.
To 2)
I think that was also the case before U12. As far as i can remember this "bug" was always there. Since it was just a wrong info message and did not have any impact on the core yield, i just ignored it.