jparnold

You can also assign a joystick button to set and release the parking brake. I have button 11 on my Logitech 3D Pro joystick assigned as I don't want to move the view to that part of the instrument panel just to release it using the mouse.

As far as I know when you purchase MSFS the download is placed onto the selected drive and it runs from there. It is not downloaded to say a download area which you then move or run. M.2 SSD drives are faster than other types of SSD drives and so IMHO you should select a partition on that drive but I would suggest not to the C: drive. You may need to create another partition on the M.s drive and if you don't want to do that then select the other SSD drive for installation. When you download addons they would normally be downloaded to a separate download folder on any drive and then be installed from there. It might depend on where they are downloaded from as some might actually install them direct.

I don't want to labor on this but MSFS shows TACANs as VOR DME yet treats them as a DME (the CDI does not work when the frequency is correct and as such appears to only use them as a DME). That is they 'half' treat them as a TACAN. ALSO the SYMBOL they display is that of a VOR (see below). If MSFS is supposed to be a true flight simulator then surely this needs to be changed so that beginners like me don't get 'trapped'.

Did this happen during the Chagual challenge? Did it happen after a crash? It should never happen. Come on MS and Asboro! It reminds me of an aircraft I had years ago (for FSX) which was given to me (the files that is :D ) which I think had fallen off the back of a truck (if you get my drift) and the outside view showed the aircraft broken into sections obviously due to the fact that the files were damaged when they "fell off the back of the truck" and something (a file?) was missing or 'broken'. Have you reported this?

I too am eagerly awaiting a DH Beaver or Otter.

What a great suggestion. Actually thinking about it I did see a tutorial video on VOR flights which used Sky Vector. I will use that in future. I have learned a lesson - don't rely on MSFS ! :(

Yes to all that. I didn't look at the "DME or GNSS Arrival Procedures". What I am really getting at is the in MSFS2020 the navaids for YMES are as follows - ESL VOR DME 108.100 IES DME 109.500 ESL NDB 350.00 These are what I guess MSFS will use for navigation regardless of the real airport charts. ESL VOR DME 108.100 cannot be used as a VOR which is very misleading. Shouldn't it be then shown as a DME? Or am I not understanding something?

Correct. Moving on I looked at the East Sale (YMES) airport which is a military airport (like YSRI mentioned in earlier posts). Strangely MSFS shows a VOR DME at 108.100 which is NOT shown on any of the airport charts at Air Services Australia which only lists an NDB (also shown in MSFS as an NDB) at 350.0 and a DME (also lshown in MSFS as just a DME) at 109.50. I wonder where MSFS obtained their navigation beacons and frequencies and why some DMEs are shown as just a DME and others incorrectly shown as a VOR/DME instead of just a DME?

Thanks for that information. I need to now know if a VOR/DME can either be BOTH a VOR and DME or simply just a DME? If so how does the pilot know what to expect? If he tunes his NAV radio to the frequency and the CDI doesn't activate he might wonder if the instrument is not operational I notice that on the Airservices Australia webpage it (110.70) is marked on both the ILS-Z OR LOC-Z RWY 28 and NDB-B OR NDB RWY 28 as just a DME which suggests that is is just a DME radio. If this is the case then perhaps it would be better if MSFS displayed it just as a DME and not a VOR/DME which is confusing - well to me anyway.

Interestingly at YSRI the Navaids (in my ERSA book) are listed as ILS/LLZ (IRI) NDB (RIC) and TACAN (RIC) 44x/110.7 and at https://www.airservicesaustralia.com/aip/current/dap/AeroProcChartsTOC.htm#R it is listed simply as a DME. It was mentioned in an earlier post that TACANs are not 'regular' VORs and therefore the (humble) C152 wouldn't be able to pick it up at YSRI. MSFS displays onscreen the TACAN as a VOR/DME yet the CDI is not activated when 110.7 is tuned anywhere (on the ground, in the air etc) and so I assume that this is because in the real world the C152 cannot access TACANs which seems to be great realism. I haven't checked to see if 110.7 will activate the relevant instrument in other aircraft. Regardless MSFS should NOT display it as a VOR/DME!

Thanks Inuss. Firstly I did not click on any knob at first but did so (the NAV1 button) when it wouldn't activate which made no difference. The flight where I was able to activate the CDI at ground level I never clicked on the NAV1 button yet it 'activated' as soon as I swapped the entered frequency to 'active'. Maybe it is selected by default and when using the NAV2 radio then the NAV2 button needs to be pressed. I remember that the nav frequencies have a finite range as I remember creating nav data for airports for FSX and the range was one of the variables.

Thanks David. I feel sure that I did 'return' to the main screen as I don't know of any other way of entering a new flight plan. I may now have the answer. I think (repeat think) that when I completed the first flight I left the NAVLOG displayed on the screen before returning the the main screen which could have (actually should not have) retained the data in the navlog from the first flight. I say this because I tried it again and 'closed' the navlog (X at top right of navlog window) before returning the the main screen and I did not have the same 'problem' as described when creating this thread. Later, when I get some time, I will experiment and see if this is true. It will take flying a complete flight to test exactly so that is now on the back burner. BTW your 'signature' doesn't disclose which country you live in let alone which state/county.

