Vienna Version 2.5 (FSX & P3D2)

[martin[flytampa]]

Fixed spacing between TL39/49. This is in the 2.5 update/Installer. If you update before Dec 23 just redownload the Update.

[trainler]

Wow that was quick. Many many thanks

[Joker767]

Hi Martin,

thank you for your detailed report + this hotfix for the taxilanes - that was really fast. Already tested it and now this looks great

Thank you very much again - merry christmas & happy new year.

[Delta777]

And here comes AES v2.34 supporting Vienna v2.5:

http://forum.aerosoft.com/index.php?/to ... n-in-2013/

[Gordon1985]

Fixed spacing between TL39/49. This is in the 2.5 update/Installer. If you update before Dec 23 just redownload the Update.

Has the v2.5 installer from Simmarket been updated?

Thanks

[gianluca311]

Couple of notes

- When V 2.0 and Skylink were first build by us, there was no final aerial imagery avail so we had to hand paint the apron and markings. Thats why most of that area isn't very precise and none of the lines were changed for 2.5. For the next version I'll revisit this thread and see about tweaking the Skylink area.

- The Skylink parking charts I noticed during the update, but I have no good way of making it work with respect to AI. Overlapping small gates onto a heavy gate like in real like is not an option. If we ignore all the south side small gates (F03,F09,F11,F17 etc) and place only heavy gates, we end up reducing the amount of parking because the jetway bridges F09, F17.. become useless. Pulling all the parking closer to the terminal I worry will result in medium and small (if they park at the heavy gate) getting their wings clipped by the secondary jetways (which are static). What I mean is I looked at the chart and saw a nightmare to get working, so it was left the same as V2.0

- H41, and others like C38, D26, F43 etc are missing because they overlap with gates next to it. It is possible to squeeze them into the Afcad by changing the sizes of some other gates, but may result in messy AI positioning.

- Because this update started as a P3D compatibility patch and turned into a little more, "Alternative Rwy Lights" were not considered, since navlights don't work in P3D2. The old V2 used default Afacad for runway lighting which were faded through the ground imagery and people complained were too dim. I know the new lights have issues, but are the best thing I have at this moment. Btw, the lights can be forced on during daytime with NAV2 113.00. The only other option right now is to delete these files:

loww_rwy_11_appr_lights.bgl
loww_rwy_11_papi.bgl
loww_rwy_16_appr_lights.bgl
loww_rwy_16_papi.bgl
loww_rwy_34_appr_lights.bgl
loww_rwy_34_papi.bgl
loww_rwy_29_appr_lights.bgl
loww_rwy_29_papi.bgl
loww_rwy_1129_lights.bgl
loww_rwy_1634_lights.bgl

And copy the attached RWY.BGL Scasm lighting from the FS9 version. Note this may cause problems with AI and not match the papi boxes and approach poles perfectly. But it will work better during Fog.

Hey,
Thanks for the update. Unfortunately I get a bug when i delete these files and insert the rwy.bgl:


Any suggestions?

[martin[flytampa]]

Has the v2.5 installer from Simmarket been updated?

Yes

[martin[flytampa]]

Hey,
Thanks for the update. Unfortunately I get a bug when i delete these files and insert the rwy.bgl:

Any suggestions?

No idea sorry. We don't normally use or recommend these use of these FS9 runways in FSX. They do generate default light dots, so perhaps it looks like that because of some texture replacement mod you have?

[gianluca311]

Hey,
Thanks for the update. Unfortunately I get a bug when i delete these files and insert the rwy.bgl:

Any suggestions?

No idea sorry. We don't normally use or recommend these use of these FS9 runways in FSX. They do generate default light dots, so perhaps it looks like that because of some texture replacement mod you have?

no, everything original.

[cgentil]

Fixed spacing between TL39/49. This is in the 2.5 update/Installer. If you update before Dec 23 just redownload the Update.

Updated

Seems same:

[driver101]

Hi Goerge,

Thanks for the info. Problem is they didn't work at night time for me. I try to reinstall LOWW ASAP. I will let you know if the problem is solved.

Cheers Jan

Hi Guys,

It's working now

Cheers Jan

[Goose]

Hello,

I just bought the great Vienna scenery a few days ago at simmarket (V2.5) for P3DV2.
Additionally I have runnning several addon planes e.g. A320X and MQ400, FTG Global,
REX4 and Open Clouds weather engine with out any problems so far...

Now lets talk about my problem at the moment.
On any airport with any airplane except the Vienna airport I can load the weather from Open Clouds tool into P3DV2 without any problem.
If I start directly at LOWW or if I load the weather on any other airport the sim crashes as soon as I switch to LOWW with the following windows error message.

Error in module C:\Windows\system32\MSVCR100.dll

I hope that some of you can help me.

Thanks in advance and all the best for 2014 to all of you
Cheers
Marc

P.S. sorry for my bad english.

[martin[flytampa]]

Does it crash with any other type of weather, like manually set, default weather themes, real world weather? I'm not aware of anything related to weather that would cause any scenery to crash. Maybe also try to test it with flytampa-vienna disabled in the library.

[Goose]

Hi Martin Happy New Year,

So far no problems at all with manually, default set weather.
At the moment there are no tools for weather available as I am still waiting
on the FSGRW weather tool upgrade to P3DV2. I can easily reproduce this error.

Today I checked to load the weather e.g. on LOWI and close the weather tool before loading LOWW that
prevends the system to ctd. but I am not sure if the weather has been change on this airport.

Br
Marc