Raven, My apologies if it seemed like I was criticizing you or anything, wasn't my intentions . I only quoted your post because you said you had no idea how the OP's sim could descend past 8,000 when yours follows the charts. In my sim, the plane descends past 8000 to whatever altitude I've entered on the control panel. Which lead me to conclude that Navigraph simply didn't put restrictions on the altitudes of the STAR, even though the actual ILS approach does have a restriction. We also weren't suggesting you (or the OP) didn't read the charts, only that when things like this happen (When the approach you select in the FMC doesn't quite hold up to what's on the charts) you use the charts as a supplement. I didn't mean in any way to suggest you didn't have charts, or that you had the constant descent issue. Sorry if it seemed that way.

...

My reply wasnt really directed towards the OP, it was more of a general slightly off topic comment. I do that alot when there's a point being made that I think deserves a further discussion. As for different data in the Navigraph data compared to the actual published FAA data, there are a bunch of examples of that, for example on CAMRN4 the navigraph data suggest HOGGS at FL190 while the FAA tells us to expect HOGGS at FL180 (or lowest usable level). Or the very SUNST2 arrival into KLAS, the speed constraint at NIPZO and SUNST isnt in Navigraphs dataset. There are many, many other similar examples

I see. while I'll re fly this one. And if I let default ATC vector me in. I will end up even lower than planned. ATC from FSX is retarded

I don't know I use default ATC (With editvoicepack) all the time into KLAS Runway 25L and don't have any issues. It hasn't flown me into the mountains yet!!

The problem has to be on my side then. Because the same exact thing happened when I was flying into KGEG (Spokane) and I ended way too low and was 4 red until I came within about a mile from touchdown.