Autopilot+

Quote from Jet-Pack (IPACS)

Thank you for the suggestion. We kind of have our own ideas for a similar feature and just ask ourselves, why stop at just one flight at a time for example... but it's too soon to announce anything, we're just brainstorming and are still collecting ideas. So right now would be a good time for you to specify exactly what you want to have (regardless of what the competition already implemented or not). We need concrete and fresh new ideas not just finger pointing at other products to copy what they are already doing.

I have following suggestion. I hope this helps you:

Activation of feature: A button in the top right menu can activate the feature. If pressed and the requirements are met, there will be a pop-up notification which says: "Background flight successfully saved as "Flight 1" ". Then the user would be able to leave the current flight.

If the requirements are not met,bit would say: "You don't meet the requirements, use of feature not possible".

Requirements: For example: Copilot turned on, altitude at least 5000 ft, a complete navigation route set or something else.

Manage ongoing background flights: In the main menu, there would be a menu called "Background flights". In the menu would be slots for the ongoing background flights. If the user clicks on them, it would show a button to delete the flight, a button to resume the flight and information about the flight, for example a map, which aircraft is used, where it took off and if set, the destination of the flight. If the start button in the main menu is pressed, it won't go to one of the background flights.

In the settings menu, there would be a few settings for this feature:

1. Notifications: The user has the option to be notified via notification if some requirements/circumstances are met, like time to arrival (adjustable), if the plane decents under a specific altitude (adjustable), if the decent starts, if the flaps start lowering or if the plane crashed. This can be adjusted for each flight individually and resets to the state set in the settings, when the flight is done.

2. Auto-pause: The game can, if wanted by the user, automatically pause the flight if some requirements/circumstances are met, like time to arrival (adjustable), if the plane decents under a specific altitude (adjustable), if the decent starts or if the flaps start lowering. This can be adjusted for each flight individually and resets to the state set in the settings, when the flight is done. This feature would allow the user to do for example the landing by himself when he wants, rather than need to do it when the plane is at its destination.

3. Auto deletion: If the user wants, the flight can auto delete itself when it isn't resumed for a week, if the plane crashed or if the plane landed.

Calculation on server: Allows that performance and battery can be saved on users devices and that the user can shut down the device completely.

User account: The user can create a user account to be able to be able to resume flights on other devices.

@IPACS, I would be very grateful for a small feedback. Thank you for reading.

Quote from 747

I have following suggestion. I hope this helps you:

Activation of feature: A button in the top right menu can activate the feature. If pressed and the requirements are met, there will be a pop-up notification which says: "Background flight successfully saved as "Flight 1" ". Then the user would be able to leave the current flight.

If the requirements are not met,bit would say: "You don't meet the requirements, use of feature not possible".

Requirements: For example: Copilot turned on, altitude at least 5000 ft, a complete navigation route set or something else.

Manage ongoing background flights: In the main menu, there would be a menu called "Background flights". In the menu would be slots for the ongoing background flights. If the user clicks on them, it would show a button to delete the flight, a button to resume the flight and information about the flight, for example a map, which aircraft is used, where it took off and if set, the destination of the flight. If the start button in the main menu is pressed, it won't go to one of the background flights.

In the settings menu, there would be a few settings for this feature:

1. Notifications: The user has the option to be notified via notification if some requirements/circumstances are met, like time to arrival (adjustable), if the plane decents under a specific altitude (adjustable), if the decent starts, if the flaps start lowering or if the plane crashed. This can be adjusted for each flight individually and resets to the state set in the settings, when the flight is done.

2. Auto-pause: The game can, if wanted by the user, automatically pause the flight if some requirements/circumstances are met, like time to arrival (adjustable), if the plane decents under a specific altitude (adjustable), if the decent starts or if the flaps start lowering. This can be adjusted for each flight individually and resets to the state set in the settings, when the flight is done.

3. Auto deletion: If the user wants, the flight can auto delete itself when it isn't resumed for a week, if the plane crashed or if the plane landed.

Calculation on server: Allows that performance and battery can be saved on users devices and that the user can shut down the device completely.

User account: The user can create a user account to be able to be able to resume flights on other devices.

Display More

