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.

Su 4 Beta

Featured Replies

13 hours ago, micstatic said:

just want to confirm something.  I use addon linker to manage my community folder.  Assume if I make no changes then this new update will not change anything?  IE, if I don't use this new folder then nothing will change.  I also don't really use marketplace for anything if that matters.  

That was my very first question. 😁

7800+4090+64ram

Just Flight RJ, 146 and F28, Piper Arrows ---A2A Aerostar and Comanche---Black Square Starship, Duke(s), TBM, Bonanza/BaronV2, KingAir---FSReborn FSR500---COWS Da42---FX P180, HJet & VJet---FlySimWare Chancellor and LearJet---FlightSimStudio EMB175 &P2006T---Fenix 320---PMDG DC6, 737(700+900), 777---C22J---Milviz Cessna 310 & Porter---SimWorksStudios Kodiak, PC12, Zenith & RV14---BigRadials Goose---IndiaFoxEcho MB3339+F35.

 

  • Replies 330
  • Views 48.8k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • It. Is. A. BETA.

  • Hello @PlumCrazy, Developers do indeed have access to new builds before they're released to the public. They get this access by opting into the beta. These pre-release builds are not "early acces

  • The only constant is the whining hyperbole. 

1 minute ago, Sonosusto said:

That was my very first question. 😁

Yes it worked fine for me. I didn’t make any changes and things loaded fine (I only have 2024 installed). The only addon not working for me is the simbrief app for the EFB. It just doesn’t show up, but the navigraph and fenix apps both work as normal. 

9800X3d, 4090, 64 GB DDR5 6000 RAM, 4 TB NVME (2x2), 4K Ultra + Framegen

GSX can't seem to read jetway data anymore, not sure if that's related to the community folder changes or something else.

Edited by Tuskin38

And now after flying the fenix for a while my controller bindings are wonky. I can't figure out how to do reverse thrust. I see that "cut" is now previous indent but nothing is working. Wow. Patience is zero. If anyone can explain it to me like I am 5 that would be great. 

7800+4090+64ram

Just Flight RJ, 146 and F28, Piper Arrows ---A2A Aerostar and Comanche---Black Square Starship, Duke(s), TBM, Bonanza/BaronV2, KingAir---FSReborn FSR500---COWS Da42---FX P180, HJet & VJet---FlySimWare Chancellor and LearJet---FlightSimStudio EMB175 &P2006T---Fenix 320---PMDG DC6, 737(700+900), 777---C22J---Milviz Cessna 310 & Porter---SimWorksStudios Kodiak, PC12, Zenith & RV14---BigRadials Goose---IndiaFoxEcho MB3339+F35.

 

47 minutes ago, Tuskin38 said:

GSX can't seem to read jetway data anymore, not sure if that's related to the community folder changes or something else.

Yes, I got the same (tried iniBuilds EGLL and Pyreegue EGPH).
Stair only stands (ORBX YMML) seemed to be OK (no GSX errors reported).

I tried activating the jetway from the Fenix EFB but that didnt seem to work either.


The other thing I noticed at EGLL was that for the first time, BATC didnt seem to be able to create any static traffic (correct SB FP was loaded), but at EGPH and YMML, had no problems creating traffic.

Edited by c912039

They added new small autogen power line models. 

SFQfUWk.png

OukfsNp.png

 

This is what they looked like in SU3 and before

07ZKwWK.png

 

New high voltage models too

SU4

Japu5Mz.png

SU3

ciT0Wce.png

Edited by Tuskin38

6 hours ago, Lucky38i said:

It just seems odd to be to opt-into a beta program and expect a seamless experience. Beta periods by general defintion is for.. bug fixing.

Exactly. But we go through this every time a beta is released. 

Folks who want to keep using all of their addons should stick with the stable release versions. 

Case closed. 

2 hours ago, Tuskin38 said:

they seem to have made shadows switch to lower quality

Ugh, was afraid that would happen as part of the “optimization”  … hopefully there is an option to overcome it?

Edited by SayAgain

Extraordinary claims require extraordinary evidence. - Carl Sagan

7 hours ago, Vitold69 said:

I can't load the plane even. Sim hangs during loading

Thanks for letting me know Vito.

SN737

1 hour ago, Ricardo41 said:

Exactly. But we go through this every time a beta is released. 

Folks who want to keep using all of their addons should stick with the stable release versions. 

Case closed. 

