#EHAM - FlyTampa

1 messages · Page 1 of 1 (latest)

marsh star
#

That would be Awesome !!

ionic marlin
#

Yes yes yes! Let's gimme Amsterdam with London-South RWY please!
Finally we have some info about that it's around the corner. My Hometown getting finally some good love and less frames!

velvet dune
#

Hmm the last official post on it I see doesn't sound like it's that soon. More like months to go

true plover
#

Sorry I meant facvebook

#

their forum is dead

velvet dune
#

Ahhh, got it. Thanks!

upbeat rain
#

@true plover great to hear you'll be making this. Small tip: the profile that is included in the current freeware mode is very good regarding all the standard pushback positions at EHAM. might take inspiration from that one.

#

In general: all/ most PB positions have a standard PB position indicated on the chart with an arrow left/right from the PB driver perspective. There are corresponding PB position markers on the apron. No specific instructions from ATC mean use the standard.. 'alternative PB' instruction means the opposite, where possible/applicable.
There are some exceptions:
*On the E/F apron and D/E apron there are some push/pull (Not yet possible in GSX I know). On the E/F apron those are usually push into A14 nose in and pull into A16 nose out.
Push from the cul-de-sac between D and E with a tail/right marking are actually onto A10 abeam D49-ish. chart has markings for most stands:

image.png
true plover
#

Thanks!

scenic sorrel
#

Pretty handy that there are ground markings for many gates indicating the pushback positions.

image.png
#

So it looks like there won´t be more than one option on these gates

true plover
upbeat rain
#

the ground markings are there for many (not all) gates for the 'standard' pushback. The 'alternative' pb by ATC when given will mean the nose in the opposite direction from the standard.

true plover
winter bane
#

Well I'm on the beta so was already planning lol🥳

#

Have all the original stuff regarding EHAM 😉

#

Will be close to real life 😉

true plover
#

So do I

#

A ramp agent sent me all the documents for every pushback on every stand

winter bane
#

By al means go ahead just to let you know

true plover
#

What do you mean with which account?

#

I am not on the Beta. I never said I was

winter bane
#

I mixed up your sentence "so do I" lol

true plover
#

That was regarding the documents for pushbacks and procedures

#

Good for you

winter bane
#

Yes got it 😉

true plover
#

You told me 4 times now

winter bane
#

you're point?

#

trying to avoid the mix up here that's all

#

So less times now

gusty marten
gusty marten
upbeat rain
#

@winter bane congrats on the great profile! after a bit of tinkering I have a few suggestions you could look into should you choose to update at some point:
*(advice from Umberto) make it so only the 'active' screen shows to conserve Simobjects
*remove handler KL and make it only KL_white, since AFAIK the white vehicles is not a style KL employs in AMS but only abroad?
*the D-remote stands stop positions for the 737 are too far back, protruding onto A10 TWY

winter bane
#

Yes you may sent me a private message appreciated the feedback

#

Yes as for the sim objects already updated the profile

#

the handlers are as per real life will have a look

upbeat rain
winter bane
#

as for the remote stands will have a look too

#

@upbeat rain appreciated 👍

winter bane
#

update with the sim objects

winter bane
#

@upbeat rain already updated the stuff, so it will show later as 1.06

upbeat rain
upbeat rain
#

