March 18, 201412 yr I have a few problems with my FS2Crew for my NGX. I will list what I know of and you guys can comment on the issues you want to question/answer 1: The F/O never says "Transition level" when he is suppose to. I usually have it at 7000 feet, and I have assured that it is both set correct in DES FORCAST page and PERF INIT page. It is random when he says this. 2: The F/O always get in contact with the cabin crew and says that "the cabin is secured" mid cruise. Shouldn't this happen after I have turned on the seat belt sign? 3: During DES/APP, the F/O always says "we are not stabilized" and "Localizer deviation". And one question: If I want to start with panel state SHORT or LONG, should I then skip to BEFORE START PROCEDURE, and the push RUN PF, or is there another way of doing it? Thanks! Øystein Johansen #25456 Øystein Johansen PMDG NGX - A2A C172 - FS2Crew - Active Sky 2016 - REX Soft Clouds - FTX Norway - Aerosoft airports - Pro ATC X - PTA - precipitFX ASUS Z170-E - Intel i7 6700K @4.5 ghz - ASUS GTX 980ti STRIX 6gb - Corsair Vengeance LPX 2400MHz 8GB - Samsung 850 EVO 500GB SSD
March 19, 201412 yr Author Does someone at least have an answer for the question i have? Øystein Johansen PMDG NGX - A2A C172 - FS2Crew - Active Sky 2016 - REX Soft Clouds - FTX Norway - Aerosoft airports - Pro ATC X - PTA - precipitFX ASUS Z170-E - Intel i7 6700K @4.5 ghz - ASUS GTX 980ti STRIX 6gb - Corsair Vengeance LPX 2400MHz 8GB - Samsung 850 EVO 500GB SSD
March 19, 201412 yr Give it time. The forum has just got back online and not everyone knows about it yet. The "we are not stabilized" and "Localizer deviation" callouts are because you have moved off the path of the localiser This means your not heading towards the runway. The same thing for "We are not stabilized" Windows 7 Ultimate 64-bit | AMD Bulldozer FX 6100 3.9Ghz | H100i | ASUS Motherboard M5A 78L-M | 16GB DDR3 RAM | EVGA Geforce GTX 770 2gb PCI Express DDR3 | 750w Corsair AX750 | 2x 1TB HDD + 180GB SSD | x2 - 24" WideScreen Monitors
March 19, 201412 yr Perhaps you should address your support request directly to the FS2 Crew developers? A Andrew Entwistle
March 19, 201412 yr Perhaps you should address your support request directly to the FS2 Crew developers? A Im sure Brian will reply to this as soon as he can. Windows 7 Ultimate 64-bit | AMD Bulldozer FX 6100 3.9Ghz | H100i | ASUS Motherboard M5A 78L-M | 16GB DDR3 RAM | EVGA Geforce GTX 770 2gb PCI Express DDR3 | 750w Corsair AX750 | 2x 1TB HDD + 180GB SSD | x2 - 24" WideScreen Monitors
March 19, 201412 yr Commercial Member For #1 and #2, you probably have your FS Units of measurement for altitude set to "Meters". It needs to be set to Feet, otherwise any altitude based calls will be totally off. For #3, you're probably not stabilized and you're probably deviating from the loc. Push "Run PF" before calling for the Before Start procedure. Cheers, B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
March 19, 201412 yr Author Thank you for the support! Changing it from metric to hybrid fixed everything. #3 was also fixed. The issue with #3 was that the F/O said "we are not stabilized" and "Localizer deviation" somethimes at 10000 - 5000 feet, when the runways was at 681 feet. The LOC wasn't even on/tuned... Anyway, thanks again Øystein Johansen PMDG NGX - A2A C172 - FS2Crew - Active Sky 2016 - REX Soft Clouds - FTX Norway - Aerosoft airports - Pro ATC X - PTA - precipitFX ASUS Z170-E - Intel i7 6700K @4.5 ghz - ASUS GTX 980ti STRIX 6gb - Corsair Vengeance LPX 2400MHz 8GB - Samsung 850 EVO 500GB SSD
Create an account or sign in to comment