That's one way to fix a bug. You outsmart it by using Murphy's law against it!
-
Greetings Commander, want a more instant approach to your questions and need for help? Check out the Galactic Academy Discord server!
Feel free to join the Galactic Academy Discord server by clicking here!
Newcomer / Intro So I'm giving it another try and now I'm having a problem.
- Thread starter Marvin the Martian
- Start date
I think it's because the game knew I was recording it.
I would hit record, hit power up, it would jump perfectly and I would stop the video.
IT KNOWS.
I would hit record, hit power up, it would jump perfectly and I would stop the video.
IT KNOWS.
digitus tribulationis it would seem
Went ahead and upgraded to Odyssey for 12 bucks. It's really nice looking even on my ancient EVGA SSC 960GTX. The only place is lags a bit is at docking where it drops to about 40 to 45 fps. The rest of the time it's spiked at 75 FPS (my old monitors max) the entire time.
The new menus are neat but overly complicated in my opinion. Love the new nav map though. A lot more user friendly to me.
The new menus are neat but overly complicated in my opinion. Love the new nav map though. A lot more user friendly to me.
-------
OK guys, it happened again just now and I've got it on video. The situation:
I'm going out on a bounty. I plot the course and it's only one jump:
Here's the jump range right before I hit the button:
Here's my Krait Mk II's range:
Here's the video of what happens - I set the course, go back to the cockpit, aim at the destination, hit the button to power up the FSD and the destination instantly vanishes and is replaced by a destination on the opposite side of the environment going the other way. This is the issue I was having that was driving me nuts when it suddenly quit doing it. Now, it's back.
Source: https://www.youtube.com/watch?v=pOfNGo5_-3E
I'm going out on a bounty. I plot the course and it's only one jump:
Here's the jump range right before I hit the button:
Here's my Krait Mk II's range:
Here's the video of what happens - I set the course, go back to the cockpit, aim at the destination, hit the button to power up the FSD and the destination instantly vanishes and is replaced by a destination on the opposite side of the environment going the other way. This is the issue I was having that was driving me nuts when it suddenly quit doing it. Now, it's back.
Last edited:
That is strange and just as you described, I suspect that everyone is going to come up blank again so you are probably going to have to visit the support website and raise a ticket there. They are usually extremely good at working stuff out.
..... downloaded the video and checked the route thing again ... looks legit.
So - I don't know why the end of your video shows COL sector .... as your destination 15.6ly away.
So - I don't know why the end of your video shows COL sector .... as your destination 15.6ly away.
That's the weird part. It had nothing at all to do with the route. This is what was happening before that was driving me nuts. I had to reset the route 4 times before it worked. Sometimes I would just go ahead and jump to the other destination it put up there and reroute it from there only to have the same thing happen again.
I would then leave the game and come back and it would work fine for a while. Then it would start doing it again.
As suddenly as the problem started, it stopped. It just now happened again.
I would then leave the game and come back and it would work fine for a while. Then it would start doing it again.
As suddenly as the problem started, it stopped. It just now happened again.
Haven't you got the Wake selected on the left hand side of the screen at all times? The COL number on the wake is the same as the one it tries to jump you too.
Can you deselect the wake and then try?
Well spotted - that is exactly what is happening. I never looked at the target box - shame on me.
I wonder why plotting the route on the gal map didn't clear that wake destination selection? - I'll have to check that in game myself. EDIT: See post further down, plotting a course does not remove the wake destination selection.
Last edited:
Ja, I'm really surprised the route selection on the galmap doesn't "overwrite" the wake selection.
This may have happened to me in the past as my muscle memory when jumping is to flick the hat switch down on my x52 to "deselect" whatever I had targeted to make the jump. I do this even when I have nothing else selected so it's possible that this used to happen to me too - it's certainly a habit i am in now!
In any case, hope that sorts it!
I just checked this in both Oddy and Horizons and found the same. Plotting a route on the gal map does not clear the selected scanned-wake destination. Obviously using "Select next system in route" keybind clears the scanned wake and selects the plotted course.
It's because you have scanned a wake and it does, rather annoyingly, flip back to the destination of the wake you scanned was going to ignoring the galaxy map route plotted. If you were bounty hunting the ship that just jumped away, this would help you follow it.
One solution is to power off the wake scanner in modules, replot the course and go. This cause was suggested on this thread a while ago, now we see it all happening on the video, so there is no doubt.
One solution is to power off the wake scanner in modules, replot the course and go. This cause was suggested on this thread a while ago, now we see it all happening on the video, so there is no doubt.
You have a scanned wake targeted. When you initiate a jump with a scanned wake targeted, it will attempt to jump to that system similarly to as if that system was directly targeted (like you would through the galaxy map or the navigation panel on your left). Like described in message #39, targeted objects/systems take priority over the route.
Plotting a route clears navigation locks (such as for planetary bodies, stations, or other systems), however, a wake is a temporary, targetable object within local space, and those stay targeted even if you plot a route. So basically, it's a dev oversight not having implemented a "clear target" command simultaneously with plotting as it does with navigation locks already, for this one edge case where a locally targeted object can alter the jump behavior.
Use a bind to change your target (such as "select target ahead", default "T" on keyboard) to deselect the wake before initiating the FSD sequence and it'll jump to the plotted route you intended.
The reason why wakes do this in the first place is because they're meant to be a tool for chasing ships that have succesfully fled a pursuer (hostile or otherwise), and as such, it wouldn't make sense to have to find the system and manually target/plot it after you've found out the system the ship jumped to when it's usually a time-sensitive situation. The material gathering mechanics for engineering were only added a few years after release and prior to that, the sole purpose of the wake scanner was for such scenarios.
If you raise a ticket in the issues tracker, you might be able to get it fixed so that such a situation doesn't happen to you or anybody else, but this is in the realm of where it could be written off as game mechanics just working in a unique, if negative, way, so I doubt it would be seriously considered to be changed.
That explains it then. I've never scanned a wake for a destination. I only do it to get the data for engineering.
That is the most ridiculous thing to do: automatically override a selected course you just plotted with a wake you scanned an hour ago.
That is the most ridiculous thing to do: automatically override a selected course you just plotted with a wake you scanned an hour ago.
.nevermind & unwatching & happy trailS!
I think it's as good as a bug in the game. If the pilot decides to plot a course to a destination, that's where the ship should jump to.
I had a wake scanner on my Orca in Colonia for quite a long time. Jacques Station is said to be the busiest station in the game, except maybe when a community goal has many commanders shipping commodities to one place. Lots of wakes to scan to collect the encoded data. Eventually the Atypical wake scan thingies - the grade 1 material - storage filled up. I had 250 of them. In the same amount of time I collected no more than a handful of grades 2 to 5. I sold all my wake scanners after that. I consider them a waste of time for material collection. I tried to do it this way because I don't like parking behind Jameson's Crashed Cobra repeatedly quitting to desktop and logging in again to reset the comms beacons so I can rescan them and get the grade 5 and 4 encoded materials. It takes about 15 minutes to fill up the grade 5 encoded material store this way - I think its encrypted data captures. I still don't know a better way to get these materials (except maybe modified embedded firmware mission rewards), so I resign myself to parking behind the Cobra if I need more.
Well technically the data gained by scanning wakes is a bonus the purpose of the Wake Scanner is to enable you to track down a target to it's destination.
I didn't spot that on your video sorry, probably because it isn't an issue I have had which will be down to pure luck in that I tend not to travel when I am doing wake scans also I do have a tendency to unlock targets once the scan has finished a carry other from scanning ships as I don't want to worry their commanders by leaving them target locked.
I am surprised that the route plotting didn't fully override the wake target it should at least show a warning of some sort.
