Patch Notes Update Wings Update 1.2.06 Incoming

Status
Thread Closed: Not open for further replies.
Since this patch I've been in two systems that are at war, and have no conflict zones, nor check points. Also I still have problems getting wing invites to players.
I guess there isn't much war's going down this weekend. :(

Sorry if I sound negative, it wasn't my intention. I appreciate the effort behind each patch, and eagerly await more. Thanks in advance.
 
- Unblock the queue of minor faction influence changes from missions ending in certain star systems

I'm curious about this one... What does this "certain star systems" exactly mean? Should we see sudden, big changes in systems where the influence has been stuck? Does this affect all the minor factions or mostly some problematic ones (like minor factions without a station in a star system)?
 
Hello Dev Team,

I do know that it is not the bug reporting forum, but I experienced several serious problems ever since the last 1.2.06 update I got to post here:

- Stuttering at RES is much worse, usually more than 1 second sometimes more. Unable to follow hostile ship movements,
- NPC AI: huh that is something I blinked when started dogfights. Like someone casted a bloodlust spell on them even novice pilots do manouvers I've never seen before, almost impossible to kill them with fixed weapons.
(I don't consider myself some sort of topdog pilot, but after destroying more than 1500 ships I've seen a "couple of" manouvers by all npc leveled fighters.)

- NPC big ships: Yesterday I was hanging at a RES and thank to the random generator there were several big ships in the area , frankly, so many were there I didn't know where to start. 2-3 wanted Imperial Clippers in the same place the paradise for a hunter.
I spotted a lonely wanted Federal Dropship with expert rank insulting a miner, so I targeted it's powerplant and as usual, the dance begun. More than 5(!) kitted out NPC Viper (Elite, Deadly) joined the party and took 5 mins(!) to take out the Federal Dropship with continous fire. Manouvering of big NPC ships are also incredible, again, never seen this before.

I think every players here do know that a minute should be enough to ghost a vessel like this if you're alone, and not more than 30 secs with backing.
Imperial Clipper and Anaconda? Even worse, I don't dare to write down how many minutes needed to ghost them. Oddly enough Pythons aren't involved in this matter.
Funny thing is: depleting their shield was quite easy even in my Cobra with two fixed pulse lasers. But the hull? NPCs used multi and fragment cannons, I used cannons, but no result.
I'm absolutely sure it's some sort of bug.

- Collisions/bumping: Yesterday was my Black Thursday (hmm it really was Thursday) in ED ever since I started playing... I collided a fatty asteroid at RES while doing an evasive manouver (around speed at 200), wasn't direct collision just a side push, that was enough to destroy my Cobra at full shield. Just a side note: it's a fully A-maxed Cobra with additional strenght.
I also had a disagreement with an asteroid in my Python yesterday absolutely the same situation, side bump at same speed ---> insta kill. 4.5m cost...
I don't give a rat &#ss about the money (it's not a complaint for) that can be earned in 1.5 hours by grinding, but this bug is a huge risk.

Let be honest: these things are impossible. I had several unwanted contacts with station inner hulls in my ASP (accidentaly press boost button instead of retracting landing gear (...)), direct hit on the wall at 300-320, low classed shield ---> lost shield and 70% hull, that's all.
My Cobra and Python got hull reinforcement packages, ASPy not. This bug might relate to this new loadout, don't know what else can be.

- Fixed canopy strenght: That's something I still cannot confirm. My Cobra's canopy got damage at hull 95%, 80% is enough to lose it.
- Disable modules: If I lost my shield and around 75% of hull, engine/thruster modules always go offline/disabled for a 5-7 secs, and "always" the key here.
- If my energy weapon got overheated, malfunction happened and it continously was firing if I used throttle (?!). It stopped after a couple of secs.
- Chaff Launcher: simply doesn't work against gimbaled weapons.
- Disappearing astronomical helpers (lines) at Supercruise.

That's all. This post is dragging on too long and you all might put me on KOS list for that, but I'd never had these problems prior to this 1.2.06 update.
I really hope Devs can fix these bugs.
In the meantime I go back to do some trade runs and hope letterbox insta-kill at stations avoids me...

Cheers
 
Last edited:
I seem to have picked up a new bug after the latest update i have some graphical anomalies in the options screen and i am unable to do a clear save is anyone else experiencing this please let me know.

Shar


Update good news im all fixed thanks frontier
 
Last edited:

Nonya

Banned
I work at an IT services company that also has developers. We use the "SCRUM" method to handle coding tasks and basic project management.
Perhaps Frontier is using something similar.
In that case, each "bug" or "fix" is given a certain number of points and how much time it will take to fix by the devs and that kind of determines which bugs get patched first. Same goes for "epics" (big new features). Fixes that are easy to resolve usually get done first unless there's an impediment that has to be resolved first.
Not sure if that's what they're using but it would really surprise me if they're not. It also helps explains why certain bugs you've never heard of get fixed first.
 
Bugs:
- Disappearing astronomical helpers (lines) at Supercruise. <-- yeah i get that too now. didnt happen before 1.2.06 iirc.
- yellow target lock circle shows trough the upper half part of the window frame in my Adder
- Text strings on the BB that are supposed to have $ signs in them are cut off.

