JC_YYZ

It works! Also looks like some attention was given to the fuel selector, as it's much easier to manipulate. Thanks so much. Flying VR in this plane is fantastic.

The plane has a free-cantering nose wheel, so you can’t steer it with the rudder pedals (unless you’re at higher speeds on takeoff/landing). You have to tap the toe brakes to steer the plane. There are some great YouTubers that show how it’s done.

Not a problem. It seems that more people are trying out VR, and a lot of developers are giving it some real attention (IXEG, X-Crafts). I must say, other than the starting position your plane performs quite well in VR. I have a few picky issues - but nothing that prevents me from flying. Great work!

Here are the coordinates that I use (in the vrconfig file) X= -0.267 Y= 0.660 Z= -0.013 Hope these help. They seem to be a good eye height (although I have never sat in a real Cirrus) so I don't know how high the glare shield would be compared to your eye height.

Update: I spent several days wiping and reinstalling all of my X-Plane files, aircraft, and scenery. The TBM 900 works now with no issues.

Also for reference I have attached a log after I started XP and opened another payware airplane (the Islander). Log.txt

So I actually unplugged the Rift S (and made sure the drivers were updated), removed and reinstalled my audio driver, and made sure that my sound setup hadn't changed. I still got the exact same issue. I have added two new payware planes in the last week or so (and haven't flown the TBM in that time), so I am suspicious that something has changed my setup. I am tempted to wipe my install and start clean. It might get me in the air again. Log (2).zip

Thanks for looking into this. I’ll give these a try and keep you posted. Very much appreciated.

Here you. Sorry about the leaving the last one unzipped. Much smaller log file this time. Still the same extremely loud wind noise, and when I tried to quit after loading, the program hung. Hopefully the log gave you everything you need though. Log.zip

Here you go. Log.txt

No luck with deleting the content of the state folder. The log file is 121,959 KB and full of lines like below: 2020-06-30 19:07:05 TBM900[wav.c:681]: Error performing alSourcef(0x100A) on WAV burn_low.wav, error 0xa003. 2020-06-30 19:07:05 TBM900[wav.c:681]: Error performing alSourcef(0x100A) on WAV burn_inn.wav, error 0xa003. 2020-06-30 19:07:05 TBM900[wav.c:681]: Error performing alSourcef(0x100A) on WAV burn.wav, error 0xa003. 2020-06-30 19:07:05 TBM900[wav.c:838]: Error performing alSourcef(0x1022) on WAV burn.wav, error 0xa003. 2020-06-30 19:07:05 TBM900[wav.c:681]: Error performing alSourcef(0x100A) on WAV burn_inn.wav, error 0xa003. 2020-06-30 19:07:05 TBM900[wav.c:681]: Error performing alSourcef(0x100A) on WAV burn2.wav, error 0xa003. 2020-06-30 19:07:05 TBM900[wav.c:838]: Error performing alSourcef(0x1022) on WAV burn2.wav, error 0xa003. 2020-06-30 19:07:05 TBM900[wav.c:681]: Error performing alSourcef(0x100A) on WAV burn_behind.wav, error 0xa003. 2020-06-30 19:07:05 TBM900[wav.c:838]: Error performing alSourcef(0x1022) on WAV burn_behind.wav, error 0xa003 No other plane is causing this issue - and as soon as I deactivate the TBM plugin in the plugins menu (while the plane is loaded) the roaring sound stops. I am wondering if I need to do a full reinstall of everything...?

