Update 18 | Update Notes

Darrack

Darrack
Helmut Grokenberger said:
I'm guessing this works best in a well organized team or group of players in a PG.
Click to expand...
Yes don't get me wrong you absolutely have to do this stuff in Open or PG, it takes too long to activate the vents Solo unless your in a fast, manoeuvrable ship.
Last night (although i hate Open) was fun, this morning though the muppets had woken up and it was a bit of a joke.

O7
 

Jack Brolin

Jack Brolin
nemolomen said:
I cut my Elite Dangerous ship combat teeth fighting Thargoid Scouts. No engineering or guardian unlocks required.

Lasers, Decontamination Limpet Controller, Repair Limpet Controller, Shields (optional), Armor and Hull Reinforcements are all normal modules and can be bought nearly everywhere.

Enhanced AX Multicannons and Enhanced AX Missile Racks are available at the Rescue Megaships.

Then all you need are a hull (Chieftain or Krait II) and the Xeno Scanner (so you can see how much hull your AX target has left) and Shutdown Field Neutralizer (for use against the shutdown field produced by Interceptors) and a Cargo Rack for your limpets.

Fast engines are a good thing to have as well.
Click to expand...

Pleased to report I have murdered some Thargoids in my Chieftain! o7
Hull got eaten because I forgot to take limpets, but I got to see an Interceptor explode before I exploded myself. Pretty. My first attempt at cold orbiting too. Need to tweak the build and get back out there...with a bunch of gauss cannons maybe
 

Alec Turner

Alec Turner
Morbad said:
This isn't remotely the first time a bug that was previously fixed has returned to Elite: Dangerous.

As has been mentioned, Frontier doesn't seem to have very good version control. They could have easily built U18 from older source than U14, or never properly merged U14's fixes.
Click to expand...
Or, code being the tangled web of spaghetti it often is, you change one bit of code to fix a bug based on the inputs it's getting and then later, change a different bit of code which then feeds different inputs into the first bit of code, causing it to go back down unexpected code paths you'd originally worked around in the first fix.
 

Ryder7

Ryder7
nemolomen said:
I cut my Elite Dangerous ship combat teeth fighting Thargoid Scouts. No engineering or guardian unlocks required.

Lasers, Decontamination Limpet Controller, Repair Limpet Controller, Shields (optional), Armor and Hull Reinforcements are all normal modules and can be bought nearly everywhere.

Enhanced AX Multicannons and Enhanced AX Missile Racks are available at the Rescue Megaships.

Then all you need are a hull (Chieftain or Krait II) and the Xeno Scanner (so you can see how much hull your AX target has left) and Shutdown Field Neutralizer (for use against the shutdown field produced by Interceptors) and a Cargo Rack for your limpets.

Fast engines are a good thing to have as well.
Click to expand...
@nemolomen : Quick slightly off topic, AX noob question: would you consider using a Vulture a viable option to try your setup mentioned above as a start against Scouts?
(Got a chieftain in hanger as a WIP for further big game, but still a long way to go before this one's ready, not to mention the pilot's untrained skills)
Thanks in advance, o7
 

Alec Turner

Alec Turner
Paul_Crowther said:
  • Introduced "Gravity Well" cockpit message to replace "Slow Down" when travelling at excessive speed near celestial bodies.
Click to expand...

Still not working for me!

Steps to reproduce:
1) go to to Euston station in the Sol system
2) observe that the message currently being displayed is still as shown in the screenshot below

49onSoS.png
 

galahad2069

G
Alec Turner said:
Still not working for me!

Steps to reproduce:
1) go to to Euston station in the Sol system
2) observe that the message currently being displayed is still as shown in the screenshot below

49onSoS.png
Click to expand...
lol

Not to mention that the current 'gravity well' warning does not even make any more sense than the original 'slow down' one, probably because there have always been 2 different scenarios when you got the warning:

1. you were trying to reach a destination somewhere within a gravity well but you entered it too fast because you throttled down too late: this was the case when the original 'slow down' message made sense (telling you that you should slow down otherwise you will overshoot your destination)

