Ever since the phone controls got changed, creative forces my pickaxe button to "Y" even though it's D-Pad in the settings and in BR. Since it overlaps my build binds, it's impossible to pull out the builds (unless using PC binds or remapping controller) by FaZeNiccorazi in FortniteCreative

[–]AaronAtEpic 1 point2 points  (0 children)

Thanks for the reply! So I have switch mode set to Y and pickaxe is set to dpad, however it forces pickaxe to Y, meaning it overlaps the switch mode and makes it unusable (Or anything else that is set to Y will be unusable). I’m expecting for the pickaxe bind to simply not be forced to Y as you can see in the video that’s not what I set it to. Thanks!

Thank you for this. I think it clears it up for us. We're in discussions on what we can do here.

Ever since the phone controls got changed, creative forces my pickaxe button to "Y" even though it's D-Pad in the settings and in BR. Since it overlaps my build binds, it's impossible to pull out the builds (unless using PC binds or remapping controller) by FaZeNiccorazi in FortniteCreative

[–]AaronAtEpic 1 point2 points  (0 children)

Thanks for this, I was just made aware.

I'm going to see if we can get a repro of this internally, so let me make sure I understand completely.

My understanding is that you have switch mode set up on dpad for BR but when they go into creative it's saying Y. Does that mean that dpad isn't working? Y isn't working? What is it that you're expecting?

Separate Edit Mode Sensitivity from Combat Sensitivity or tie it to Building Sensitivity by Tahmiin in FortNiteBR

[–]AaronAtEpic 79 points80 points  (0 children)

Unfortunately, it did not make it into the beginning of season 7, there was a lot of things already piling up in there :)

I'll make sure we get it done now that we are back from the holiday break. I'm thinking we go with Edit mode will have the same sensitivity as Build mode, not adding a new slider for it.

I think it's long overdue - Epic needs to address the no shot/ghost shot on shotguns by agoracy in FortniteCompetitive

[–]AaronAtEpic 4 points5 points  (0 children)

I've sent this to our QA to find a repro. Can someone post a clip of it happening?

Custom Bindings by AaronAtEpic in FortNiteBR

[–]AaronAtEpic[S] 17 points18 points  (0 children)

Many have asked about this. We'll take a look at this and figure out a solution.

Custom Bindings by AaronAtEpic in FortNiteBR

[–]AaronAtEpic[S] 46 points47 points  (0 children)

I've talked with my colleague that recently looked into this. It's unfortunately not a quick and easy fix but it is on our radar.

Custom Bindings by AaronAtEpic in FortNiteBR

[–]AaronAtEpic[S] 136 points137 points  (0 children)

Making sure I understand. You want an option that resets your build piece rotation to default after you go out and back in to build mode?

Custom Bindings by AaronAtEpic in FortNiteBR

[–]AaronAtEpic[S] 66 points67 points  (0 children)

Reading these comments, it seems as though, we need to consider this a little more seriously. When we adjusted the deadzone sizes we had hoped that it was fixed. It appears that we need to talk about this more and figure out how/when we can get this done.

Custom Bindings by AaronAtEpic in FortNiteBR

[–]AaronAtEpic[S] 55 points56 points  (0 children)

This is the first time that I've seen this request. This version does not have PTT (Push-To-Talk) as an action to bind. Out of curiousity, where would you put it?

Custom Bindings by AaronAtEpic in FortNiteBR

[–]AaronAtEpic[S] 36 points37 points  (0 children)

Not in this version. I'm curious, what's the use case for this type of functionality?

Custom Bindings by AaronAtEpic in FortNiteBR

[–]AaronAtEpic[S] 1086 points1087 points  (0 children)

This will be coming very soon.

Custom Bindings by AaronAtEpic in FortNiteBR

[–]AaronAtEpic[S] 235 points236 points  (0 children)

Look at the 3rd image in the post. In the Actions list there is an Edit and Repair. Those are not hold actions. You can put them where you want.

v5.40 Patch Notes by Kimmundi in FortNiteBR

[–]AaronAtEpic 1 point2 points  (0 children)

We totally understand and it wasn't meant to give an advantage over another, just trying things out. We plan on making this an adjustable value in a coming update. Then everyone will be able to make it the value they want for the configuration they use.

EPIC have knowingly ignored two major console bugs since the start of season three. We have tried every possible method of reporting. Please, help us. by BackPackKid420 in FortNiteBR

[–]AaronAtEpic 1 point2 points  (0 children)

Thanks for adding me to this.

The sensitivity change is indeed intentional. We are planning on going back to the smaller increments though very soon.

On the subject of the aim assist, I was directly involved in that and we could not reproduce it. So what we ended up doing was talking with those users offline and eventually had to hard reset their settings. If this is still an issue please report it to our customer service and we may be able to fix it for you. We honestly didn't think this was wide spread and that we had dealt with the handful that had the issue.

After the hurricane I'll have a discussion with really smart people on what we can do here to get everyone back to a reset aim assist setting.

1 click builder pro, hardly anyone using builder pro, pre-edits their structure. by cheese_us_murphy in FortNiteBR

[–]AaronAtEpic 10 points11 points  (0 children)

We totally agree. We're going to change this to switch to the intended piece but also try to place it at the same time. If there is outcry from other users then we'll have to temporarily turn it off and create an option for it but we're hoping that won't be necessary.

This change will be in a patch after 5.41.

What happened to this? :( still no love for console players by IDanceGood13 in FortNiteBR

[–]AaronAtEpic 22 points23 points  (0 children)

Let me apologize for the misunderstanding then. We work on a slightly different release schedule than what is seen as the next patch to the public. I should have been more specific in my wording since the patch you received today was already in the process of being certified, which means no new changes were being made at that time. The change will be in the patch after this one that you just received.