Thanks. That worked fine. Nice to see the apron, taxyways and all of the runway. Had to move the building on A1 by the threshold of 08 though.

 

Thanks again

 

Colin B

Gentlemen, the journey is really over now. It was a pleasure to share some impressions with you. I hope you had fun with them.

http://forum.avsim.net/topic/469595-warsaw-leipzig-via-dresden-with-the-tu-134/

 

With best regards,

Harald

 

 

Thanks. That worked fine

 

My pleasure. I flew LUX-FRU again ….. fourth time lucky.

 

This time the flight was perfect. After removing the navdata file in the UAFM scenery folder my KALIN approach worked perfectly (I will now go on to write the rest) and the ground texture bleed through again was non-existent. 

 

In my experience making a flight between two ports in FS is never a simple affair.

I have changed Manas Airport ICAO code to UCFM (as it is today) and with editvoicepak added its ICAO name and agent "Manas"

 

All ILS approaches have been written and work. No bleed throughs to be seen.

 

I am going to do one more long haul to test it and make a very short video of the approach so it can be seen how it all works so well (good ol' FS ATC)……and share the relevant files for those who are interested. :smile:  

 

Here is how my last video flight LUX/FRU should have ended.

 

UAFM is now UCFM, all ILS approaches written, no bleed throughs, editvoicepack edited for UCFM.

 

If anyone would like to try my files. http://www.mediafire.com/download/5rftl1wzcctdlx5/Manas_UCFM.zip

 

Ed, how do I keep your new AFCAD changes but keep the old UAFM code? I have a lot of AI going to that airport and I rather keep the old code then going through all my flight plans and changing them to the new airport code.

Ed, how do I keep your new AFCAD changes but keep the old UAFM code? I have a lot of AI going to that airport and I rather keep the old code then going through all my flight plans and changing them to the new airport code.

 

I would think you would want to keep your parking codes and sizes also so…..

 

Open your UAFM afcad using ADE only: If you are getting ground texture bleed through change the airport altitude to 2089.865 feet then add a flatten.

Then all you would want is the approach codes. In ADE approach mode import the codes from my UCFM afcad….and compile.

 

That's it….remember to remove the navdata file in the Manas scenery folder and you would need none of my files.

Thanks Ed. I will give it a try. I never made a flatten file before so that will be new for me (yes I do need a flatten file. I once tried to fix up the original AFCAD and got bleed through).

Thanks Ed. I will give it a try. I never made a flatten file before so that will be new for me (yes I do need a flatten file. I once tried to fix up the original AFCAD and got bleed through).

 

There is nothing easier than writing a flatten using ADE (far easier and better than writing it in the scenery cfg)

 

After getting your airport altitude correct simply click on the add polygon icon and draw a square around the airport. (I didn't even look at what I was doing in FS)

Thanks Ed for investigating the correct airport elevation for Manas. How did you find it after all?

And where did you get the fine traffic for the USAF base? Own creation? I especially look for the correct aircraft types and flight planes.

Thanks Ed for investigating the correct airport elevation for Manas. How did you find it after all?

 

It was a guestimate….but it worked. 

 

 

 

And where did you get the fine traffic for the USAF base? Own creation? I especially look for the correct aircraft types and flight planes

 

My video looks exactly like the first Manas video I googled….I was very surprised to see all that American hardware ….probably not there now. https://www.youtube.com/watch?v=-zRbA4A_vPE

 

I quickly put it together myself using MAIW aircraft. (C-17's and KC-135R's back and forth trips to Kabul) …plus it tested the new ICAO (UCFM) for traffic. I did put together some Russian AI as well but none of them showed up. :(

I see now: The Manas Air Transit Center was closed in 2014.

Regarding the code change: Changing the code in the scenery and the AI traffic files is quite easy for me, but how do you get rid of the code from the stock file? When doing that for UGGG -> UGTB I divided the stock file (APxxxxxx.bgl) into all its single airports. Is there a way less complicated? (I.e. is there a method allowing a "surgical" edit of the stock file without changing Kant, Taraz and Lugovoy?)

but how do you get rid of the code from the stock file?

 

The stock code is still there but overridden by the UAFM afcad in my uploaded file.

 

Basically I opened the stock UAFM using ADE….. erased all of it's components. (remember to erase all comms and approaches) and then complied it as a UAFM afcad which I put in my add-on scenery/ scenery folder.

 

UCFM is a new airport in the same place but you have to use editvoicepak to add the airport name etc for FS ATC. 

 

edit* You might want to check this post…looks like you need a Pro key to change the identifier. Personally I think ADE deserves a donation anyway. http://www.fsdeveloper.com/forum/threads/change-identifier.433463/#post-704609

 

 

I think ADE deserves a donation anyway

You're definitely right. ADE is an awesome tool.

I understand your method. Mine just aimed to erase the old code from maps, from my navigation tool (FSC) etc.

Hi FS9ers,

you may ask when the Tu-134 will take off into the skies for the next time. I frankly don't know; recently I like some GA-flying, eastward again, will see how far it takes me. I have taken a few shots nevertheless, as you can see here. Hope you'll like it.

 

http://forum.avsim.net/topic/470771-the-colours-of-the-summer-ga-in-hungary/

 

http://forum.avsim.net/topic/471863-fs9evo-eastward-ga-in-ukraine-russia/

 

Regards,

Harald