2. you were trying to reach a distant destination in supercruise, but you happened to fly too close to a planet, which had a decelerating effect and prevented you from accelerating again until you have left the gravity well: in this case the spelling 'slowdown' would have made more sense (telling you that something is slowing you down)

Now we have a 'gravity well' notification in both cases, but that does not make sense either, since the warning will go away as soon as you have managed to slow down, while you are very clearly still inside the exact same gravity well, so why does the notification get removed?
 
Last edited:

Shadowsnog

Shadowsnog
galahad2069 said:
lol

Not to mention that the current 'gravity well' warning does not even make any more sense than the original 'slow down' one, probably because there have always been 2 different scenarios when you got the warning:

1. you were trying to reach a destination somewhere within a gravity well but you entered it too fast because you throttled down too late: this was the case when the original 'slow down' message made sense (telling you that you should slow down otherwise you will overshoot your destination)

2. you were trying to reach a distant destination in supercruise, but you happened to fly too close to a planet, which had a decelerating effect and prevented you from accelerating again until you have left the gravity well: in this case the spelling 'slowdown' would have made more sense (telling you that something is slowing you down)

Now we have a 'gravity well' notification in both cases, but that does not make sense either, since the warning will go away as soon as you have managed to slow down, while you are very clearly still inside the exact same gravity well, so why does the notification gets removed?
Click to expand...
id guess it sounded more like an instruction to slow down, rather than an alert to the presence of the
gravity well!
 

Alec Turner

Alec Turner
galahad2069 said:
lol

Not to mention that the current 'gravity well' warning does not even make any more sense than the original 'slow down' one, probably because there have always been 2 different scenarios when you got the warning:

1. you were trying to reach a destination somewhere within a gravity well but you entered it too fast because you throttled down too late: this was the case when the original 'slow down' message made sense (telling you that you should slow down otherwise you will overshoot your destination)

2. you were trying to reach a distant destination in supercruise, but you happened to fly too close to a planet, which had a decelerating effect and prevented you from accelerating again until you have left the gravity well: in this case the spelling 'slowdown' would have made more sense (telling you that something is slowing you down)

Now we have a 'gravity well' notification in both cases, but that does not make sense either, since the warning will go away as soon as you have managed to slow down, while you are very clearly still inside the exact same gravity well, so why does the notification get removed?
Click to expand...

Fixed it!

strMsg = "SLOW" + (target.isWithin(body) ? " " : "") + "DOWN";
 

galahad2069

G
DjVortex said:
A better expression would have been "experiencing slowdown".
Click to expand...
or "experiencing insufficient slowdown, gonna overshoot, help, help" in scenario #1 :)

The problem is, the 2 scenarios are the polar opposite of one another, in the first case you would like to go slower (but can't), while in the second one you'd like to go faster (but can't), that's why the same notification cannot really work in both cases.
 
Last edited:

Ozric

Volunteer Moderator
Ozric
galahad2069 said:
there have always been 2 different scenarios when you got the warning:

1. you were trying to reach a destination somewhere within a gravity well but you entered it too fast because you throttled down too late: this was the case when the original 'slow down' message made sense (telling you that you should slow down otherwise you will overshoot your destination)
Click to expand...
That's not correct. The message has always been to indicate you are experiencing 'Slow Down' due to being in a 'Gravity Well' of some description.

It's to do with how the mass of the object affects the FSD's ability to compress space and function optimally. If you operating well within limits i.e going very slowly, then the gravity of an object doesn't affect it enough to become a problem so you are not slowed down any more.
 

galahad2069

G
Ozric said:
That's not correct. The message has always been to indicate you are experiencing 'Slow Down' due to being in a 'Gravity Well' of some description.
Click to expand...
I'm not a native speaker of English, but "slow down" does not seem to be something you experience (that would be spelled "slowdown"), it's something you are told to do.

Besides, what kind of deceleration you experience will make you overshoot the target while the lack of it won't? :)
 
You must log in or register to reply here.
Back
Top Bottom