Yes true. Half dont work but its nice flying the fenix with better performance. 

7800+4090+64ram

Just Flight RJ, 146 and F28, Piper Arrows ---A2A Aerostar and Comanche---Black Square Starship, Duke(s), TBM, Bonanza/BaronV2, KingAir---FSReborn FSR500---COWS Da42---FX P180, HJet & VJet---FlySimWare Chancellor and LearJet---FlightSimStudio EMB175 &P2006T---Fenix 320---PMDG DC6, 737(700+900), 777---C22J---Milviz Cessna 310 & Porter---SimWorksStudios Kodiak, PC12, Zenith & RV14---BigRadials Goose---IndiaFoxEcho MB3339+F35.

 

5 hours ago, SayAgain said:

The problem here is that most developers will NOT do a lot of work on their products to make them work with Beta updates because they are Beta and a lot can change between each beta update and then final Release (aka not Beta).

Just not enough development resources to re-test everything on each beta update, hence waiting for final release to start work on testing one’s product.  Can be pretty expensive to do a lot of adjustments on early Beta updates only to have to undo them in later Beta updates because of impacting changes.

You see that sentiment reiterated on numerous add-on content developer’s public websites and non-public. 

Exactly this. I know that PMDG (for example) will not release an update to their existing fleet of aircraft just to make them work with an MSFS beta. Nor should they. The goalposts keep moving with each new beta update. It is my understanding that some (but not all) WASM aircraft have been broken by this initial release of SU4 beta.

The PMDG 777s will not activate, and I believe a similar problem exists with the IFly 737Max. But other aircraft that use WASM (like the Fenix) appear to be working. The release notes for the initial SU4 beta state that Asobo made changes to WASM. Perhaps those changes are affecting the activation code that PMDG and IFly are currently using - or maybe it is a bug on Asobo’s side.

I seem to recall that a similar activation problem (affecting PMDG specifically) cropped up in the early SU3 beta builds, that Asobo was able to fix on their end without PMDG having to make any changes to their existing released aircraft. 

On the other hand, if the changes that Asobo made to WASM will require that PMDG’s activation code has to be permanently changed to be compatible with the latest SDK, then I wouldn’t expect them to make their aircraft SU4-compatible until SU4 is officially released. 

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.

Every dev that chooses to work on the MSFS platform knows they're going to be working with a constantly evolving beast. Yes, it's more work but the benefit if having access to the biggest market in the flight sim space. It is what it is.

5800X3D. 32 GB RAM. 1TB SATA SSD. 3TB HDD. RX  9070XT.

We are all connected..... To each other, biologically...... To the Earth, chemically...... To the rest of the Universe atomically.
 
Devons rig
Intel Core i5 13600K @ 5.1GHz / G.SKILL Trident Z5 RGB Series Ram 64GB / GIGABYTE GeForce RTX 4070 Ti GAMING OC 12G Graphics Card / Sound Blaster Z / Meta Quest 2 VR Headset / Klipsch® Promedia 2.1 Computer Speakers / ASUS ROG SWIFT PG279Q ‑ 27" IPS LED Monitor ‑ QHD / 1x Samsung SSD 850 EVO 500GB / 2x Samsung SSD 860 EVO 1TB /  1x Samsung - 970 EVO Plus 2TB NVMe /  1x Samsung 980 NVMe 1TB / 2 other regular hd's with up to 10 terabyte capacity / Windows 11 Pro 64-bit / Gigabyte Z790 Aorus Elite AX Motherboard LGA 1700 DDR5
7 hours ago, monica6211 said:

My mouse is working just fine in VR, Reverb G2, Oasis driver

It appears to be strangely random, other people using that oasis driver with their G2 can't see the mouse either. Seems to be a VR controller issue to me, hope they get it fixed soon either way as the games unusable now.

Edited by MarcG

Pico Neo3 Link VR - Windows 11 64bit, Gigabyte Z590 Aorus Elite Mobo, i7-10700KF CPU, Gigabyte RX 9070 XT OC 16gb (AMD GPU), 32gig Corsair 3600mhz RAM, SSD x2 + M.2 SSD 1tb x1

Saitek X45 HOTAS - Saitek Pro Rudder Pedals - Logitech Flight Yoke - Homemade 3 Button & 8-directional Joystick Box, SNES Controller (used as a Button Box - Additional USB Numpad (used as a Button Box)

Create an account or sign in to comment

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.