First Time Using PACX and First Impressions

Recommended Posts

Hello TFDI,

Had a positive experience using PACX for the first time. There is something great in the making here, and I am sure it will sure prove it's worth. There are some aspects that could do with some rethinking in my opinion, though. I will list them below in subheadings for each menu.

Flight status/Passenger View:

Would like to see each of the icons for the different needs and attributes of the passengers be shown in different colours. What I mean is if a person is male or female, the logo should be blue or pink, or if they're very hungry, the logo shows up as blue. Would look a lot more visually appealing than the current green logos. Also would be cool to see different logos or pictures depending on these needs.

I think it might also be a good idea to have a manual override for the different stages of flight. Good option to get things back on track if your FS or PACX decides you've landed at 35,000 feet.


I don't like the current UI for settings. The "auto-hide delay" option is likely to be the most used option, and I think on the main ui page there should be a toggle to turn off or on auto hide. The auto hide is likely to be kept on while people are entering data into the flight planning page, while people double check their flight time, number of pax etc. on a different tab. The current process is really tedious, as it is quite easy to forget to scroll to the bottom of the page to apply the settings, especially considering the current option is within eyesight once immediately opening the menu. Most menus with an "apply" button have that button visible at all times on the menu page. Given this, I would just remove that button.

Flight Planning Page:

Generally with the menu, I was confused at how to format some of the information to be used by the program. eg. Should flight time by 90 or 1:30? Should Cruise Altitude be FL350 or 35,000? Either include in the title or add little tooltips to give people a hand filling this out. 

Also, I found that if I clicked OK without a valid input, I would not be able to exit the page, with the "Cancel" and "OK" buttons dimming a little. I don't know if I'm doing something wrong here, but have a check of that.

When typing in the ICAO codes, they should be capitalised. If possible, they could also give the name of the airport.

I think time until takeoff should be replaced be the Scheduled time of departure, this makes it easier to copy a real-life schedule, especially considering these schedules consider the time to leave the gate. Given this, scheduled time of arrival would also make sense, instead of flight time. The estimated flight time could be calculated comparing these two times.

I'm guessing there are so many little things that you guys are itching to add in and us simmers are itching to see, but here are my two cents about you guys can create a really strong foundation for a product I can't wait to see develop.


Share this post

Link to post
Share on other sites

@ghant312 I've responded to each item below.

  • Regarding the in-flight status icons: I agree and we'll see about expanding this in the future.
  • Regarding the manual override: this doesn't really agree with the way the program is designed, but I understand your point. Are you experiencing issues with PACX not detecting your flight phase properly? There is code built in to handle reject takeoff, go-arounds, etc.
  • Regarding settings, I agree. There is a bit of an issue with the apply button not being easily found. It used to be instant (the second it was changed, it applied), but some settings required more validation.
  • The formats are pretty open for the start flight page. Times can be entered as hh:mm, hhmm, #.#, or just minutes. The same is true for flight levels: you can enter it as FL###, #####, ### (which will automatically become a flight level). It's built to handle input in as many formats as possible.
  • The Cancel and OK buttons remaining disabled is a bug. I just corrected it in my version and it will be resolved in the next build.
  • I agree. I've made the departure ICAO, arrival ICAO, and flight number box automatically capitalized.
  • Part of why we did the time until takeoff and flight time options is because it became difficult to associate the simulator time with an actual time. The only way we could reliable handle this would be to make it based on system time.

Thank you for the feedback! We're actively trying to improve the product, and feedback like this helps us.

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.