1 hour ago, Speedbird 217 said:

Are moderators still a thing here or have they all left the building for Thanksgiving?
This thread has to be one of the most ridiculous ones in avsim history…and that’s quite an achievement. 

You can simply ignore/not enter the thread. I think its a much better option than MS official forum where every 2nd post is "hidden due to being flagged"... 

In both places, more or less nerdy cranks are at work, virtually experts in highly complex machines. But socially, many seem to suffer from a 'regression bug'.

The veneer of civilization isn't all it's cracked up to be. And that's evident: there as well as here.

Ignoring the usual in house scraps, I just did a flight in this latest beta and it was pretty much Bliss, aside the known issues they were easily ignored. Maybe a few things still to iron out but SU4 is certainly edging closer to release it seems.

1 hour ago, Sonosusto said:

Ignore button is a glorious option. When enough people use it, they'll have no idea why most people dont even respond to them. Its like they vanished.

Unfortunately you still see them when someone else quotes them 😉  

Yes, ignore is a wonderful feature.  I wish I could tape an ignore button to a lot of people's foreheads in real life too 😂

Nice to be nice on Thanksgiving but I don't have a turkey airplane cuz I only fly the HJET.

dd

51 minutes ago, psolk said:

Unfortunately you still see them when someone else quotes them 😉  

Yes, ignore is a wonderful feature.  I wish I could tape an ignore button to a lot of people's foreheads in real life too 😂

Thats fair 😄😁

13 minutes ago, Sky_Pilot071 said:

Nice to be nice on Thanksgiving but I don't have a turkey airplane cuz I only fly the HJET.

dd

It does look like a bird haha. How is holding up in this latest build? I haven't tried it in a few weeks. 

23 minutes ago, Sonosusto said:

Thats fair 😄😁

It does look like a bird haha. How is holding up in this latest build? I haven't tried it in a few weeks. 

Marwan is working his mastery.  Can't wait.

dd

Edited November 27, 2025Nov 27 by Sky_Pilot071

19 minutes ago, Sky_Pilot071 said:

Marwan is working his mastery.  Can't wait.

dd

That and their piaggio and Citation. LOVE their planes

4 hours ago, DavidP said:

I find it truly hard to believe that allegedly "professional" airline pilots would come to Avsim and carry on about a simulator game.

You are only the smartest person in the room when you're the only one in the room.

Some of us grew up on flight simulator. I did. My first was fs98. I came on a sim a long time ago when it was more civil and productive. I still come on here for the fact that breaking FS news is plentiful. Second, I still believe constructive and fun conversations can be had on Flightsim forums. Unfortunately, that’s quickly going away. 
 

I’ll always play Flightsim. It’s turned into art and relaxation for me. A long time ago it was to pretend I was doing what I wanted to do when “I grow up.” 
 

Some of us airline pilots on here sound like complete morons though. I’ve fallen into that category once or twice. 
 

but yeah…I get you lol

13 hours ago, NextGenSimmer said:

Out of curiosity i decided to try in the U.S. 

KEWR, ILS 22R, Fenix A320, Autoland right on the G/S. 

Crossed runway threshold at about 200ft... 

I guess not a Europe thing after all. 

Both runway 22L and 22R at KEWR have significant displaced thresholds which are 1800 feet from the end of the runway. Were you 200 feet above the end of the runway, or the actual threshold (with the white “piano key” markings)?

I have never flown into EWR, but I’ll try tomorrow. 

Depending on how the airport designer created the runway, and what data sources they used, the displaced threshold might not be located correctly. If so, having an accurately placed glideslope transmitter (whose lat/lon is based on FAA data) might actually exacerbate the problem if the runway markings do not exactly correspond to the actual runway in terms of the distance of the displaced threshold from the physical runway end, and the distance from the displaced threshold to the touchdown aiming markings.

I did a flight this evening in the PMDG 777F to KSEA , and did an ILS 34R approach. The aircraft crossed the threshold at 60 feet, and touched down just past the aiming point. 

Just made small test GA flights with this 1.6.30 Beta. The first ones with an empty community and 310.1 DLSS files. All smooth. Enjoyable.

My next test flight was with my usual community (packed of GA Sceneries in Southern California), and still DLSS 310.1. Stutters fest. Pretty much like the two or three previous Beta.

Finally, replaced DLLS with the 310.4 and activate my packed Community. Way way better. Almost no stutters. Only when panning very fast with the Tobii and hard-for-performance areas like downtown San Diego photogrammetry + payware + my bunch of freeware sceneries.

Need further tests (and need to work as well to pay the real flight hours) but very positive and promising.

No issues flying so far with 1.6.30.0 for me with my Aerostar and JF Bonanza/Baron Professional.

On 11/27/2025 at 1:56 PM, Bdub22 said:

Dude, you're insufferable. 

It amazes me how people jump to the wrong conclusion and let hate take control. It was a collective "WE" statement, a humble one. Simply put, we "ALL" tend to overestimate our own qualifications. 

20 hours ago, ahsmatt7 said:

Some of us airline pilots on here sound like complete morons though.

 

Let me understand, because somebody is asking questions, has a different opinion, you think that is appropriate to be offensive? It's not the first time you've shown this kind of poor behaviour. Very disappointing. 

On 11/27/2025 at 11:43 AM, NextGenSimmer said:

Out of curiosity i decided to try in the U.S. 

KEWR, ILS 22R, Fenix A320, Autoland right on the G/S. 

Crossed runway threshold at about 200ft... 

I guess not a Europe thing after all. 

Additional info to my first post.

I tested the G/S threshold crossing height at Asobo default KEWR 22R by spawning on the threshold in the Asobo default G-1000 Cessna 172. I tuned the ILS 22R (110.75) and displayed it on the PFD, then popped out the PFD in its own window so it was visible in slew mode, which only allows an external view. I also enabled the “full” HUD display in external view by selecting it in “Interface Options”. (The PFD altimeter does not work in slew mode, but the HUD altimeter does.)

I entered Slew mode (SHIFT-Z) and slewed straight up until the glideslope diamond centered, and checked my indicated altitude. Initial altitude was 10 feet, and the G/S centered at 55 feet, indicating that the G/S crossed the threshold in a Cessna at 45 feet AGL, which was close to the published value of 50 feet.

This is a test that could be used to check the glide slope accuracy at any MSFS airport.

I did the same test at (default) EDDL 23R featured in Emi’s video linked a few posts above. The G/S crossed the threshold at 60 feet AGL, which is very close to the published TCH of 57 feet.

I do not know if EMI was using the default Asobo EDDL or an add-on, but my conclusion is that there is absolutely nothing wrong with the G/S at either default KEWR 22R or EDDL 23R.

I am assuming the disparity comes from which specific aircraft is being used. I am pretty sure that all the default MSFS aircraft use the standard simconnect variables to indicate localizer and glideslope deviation on the cockpit displays, as does the PMDG 777F, which I fly almost exclusively.

Other add-on aircraft such as the Fenix may  be using a custom implementation of their ILS LOC and G/S subsystem which could lead to the aircraft being too high crossing the threshold with a centered glide slope. I don’t know what specific Airbus model Emi was flying in his video.

And of course, 3rd party airport sceneries may be using custom data for navaids which may (or may not) be accurate to the actual navaids.

 

 

Edited November 28, 2025Nov 28 by JRBarrett