I went to fly the TBM today and upon loading, there was an extremely loud sound (similar to a loud wind or fire sound). Muting all sounds in X-Plane (including turning off master volume via the XP sound panel) did not stop this sound, nor did re-loading the plane or creating a new airframe. The only time the sound stopped was when I loaded a new (different model) plane in the sim. This occurred when the plane was in its cold and dark state. I tried uninstalling the plane and reinstalling it - still with the same issue. When I uncheck the TBM plugin in the plugin menu, the sound stops. I have never had this happen before and the only thing that has changed is that I installed the latest IXEG 737 along with the Gizmo beta. Does the TBM rely on the Gizmo plugin? A different version perhaps? Has anyone else experienced this? Update: I have checked my log and I have thousands upon thousands of lines like this: (I have reinstalled the plane twice) 2020-06-30 17:03:20 TBM900[wav.c:681]: Error performing alSourcef(0x100A) on WAV burn_low.wav, error 0xa003. 2020-06-30 17:03:20 TBM900[wav.c:681]: Error performing alSourcef(0x100A) on WAV burn_inn.wav, error 0xa003. 2020-06-30 17:03:20 TBM900[wav.c:681]: Error performing alSourcef(0x100A) on WAV burn.wav, error 0xa003. 2020-06-30 17:03:20 TBM900[wav.c:838]: Error performing alSourcef(0x1022) on WAV burn.wav, error 0xa003. 2020-06-30 17:03:20 TBM900[wav.c:681]: Error performing alSourcef(0x100A) on WAV burn_inn.wav, error 0xa003. 2020-06-30 17:03:20 TBM900[wav.c:681]: Error performing alSourcef(0x100A) on WAV burn2.wav, error 0xa003. 2020-06-30 17:03:20 TBM900[wav.c:838]: Error performing alSourcef(0x1022) on WAV burn2.wav, error 0xa003. 2020-06-30 17:03:20 TBM900[wav.c:681]: Error performing alSourcef(0x100A) on WAV burn_behind.wav, error 0xa003. 2020-06-30 17:03:20 TBM900[wav.c:838]: Error performing alSourcef(0x1022) on WAV burn_behind.wav, error 0xa003. 2020-06-30 17:03:20 TBM900[wav.c:681]: Error performing alSourcef(0x100A) on WAV burn_start_inn.wav, error 0xa003. 2020-06-30 17:03:20 TBM900[wav.c:681]: Error performing alSourcef(0x100A) on WAV burn_start_out.wav, error 0xa003. 2020-06-30 17:03:20 TBM900[wav.c:681]: Error performing alSourcef(0x100A) on WAV prop_300rpm.wav, error 0xa003. 2020-06-30 17:03:20 TBM900[wav.c:681]: Error performing alSourcef(0x100A) on WAV prop_300rpm.wav, error 0xa003. 2020-06-30 17:03:20 TBM900[wav.c:838]: Error performing alSourcef(0x1022) on WAV prop_300rpm.wav, error 0xa003. 2020-06-30 17:03:20 TBM900[wav.c:681]: Error performing alSourcef(0x100A) on WAV prop_1200rpm_LF.wav, error 0xa003. 2020-06-30 17:03:20 TBM900[wav.c:681]: Error performing alSourcef(0x100A) on WAV prop_1200rpm_LF.wav, error 0xa003. 2020-06-30 17:03:20 TBM900[wav.c:681]: Error performing alSourcef(0x100A) on WAV prop_1150rpm.wav, error 0xa003. 2020-06-30 17:03:20 TBM900[wav.c:838]: Error performing alSourcef(0x1022) on WAV prop_1150rpm.wav, error 0xa003. 2020-06-30 17:03:20 TBM900[wav.c:681]: Error performing alSourcef(0x100A) on WAV prop_2000_front.wav, error 0xa003. 2020-06-30 17:03:20 TBM900[wav.c:838]: Error performing alSourcef(0x1022) on WAV prop_2000_front.wav, error 0xa003. 2020-06-30 17:03:20 TBM900[wav.c:681]: Error performing alSourcef(0x100A) on WAV prop_2000rpm_side.wav, error 0xa003. 2020-06-30 17:03:20 TBM900[wav.c:838]: Error performing alSourcef(0x1022) on WAV prop_2000rpm_side.wav, error 0xa003. 2020-06-30 17:03:20 TBM900[wav.c:681]: Error performing alSourcef(0x100A) on WAV prop_2000rpm_inside.wav, error 0xa003. 2020-06-30 17:03:20 TBM900[wav.c:681]: Error performing alSourcef(0x100A) on WAV woosh.wav, error 0xa003. 2020-06-30 17:03:20 TBM900[wav.c:838]: Error performing alSourcef(0x1022) on WAV woosh.wav, error 0xa003. 2020-06-30 17:03:20 TBM900[wav.c:681]: Error performing alSourcef(0x100A) on WAV woosh_bass.wav, error 0xa003. 2020-06-30 17:03:20 TBM900[wav.c:838]: Error performing alSourcef(0x1022) on WAV woosh_bass.wav, error 0xa003. 2020-06-30 17:03:20 TBM900[wav.c:681]: Error performing alSourcef(0x100A) on WAV start_init_inside.wav, error 0xa003. 2020-06-30 17:03:20 TBM900[wav.c:681]: Error performing alSourcef(0x100A) on WAV start_wind.wav, error 0xa003. 2020-06-30 17:03:20 TBM900[wav.c:681]: Error performing alSourcef(0x100A) on WAV start_click_inside.wav, error 0xa003. 2020-06-30 17:03:20 TBM900[wav.c:681]: Error performing alSourcef(0x100A) on WAV start_click.wav, error 0xa003.