I get what you’re trying to do here, but it feels very similar to features that already exist in other simulators. As Jet mentioned, Aerofly is trying to go in a different direction, and most of these ideas are basically things we’ve already seen elsewhere.

About the auto pause, I honestly don’t see much point in it. It’s a flight simulator. If you need to stop, you can just pause the sim or leave the flight and come back later. We already have that functionality, so adding another system for it just feels unnecessary.

The user account idea is actually something I agree with, but I think it should come together with a proper multiplayer mode. And realistically, that’s probably still far away since IPACS seems focused on other priorities right now.

For the background flights, I do like the idea, but it definitely needs limits. Having just one background flight at a time would make much more sense. Letting people run multiple flights simultaneously would probably be overkill and might even make things confusing.

Now, what the simulator really needs, in my opinion, is multiplayer. That would make a huge difference. Right now, I’m honestly trying not to lose interest. I keep making new routes and liveries just to keep things fresh.

Overall, Aerofly really needs some kind of refresh. Things like a proper rain system, a more realistic atmosphere, and visual improvements would go a long way. If they focused on that and did it right, I think most people wouldn’t even mind waiting a bit longer for multiplayer.

Quote from alvessz

I get what you’re trying to do here, but it feels very similar to features that already exist in other simulators. As Jet mentioned, Aerofly is trying to go in a different direction, and most of these ideas are basically things we’ve already seen elsewhere.

About the auto pause, I honestly don’t see much point in it. It’s a flight simulator. If you need to stop, you can just pause the sim or leave the flight and come back later. We already have that functionality, so adding another system for it just feels unnecessary.

The user account idea is actually something I agree with, but I think it should come together with a proper multiplayer mode. And realistically, that’s probably still far away since IPACS seems focused on other priorities right now.

For the background flights, I do like the idea, but it definitely needs limits. Having just one background flight at a time would make much more sense. Letting people run multiple flights simultaneously would probably be overkill and might even make things confusing.

Now, what the simulator really needs, in my opinion, is multiplayer. That would make a huge difference. Right now, I’m honestly trying not to lose interest. I keep making new routes and liveries just to keep things fresh.

Overall, Aerofly really needs some kind of refresh. Things like a proper rain system, a more realistic atmosphere, and visual improvements would go a long way. If they focused on that and did it right, I think most people wouldn’t even mind waiting a bit longer for multiplayer.

Display More

I get what you’re trying to do here, but it feels very similar to features that already exist in other simulators.

Quote Jan: "We kind of have our own ideas for a similar feature and just ask ourselves, why stop at just one flight at a time for example... He said a similar feature. So I gave a suggestion similar feature.

As Jet mentioned, Aerofly is trying to go in a different direction, and most of these ideas are basically things we’ve already seen elsewhere.

Quote Jan: "regardless of what the competition already implemented or not" I just said how I would do the feature, regardless of what the competition already implemented or not.

About the auto pause, I honestly don’t see much point in it. It’s a flight simulator. If you need to stop, you can just pause the sim or leave the flight and come back later. We already have that functionality, so adding another system for it just feels unnecessary.

The auto pause is meant so that the user can do for example the landing by itself when he wants rather having to do the landing when the plane reaches the airport.

The user account idea is actually something I agree with, but I think it should come together with a proper multiplayer mode. And realistically, that’s probably still far away since IPACS seems focused on other priorities right now.

My post was just a detailed suggestion. Off course the account can also be used for multiplayer or global rankings.

For the background flights, I do like the idea, but it definitely needs limits. Having just one background flight at a time would make much more sense. Letting people run multiple flights simultaneously would probably be overkill and might even make things confusing.

Quote Jan: "We kind of have our own ideas for a similar feature and just ask ourselves, why stop at just one flight at a time for example..." A big part of my suggestion is based on this sentence. But a limit, for example a maximum of three background flights at a time is a good idea.

Now, what the simulator really needs, in my opinion, is multiplayer. That would make a huge difference. Right now.

I don't agree. Features like more weather customizability or weight adjustability and fuel burn for all aircrafts are more important for me.

It's your opinion, let's wait what IPACS says to my suggestion... I will sleep a night over it and I'll see if I can come up with anything else.

The IPACS spokesperson clearly knows how to express himself.