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.

For me, NZTG and Cessna 172 dont like each other.

Featured Replies

Hi all
I have a strange issue with my install of MSFS.
  • The sim freezing then CTD when landing at Tauranga (NZTG) ONLY with a Cessna 172!.
  • It would appear that on my set up ANY Cessna 172 and ANY NZTG dont like each other.
  • I can land with no problem at all other airports I have tried in the Cessna 172 with the WB Sim add-on.
  • Also every other aircraft I have tried is fine landing at NZTG.
  • However if I try to land either the default Cessna 172 or the WB Sim enhanced Cessna 172 I get a freeze then a CTD as soon as the wheels touch the runway at NZTG.
  • This is with NZA Tauranga enabled or removed.
  • Very odd.
  • Note I even did the default Cessna 152 and the WB sims 152 at NZTG with no problems at all.
  • So for me, at the moment the solution is simple (if I wish to fly a Cessna 172 simply avoid NZTG)!
  • This is certainly not a show stopper, but I just thought I would ask If anyone else had a similar issue, or if the wise people hear could offer some guidance .
  • Thanks in advance if you can help.
  • Best wishes.
  • Bob

Have you tried different versions of the 172, liveries and panel configs, to try and isolate the problem?

Cheers

Steve Hall

Hi Bob (!) ... do you have any of the freeware mods for NZTG that might be clashing? I have also have NZA installed, so will give it a whirl. Watch this space!

NZFSIM_Signature_257_60.png

 

The problem is that the OP only has issues with the 172. All other aircraft seem to be ok. It suggests that something is wrong with the 172 rather than sceneries.

Cheers

Steve Hall

I just landing at Nztg with wb sim 172 without issues.

No issues here either - in either runway direction. One thing I did notice, however, is that my ATC fires up a message as soon as I touch down ... could that be a clue?

NZFSIM_Signature_257_60.png

 

  • Author

Hi all

Thanks for the responses and for also testing

Adam.

  • Good to hear from you.
  • I only have the NZA Tauranga and it CTD with this enabled or disabled. so my instinct is it is not NZA Tauranga?
  • Also, last night it also froze then CTD whilst landing at NZCH,so I do think its something with the Cessna 172?
  • I also dont think its the WB sim enhancement as it also froze then CTD with the default Cessna 172.
  • I am wondering if there is a way to uninstall then reinstall a default aircraft? 
  • I may do a google search re uninstalling / reinstalling a default aircraft.
  • Also someone else suggested trying a different skin?  I cant see this making a difference but I may give it a go
    • I only have the default skins so I only have one other to try.
  • It may be something to do with ATC as I have this turned off. (I have always turned this off as I never do what it says and ATC tend to annoy me)

Thanks again for the help and suggestions.

Best wishes.

Bob

 

Edited by rlaycock

No issues here either ...a clean reinstall with NZTG

Just tried the WBSim variant ... no problems either. A few things to try though:

1) It could be a missing sound (tyre screech) ... but then you'd get the problem everywhere <?>.

2) Mesh problem. Have you disabled/removed ORBX NZ mesh? It's now redundant.

3) Check to see if there any other 172-specific mods.

Uninstalling is easy. Just go to Profiles/Content Manager and delete. They will then show as "Uninstalled". Clear your cache, then restart MSFS (maybe reboot the PC as well). You should then be able to re-install them from the Content Manager.

NZFSIM_Signature_257_60.png

 

  • Author
On 7/6/2024 at 6:12 PM, Adamski_NZ said:

Just tried the WBSim variant ... no problems either. A few things to try though:

1) It could be a missing sound (tyre screech) ... but then you'd get the problem everywhere <?>.

2) Mesh problem. Have you disabled/removed ORBX NZ mesh? It's now redundant.

3) Check to see if there any other 172-specific mods.

Uninstalling is easy. Just go to Profiles/Content Manager and delete. They will then show as "Uninstalled". Clear your cache, then restart MSFS (maybe reboot the PC as well). You should then be able to re-install them from the Content Manager.

Hi Adam

  • re missing sound:  I agree I think it would do it at other landings.
  • Re ORBX mesh, I haven't used it since MSFS world update for NZ was released
  • Re other 172 mods:  I do use the Boris sound mod bought via ORBX but it crashes with or without it being enabled.
  • However I am making some progress.
    • I removed just about all NZ freeware scenery add-ons from the community folder and it has made a difference.
    • I am currently re activating them slowly to see if I can identify the one that may be giving me the issue
    • So far I have restored a few that I would be upset if i could not use
      • NZAR-NZNE-NZHN-NZNR.
      • Although I feel it did crash once it would appear to be lot more stable.
  • What I find bizarre is its only with the 172 all other aircraft do not give the issue.
    • But I guess that's software?

Best wishes and thanks again for the advice.

Bob

Edited by rlaycock

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.