Yep, this is for real. ATC is coming to Aerofly FS2 and probably a lot sooner that most are expecting. This is not the IPACS version that has supposedly been in work for the last few years, but, from a 3rd party developer.
The Open GL version is working like a charm and the Vulkan version is close at hand. Those FS2 pilots with the Saitek Panels will absolutely love it, but, the VR pilots will still be challenged to respond to the Controllers in a timely manner. The configuration screen allows for adapting your FS2 weather to the current METAR with changes in clouds cover, visibility and turbulence. One of the most recent features that I pushed for was to be able to map the ATC requests and replies to my HOTAS buttons and this works great.
Well good news. I'm sure whatever Ipacs had planned would have been the absolute cats meow, but..
it's closing in on Halloween, and headless Pilots are all the rage!
I remember years ago in Outerra, users wanted Multiplayer so badly that they created it themselves! It was glitchy, and had lag, but it was so cool seeing a dedicated community working hard together.
Some day..... Maybe.
No problem here, so I doubt it was one of their silent updates that was the culprit.
Dense scenery is nice theoretically, but all those buildings merged into one another I'm not so sure about.....
No sound when launched from my desktop Icon..... But once I started it from within steam, some sort of connection occurred because suddenly sound is working again, including when launched from the desktop icon.....
Suddenly the sim has no sound either on speaker or headphone. All other sounds from other games/videos etc are fine.
Pressing Q does nothing.
Deleting main MCF does not fix it.
I was just wondering if there is a scenery object for this ship? I could not see it when using the Oahu scenery and cultivation.
Good on you for just getting the scenery up and running! Its one of the ones with absolutely no instructions, so I never did figure out quite how to install it.
Some changes which may or may not affect your user experience while using various apps, including aerofly
Update 1.7.15 includes a new VR view, updated icons, and more. https://steamcommunity.com/gam…etail/1599262707999562008
Today's update features big improvements to the VR View window and device status icons.
By default, the new VR View is docked to the bottom of the status window with the option to undock or go full screen. The undocked view also comes with a new "Both Eyes" mode that blends the left and right views together for a better approximation of the field of view visible in the headset. We're also bringing you updated device status icons sporting new colors and support for high-DPI displays.
Finally, our campaign against crashes and other bugs in SteamVR continues and many more bugs have been squashed. Sorry, bugs.
Full Update Notes
- Simplified the user experience to more clearly and consistently communicate general VR and specific device status.
- Added an improved VR display view, with new docked preview and full screen modes, plus new blended left/right-eye views. To display or hide the new VR View, visit the SteamVR status window menu or right-click on the headset icon, then select this item in its context menu.
- Device icons updated to reflect Steam, SteamVR, and Valve Index styles.
- Device icons updated to support high-DPI displays for Valve Index, Valve Index Controllers, Vive, Vive Pro, Vive Controllers, Vive Trackers, Rift S, and Rift S Controllers.
- Fixed issue with only one auto-launching overlay app starting when multiple were set to auto-launch.
- Added URL handler to open the Debug Commands window. vrmonitor://debugcommands
- Added ‘Open Debug Commands’ to VR View menu.
- Added url hander for individual debug commands (e.g. vrmonitor://debugcommands/async_mode_toggle).
- Fixed keyboard placement relative to overlays so it will stop obscuring the overlay that the input is going to.
- Chaperone restricts room center to be within 1km of your tracking system origin. 1km ought to be enough for anybody. (This prevents chaperone adjustment tools from accidentally moving the center of your room outside the solar system, causing floating point math issues that manifest as things like “flickering in HMD”).
- Fix a case where launching a VR app from Steam that never connected to SteamVR would prevent you from launching other VR apps from Steam until that launch transition timed out.
- Fix for a minor set of Index’s Bluetooth initialization errors locking out one of the two Index HMD radios. This caused connectivity issues on one of the controllers.
- Fixed an issue that could cause room setup to automatically launch for drivers that provide their own chaperone bounds. This should fix Oculus users who were being prompted to run room setup after reboot.
- Fixed “show controls” UI breaking when switching to another action set in certain titles. Notably, this affected “On Foot” in No Man’s Sky.
- Fix a rare crash when a user hand-edits their settings file to be valid JSON but not valid settings.
- Fixed Friend count not showing up in lobby panels.
- Fixed a bug where in some cases on Windows 10, SteamVR Home would incorrectly claim that its files were corrupted and fail to load
- Fixed Thor’s Hammer collectible not spawning in game
- Fixed sorting issues with screenshot/image panels
- Fixed vrwebhelper apps showing up in recent games panel
- Fixed Linux crash
- Added setting in binding configs called “Return bindings with X hand” that cause the gamepad or treadmill bindings to also apply to left/right hand devices when a SteamVR Input application restricts its action results by device.
- For legacy input applications, when the trigger is clicked the trigger value will not be set to 1.0 if the click action is already coming from the trigger. This fixes a bug with Oculus Touch controllers in games like VRChat, where the grip trigger value would jump from partially pulled to fully pulled. For legacy bindings that put a trigger click action on another button, the existing behavior remains and the axis value will be set to 1.0.
- Fixed issue that prevented ‘axis 2’ from being used as a trigger in legacy games on Index Controllers. When combined with new bindings this fixes The Forest, and possibly other games.
- Fixed issue with the changed bit being incorrect when Get*ActionData is called more than once per frame.
- Fixed issue with retrieving a pose from a skeletal action returning the default pose instead of whatever is bound (and also spamming the log in the process.)
- Fixed unsafe conditions for games that call GetDigitalActionData and GetAnalogActionData from multiple threads.
- Fixed a gpu scheduling issue with motion smoothing on AMD hardware which was causing motion smoothing to disable itself after a while due to poor performance.
- Improved throttling logic when motion smoothing is enabled. Previously, throttling and prediction were locked together when motion smoothing is enabled. This update allows throttling to back off of the prediction level based on the current average gpu performance. A typical example is when an app can render at half-rate (i.e. each rendered frame takes more than a single frame to finish, but less than two), but spends an extra frame on the cpu performing the draw calls, etc. This makes each of those frames a total of three frame latent, but can still deliver a new frame every other vsync interval. Note: This only applies to Lighthouse based hmds (e.g. Vive, Index) since most other headsets (e.g. Rift, WMR) use their own compositor and associated logic for throttling and prediction.
- Fixed passing depth through to the Oculus runtime from apps which provide it.
- Added support for importing standing-only guardian setups. This fixes the issue where running guardian setup to set the floor level but skipping the room bounds step was resulting in the headset being stuck in the floor in SteamVR.
- When the Oculus runtime returns one of its library load errors (ovrError_LibLoad, ovrError_LibSymbols, or ovrError_LibPath) and we know the HMD is present and the service is running, attempt to fix the PATH and try ovr_Initialize again. This is the case that results in SteamVR error 1114 (which currently suggests a re-install of Oculus SW or a reboot to fix PATH issues). Known causes of this PATH issue: Users manually placing Steam first in their path (possibly combined with putting unknown “fix” DLLs into the Steam folder), users who have the Oculus runtime installed but not in their path, and users launching VR from third party tools (like Unity Editor) which completely replace the path prior to launch.
- Improve the registration of controllers to headsets when moving together rigidly coupled, such as with a gun stock accessory. This applies to all combinations of HMDs, controllers, and tracking pucks made by Valve and HTC.
- Fix an issue where launching SteamVR with a wireless controller already connected (such as when using the controller itself to launch SteamVR from Steam) could prevent the controller from tracking.
- Reduce the amount of tracking disruption caused by plugging in additional USB devices in the middle of a play session.
- Changed default index controller binding for keyboard to move Shift and Symbols to the A buttons, and analog tracking to the thumbsticks+triggers.
- Added brightness control, set in-headset under Display Settings (firmware update required)
- Enabled column correction to mitigate vertical "screen door" (firmware update required). Column correction is only active during SteamVR [beta] usage. Controls are available in-headset, under Display Settings -> Advanced.
- Reduce default loadPriority of the Valve-supplied gamepad driver so that it loads after most VR drivers. This is to favor VR drivers in the case where both drivers want to load gamepad related DLLs and there are version conflicts.
- Fixed various performance issues.
- Fixed IVRCompositor::GetFrameTiming() reporting bad data when async mode was enabled, correcting the reporting of impossibly long frame times in the frame timing window.
- Fixed a system hang when async compute is enabled.
- Reduce CPU utilization when async reprojection is disabled.
- Note to external SteamVR driver developers: The runtime now looks for icons with @2x variants and will automatically pick them up for your driver(s) if provided. See the drivers that ship with SteamVR for reference (e.g. runtime/drivers/indexhmd/resources/icons).
- On first launch, if the stylized icons do not exist, they will be automatically generated and saved next to your existing icons with a custom postfix, then used for subsequent launches. You are encouraged to ship these generated icons with your driver(s) alongside your existing icons, which should remain unchanged. Doing so will enable your icons to already exist on disk for users upon launch. You also should feel free to hand-edit the automated output as needed. Please contact us if you have any questions.
- Icon style changes can be reverted by setting they keys customIconStyle and customOffIconStyle to the empty string in your steamvr.vrsettings file. As always, exercise extreme caution when modifying this file as no error checking is performed.
So......... where is tha' fuel cutoff switch? (After crawling around on the floor in VR looking for it)
I thought I heard once they were sending data in a format compatible with x-plane
Looking at the four most recently active threads as I write this, they are all in German. That can't be a good thing for the forum, can it?
I an not xenophobic or anti-immigrant or nativist etc., but based on the activity on FSCloudPort most of our community is probably shut out from those posts.
Not really , at least not for me. Google Chrome automatically translates these to English for me .
This is one of my favorite planes. I have it for another sim, and it has a copilot (or maybe she's a passenger) who takes in the scenery while I fly.
Some of the attitudes about sims in this thread are soooo different from mine...
(Not for the first time, I feel like an alien in the community, sometimes)
So many seem to act as if there can be only one sim in their lives, and once the decisions been made, all others must of course be deleted and given up for dead.
To me, that would be sooooo boring!
I don't even know how many flight sims are on my computer at this point, but none of them are perfect, and each in its own way has something to offer.
Will I fly aerofly today? Maybe not, but there's always War Thunder, or P3D or.... whatever. It changes with my mood, and when my mood is for smoothness and other things in VR, it's back to Aerofly and maybe a trip over Lukla.
Even when the new God-Sim (supposedly) arrives, I have no doubt I will still be Visiting Aerofly. And X-Plane.... And Wings of Prey, and.....
Why should there be only one? Or even just two? Or Three! (or six!)