Talonclaw

Very surprising changes and well met indeed. thank you

yeap i think it's fixed. silly me creating a post a day after NQ finally fixed the issue, an issue they've never mentioned in any patch notes. Thank you for testing

no. ive done 2500 scans, 500 were on Ion. im familiar with micro movements. easy way to test it is with the maneuvre tool, if it hangs in mid air after using the tool, it's fixed. If it drops to the ground, it hasn't settled yet. (There is a trick when landing u can do to make it settle very quickly, it involves the air brake and alt-c in the right order. something i learnt on Ion. tested with the maneuvre tool almost every time. I say alt-c but ive rebound mine to c, far more sensible ) There may have been some kinda pattern between amd and intel before demeter, if you look through the above posts you might see it. but post-demeter seems to have fixed it. As for the people still, having problems.. maybe you have a point in their cases. but pre-demeter, a shifting ship simply doesn't explain the number of cases. A knowledgable helpful super-present player in discord told me that it's meant to stop when u get too far away. that's how common the problem was, yet for some players, the units never ceased scanning no matter how far away they got. Most of the tests, players have reported on this thread are not skewed by user error. there's simply too many from experienced people. Also, if the ship shifts, all of the units would turn off, not 1 or 2 as has been the case in a few reports here and elsewhere.

This post is in 2 parts. I recommend scrolling to the edit. Good idea, the only contradictions on this thread so far are a Ryzen 9 and an Intel 5 one is a very new Ryzen and the other a 2009 Intel. If there's any truth in this, the contradictions seem to point towards something modern in the architecture that Ryzen have only just caught up with. R9 and R5 both have the same set of extensions, so it's not that. Mine is a Ryzen 5 3600 I should have considered that but can attest that although i haven't tested it since the patch, a colleague with the same CPU has. So R5 3600 is affected unless, it has nothing to do with the CPU a support ticket on the issue has been filed and this thread has been provided. ----------------------------------------------------------------------------------------- EDIT / 2nd post ----------------------------------------------------------------------------------------- I tested this myself just now, with highly different results compared to pre-demeter; 0600-0700 UTC 1 - Flew 10km away from scanner flew back, it was still running 2 - Flew 10km away from scanner, got out, walked around for 1 min, flew back, it was still running. 3 - Flew 30km into space, got out for a space walk, didn't realise cockpits eject you when u do that in space.(upgraded S core now that NQ finally sorted the cockpits HUD). The jet fell beneath me, i was floating unable to reach it or turn on the jetpack for some reason, did a force respawn.. walked 20 metres back to the scanner, which was still running. (So even through a quick load screen it was still running). 4 - Flew to District 6 started scanner, flew 10km away, got out for 1 min then returned, scanner still running. 5 - Flew to Madis, tested, still no problem. 6 - Flew to Teoma and switched on 3 of them.. 10km and back. all still on. Judging by the previous posts, there clearly is a pattern at play between AMD and Intel but im beginning to suspect that what CPU you have affected network performance if not now, then before Which is something i know nothing about. My scanners used to shut off, they no longer seem to. Yet for others the problem is still there. One of my colleagues told me that for them, they'd return to the triscanner, one or two of the scanners would be off but not all of them. which i feel also supports the network performance hypothesis (failed to handshake), tho it could be something else. bit of a rabbithole. From another user in discord we need dev intervention if people are still suffering the problem.

upon request, he's now added ENglish subtitles.

Yes, the settings was the first suspect. both of the original test subjects had the same settings but different CPU's. We ruled it out before i posted.

You guess wrong, i researched it many years ago. Thank you for the toxicity and the unconstructive commitment to the thread. I was a `PC expert` by 1994 and began in 1986 but i haven't owned an intel since the 486. I would humour you and explain the thought process behind, is it a problem with multitasking but i don't respect you enough to try. It may be a function that DU utilises in the Intel coreset that AMD doesn't have, who knows.. not me. Hey Vhae yeah me too.. i was always annoyed and have had to stick to triscanner ships but learnt a few days ago that my friend with his M core that launches pods.. can launch way more than 3 and have a complete scan. I would like to build a pod ship please 2500 scans with a triscanner took a long time

There is a video guide but it's in French and the subtitles are only in French. Thank you to the champion that finally does one in English. why doesn't youtube scan uploads to provide subtitles in whichever language u need. Course it only takes the uploader 2 seconds to add them but hey. The vid gives you a semblance of an idea but as you can imagine, from such a non intuitive system, context is missing without speech or text.

Hello, myself and another Ryzen user need only get about 3km (or less) away from a Territory Scanner before it switches off / unloads from its own process. But, a very trustworthy friend named Gunhand who has an Intel.. can travel in excess of 25km and they'll still be on when he gets back. Someone else with an intel on discord mentioned he can fly into space and back, it'll still be scanning. 2 other users in discord did the experiment, intel users, they too had no limit to distance before the scanner turned off. Could someone please clear this up? I don't know enough about Hyperthreading vs Multithreading to form a theory, i certainly could be wrong about the cause. Though there is, a serious problem here, the harsh contrast of the evidence is very compelling. If you test it, be sure to travel at least 10km from the scanner and back, so it's a clean result. The scanner needs to be scanning, not presenting scan results.

you silly, shortsighted git. *adds his first user to ignore*

I have to commit to this thread. It isn't just the market place. I don't feel that there's anything wrong with space elevators because they have a column but these floating, tiny, black platforms.. one user called them `death-twigs` I first crashed into one and died, it's 4500m above sanc10, 10km out. it cannot be seen by radar and most of the time cannot be seen during flight. (unless you use the fixed camera angle and happen to be focusing) these things are common and will become an even greater hazard over time. I wonder how many deaths it's going to take for something to be done. Eventually an NQ staff member-player will suffer the misfortune. I'd rather something was done sooner. I don't seek to belittle any of the comments on this thread, the solution for what i've written here might well be connected to the solution for the above.

Make the colour of the sun, planetside, a different colour depending on the atmosphere of the planet. (In E:D Sol is yellow when seen in space. cept it isn't.. i added the suggestion there during beta, no one cared. That is why im putting it here instead of the upvote page) Apparently it's a useless suggestion.

please vote if you feel (or think) this is needed. https://upvote.dualuniverse.game/suggestions/125004/waypoints-how-to-tell-if-on-other-side-of-planet

added to the upvote library, awaiting moderation.

Parenting Ships - Dragged to PVP Space: This is a hot topic and one we wish to be very clear on. Intentionally parenting any construct without permission of the owner is not intended for game play. A fix has been rolled out that will address the ability to parent constructs together via the maneuver tool. As we have not previously clarified this point, we will not retroactively punish this abuse, as of this moment forward abusing similar bugs/tools to replicate this maneuver in its current state can result in disciplinary actions on an account. [Not Allowed]