Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Fenix V2 B1 Released

Featured Replies

53 minutes ago, jarmstro said:

No issues with V2. It's easy to fly. Even with the misaligned IRS coming into  Naples eastbound RW 06. I wish I could remember where I bought this airport so I could raise a ticket. Not that the dev would do anything about it. Or is it Navigraph or the Fenix?

did you mean ILS , and i think 06 at LIRN is an offset ILS isnt it ?

ROG Crossair Hero X670e , 9900X, TUF 4090 , X4 NVME's. OS  2TB 980 Pro , MSFS  2TB WD Black , Kington Fury 64GB ram ( 6000) Corsair RM1000 PSU, Artic Freezer iii 360 AIO  . Phanteks P600s Case ,TCL QM8B 50" 120 Hz  TV,second 24 inch screen for charts you tube etc, and 11" touch screen for the EFB. Warthog Stick and TCA Captains throttle ( full pack)  Velocity 1 Rudder Pedals , extreme3D for the Tiller,Streamdeck XL x2 / Streamdeck +/Streamdeck mini because i like pressing buttons 

  • Replies 307
  • Views 52.9k
  • Created
  • Last Reply

I must say I’m really enjoy 2.0 . The only thing I miss is basic WX radar for immersive purposes 

Life time flight sim enthusiast, current airplane owner 172P (past C182F). FAA CP/IR ASEL/AMEL, FI ASEL

My System: AMD Ryzen 9 9950X3D , MSI X870 GAMING PLUS, 64G RAM, ASUS RTX5090, 4T SSD

Put my hands on (pic/dual/given)

7GCAA, 8KCAB, BE24, BE76, BE35-C33, BE35, C150, C152, C172B/N/P/R/SP, 182F, M20E,M20C, M20J, AT6(SNJ4), PA28-140,PA28-151, PA28-161,PA28-181,PA28RT-201,PA28R-180/201T, PA24-250, PA32-300R, PA44, AC114, YAK-18T, YAK-52, SR22

 

20 minutes ago, sd_flyer said:

I must say I’m really enjoy 2.0 . The only thing I miss is basic WX radar for immersive purposes 

Send Asobo and email...😉

 

 

 

22 hours ago, leonbr said:

Has anyone tested how is the performance compared to the 737 from PMDG? According to the official slides, the performance would be on par, but how is it in reality, with AI Traffic and third-party airports? What still holds me back from purchasing this plane is some reports here of low FPS.

 

22 hours ago, vrdubin6 said:

Specs in signature.

Verticalsim KBOI with FSLTL traffic. Same exact scenario. 4k everything ultra with 200 TLOD.

PMDG: 102 FPS

Fenix: 99 FPS

Fenix used to be about 80 FPS and noticeably choppier. In my experience they now both feel the exact same in regards to fluidity.

Results with my low end system (8700k, 1080TI) in an average testing scenario:

PMDG 38 FPS

FenixV2 39 FPS

FenixV1 35 FPS.

 

2 minutes ago, RALF9636 said:

 

Results with my low end system (8700k, 1080TI) in an average testing scenario:

PMDG 38 FPS

FenixV2 39 FPS

FenixV1 35 FPS.

 

And the Fenix has an EFB    😉

 

 

 

41 minutes ago, Bobsk8 said:

Send Asobo and email...😉

Why? Tory already have API for basic radar 

Life time flight sim enthusiast, current airplane owner 172P (past C182F). FAA CP/IR ASEL/AMEL, FI ASEL

My System: AMD Ryzen 9 9950X3D , MSI X870 GAMING PLUS, 64G RAM, ASUS RTX5090, 4T SSD

Put my hands on (pic/dual/given)

7GCAA, 8KCAB, BE24, BE76, BE35-C33, BE35, C150, C152, C172B/N/P/R/SP, 182F, M20E,M20C, M20J, AT6(SNJ4), PA28-140,PA28-151, PA28-161,PA28-181,PA28RT-201,PA28R-180/201T, PA24-250, PA32-300R, PA44, AC114, YAK-18T, YAK-52, SR22

 

1 minute ago, sd_flyer said:

Why? Tory already have API for basic radar 

Who is Tory?

 

 

 

 

2 hours ago, Bobsk8 said:

Who is Tory?

 

Sorry Asobo. I was typing on the phone (while walking) LOL

Life time flight sim enthusiast, current airplane owner 172P (past C182F). FAA CP/IR ASEL/AMEL, FI ASEL

My System: AMD Ryzen 9 9950X3D , MSI X870 GAMING PLUS, 64G RAM, ASUS RTX5090, 4T SSD

Put my hands on (pic/dual/given)

7GCAA, 8KCAB, BE24, BE76, BE35-C33, BE35, C150, C152, C172B/N/P/R/SP, 182F, M20E,M20C, M20J, AT6(SNJ4), PA28-140,PA28-151, PA28-161,PA28-181,PA28RT-201,PA28R-180/201T, PA24-250, PA32-300R, PA44, AC114, YAK-18T, YAK-52, SR22

 

I don’t think the API is for Wx Radar…. rather for NEXRAD. I too would love accurate Wx depictions, but we are still working on accurate Wx…

Best-

Carl Avari-Cooper

18 hours ago, jarmstro said:

No issues with V2. It's easy to fly. Even with the misaligned IRS coming into  Naples eastbound RW 06. I wish I could remember where I bought this airport so I could raise a ticket. Not that the dev would do anything about it. Or is it Navigraph or the Fenix?