Thanks to you all for your replies. I have got success - read below. If OBS knob only seems to have an effect if the CDI is active (the TO or FROM is displayed and the needles have moved). The TO or FROM was not displayed as previously mentioned. I won't mention any other replies/suggestions as I had tried them all before creating the thread and as I mentioned originally I was able to get the CDI active for (only) ONE flight YBSG (the military airport) to YBWP (commercial airport) with a VOR DME of 112.80 This morning I decided to try again and once again the CDI did not activate when the correct VOR was entered not was there the morse code heard etc etc. Knowing that NDB's are not always picked up unless in the air, I decided to take off. It was not long (about 400 feet altitude) when the CDI activated and the morse code could be heard. I knew that ADF didn't always work unless in the air but did NOT know the same was true for VORs? Searching the internet I find the following - NDB signals follow the curvature of the Earth, so they can be received at much greater distances at lower altitudes, a major advantage over VOR. However, NDB signals are also affected more by atmospheric conditions, mountainous terrain, coastal refraction and electrical storms, particularly at long range. The elevation of YBSG where I took off from is 1560 feet and the VOR is close to being at sea level. Maybe there are mountains in between. Anyway this has been a learning experience albeit a very frustrating one. Thanks again for your replies.

Thanks for your reply and suggestion. YES Richmond is a military airport with TACAN although FS2020 displays a VOR (not TACAN). I also tried other airports in Australia both in the state of NSW and Victoria and Queensland. The only one which worked was the one in far north Queensland. I also tried a flight from YMBA (Mareeba, Queensland) to YBCS (Cairns Queensland which is a normal commercial airport - VOR DME 113.00) which did not work. Also YSLE ( St. Leonards, Victoria) to YMAV (Avalon Victoria which also is a commercial airport VOR DME 116.10) which also doesn't work. Just doesn't make sense. Which chart are you referring to, the airport charts?

This is mighty strange. I just created exactly the same flight as in the video tutorial (San Luis Obispo to Santa Barbara) started the flight and entered the same VOR frequency (112.40) and the CDI came to life displaying NAV and FROM. Why won't it work for me for a flight in Australia between VORs just 15 miles apart? The VOR is the same type (VOR DME) as the one in the video tutorial. I have tried many departures airports with two different destinations. The shortest flight is from YSSY to YSRI (also the reverse flight with different VOR frequency of course). The VOR at YSRI is 110.70 I then tried other places in Australia to set up a short flight to a nearby airport with a VOR. They all resulted in the same HOWEVER I then tried a short flight at the very top of Australia (York Peninsular) from YBSG to YBWP and the VOR (VOR DME) frequency at last worked and the CDI came to life. Why then do FOUR other places all with VOR DME frequencies NOT work? I am spending more time trying to work these thing out as I am in the 'air' which is spoiling the use of FS2020 for me and so I am becoming very frustrated. Any help/advise would be appreciated.

I have decided to try and navigate using the C152 via VOR. I enter my flight plan and note the VOR frequency for the destination airport which is only about 20 miles away so should be within range. I start the flight and the both CDI gauges move quickly during initial display as they initialiase. I enter the VOR frequency for the destination into the NAV1 and then select the swap button so that the frequency becomes the USE/active frequency. The top CDI does NOT move. I watched a tutorial video and I seem to be doing exactly as the author does and the CDI changes as soon as the author selects the USE button. I must be doing something wrong and/or not doing something that I don't notice in the video. I need help. Can anyone advise? Thanks

I have never tried using VNAV either however a quick search of the internet turned up the following which someone replied to saying that VNAV was never implemented into General Aviation aircraft (dated Aug last year so not sure if this has changed with updates since). https://forums.flightsimulator.com/t/tbm-930-vnav/184011 BTW how are threads created at the flightsimulator.com forum?

557 views and no replies? Seems that no one must know.

For anyone wanting small airports in France there are others available at the link given - just click on the Downloads button when you get there.

I completed a VFR flight from YEGG to YORG (Orange NSW) creating the flight plan manually within FS2020. On successful completion I decided to do a completely different VFR flight from YFST (Forster) to YOBR. I created the flight plan within FS2020 selecting YFST as the departure airport and YOBR as the destination. I started the flight and displayed both the VFR map and the NAVLOG. To my frustration the NAVLOG shows the departure as YEGG and YORG as the destination YET the VFR map shows the airports in my new flight plan correctly. How do I reset the navlog to correctly use my newly entered flight plan or have I discovered another bug?

Thanks for that info.

I have now attempted to recreate the bug but cannot BUT each time I retried I landed with out any error and I THINK that just before the situation described I had flown the challenge which resulted in a FAIL. I can't remember the fail message but think it could have been 'you did not land on the correct runway' yet I did land on the correct runway BUT did land on the very front/leading edge on the runway (where the chevrons are) and assumed that because I landed a bit short then it was deemed to be 'not on the correct runway'. It was AFTER this fail and on the next RESTART that the 'problem' occurred and I have been unable to recreate that.

I just had FS2020 do a HUGE 'hiccup' I was doing the Chagual - current live event landing challenge. I did not complete it correctly so selected RESTART. The challenge restarted in the air as expected and the engine was running BUT I could see the prop STATIONARY so I checked the outside view. Not only was the prop stationary but there was a 'growth' on top of the fuselage. Have a look at the screen shot. Comments please. Note I have performed a restart of this challenge BEFORE the latest update and had no problems? Has the latest update introduced a 'bug'?

A quick check of the Australian Ebay site has a few listed but all over $A1300 (£715). I recently (a month ago) checked at my local PC store about a graphic card update and nearly fell over backwards at how much they have gone up in price since I purchased my RTX2060 OC 6GB and was told something which sounded like the reason is caused by a shortage video cards and/or GDDR ram.

I too have 16Gb RAM (and usually get a decent fps with virtually no stuttering) and have considered if I should get more even just another 8Gb however the other day looking at memory usage while MSFS2020 was running it showed that I was using much less than 16Gb (could have been as low as 10Gb) and so I then considered that more RAM would probably have little effect and so I will leave my money in my bank. MS suggest the optimal PC to run FS2020 has 32Gb memory and I wonder why. There must be a reason.