Summary
Since Chapter 7, Battle Royale / Reload / Blitz lets you ADS while jumping/falling for every gun. In UEFN only some guns allow it. Please add a simple on/off toggle in Island Settings so creators can enable mid-air ADS for every gun.
Please select what you are reporting on:
Unreal Editor for Fortnite
What Type of Bug are you experiencing?
Island Settings
Steps to Reproduce
- Place any gun in a UEFN island
- Jump or fall in the air and try to ADS
- Only recently added BR guns work - most others don’t.
Expected Result
A toggle in Island Settings to enable/disable mid-air ADS for all weapons.
Observed Result
Only very few guns (recently added to BR) can ADS in air.
Platform(s)
All platforms
Additional Notes
This has been a popular feature in BR since Chapter 7. Adding it to UEFN would improve parity and enable more varied creative gameplay.
Exact current state in UEFN:
- New Chapter 7 guns and old guns brought back to BR can ADS in air.
- All other guns cannot.
I noticed a similar report here:
https://forums.unrealengine.com/t/cannot-ads-with-some-guns-in-creative/2703725
(Closed as “working as intended”).
To make the request clearer:
In all Epic official modes (Reload, Blitz, etc.), every weapon can ADS mid-air - including old guns from previous chapters.
In UEFN those same older guns still cannot.
If mid-air ADS was limited to only newly added Chapter 7 guns even in Epic’s modes, it would match UEFN.
But since Epic enables it for all guns (old and new) in all their modes, the restriction in UEFN creates a clear inconsistency.
A simple on/off toggle in Island Settings would fully resolve this.
@Flak Could you please take a look at this? Would be much appreciated!
7 Likes
As of Chapter 7 Season 2, even new guns no longer allow mid-air ADS in UEFN.
This highlights the broader issue: UEFN currently doesn’t let creators control mid-air ADS for any weapon, creating inconsistencies with Epic’s official modes and limiting what creators can do.
A simple Island Settings toggle to enable or disable mid-air ADS for all weapons would fully resolve this.
4 Likes
FORT-1074535’s status has changed to ‘Ready for QA’. A member of the QA department is investigating the issue.
1 Like
Any news on this?
This ticket seems to have made it all the way to “A fix has been submitted” and then gone back through the process around 3 times now, and it’s currently back at Ready for QA.
Made this follow-up since the thread closes in 2 days. Would be great if this could get another look and make it through this time. A lot of people have been looking forward to this. @Flak @rhyan.smith
Hi @FeedbackUser,
I took a look at the internal ticket and it has been assigned a release so it will come out soon, after 42.20.
I’m intentionally not mentioning which release it’s assigned to right now in case things change.
Once it is locked in the bot should close the ticket and mention the release version.
I also extended the automatic closing time for the thread
2 Likes
