Romeo_Tango

I've recently noticed that airport characters do not show when I am in VR mode. They appear in abundance when in 2D mode but disappear the instant I switch to VR mode. I checked that I have the correct setting in VR mode. In fact, I have the same settings in both 2D and VR modes. I have disabled the community folder to see if I am having conflicts with any of my addons, but the problem persists. I am not even sure when this started happening. I have only noticed the issue since last week. I even left the Beta and went back to the main release, hoping that the Beta was the problem, but that made no difference. Does anyone here have this issue or have any idea how to make the airport workers appear when in VR? Please share. Thanks in advance.

So long ago I do not remember the individual snippets I downloaded, so I have uploaded my entire switch panel. It is Id 16072 and named A2A Comanche Author romeo_tango. I hope this works for you. I'm not sure how much experience you have with SPAD, but you don't need to download the entire device; you can download and install only the landing gear section. Good luck, and if convenient, please report here if this works

I suggest going to the online snippets. This is what I used to build my Comanche and Aerostar profiles, as I have no clue how to program SPAD. My gear switch works perfectly with the 'realistic' setting, and this is an online snippet I downloaded from when the Comanche was released for MSFS 2020, and it works just fine with the native Comanche in MSFS 2024

The ability to remove the copilot with a button click on the fly, rather than the convoluted method we currently have.

I am seeking guidance to find the controls profile folder for MSFS 2024. Thanks in advance for your attention.

Hi everyone, the following is a copy/ paste of a comment I left at the official MSFS beta 'regression' topic. It was 'hidden' by the 'community' PLease Asobo, now that you have brought so much attention to one of your silly ideas, wont you please listen to the community of serious simmers and also remove the stupid TOGGLE EFB__SHIFT+C ENTER AIRCRAFT message in the walk around mode. I realize that the ‘gamers’ are the users you most depend on, and without them, this huge project could fail. However, please, can’t you make these annoying messages optional? Most ‘simmers’ don’t want or need these messages taking away from our immersion. End quote. The following is the reason given for the post being hidden. Your post was flagged as inappropriate: the community feels it is offensive, abusive, to be hateful conduct or a violation of our community guidelines. Your post has been hidden due to the amount of times it was flagged by community members. If it was not deleted or removed by a moderator due to the severity of the content, please consider how you will revise your post to reflect the feedback from moderators. You can edit your post after 10 minutes, and it will be automatically unhidden. However, if the post is hidden a second time, it will remain hidden until handled by staff. For additional guidance, please refer to our Code of Conduct. End quote. I am curious; was my post offensive? And how have I violated the code of conduct? Please educate me.

I too have had freezes with say-Intentions and Beta V1.6.13 I wasn't sure SI was the cause because it doesn't happen on every flight and because I fly exclusively in VR mode, I thought perhaps I have settings too high.

Well, I know your pain. I just tried the latest beta after being unable to test the last two versions.I am also experiencing freezes, but in VR. I have also seen that frame gen causes screen flickering in both 2D and VR modes. Back to the release ver. for me.

Have you tried disabling addons in the community folder?

No more double views on the monitor screen when in VR.

I get a flickering screen in 2d if frame generation is turned on. All seems well in VR.

Su 4 Beta is available now.

AAH! Seems you had a default installation, and when you uninstalled the Beta, all MSFS-related folders from your App Data folder were deleted. If you plan to participate in future MSFS Betas, please ensure you do not install to the default location. I also suggest that you move your Community folder to a custom location, preferably to a different physical drive.

I suspect that you previously moved your community folder from its default location, and the re-install is now pointing to the default location. I had the same experience. I used the config file to point to the custom location of my community folder, and all was well with my Comanche and Aerostar again. Good luck.

The last time I did this, instead of the latest BETA, I ended with a reinstall of the release version. I then had to reinstall the latest BETA. Is this what to expect, or should I expect the newest BETA when I uninstall my current BETA? I don't want to mess things up, as Version 21 has been the best-performing version of MSFS2024 I have experienced.