Mark Amber

Hello- I was just enjoying a calm flight in the passenger variant of the Saab 340A on VOR approach procedure in VR I turned the sector knob up from Rose up one click (I didn’t intend to do this- I was trying to modify the brightness of the display one knob to the left, but this thread is not about that) and what happened was I got an error console popping up taking up my entire vision. Now I don’t know what the error was. Things happen from time to time. That’s ok. The problem was that the gizmo console took up my entire view and parked itself right there. I couldn’t see the exit button or anything on the corners. It was remarkably huge- looked to be 1 meter in width and only a handful of centimeters from me. I thought I would be clever and try to click up where the “red light” exit button was but my plan was foiled- I hit reboot by mistake. do I have any way to adjust the default size of that window in VR so this does not happen? I have noticed this being a problem in general in VR. But I have never seen one show up quite so huge. Same problem is present on the Toliss 321 and TBM900. But with those at least the popups I can see behind and close them too. Maybe there is a setting or maybe this is something that can be fixed in the aircraft addon just to be sure that if this window pops up it will not completely blind me from all instruments and cockpit. Thanks for any help! Mark

alright- I got back to it finally! I had a successful flight! so- here’s the thing that fixed the blur... I had the scaling setting set to 75% for the system. Now I know what everyone is thinking “well there’s your problem!”... but hold on! The default 172 and the ZIBO 738 handles this setting moderately well - or at least it’s good enough and I can live with the better performance. But the TBM? No way! Need this all set to 100% for system and game. I’m guessing that there is something slightly different about the textures here and they don’t scale down as well. Probably because the 737 is so digital and squared off it is easier to scale up and down. And the 172 is all gauges! now as for the windows. I have gotten very careful, but it’s still annoying. I found that if I can somehow hit the touch point while the giant pop-out covers my vision. My final notes: 1: The default seated position for VR is really far forward. I’m basing this on the headrest. I like it so the seated position is right against my headrest. 2: there are way too many view points (this might not be adjustable to devs- I think they coincide with the hard coded viewpoints) when you sit back a little further it is much easier to manipulate the avionics without them being hyper sensitive. so overall I’m really happy now and I did a lot of experimentation. If anyone else is having issues ill check this thread again and keep notifications on for it! This is a fantastic add on... so much better than the Microsoft flight sim 930 and even with my new settings it really performs worse on paper but I have no side effects from being in VR.

Sorry all I haven’t gotten back in the TMB yet. Lots of festivities. I’m keen to try again tonight. Here’s my take, the performance seems to be fine. Honestly I never look at the FPS values. Maybe it’s because I have a 10core CPU and that’s making up for the aging GPU. But more likely I’m not that sensitive to it. The ZIBO is a bit jerky but it works for me. Is this specific to the TBM for you too? Default 172, ZIBO... all of that is tack sharp. But the speed card by the window is a complete blur. Even if I get my eyes right up on it. It’s like as if all the textures were fully loaded, squashed to 1/16 size, then blown back up. I was playing with Microsoft 2020 in VR and there were some settings I messed with to get everything working a bit better - maybe I just have something messed up!

Thanks- I will play with AA after work. I am limited by a 1080Ti at this time so I think I’m stuck with a lower setting. I understand that a 1080Ti cannot always be tack sharp on a brand new 2020 HP headset with 2kX2k in each eye but it’s quite puzzling to me that every other aircraft looks better. I will take a shot into the lens tonight too. Once a panel pops out I cannot close it without inducing crashing the game (task manager or open some WMR feature I know that crashes the game) , as I am unable to see the menu to enable the mouse cursor to close the box. I cannot use the VR wands to close it to the best of my knowledge.

Hello! I just got my VR setup working and I have some questions/observations about the TBM900 for VR - I have figured out that if I click on any of the PFD/MFD screens they will “pop out” and fill my entire vision. That’s nice but how do I close these without restarting the flight? They are so big that the edges will get cut off behind the cockpit so I might just have to look a certain direction. They do not have the window border like the payload window - everything here seems a bit fuzzy. Much more so than the Zibo 737-800X (4k and non-4k) and the default 172. This is regardless of if I bring my face really close to the text or not. In the zibo things look sharp just like in 2D, yes sometimes I need to lean in but it’s fine. but in the TBM it seems intentionally fuzzed even when I lean in or use the zoom hotkey. - the G1000 controls are super sensitive (in addition to being fuzzy) I found a thread where it looks like I can edit some config file and slow them down but this will be wiped out when I update and I do not like generally messing with these files myself. Is this on the roadmap to get fixed? - in VR in “walk around mode” (outside the aircraft) I can’t seem to get the covers off. I have to use the payload window. I thought I managed to click the fuel cap once but now I cant get it. Is there any way to increase the hitbox? The first three issues are really hurting the experience. Please let me know if there are further questions I can answer regarding my setup.

I now cannot re-create this today. is there a setting which could be bound to a joystick button (besides AP trims switch in the 3D cockpit) which could cause the altitude hold/AP to lose effectiveness and explain what was happening yesterday?

When this happened to me I assumed I broke the gear or something on landing or mis configured a system. I was having almost no hydraulic pressure. I never found out what it was that caused the pressure to fall what error or omission I made or if it was a bug, but I did not have the issue again. Try a hard landing on the nose gear or simulating a failure of the hydraulics and see if the symptoms match. Maybe I will take the Saab 340 for a flight today and see.

I am going try some other configurations of the cabin and payloads tomorrow. After going back and forth I can say with the experimental flight model ON it seems to all work better overall. The runway “bumpiness” is obviously just nonsense but everything else about it feels better. tonight I did go through the joystick settings and check for phantom axis. I imagine that “experimental mode off” was a crutch and with experimental mode “on” I am just seeing either a weird sim-specific problem (joystick button mapping problem... again, the axis are all fine) or some sort of user error on my part. I will try to recreate my flight tomorrow where I had this issue.

Hello, I have been happily flying TBM900 without the “experimental flight model” button checked in XP. Everything seems to work as I would expect. Somewhere here on the forum I was reading that the experimental flight model was either recommended or optional. So I turned it on and started a new flight. I even made a new airframe (I wasn’t sure if this was needed). I did have a well documented “bumping” issue. I was bouncing up and down like a bus on a street with potholes on the runway. in addition to that issue and more problematic, I started having more issues around 15k feet. It felt like the flaps were in T/O with the autopilot off. Like there was a lot of drag and a LOT of lift. The autopilot would not hold the attitude of the flight director. It was trying to trim, and it was commanding the control surfaces. The autopilot was unable to maintain FL270 with Torque power in the “cruise” band, even with the FD showing nose down it continued to climb at 100-150 ft/min any additional throttle just added to the pitch up with the autopilot unable to correct further. I imagine based on this there is some limit which the autopilot runs the trim out to, because I was able to trim nose down manually, disengaging the autopilot, and fly level by hand but I was almost out of trim. In the old flight model this is not a problem. In “non experimental” I am flying right now at FL270 with power in the cruise band at Mach 0.54 and the autopilot works fine So I expect this is a regression in the experimental model or my user error. Do you developers have any idea? I am happy to go through the paces, but also maybe you could talk a little about if the experimental model is needed. -mark