Update 18 | Update Notes

Same here, if I'm honest.

Business as usual for me.
As much as I'd love to fight at the Titans, I am enjoying my current trip far away from the bubble, where I shall stay for a few more weeks/months.

My guess is that any new mechanics will not be a one off event, but will stick around.
Even if the eight titans are hypothetically going to be defeated now, there might be more coming in the future. 🤔
 
Also to those complaining about bugs, if you're not checking the Issue Tracker and submitting bugs that you find, you have zero reason to complain on the forums here. There's a place for that. Not everything can be fixed in a single update, and just because it's not on the U18 patch notes doesn't mean Fdev are never going to fix it.

Again: post to the Issue Tracker.
It’s not really the player’s responsibility to track down bugs and then jump through hoops to report them.
 
Sure it is. Just stop running so far away from them and they won't de-agro.
For me it is not possible to stay in shooting range of a Hydra the whole fight. Please make a video and enlighten me.
When I get more than 4km away two things happen immediately:
  • the swarm turns the other way (more than 10km) - so bringing down the swarm in time is not possible
  • the Interceptor turns and jumps to whichspace.
In AX Zones its still possible to fight the big Interceptors. I only talk about real Solos in the pleiades.
 
  • Introduced "Gravity Well" cockpit message to replace "Slow Down" when travelling at excessive speed near celestial bodies.

I'm not sure I should be as happy to see this as I am, but there you are.:)

Agreed ... I damn near fell off my chair when I read that.
Now I can finally stop asking myself whether 'Slow down' is a situational report or an injunction.
 
For me it is not possible to stay in shooting range of a Hydra the whole fight. Please make a video and enlighten me.
When I get more than 4km away two things happen immediately:
  • the swarm turns the other way (more than 10km) - so bringing down the swarm in time is not possible
  • the Interceptor turns and jumps to whichspace.
In AX Zones its still possible to fight the big Interceptors. I only talk about real Solos in the pleiades.
Interceptors will only fire at you if you're within 3km. So that's at least one whole kilometre of range you can safely stay within, much more if you've got a thermal vent beam.
 
It’s not really the player’s responsibility to track down bugs and then jump through hoops to report them.
It's actually quite normal and expected in the FOSS world. Finding bugs is hard work and many times occur under specific conditions that the devs have not thought of, when specific hardware is used that the devs don't have or some obscure dependency requirement is not met (hence why containerization is so popular—it gets rid of most "Works fine on my machine!" situations). Ability for the users to report bugs helps both the devs and the end users, making bug-stomping much faster and more responsive process.
 
So ... you're saying it is working all correctly. Good to know (y)

(It's no wonder some of these 'bugs' are longstanding when they're in ppls heads :) )
Are you Joker?
Not work... there is simply not work. It was never necessary to go into explorer mode with the xeno scanner to grab the Codex data. To go to exploration mode in the middle of firefight. Is it a joke?
The IQ is most faster that you understand.
:ROFLMAO: (y)
 
Are you Joker?
Not work... there is simply not work. It was never necessary to go into explorer mode with the xeno scanner to grab the Codex data. To go to exploration mode in the middle of firefight. Is it a joke?
The IQ is most faster that you understand.
:ROFLMAO: (y)

The xeno scanner is used to scan the enemies for targeting/info data - nor for codex entries.
And i was never bothered by that because i always had all scanners bound to the same key, including the xeno scanner - so when i was scanning the Cyclops using the xeno scanner i was also using the composition scanner and got the Codex entry.

Maybe you were used to do the same, but with the enhanced range scanner this may not be possible since you're being much more farther away.

Just saying 🤷‍♂️
 
  • Introduced "Gravity Well" cockpit message to replace "Slow Down" when travelling at excessive speed near celestial bodies.

Oh! That message has always annoyed me - I spent the first months playing wondering if there was some sort of speed cop I didn't know about :)
 
The xeno scanner is used to scan the enemies for targeting/info data - nor for codex entries.
And i was never bothered by that because i always had all scanners bound to the same key, including the xeno scanner - so when i was scanning the Cyclops using the xeno scanner i was also using the composition scanner and got the Codex entry.

Maybe you were used to do the same, but with the enhanced range scanner this may not be possible since you're being much more farther away.

Just saying 🤷‍♂️
It's possible but Xeno Scanner use in combat mode and the data is in explore mode.
Sorry, but I don't remeber use the data scanner for "the flowers" (aka interceptors) ... long time ago...

Regards.-

PD: And remenber that new vessel (hunter class and Orthus) are very faster and agressive for take you time.
 
It’s not really the player’s responsibility to track down bugs and then jump through hoops to report them.
In an ideal world, the QA team would find and flag every bug in the game, but with a game with a playerbase on the order of thousands, players will find more bugs than any reasonable QA team could ever find. If you find a bug, report it. If you don't report it and cry that it's not being fixed (maybe because internal testing hasn't caught it), then you just look like an idiot. There are also no hoops to jump through when reporting bugs in Elite, it's as simple as creating a post on the Issue Tracker.
 
Back
Top Bottom