57 minutes ago, OverTheEDJ said:

How do you (having had a good experience) get to throw around a term like ignorance when there are people with issues that you are not aware of

I am aware of them as they are discussed enough on here.  My use of the term 'ignorance' was in relation to the op saying 2024 'is not flyable'.  Clearly it is flyable for many.  If the op had said it wasn't flyable for him, then I would not have had reason to respond in the way I did.

1 hour ago, JRBarrett said:

Have never seen that happen. I set up all my controls when I first installed 2024 in late November, and they have never changed or been lost in all the time since then.

That's something to note, and we need to uncover the secret. So many people are complaining about this issue, and numerous YouTubers are attempting to assist and resolve it without success. Did you try setting up a few profiles for different aircraft, and they never changed after a restart? If so, please share your steps to prevent that issue. Many will appreciate your solution. 

40 minutes ago, Richard Sennett said:

DX11 or DX12 works on Win 11 - just depends on what the game was made in DX11 or DX12

Thanks Richard

7 minutes ago, psolk said:

Thanks Richard

My pleasure Paul 🙂

27 minutes ago, LRBS said:

That's something to note, and we need to uncover the secret. So many people are complaining about this issue, and numerous YouTubers are attempting to assist and resolve it without success. Did you try setting up a few profiles for different aircraft, and they never changed after a restart? If so, please share your steps to prevent that issue. Many will appreciate your solution. 

It’s could be hardware  or OS system issue . when every time someone restart PC controllers get different hardware id and MSFS treated as new, therefore loosing profile 

34 minutes ago, sd_flyer said:

It’s could be hardware  or OS system issue . when every time someone restart PC controllers get different hardware id and MSFS treated as new, therefore loosing profile 

I wouldn't know. So many people have this issue with controllers, menus, and graphic settings. I was thinking the same way, but I can't see any changes in hardware or profiles. To my knowledge, this is the first "simulator" to have this issue. That's why I'm asking him for step-by-step instructions on how to resolve it. As I mentioned, three different systems and many users have this issue, yet nobody has resolved it. The bottom line is that this should not be an issue, and the customer should not have to spend any more money on additional software like FSUIPC or AXIS and OHS due to ASOBO's incompetence. 

2 hours ago, Tuskin38 said:

  

 

Please learn to read everything before talking, It says right here in the blog:

4 then

 

17 hours ago, MrFuzzy said:

LOL, AVSim is known for its negativity but the users' reactions to this dev blog are so tame in comparison with the censored official forum outrage:

https://forums.flightsimulator.com/t/january-16-2025-development-update-blog-discussion/698449

There is plenty of unneeded censorship that happens right here on AvSim.

6 hours ago, Donka said:

I'm genuinely surprised by how little a priority VR gets. It is very broken at the moment in 2024.

How is it broken? I'm curious as I use it everyday.

There are a couple of minor annoyances.

Apparently different folks have problems that others don't.

2 hours ago, JRBarrett said:

Have never seen that happen. I set up all my controls when I first installed 2024 in late November, and they have never changed or been lost in all the time since then.

Same here. No issues with controller profiles. Must be hardware specific as it definitely is not affecting all.

2 hours ago, MrBitstFlyer said:

I am aware of them as they are discussed enough on here.  My use of the term 'ignorance' was in relation to the op saying 2024 'is not flyable'.  Clearly it is flyable for many.  If the op had said it wasn't flyable for him, then I would not have had reason to respond in the way I did.

Nope, your reasoning doesn't "fly" here.

Clearly 2024 is not flyable for "many"; hence the refunds, many poor reviews, and issues discussed on the OF.

So if it works for many and not for many, how does your use of the word ignorance apply given all that you are not aware of (or don't know) as it relates to the experience for those with the issues? Do you have any solutions for them to somehow align their poor experience with your positive experience?

 

Edited January 17, 20251 yr by OverTheEDJ

3 hours ago, Bond said:

That bug-logged is from MS. Get a grip.

Seems you just don't know how the forum works, do you?

Get a grip?  What an odd thing to say.  Have you ever partaken in a conversation?

There is not VRAM bug.  VRAM optimization is needed in DX12.  It takes time and I'm sure they are working on it...hence SU2 timeframe.

1 hour ago, LRBS said:

I wouldn't know. So many people have this issue with controllers, menus, and graphic settings. I was thinking the same way, but I can't see any changes in hardware or profiles. To my knowledge, this is the first "simulator" to have this issue. That's why I'm asking him for step-by-step instructions on how to resolve it. As I mentioned, three different systems and many users have this issue, yet nobody has resolved it. The bottom line is that this should not be an issue, and the customer should not have to spend any more money on additional software like FSUIPC or AXIS and OHS due to ASOBO's incompetence. 

I'm not trying to defend Asobo, but I deal with a lot of customers (in my line of business) who have a lot of issues with system, setup, privileges, and 3rd party software, you name it - that interfere with software I sell. "Many users" is not a thing.  It's an impression of what people see on public forum. Most of the posts people see are usually complains and bug reports not praises! There could be many users who don't have a problem and we never hear from them . 

I personally don't have any issue with settings. Of course it doesn't mean other shouldn't. It could be very specific user to user. I did lost once 2024 profile for my T.320 stick, when windows 11 update decided to reintroduce my T.320 as new hardware. LOL I hardly can blame Asobo for that but rather Microsoft LOL I know it's almost the same but still factually Asobo develop MSFS software, and I strongly believe that xbox app or clouds are on Microsoft side.

I deal a lot with SDKs from our partners. And yes it could be a pain and a lot of back and forth communication while  a lot of customer suffers.

I as they say: people my praise something  for a long time, but it takes only one fault to forget all the good and remember only bad.   

Edited January 17, 20251 yr by sd_flyer

3 hours ago, psolk said:

So forgive the ignorance but I thought the 1st update or maybe the 2nd also contained some WASM debug tools.  I "assumed" and I am very good at making an a** of myself naturally so don't often need help that also meant iFly, PMDG and others may have had what they needed to at least begin to troubleshoot their planes in 2024.  

Has anyone heard anything from either of them?  Not sure what other devs were also waiting on the WASM tools or if anyone else has said anything along these lines... 

Cheers.

You're correct but it didn't happen in the 1st update if I remember correctly. Since that update to the SDK, I have seen PMDG staff in the dev forum asking questions about how things work, including how to get the rain wipe effect to work with windshield wipers so they're definitely in active compatibility development now.

1 hour ago, sd_flyer said:

I personally don't have any issue with settings.

I wonder what is so different about your system that doesn't have those issues. There are no problems, as I mentioned, with the 2020. I still believe that something is very wrong here when so many people complain all over the internet and in forums about it. That's why I wonder what specific user-to-user issue is affecting so many with the same problem.

As I mentioned earlier, even though I cleaned the USB memory of any previous installations, deleted all the profiles, uninstalled and reinstalled 2024, followed all the tutorials, formatted my PC, and reinstalled everything without any addons that might interfere, I'm at a loss here. As I said, there are three of us with three different computers, and together with others, we are experiencing the same issue. It's not as you mentioned; we lost a joystick profile. It does not remember the settings or the aircraft profiles saved. 

As I asked @JRBarret, I would also like to encourage you to consider that there are some issues with this, and perhaps you all have an idea or solution that could help many of us. 

 

Edited January 18, 20251 yr by LRBS