For sure! That’s not a problem at all. I dropped the suggestion in response to the initial call/ask for suggestions related to VR and their airplane in the post - perhaps hoping to have it added to the list for future versions. In the meantime, happy to mix in a little 2D work as well (I use it for Better Pushback anyway).

The video is great and very informative. A huge thank you to the team for their attention to VR. I am fairly new to VR (and to the IXEG) and I thoroughly enjoy both. There are some great features coming, but one I didn’t notice is the ability to access the load and configuration windows from within VR. I don’t have much experience with this plane, so it may already be possible - but if not, it would be a welcome feature (similar to the ToLiss and the TBM where you can ‘float’ the window in VR and use it while setting up your flight in the cockpit). As always, thanks so much for all of the time and work you and the team put into this.

This is great news! Again, thanks for your work and dedication to the plane. I know you mentioned a list of obstacles, but I am sure that most pilots are eager to get their headsets on and flying despite some of those issues. I know a lot of us use external controllers (yoke, rudder pedals) and also configure our flights in 2D before putting on the headset (payload, pushback, etc). Thanks again and looking forward to 1.31!

That is great news. I have been flying sims for years, but I am new to both the IXEG and this past week, new to VR. I have to say that I can't believe I waited this long to get into VR flying and I am excited to see that you're working hard to bring this unique experience to the update. I want to echo the other posts and thank you for all the hard work you put into this simulations. It can often be thankless work, so just know that it's appreciated.

This might be where I am getting hung up. Instead of using proper piloting skills, I was essentially relying on the VNAV to take me right to BOD without using any constraints in between. I will alter my flying accordingly and stop being lazy! LOL

I have tried that. I even scroll it to change the altitude by 100 feet in either direction, I hit ENT and it jumps to the next line while leaving the VNAV profile empty. And every YT video I have watched, the pilot simply hits ENT and it populates the window. This only occurs for me inside the approach legs. I have included a quick clip to show what I mean. https://youtu.be/ZYQggNX-VaU

So, I want to start by saying that most likely I am doing this wrong. I have consulted a lot of YouTube videos, manuals and forums, and I can't seem to find a solution. I input my route: Dep. Apt. > DEP > waypoints > Arv. Apt. > Arrival (if applicable) > Approach Once I have all of this input, I move to the arrival because I want to designate an altitude on the waypoint before the IAF. I know the altitude needs to be cyan (as opposed to white) and when I highlight it and hit ENT, the cursor just moves to the next line (usually the IAF which is below) and nothing is entered in the VNAV profile window. This happens every time. No matter the route. I always have to add the same waypoint above the white title line the signifies the approach, and then add the altitude and without fail, I can designate that altitude and it gives me my TOD and all the VNAV goodies I need. Am I (most likely) doing something wrong? Or am I asking the system to do something it isn't designed to do? Thanks in advance.