146 Professional

I have been trying for several hours to make the thrustlevers work with these LVARs but although I do get some sort of movement the thrustlevers seem to jump straight back to the position I have put them at in the virtual cockpit with the mouse. I have made sure that there are no double axis assignments in MSFS2020 or SPAD.NEXT. I did notice that there are actually three LVAR variants available once MSFS2020 is running: e.g. PED_MID_ENG1_THROTTLE PED_MID_ENG1_THROTTLE_il PED_MID_ENG1_THROTTLE_SHAFT_VC Any more suggestions would be very much appreciated.

We would be happy to work together with FSDT on this if they decided it was something they would like to add to GSX. This would be a decision for FSDT to take though with GSX being their product. Mark - Just Flight

We currently have an update to the UNS-1 in development and we do have a fix for this procedure included in that. This update will be included in both the 146 and F28 once we have tested and approved it for release. Mark - Just Flight

Thanks for reporting this. We have replicated this and we'll pass this on to the UNS-1's development team to investigate further. Mark - Just Flight

Looking at our reference material for the UNS-1 I don't believe this would be possible on the PATH VNAV page. On the real unit, it looks like the VNAV page will only display "@" altitudes (i.e. a fixed altitude for each waypoint). I suspect this is so the UNS-1 can calculate a decent path more easily and doesn't have to factor in if an aircraft is going to be "at or above" or "at and below" a certain altitude at each waypoint. In our simulation of the UNS-1, the PATH VNAV is automatically populated with the waypoints and altitude restrictions on a STAR, and we did add up/down arrows to the altitudes as a quality-of-life addition so that users can more easily see any altitude restrictions without references charts. Mark - Just Flight

We chose to have the airstairs deployed when the "Start Boarding" option is triggered so that passengers would always be able to board the aircraft regardless of whether the gate has a jetway. However, we have logged this on our internal feature request tracker to see if there is a way that we can detect if a gate has a jetway, so that the airstairs only deploy if needed. Mark - Just Flight

Thank you for the feedback. We have logged this on our internal bugs/feature request tracker for our development team to look into. Mark - Just Flight

It likes to do pitch oscillations too, especially at lower speeds. I flew into EGLC now, and on the last legs of the approach as the plane slows down to 210 and then 185, it becomes a veritable lowrider. GS was completely useless so I had to hand-fly the whole thing. At higher speeds it was perfectly fine.

In the mean time if the issue is that you have too many company routes and it is hard to find them in the list, you could add a task in windows to clear out that folder once a day (or each time you log in / start your computer etc) so the folder won't fill up with old flight plans

The beacon lights that we have simulated in the 146 are asynchronous and are based on the type of lights shown in this video: https://youtu.be/WMDocoUILq8?si=WUAZloGVA3SHTpYF&t=187 I do seem to recall that when we researched this there were different flash sequences from aircraft to aircraft, so we just had to pick one of the sequences for our simulation (we have the type that flashes at different speeds so they go in/out of sync with each other). We will log a request to increase the brightness of the beacon lights on out internal feature request tracker. Mark - Just Flight

Yep, it works when i enter 07000, a bit strange and unnecessary complication, but it works.

You are right Mark, described issue does not prevent from using UNS, only visually looks weird.

Mark - thanks for clarification

I dont´t know if this helps, but regarding Axis and Oh´s I have found out that with the current release v0.2.2 the Rudder Axis did not work and i have to set an Event "Axis_Rudde_Set" [image: dd799a0b-cafb-476c-83e0-fbe49746a8ae.jpg] [image: 10d6e978-60a5-445c-9bf3-2898ebca86ad.jpg]

We have a few members of the development team that have both products installed and we aren't seeing any compatibility issues between the two, so I suspect the cause of this may be elsewhere. Typically, the most common cause of our EFBs freezing is a conflict with some other mod in the Community folder (like the Horizon Sim 787. or Heavy Division 787 mods). So the first steps to check if this is the case would be to rename your Community folder to something like "Community.old" and then create a new Community folder named "Community" and install the 146 into it. If you then load the simulator with only the 146 installed and the EFB works, then there must be a conflict with one of the mods in the "Community.old" folder. If the issue continues to persist, or if you would like any further assistance troubleshooting this, please do get in touch Just Flight support via the following link, and our support team will be able to assist: https://www.justflight.com/support Mark - Just Flight

Yes, that is intentional logic. The correct procedure is to switch on the L INNER fuel pump prior to starting the APU, but if it's not switched on the APU can draw its own fuel from the system (the same as the real aircraft). Mark - Just Flight

Thank you for taking the time to to reply, that's good to know. Nice that it is in the tracker, but yes I can agree it's a 'nice to have' - I mainly asked as I was worried that I'd messed up the installation or aircraft config.

Thanks Mark, I'm hoping to hear from you again soon about a possible solution for this problem.

Make sure you do not have anything enable the wheel brakes even a small bit while being moved back, that's what usually makes my planes sit up like a good dog.

Firstly, you will need to have 5 separate, A4 sized .PNG files. If you then go to the …\Community\justflight-aircraft-146\Data\Images\Checklist and …\Community\justflight-aircraft-146\Data\Images\Chart file directories, you should find the .PNG files of the default checklists and charts. The simplest way of getting your documents to appear in the sim, is to give your files the exact same names as the default files, then drag and drop the new files into the folder and overwrite them when prompted. This will mean you don't have to edit the .ini file but your new files will appear in the sim under the same titles as the default files. If you would like to change the order or titles of your files, this can be done in the 146_checklist_list.ini and 146_chart.ini files. In these .ini files, "FILENAME=" is the actual name of the file in the file directory listed in part 2. "DISPLAYNAME=" is the name that will be shown on the INDEX page in the sim for this file. "ATCINFO=0" means no ATC information will be shown at the top left corner of the page. "ATCINFO=1" means ATC information will be shown at the top left corner of the page. If you get stuck, there are some further instructions in the top lines of .ini files that further explain each parameter. We also have some information on how to use the interactive charts and checklists on pages 57-60 of the 146 Professional (MSFS) Operations Manual: https://downloads.justflight.com/products/JFF003642/146_Professional_MSFS_manual.pdf I hope that helps. Mark - Just Flight