LSZH V2.5 ERRORS

[newmanix]

So far I have noticed the following problems with the new update. I can get to how much I love the update later.

User and all AI aircraft float above the ground. Maybe an AFCAD dupe now that I think about it which means the old AFCAD is not being overwritten with the new installer. Also I did disable AES which made the old jetbridges go away but some old scenery objects remained.

Please see picture of floating aircraft and old left over objects.

D'

[Saturn_29]

My AI and user planes are fine, but I too have that square thing floating above the new terminal. I also have those glass sqaure things that are in the screenshot in the first post.

(One glass thing is at gate B41 and the other is on the corner of the new terminal to the left of gate B47)

[virtuali]

Floating AI don't have anything to do with the scenery, they are surely caused by another AFCAD in conflict.

To remove the double objects, see if you have an LSZH_ED_TMB_vtr.BGL file in your fsdreamteam\Zurich\scenery folder, and remove it. The 2.5 installer should have removed it, but it didn't for some reason...

[Rafal]

I have three files connected with LSZH_ED_TMB:
- LSZH_ED_TMB
- LSZH_ED_TMB_M
- LSZH_ED_TMB_vtr
Should I remove only the last one?

[swiss1]

After removing LSZH_ED_TMB_vtr,
no floating objects anymore, but isolated jetways at gate 43, 45 (see picture) on the ground.
By the way, Is the folder Zurich_terrain with a Lanclass file still necessary?

Ai aircraft are not floating and perfectly on the ground !

Thanks for this Christmas gift.

[Thorsten_W]

but isolated jetways at gate 43, 45 (see picture) on the ground.

I have the same issue...It seems that the old 'Dock B' jetways are still there.

Thanks for this nice gift, FSDT!

[Dimon]

After removing LSZH_ED_TMB_vtr,
no floating objects anymore, but isolated jetways at gate 43, 45 (see picture) on the ground.
By the way, Is the folder Zurich_terrain with a Lanclass file still necessary?

Ai aircraft are not floating and perfectly on the ground !

Thanks for this Christmas gift.

De-activate AES and it will go away. Version 2.5 isn't AES ready. Yet.

[virtuali]

- LSZH_ED_TMB_vtr
Should I remove only the last one?

Only that one, just as I said.

[flusispieler]

Now Oliver has released a fix for AES v2.14/2.20 for Zürich v2.5.
And he notes that the second gateways aren't moveable, because they cannot be removed by AES.
Why is that?

[virtuali]

It always been like that at Zurich since years, no change with this version, the secondary jetways are part of the terminal, so they can't be excluded.

[Rafal]

just as I said.

No need to be angry.
Just asking.

Have a nice evening!

[flusispieler]

It always been like that at Zurich since years, no change with this version, the secondary jetways are part of the terminal, so they can't be excluded.

Ah ok, thanks for you answer
just out of inteterest:
Why didn't you export the secondary jetways seperated from the termainal?

Merry Christmas!

[virtuali]

Why didn't you export the secondary jetways seperated from the termainal?

Because it's always been like this for the past 4 years since Zurich was initially released, and of course because splitting objects lowers the frame rate. We don't have plans right now to change this, we'll might revisit Zurich again in the future, but that update will be FSX only.

[newmanix]

Why didn't you export the secondary jetways seperated from the termainal?

Because it's always been like this for the past 4 years since Zurich was initially released, and of course because splitting objects lowers the frame rate. We don't have plans right now to change this, we'll might revisit Zurich again in the future, but that update will be FSX only.

Hi Umberto, do have any idea why my aircraft would float? I did a complete search including complete uninstalls looking dor due afcads but none exist and this started only with the new update.

[virtuali]

Hi Umberto, do have any idea why my aircraft would float? I did a complete search including complete uninstalls looking dor due afcads but none exist and this started only with the new update.

Sorry, but it can't be something related to the update, you must sill have some other file from another product hanging around. Problems with floating airplanes are usually caused by another AFCAD, but that's only the most common cause, not the only one, if it's a non-AFCAD .BGL, scanning program won't find it, so you have to search it manually.