New Zealand South Island Bush Trip Leg 3 Can’t Be Completed - NZWE Not Available

Hello to each other,

You don’t need to keep trying to finish the trip, no one will succeed. NZWE is now called NZ17, the airport has been renamed but the BT has not been adjusted to the new name. MSFS does not recognize with this that the leg has been completed. I can only wait until the BT has been updated.

Greetings, Koschi

1 Like

Thanks Koschi

I have the same problem. I followed the route and can land fine but there is no option to progress to the next stage. Obviously the developer failed to test the software to avoid this very obvious bug.

Hi SC489.

The developer of the bush trip is not to blame. If MS/Asobo releases a new update and changes ICAOs or names of airports, there is no information about it. I myself have created many bush trips and only find out through the users if something is wrong in this matter. I cannot test all BTs after each update. I don’t have the time for that. I hope the creator of the BT reads this and can react accordingly. Unfortunately, I have no idea who the creator of this BT is, which is the issue here.

Greetings, Koschi

It’s the responsibility of MS to manage and sort out such issues for bush trips bundled as standard with the game

1 Like

Do you have the same issue if you follow the OP’s steps to reproduce it?

yes same issue, thankyou for perfect description, guess just have to wait for fix…

Provide extra information to complete the original description of the issue:

Correctly described

If relevant, provide additional screenshots/video:

I’ve got the same prom, no solution yet?

Same problem here. Even if you manage successfully to land on NZ17 the leg is not registered as completed and a restart bumps you back 10,000+ ft over Lake Ellery. That happens even if you instead continue follow the route to NZGT or even NZHK - no credit for accomplishing legs 4 and 5.

Just download the Neils Beach Airstrip from flightsim.to and it should work fine.

2 Likes

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

no airport named NZWE

If relevant, provide additional screenshots/video:

Bush Trip leg will not register at NZWE

Same issue here today with latest SU at this date. NZWE does not register and also continue flying to the next airport per GPS does not complete leg 3 or 4. A shame, same happened to me on the Pyrenees bush trip just a week ago.

Do you have the same issue if you follow the OP’s steps to reproduce it?

Same issue, leg 3 does not let you land at NZ17 to complete it, although the VFR map correctly shows where the trip continues past Lake Ellery

Provide extra information to complete the original description of the issue:

The Navlog lists the next waypoint as “NZWE”, although the instruction (08) tells you to "continue and land at Neils Beach airport. Actually landing there does not trigger the completion of Leg 3.

When resuming the bush trip, one is dropped over Lake Ellery, and the VFR map skips NZ17, and the next waypoint is the first one on Leg 3. In fact, if one continues to follow the GPS waypoints , I am afraid that it probably takes you all the way to… NZWE, whicjh is Auckland’s airport at the most norther point of the … North Island !..

See screenshots

If relevant, provide additional screenshots/video:

Navlog - last stage end NZ17 skipped

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

I had the same problem. I tried stopping at every point in the area of Neil’s Beach airstrip but it wouldn’t register. I tried continuing on to the next waypoint. I even tried landing on Lake Ellery at the spot that the simulator showed as my last waypoint but it still didn’t register. It would always just continue above the lake. The trip disappeared after one update and reappeared after the next one but it still can’t be completed.

1 Like

All users are affected simply because the ident of the airport has been changed. I have adjusted the relevant files and made them available to download:

Unfortunately, it is only possible to replace the files on the PC, so it is not possible for me to offer this for the Xbox users as well. All apologies.

2 Likes

Hi @BuffyGC
Thanks for this, worked like a charm.

Wonder how was this adjusted, are you using any tool to adjust this?
Asking since we have same problem on Bushtrip Pyrenees Excursion.

But i saw you already provided a fix on the Pyrenees Excursion thread

Once again thanks for it, but i wonder if this is something we can fix ourselves with some specific tool.

Hi
yes of course I use tools to make it easier for myself, but I don’t know of a one-click tool either.

The individual steps that I perform:

  1. PLN file: Replace the waypoint ids ATCWaypoint and ICAOIdent. A replace-all is not possible. I do this with Notepad.
  2. FLT file: Replace the waypoints, but not other things such as references to language entries, images or sound files. I also use Notepad here
  3. Decompile SPB file to xml file. You can use any SPB2XML decompiler (available on Github and other freeware sites). I use my BushTripInjector for this, it also contains an SPB decompiler and I don’t need another tool for this.
  4. Replace the relevant Ids with Notepad. But beware: replace-all does not work here either, only the waypoint and airport Ids may be changed.
  5. Compile the changed xml-file to a SPB: You can use the normal SDK of the simulator or the fspackage-tool. I also use the BushTripInjector here, as I have it anyway and therefore don’t need any other tools. In both cases, however, you need a compilable project (according to the MSFS SDK guidelines or a BIT project), which you may have to create first.

As you can see, it’s always easy if you know how to do it. If you don’t know, everything written above sounds very complicated. All in all, it takes me longer to test if everything is correct than it does to make the changes. With the Pyrenees, for example, you can see that the SPB is 15 minutes younger. I had previously forgotten an entry and only noticed this when testing.

Happy New Year
BuffyGC

Do you have the same issue if you follow the OP’s steps to reproduce it?

YES

Provide extra information to complete the original description of the issue:

Same issue, landed at location provided by NAVLOG and GPS location is exact good. Filename is NOT NZWE but in garmin NZ17

If relevant, provide additional screenshots/video:


strong text