Super annoying bugs:
- In about 1/10 interdictions, i get graphical artifacts that causes the window view to flicker and shift, making it impossible to navigate towards the escape vector and i always lose them.
- Collisions/bumping: The guy above kind of just explained what the h.. happened to my ship yesterday. i parked near an asteroid for 5 minutes (needed a quick break) at speed 0, came back to a lost ship and a 9000 CR fine for losing 4 silver i was hauling :(
 
Last edited:
This update seems to have wiped out all my controller bindings. Is there an easy way to get them back or do I just have to set them all up again? Anyone know what file they're stored in?
 
This update seems to have wiped out all my controller bindings. Is there an easy way to get them back or do I just have to set them all up again? Anyone know what file they're stored in?

User/App Data/Frontier Developments/Elite Dangerous/Options/Bindings. (hidden folder).
First load the game assign new settings for your controller then save and quit. This folder got a "Custom binds" file, copy somewhere else because it contains your new settings. Rename the copied file to "mycontroller" or whatever name you wish then copy back into this folder.
Once it's done, start the game, your controller menu has a preset window where your new bind gonna show up. Whatever happens with the custom bind file, you can always select this one and your settings won't be wiped out.
 
Last edited:
I know I shouldn't complain but everytime I login to play I have to download patches which take ages! Its not just that my internet is poor but they don't even download at 100% of my rubbish 1.5 megs its more like 100-500K! I need to login the day before to make sure the game is patched so I can play!
 
User/App Data/Local/Frontier Developments/Elite Dangerous/Options/Bindings. (hidden folder).

Thanks. Had to put them all back in manually but thanks to you I now have a backup:)

Had a few surprises before I got everything right: turned my lights on (or so I thought) and my landing gear deployed instead. Worse, had to run away fast at one point, hit the boost and nothing happened:eek:

Think I've got it all sorted though. Now if only I can work out what happened to the little orange dot in the middle of the screen...
 
Had a few surprises before I got everything right: turned my lights on (or so I thought) and my landing gear deployed instead. Worse, had to run away fast at one point, hit the boost and nothing happened
eek.png

Check your primary and secondary key binds you might added the same to both command.


Think I've got it all sorted though. Now if only I can work out what happened to the little orange dot in the middle of the screen...

Not sure, but that option might be at the mouse settings.
 
Last edited:
Once I knew where to find the bindings file I restored it from a previous Acronis backup. All good now and the orange dot has returned.

Cheers again.
 
Looks like this bug is back:

https://www.youtube.com/watch?v=TRkYYgB6rbA

Today my Clipper exploded in station in similar way :(

reading the youtube comments, it mentions type 7 pilots experiencing this. Can't say I've noticed, but then I don't come in as hard as that - I also make sure I'm lined up with the slot on the approach, in a big ship. Small fighters can get away with approaching offline and swerving through the letterbox, but the type 7 is a closer fit. Clippers, also, have those wide spaced engine pods, so I guess will have to come in pretty much down the middle like a type 9. The one in the video looks like he comes in too high, so he's approaching the slot at an angle. Not that I've flown the anaconda myself, of course.

I have seen quite a few NPC clippers getting taken out by station lasers. I assume this is for loitering, or maybe the NPCs are programmed to forget to get clearance sometimes :) I did once get pretty close to being shot for trespassing, in the Asp. Emergency full astern and backed out just in time - it was late in the evening and I forgot to get docking permission...
 
Last edited:
- Collisions/bumping: Yesterday was my Black Thursday (hmm it really was Thursday) in ED ever since I started playing... I collided a fatty asteroid at RES while doing an evasive manouver (around speed at 200), wasn't direct collision just a side push, that was enough to destroy my Cobra at full shield. Just a side note: it's a fully A-maxed Cobra with additional strenght.
I also had a disagreement with an asteroid in my Python yesterday absolutely the same situation, side bump at same speed ---> insta kill. 4.5m cost...
I don't give a rat &#ss about the money (it's not a complaint for) that can be earned in 1.5 hours by grinding, but this bug is a huge risk.

Cheers

I don't think this is a bug :). An empty, stock anaconda is 400 T (400,000 kg). Going at 200 m/s (i.e. 450 miles per hour), the momentum is 80,000,000 kg.m. In order to get the damage, we have a choice, either look at the impulse (change in momentum over time), or take the ship as a frame of rerefence, and have the asteroid hurtling towards you at 200 m/s. Either way, the ship goes boom :p.

For example, taking a collision time of 0.1s, gives an impulse equivalent to ~800 MW. A class 3 beam laser has a 1.8 MW draw, meaning that the impact is as destructive as having a Class 3 beam laser hitting you non-stop for 7 minutes (I think, I'm a bit rusty to be honest :p)
 
Last edited:
I don't think this is a bug :). An empty, stock anaconda is 400 T (400,000 kg). Going at 200 m/s (i.e. 450 miles per hour), the momentum is 80,000,000 kg.m. In order to get the damage, we have a choice, either look at the impulse (change in momentum over time), or take the ship as a frame of rerefence, and have the asteroid hurtling towards you at 200 m/s. Either way, the ship goes boom :p

I don't have Anaconda. Doesn't matter what ship I fly this issue occurs every time I bump an asteroid. There was no such a sudden death prior to the last update. Shield depleted in a second then RIP.
Of course, it needs to do some damage but not an insta kill on kitted out ships at moderate speed.
Collide someting face to face and side push are two different things.
As you may noticed (if you take a look at the bug reporting forum) several players reported the same plus NPCs are suffering from the very same issue, mainly miners at speed 20-40 m/s. So how could that happen?
Stations aren't involved in this case, at least I didn't experince that (read my ASP story above), but you can find tons of vids about Conda vs letterbox problem, that is something you also cannot explain with momentum and inertia.
 
Last edited:
Status
Thread Closed: Not open for further replies.
Back
Top Bottom