plovdiv74

I live in Denver and fly the many strips in Colorado often. Telluride is one of my favorites. (Sim and real-life.) Next time give runway 27 visual a try. Here's Premier 1 Driver doing it: Eagle Departure with a rwy 27 landing at T-ride - YouTube Aspen (KASE) visual into runway 33 is fun too. 🙂

I began experiencing this following one of the early updates after the product launch. (I don't recall the specific release.) I can say for certain that this was not a problem from the first tech alpha through product launch. For me, the issue occurs with all of the aircraft I frequently fly: the TBM, Baron, and C172-G1000 while definitely having "modern" flight model selected. One common thread here is that these aircraft are all Garmin-glass equipped. I have CH pro yoke and pedals. When the problem occurs, I can often resolve it by "nudging" the yoke to get back to wings level. Sometimes this works; sometimes not. I've reported the issue twice to Zendesk and it has yet to be fixed. It happens so often, I find it hard to believe the Asobo devs/QA can't reproduce it.

Hi Peter, We recently made significant changes to our website structure and changed our email hosting. Jan at IPACS let me know of your licensing issue and that you were having trouble contacting us. We've resolved the issue with the email address we use to support the AFS2 RC ATC software (admin@advresgrp.com). I can only assume something has changed with your hardware or Windows installation. Please reply to the email I sent you earlier today with your product id and we'll create a new license key. Thanks. Regards, Karl

Hello Peter, I've replied to your personal email as well as the IPACS forum. Thanks to Jan, who brought your issue to my attention, we've gotten the support email address back up and running (admin@advresgrp.com). Have you made any changes to your hardware or installed a major Windows update recently? Please reply to the email I sent you earlier today with your product id. We can create a new license key for you or otherwise identify the problem causing the license failure. No worries, we'll get you back up and running. Regards, Karl

No problems now.

Yes, but TA1 still works. Maybe forum updates in prep for TA2?

Hi Richard, I used the map to select the waypoints as I'm unsure of what works or doesn't work in the FMS itself. After selecting a "fair number" of waypoints (not sure exactly how many at that point), AFS2 seemed to intermittently freeze. Each time that occurred, I'd click away from AFS2 then back (I have a second monitor). I also noticed some visual issues when zooming in and out. I'll have to try and reproduce what I observed and give IPACS a heads-up. With respect to point "1", based on my own experience this afternoon, I don't doubt their flight planner has some internal limits that aren't being handled as gracefully as they could. Given I can provide IPACS with concise steps to reproduce what I saw, I'm sure they'll be able to resolve the issues. By all means post what you've experienced on their General Discussions forum. Regards, Karl

Hi Richard, All Flamingpie's points are correct. I went ahead and did a bit of testing to see how closely I could match up your flight plan in AFS2. It worked very well. My initial intent was to use only the VOR waypoints for simplicity but ended up adding a number of the intersections as well. (Not an awesome process but not too bad.) Due to time constraints, I only flew to PALMM (on J191). The weather at the time was KLGA 121751Z 31021G29KT 10SM FEW023 BKN049 OVC060 03/M03 A2990 RMK AO2 PK WND 31029/1751 SLP124 60002 T00281033 10139 20022 51033 KOPF 121753Z 25009KT 10SM FEW055 29/17 A2994 RMK AO2 SLP138 T02940172 10306 20217 58019 so I selected 31 for departure and 27R for arrival. Up to PALMM, I was able to use the FMS without issue. I suspect the remainder of the flight would have tracked just fine until hand-off to arrival (~30 - 40 miles from FAF) - HDG mode from there. Here's the plan I created in Little Navmap: KLGA to KOPF plan And in AFS2: KLGA-KOPF image Let me know how you make out or if you have more questions. Regards, Karl

Hi Flamingpie, Your points are well taken. I can see how the number steps, programs and my abundance of documentation might seem daunting. As mentioned, I have opportunities to improve the current install process. Your comments are enough to convince me that moving forward with streamlining the install process is absolutely necessary. I won't be able to do anything about Radar Contact's licensing; it is what it is. I'm a fan of Steam and have purchased my sims (outside of P3D) and most add-on DLC (except for example, Orbx scenery and Active Sky), as well as non sim-related titles there. You are correct, Steam's ease of use installing and keeping products updated can't be beat. I do plan to offer Aerofly FS2 RC ATC through Steam in the near future. Stay tuned. As for flight planning, Online Flight Planner, is a good choice without any installation. Also as mentioned in my post to Richard, supporting AFS2's integrated flight planner is being evaluated for the best approach. Your input is welcome. Thanks again for your feedback. Regards, AdvResGrpDev (developer of Aerofly FS2 RC ATC)

Hi Richard, You can use any flight planner that can create flight plans compatible with FSX or P3D. I use Little Navmap to generate the compatible flight plan in conjunction with SkyVector and/or FlightAware for real-world routes plus SIDs and STARs. There's also Online Flight Planner. I've received feedback about incorporating Aerofly FS2's simple flight planning with Radar Contact (this actually came up during beta testing). Based on this feedback, I have some ideas of how this might be accomplished. I'll share more as I move forward. I'd appreciate your ideas as well. Thanks very much. Regards, AdvResGrpDev (developer of Aerofly FS2 RC ATC)

Hi Flamingpie, Thanks very much for the feedback. I’d be the first to admit that installing Radar Contact is less straightforward than it could be. Also, I don’t disagree that installing two products, each with their own licensing, is less than ideal. I do have opportunities to improve the user experience on both fronts. I have a few questions if you wouldn't mind expanding on your comments. "- the addon brings cumbersome FSX-like download and install routines into the up to now simple AFS2 world: you need three programs with their own downloads, keys, etc. and complicated install routines which require manual work arounds (like creating folders in the root of 😄 and skipping steps) to get things done" What is it you found cumbersome about downloading and installing Aerofly FS2 RC ATC? Are you referring to Radar Contact's key generator as the third program? Installing Radar Contact to the root of C: is not required. It's just a suggested location as Radar Contact is not required to be run as administrator when installed outside of protected folders. Can you be more specific with regard to "manual workarounds?" Are you referring to not needing to install FSUIPC as "skipping steps?" Thanks again for your feedback. Regards, AdvResGrpDev (developer of Aerofly FS2 RC ATC)

Hello Radar Contact fans, I've developed interface software to allow Aerofly FS2 to work with Radar Contact. To help my users get started, I created two documents describing step-by step, including screenshots, how to install then register Radar Contact. You'll find link to these documents at the conclusion of this post. Perhaps they'll be helpful to new users and ease Ray's support burden a bit. I'll follow with another step-by-step guide to resolve common problems encountered when first getting Radar Contact up and running. For example, how to install and enable the file mssstdfmt.dll not installed by Radar Contact. Regards, Karl Step by Step guide to Installing Radar Contact Step by Step guide to Registering Radar Contact

I've posted the first demo video of my upcoming air traffic control solution, Aerofly FS 2 RC ATC. The flight is from my home airport, KAPA - Centennial, to KASE - Aspen Pitkin County. It's a fairly short but fun flight with a challenging approach and landing, and is regularly scheduled from Denver International. Captured using OBS at 4K and downsampled to HD (prior to upload to YouTube), the video is 42 minutes long and unedited. What follows is a timeline of ATC interactions in case you'd like to jump around. ATIS 00:40 CLR DEL 00:40 GND 02:52, 03:18 request runway 35R Hand-off to TWR 05:34 TWR 05:49 Take-off 08:01 Hand-off to DEP 09:14 DEP 09:26 Hand-off to DEN CTR 11:24 DEN CTR 11:37 Instructed initial descent with restriction 15:36 Hand-off to next DEN CTR 16:55 Mount Evans (14,285) 17:38, highest “14er” in CO; highest auto road in North America Lake Dillon, Frisco and road to Breckenridge 19:50, next to Vail, mine and my wife's favorite spots in CO Hand-off to APP 21:19 Expected runway 33, APP 21:33, 21:55 request runway 15 Begin vectoring to runway 15 22:42 Altimeter confirmation 23:06 Vectored downwind leg 25:36 Approaching KEGE (Eagle County) 28:45, ORBX excellence! Vectored base leg 29:45 Vectored final approach 31:06 Hand-off to TWR 37:36 TWR, wind report 37:57 TWR, cleared to land 38:20 Hand-off to GND 40:20 GND 40:44 Have a look. Questions and comments most welcome! Link to YouTube demo flight video

Hi fellow Aeroflyers, “Aerofly FS 2 RC ATC” is set to be released this coming Saturday, November 9 and will be initially available for download and purchase at the product’s website (still under construction). The product leverages the exceptional air traffic control implementation of Radar Contact v4 by providing a bridge between it and Aerofly FS 2 (AFS2). Before touching on product highlights, it must be mentioned that the foundation of the development of this product is threefold: user experience, performance and stability. The product has been developed using commercial software development industry best practices and extensively tested. The product is designed to make intelligent use of hardware capabilities, both CPU and GPU. You will experience zero effect on performance (i.e., FPS). Worth noting is that the rendering of the Radar Contact menu within the AFS2 screen is measured in microseconds (not milliseconds). Some feature highlights: · Radar Contact’s “menu” is displayed within the AFS2 window using OpenGL or Vulkan by default but can also be displayed in a secondary popup window if desired. Display of Radar Contact’s menu can also be disabled altogether. · The size and color of the text is configurable. · The screen location of the text is also configurable and can be positioned at one of the four corners of the screen (upper left, upper right, lower left, lower right). This allows for view of the Radar Contact menu without obscuring the instrument panel or the window view. · For ATIS and enroute weather reports, metar data is downloaded periodically from one of over 11000 weather reporting stations. The weather download period is configurable with a default period of 15 minutes. Weather download can be disabled if desired. · While complete control of weather is not possible at this time due to limitations of the IPACS SDK interface, Visibility can be controlled. · As depiction of visibility is highly subjective, it is highly configurable for fine tuning to the user’s preferences. Visibility control can also be disabled if desired. · Radar Contact is limited to interaction using only the keyboard. Aerofly FS 2 RC ATC eliminates this limitation by providing complete support for ATC interaction using flight controller buttons (joysticks, yokes, etc.). If the controller is supported by AFS2, it will be supported for interacting with ATC. · Aerofly FS 2 RC ATC includes extensive, category-based logging facilities for troubleshooting in the event of unexpected behavior. When enabled, a log file will be created that can then be emailed to product support for evaluation. · Support will be provided via email through a dedicated email address, here on IPACS’ forum and the “usual suspect” flight sim enthusiast sites like Avsim (which also has a dedicated Radar Contact forum). · Try before you buy! A seven-day trial period is available if desired. Perhaps you’re unfamiliar with Radar Contact or air traffic control in general. Download the product and request a license prior to purchase. A license enabling the trial period will be sent via email reply. · Once purchased, two permanent licenses can be requested allowing for use, for example, on a desktop computer and a laptop. The purchase price is $29.95 US. All product enhancements will be freely downloadable as they become available. The first planned enhancement is support for VR. If you’re interested in adding air traffic control to your Aerofly FS 2 experience, I highly recommend visiting the Radar Contact website to familiarize yourself of its capabilities. By far, the majority of challenges experienced by my test team were related to getting Radar Contact up and running. Questions and comments are most welcome. I encourage my test team to share their experiences with the product.