It’s not a bug, nor something that needs to be fixed. The runway 6 ILS at LIRN is not misaligned due to an error in the scenery or any add-on aircraft.

The r/w localizer is deliberately offset 3 degrees to the right of the runway centerline. This is annotated on the r/w approach chart.

The reason they do that is because of the 1745-foot hill that sits just to the left of the extended centerline 4.5 miles from the threshold. If the localizer was perfectly aligned with the runway centerline, aircraft would come too close to that hill for safe terrain clearance. 

Jim Barrett

Licensed Airframe & Powerplant Mechanic, Avionics, Electrical & Air Data Systems Specialist. Qualified on: Falcon 900, CRJ-200, Dornier 328-100, Hawker 850XP and 1000, Lear 35, 45, 55 and 60, Gulfstream IV and 550, Embraer 135, Beech Premiere and 400A, MD-80.

11 minutes ago, JRBarrett said:

It’s not a bug, nor something that needs to be fixed. The runway 6 ILS at LIRN is not misaligned due to an error in the scenery or any add-on aircraft.

The r/w localizer is deliberately offset 3 degrees to the right of the runway centerline. This is annotated on the r/w approach chart.

The reason they do that is because of the 1745-foot hill that sits just to the left of the extended centerline 4.5 miles from the threshold. If the localizer was perfectly aligned with the runway centerline, aircraft would come too close to that hill for safe terrain clearance. 

That is why it pays to look at the approach plate. 

 

 

 

1 hour ago, JRBarrett said:

It’s not a bug, nor something that needs to be fixed. The runway 6 ILS at LIRN is not misaligned due to an error in the scenery or any add-on aircraft.

The r/w localizer is deliberately offset 3 degrees to the right of the runway centerline. This is annotated on the r/w approach chart.

The reason they do that is because of the 1745-foot hill that sits just to the left of the extended centerline 4.5 miles from the threshold. If the localizer was perfectly aligned with the runway centerline, aircraft would come too close to that hill for safe terrain clearance. 

Ah! Thanks so much for the clarification.  I've never heard of such a thing before? I'll have to read up on the normal landing procedure Ie at which point do you deviate from the ILS track and line up with the runway?

Edited by jarmstro

42 minutes ago, jarmstro said:

Ah! Thanks so much for the clarification.  I've never heard of such a thing before? I'll have to read up on the normal landing procedure Ie at which point do you deviate from the ILS track and line up with the runway?

When visual with the runway and the area and clear of the obstacle.

45 minutes ago, jarmstro said:

Ah! Thanks so much for the clarification.  I've never heard of such a thing before? I'll have to read up on the normal landing procedure Ie at which point do you deviate from the ILS track and line up with the runway?

Usually when a localizer is offset, it will cross the runway centerline at the point where you arrive at the missed approach altitude. Just a matter of making a slight turn at that point to align with the runway.

Localizers can be offset for a variety of reasons. Sometimes it is done for terrain clearance as with the ILS06 at LIRN.

Sometimes it is done for technical reasons. Runway 22R at KJFK is offset 2.5 degrees, because if they had tried to build the localizer antenna directly on the runway centerline, it would have had to been constructed in the water of the bay that is right beyond the threshold at the opposite end.

The most extreme offset in the US is the LDA 19 approach at KDCA, which is offset by almost 40 degrees. There is no glideslope - it is a localizer only. That is done to keep arriving aircraft out of the restricted airspace over the center of Washington DC. That approach has high minimums and requires a substantial right turn (in visual conditions) when arriving at the MDA to align with the runway.

Edited by JRBarrett

Jim Barrett

Licensed Airframe & Powerplant Mechanic, Avionics, Electrical & Air Data Systems Specialist. Qualified on: Falcon 900, CRJ-200, Dornier 328-100, Hawker 850XP and 1000, Lear 35, 45, 55 and 60, Gulfstream IV and 550, Embraer 135, Beech Premiere and 400A, MD-80.

51 minutes ago, jarmstro said:

Ah! Thanks so much for the clarification.  I've never heard of such a thing before?

Kai Tak and the famous IGS13?

Best regards,
Luis Hernández 20px-Flag_of_Colombia.svg.png20px-Flag_of_Argentina.svg.png

Main rig: self built, AMD Ryzen 7 5700X3D (with SMT off and CO -50 mV), 2x16 GB DDR4-3200 RAM, Nvidia RTX 5060Ti 16GB, 256 GB M.2 SSD (OS+apps) + 2x1 TB SATA III SSD (sims) + 1 TB 7200 rpm HDD (storage), ID-Cooling SE-224-XTS air cooler, Viewsonic VX2458-MHD 1920x1080@120-144 Hz (G-sync compatible), Windows 11. Running P3D v5.4 (with v4.5 scenery objects as an additional library, just in case), FSX-SE, MSFS2020, MSFS2024 and even FS9! Lossless Scaling for all my sims. What a godsend...

Mobile rig: ASUS Zenbook UM425QA (AMD Ryzen 7 5800H APU @3.2 GHz and boost disabled, 1 TB M.2 SSD, 16 GB RAM, Windows 11 Pro). Running FS9 there .

VKB Gladiator NXT Premium Left + GNX THQ as primary controllers. Xbox Series X|S wireless controller as standby/mobile.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.