@winter bane there are quite a few issues with the 737 stop positions, mostly around the D en C pier. They are WAY too far back (tales are often significantly over the red line). I think there is an issue in the .py file where (although i'm not 100% sure how to read it) there is a huge offset between the airbusses and the 737's

d-gates.png
#

for reference, see this picture. this is the Fenix AFTER I moved the stop position in the 738 forwards to a reasonable position. The new 738 stop position is roughly where I professionally painted the orange line 😬 . This then makes the Fenix stop position too far forward.

C7.png
#

pmdg at same gate, no editing of position between these two pictures

c7_pmdg_737.png
upbeat rain
#

When did you last update GSX? There were issues on sunday night but some of us did some troubleshooting then and it's been stable again since yesterday...

#

try running the updater anyway, there were 2 fixes today I believe.

winter bane
#

Make sure when you start to repostion your aircraft via GSX at the current gate

upbeat rain
winter bane
#

that will place the aircraft at the correct location

#

this will differ also in real life

#

So you can't edit the stop postion via GSX it's and offset

#

via the scripting

#

Will make a screenshot how C7 looks local here

upbeat rain
#

Yes you can edit the parking, and the offset will be based of the stop position. However the issue seems to be to much backward offset on the PMDG at the D and C gates.

winter bane
#

Will have a look but tested with gate docking and all was working fine

upbeat rain
#

they will differ in real life but tail sticking 2/3 meters onto the TWY is not correct.

winter bane
#

Almost not possible maybe something changed in the latest update FSDT

upbeat rain
winter bane
#

Will load to and have a look

upbeat rain
#

this is with the pmdg 737-900 with a freshly downloaded profile, not my edited one.

image.png image.png image.png
winter bane
#

Yep something missed in this one have so something to test for you fix is pretty simple have only to check my info @upbeat rain appreciated 👏🏼

upbeat rain
#

as reference the same gates in the Fenix: perfect. To illustrate the issue is in the offsets.

image.png image.png image.png
winter bane
#

Yep correcting already the missing values really appreciated the feedback

upbeat rain
winter bane
#

Something so to test if you are willing?

upbeat rain
#

sure

winter bane
#

Thanks

scenic sorrel
#

Hey, I just noticed that at H Gates (it also happens in other positions, but just glimpsed it so I can´t say for sure in which ones), the parking position is not exactly on top of the center line but either to the left or the right. It is not really that important but it would be appreciated if it could be looked into. Thanks.

winter bane
#

Yep thanks edit a lot of those will have a look

scenic sorrel
winter bane
winter bane
hushed sinew
winter bane
#

Will be updating 1.07 later this evening with FT stuff Lot of gates tweaked again and adjusted plus catering and stop positions... Have gone through all of them again 🤣

final bridge
winter bane
#

The files are only there to download... in the Flytampa Amsterdam forum

winter bane
#

Will report back when it's up, thanks guys for the feedback really appreciated 👍

winter bane
loud ledge
#

still not working for me. latest update and getting this error couatl v4.8 (build 5268)
panic log started on Wed Oct 11 17:15:17 2023

problem raised by addon AppData
Traceback (most recent call last):
File ".\GSX\parkingServices_init_.py", line 26, in willMaterialize
File ".\GSX\parkingServices\safedock3.py", line 100, in materialize
File ".\GSX\parkingServices\basic.py", line 142, in materialize
File ".\GSX\airportCustomization.py", line 625, in computePositionsForAircraft
File ".\GSX\airportCustomization.py", line 605, in computeStopOffsetForAircraft
File "C:\Users\xxxxx\AppData\Roaming\Virtuali/GSX/MSFS/eham-flytampa.py", line 171, in customOffsetDpiergatesGen
return Distance.fromMeters(table737.get(aircraftData.idMinor))
Boost.Python.ArgumentError: Python argument types in
Distance.fromMeters(NoneType)
did not match C++ signature:
fromMeters(double)
{'Airport': 'EHAM', 'Requested parking services to': 'D-Pier =< Cat 4 schengen|Gate 44 ', 'User Pos': (52.30902215734155, 4.7711166594667604, -0.648827 m, 2.44749 m, 3.0011006877783086, 0.02378152124583721, 0.024434609338641167, 0.00048296564575397646, 2.553919111633301, 1.0)}
emulateMenu_MSFS

hushed sinew
winter bane
#

to add which aircraft you used (looks like pmdg 737?)

#

Going to check now at gate D44 here local

#

No panic log here working fine see screenshots no ERR file

#

So check your FSDT installation as for GSX and the PY script working fine here local

loud ledge
#

OK thanks. Doing all steps again

#

It was the b736 by the way

winter bane
#

Ok will do that again with the 736 to make sure

#

but all those are tested with the 737-6/7/8

#

tripple check rprt back

#

Working fine see screenshots below

winter bane
loud ledge
#

I did 3 times the steps as described and 3rd time it worked! Offline installer, update, test etc. No idea why it didn't work 1st or 2nd time. Anyway, thanks for the help.

gusty marten
winter bane
winter bane
#

Update for FT Amsterdam 1.1

gusty marten
#

Two small things i noticed during my flight today:

  • at the KLC Gates it seems like the stop position for the e-jets is about a meter to far forward (FSS E175)
  • Gate 63 rear stair drives a funky route, best you reposition it (it drives backward through the plane and connects from the wrong side, no idea what GSX is doing there)

maybe you can also add the A to the gate names in the .py file. Not required of course would just be nice to see

winter bane
gusty marten
#

Will post one later 👍

winter bane
#

thanks appreciated

upbeat rain
#

small detail I forgot to mention yesterday: on one of the D remote stand, I believe D94, the pushback truck position is too far forward, clip[ping the parking position.

gusty marten
winter bane
#

that's the E175?

gusty marten
#

yes

#

should be the same for the 170 though

winter bane
#

ok thanks will have a look....

#

How is that Ejet?

gusty marten
#

Okay. Will be great once they add the custom LNAV and VNAV

winter bane
#

Is there a GSX profile for that Ejet?

#

or in the default

gusty marten
#

I made my own one for it. But there should be one on fs.to, its not included in default GSX

winter bane
#

Ok

hushed sinew
#

I cant get the 170/190 to be recognised from my .py file. It always aligns with the 0 value. What do you use and does it work?

winter bane
#

Have to check wil report back later

winter bane
#

If this one isn’ t in the default database the aircraft isn’t recognised by GSX it will place it at the default 0 position. Simon has one profile and that one has a different position as the default FSS E175 so ultimate FSDT should add this one… to have it working correctly Will check later. As for the A platform there is just one stop position will add it to py file that every aircraft no matter what starts there..

winter bane
#

So going to test a bit more later on maybe we could request a default profile @open anvil for the FSS 170/175

hushed sinew
#

Hes already stated its in the default database which is why i asked if it was just mine. Ill ask in quick questions to add it then.

winter bane
#

It’s not recognised gives an error file

winter bane
#

Now off to Aerosoft EBBR Brussel and update that one with the latest

misty fjord
#

👍

winter bane
winter bane
#

Expect an update with the new feature push and pull soon🥳

ionic marlin
upbeat rain
winter bane
upbeat rain
winter bane
#

I have per gate the official push routes

ionic marlin
#

I only know the push/pull from D (next to E) in the corner because I have witnessed that myself 😅

upbeat rain
winter bane
#

there are a lot more at AMS

ionic marlin
winter bane
#

even if the push at the gate first to the right or left and then to the correct stop position

#

some tweaks to add also going from B to H again already did that so many times 🤣

upbeat rain
#

lots of gates... 😁

winter bane
#

Yep 🥵

winter bane
#

Changelog GSX Pro SPL 1.10

  • GSX Pro Push and Pull function: lot of gates and routes changed according real life gates with push and pull
  • H gates added push and hold routine to vop G71 stand
  • Added taxi line number in pushback or push pull description for ATC convenient
  • Added and changed=< Cat4 into =<Medium and => Cat5 into => Heavy into the description
  • Removed Schengen in sorting menu GSX
  • More logical and simplified grouping in GSX menu for faster navigation
  • Small tweaks
#

Soon available

scenic sorrel
#

@winter bane Hey! I just wanted to let you know that now, with al the A300 mania, when parking on both the S and R apron, the AGNIS PAPA system doesn´t show up, although the stands are marked to have one. It is not until you enter on the editor mode when it pops up

#

Have a great new year ☺️

winter bane
scenic sorrel
astral scaffold
winter bane
#

Files are ready but waiting for FT to return and upload… so hoping in the upcoming days

cyan canyon
#

Cant wait!

winter bane
#

Emilios is back later so I will temporary place the files here for you guys

astral scaffold
#

Thanks!

cyan canyon
#

You are amazing

#

Thanks a lot

barren plank
#

Thank you so much!

royal tulip
#

Any update on this ?

winter bane
#

It should be hopefully later this week...

winter bane
#

Some delays in the meantime I share it here again...

#

Changelog GSX Pro SPL 1.10

GSX Pro Push and Pull function: lot of gates and routes changed according real life gates with push and pull
H gates added push and hold routine to vop G71 stand
Added taxi line number in pushback or push pull description for ATC convenient
Added and changed=< Cat4 into =<Medium and => Cat5 into => Heavy into the description
Added FSS 190/195 and the inibuilds A300 placements at AMS
Added compatibility drag and drop installer from https://elevatesolutions.live/DDI_pages/DDIOverview/
Removed Schengen in sorting menu GSX
More logical and simplified grouping in GSX menu for faster navigation
Small tweaks

winter bane
#

Update is available now

hushed sinew
cyan canyon
#

Why do I have still the schengen and non schengen options in the GSX menu? I mean its handy, but I believe with the new V1.1 GSX you wouldnt have it, right?

winter bane
#

did you saved the py file also?

#

with version 1.10

#

Just overwrite the old one

#

check the py file in the header there is also the file version should be 1.10

winter bane
cyan canyon
round ibex
#

@winter bane E19 push with widebody is a bit broken, puts you almost in the terminal haha

image.png
winter bane
#

@round ibex thanks will have a look tested with 787 and 306

winter bane
round ibex
winter bane
#

I will have look to tweak it a bit to have more room

winter bane
#

Small update I'm preparing so I tweaked it a little bit... the real life push line(white dashed line on the scenery) is difficult to follow with GSX ... working fine now (788/789/78X) tested

winter bane
barren plank
#

Hi @winter bane I added, fully based on your amazing work, engine start points.
Added your py file for convenience. Any feedback is appreciated.
Thanks again for your amazing work, I use it daily!

📎 eham-flytampa.ini 📎 eham-flytampa.py
winter bane
winter bane
#

@barren plank Will check if it makes sense at AMS the engine start points compared to the RW, as for the wing walkers I'm already busy with an update for AMS (in which they are all disabled) and some other stuff...

winter bane
#

@barren plank ben je uitgegaan van de rode klaringslijn?

barren plank
barren plank
barren plank
winter bane
#

@barren plank Real busy now will come back to this and adjust and test your settings for start up.... (don't want to reinvent the wheel again 👍 )

winter bane
#

@barren plank Will be testing upcoming week and some adjustments 😎

#

So when you are around?

barren plank
winter bane
#

@barren plank No problem, busy myself will give you a heads-up