Please take note that the developer has returned here to offer support, explanation, and a programming solution WITH the numbers necessary to achieve a requested result.

Excellent service from Umberto. I can't like posts any longer but I have given the topic 4 stars. I'd encourage others to do the same if they're satisfied.

 

I had a brief play with the readout utility and it does help a lot. It's important that you can control taxi speed to around 5kts for maximum effect and control.

Hi Ray

 

How did you manage to get that readout utility to work. When I clicked on that link that Umberto posted, all I could see was gobbledegook.

Hi Rick,

 

Right-click the link and choose "Save Link as". Point it to your download folder. Find the original and rename it in case you want to revert.

 

Copy the new file to the location given.

Having used the readout to accurately park my 737-800 I noticed afterwards my nose-wheel is short of the 737 marker. This might explain why I was never able to make the marshal happy. This is at LEPA with 3rd party scenery.

 

I didn't get chastised for poor parking but I didn't make him dance either. Maybe next time.

 

One comment. The readout becomes visible as soon as a gate is selected. Mine was a couple of hundred yards away. How about if the readout only becomes visible once within 50 yards?

 

Hi Ray

 

Thanks for that.

 

Got it, job done.

The link in virtuali message doesn't work.  Anybody have another location to try?

The link works, but you should probably select the option to save it, otherwise the browser might try to open it directly.

Having used the readout to accurately park my 737-800 I noticed afterwards my nose-wheel is short of the 737 marker. This might explain why I was never able to make the marshal happy. This is at LEPA with 3rd party scenery.

As I've said, the marshaller or the docking system, don't have any knowledge of the scenery ground lines, especially when using 3rd party airports.

 

It would require programming the marshaller to recognize the pixel/meters ratio of the custom texture used by that specific scenery, that might not even be the same across all parking spots of the same scenery.

 

GSX CAN do this, and it can even apply an offset depending on the airplane type used, but it does it only at FSDT airports, where we obviously know the textures we used for custom ground markings, and we take care to do that as part of the scenery work.

 

Doing this for 3rd party airports would require a specific programming for each one, which would basically mean charging per-airport.

 

 

Doing this for 3rd party airports would require a specific programming for each one, which would basically mean charging per-airport.

 

Hi Umberto,

 

That would mean it becomes the same as AES and there's no sense in going down that path. I hope my message didn't come across as negative. I find the readout very helpful and it highlights how even small movements impact on parking accuracy. I love the new feature. :smile:

 

DreamFlight767, read message number 34.

In the meantime, I've updated the file to display the readout only during the last 50 meters of the approach, let me know if it's all fine now, so I can publish it as an official Live Update.

Please take note that the developer has returned here to offer support, explanation, and a programming solution WITH the numbers necessary to achieve a requested result.

Yeah that's pretty Bad $SS something I was not expecting at all, in fact I made the original post in the Hangar Chat forum with the only intent of bringing some lighthearted humor to others that have had the same experience with the Marshaller giving me the business about my poor parking. 

 

I was already a fan and supporter of FSDreamteam products but having Umberto step in here with a mod is top shelf: this isn't event the FSDreamteam forum!  "Thanks, Umberto"!

 

I think it's time to go pick up that Houston Scenery I have been pondering over.

In the meantime, I've updated the file to display the readout only during the last 50 meters of the approach, let me know if it's all fine now, so I can publish it as an official Live Update.

 

Umberto,

 

I updated Couatl when prompted and the new version that comes alive at 50 meters is fine. I did 3 practices and on the last one finally got a great parking and the marshaller danced for me!  

 

After that perfect parking I tried another airport but after selecting the gate number the display was immediately visible rather than at 50 meters. Can you check everything is being initialised?

Hi Umberto,

 

That would mean it becomes the same as AES and there's no sense in going down that path. I hope my message didn't come across as negative. I find the readout very helpful and it highlights how even small movements impact on parking accuracy. I love the new feature. :smile:

 

DreamFlight767, read message number 34.

 

Thank you.  Sorry.  Don't know how I over looked that post.

Hello to all,

 

we had another update today, which makes the distance readout much nicer and fps friendly:

 

http://www.fsdreamteam.com/forum/index.php/topic,10803.msg83909.html#msg83909

Hello to all,

 

we had another update today, which makes the distance readout much nicer and fps friendly:

 

http://www.fsdreamteam.com/forum/index.php/topic,10803.msg83909.html#msg83909

I posted on your forum, but I'll state it again, this solution is much cleaner, and I absolutely have found no negative issues with it. I got a very good parking rating the very first time using it!!

 

Thanks!!