Microsoft Flight Simulator 2020 Plugin 1.1.3.0

I've attached the debug version of SimConnect_UDP.exe, which prints to the console the data sent in every UDP packet. You can replace the file in AppData\Local\SimTools\MFS2020. Let me know what it prints out - this will tell me whether the problem is in the sending of data from the game to SimConnect_UDP, or from SimConnect_UDP to the SimTools plugin. If the print statements are too fast to see, you can lower the packet rate in SimConnect_UDP_config.txt.

This would be useful for anyone else having data problems as well.

I'm about to take the plunge and buy FS 2020. After reading this thread, I'd like to ask should I buy from the MS Store or Steam? I like to have all my games in 1 place in Steam for many reasons, but there might reasons why I should get it from the MS store directly? Thoughts?

I have the Steam version, so the plugin was written using that version for testing, and some people were initially having problems with the MS Store version. The latest plugin update should fix those, so it hopefully doesn't matter which version you have. That said, having the same version as me would probably decrease your chances of future plugin issues, so I would lean towards Steam.

I surely agree with your statement Count me in!! I'm very appreciative and grateful for the time you took to create the plugin.

I Tried.
Did not work.

Can you send a picture of the console window for SimConnect_UDP.exe, using this debug version? It will be helpful for me to see what data is being sent.

Ok.
Unusual movements.

Ah, I think that solves it! Your locale (Brazilian Portuguese?) is using a comma, rather than a period, to separate the integer part of the number from the decimal places. The UDP application sends numbers in this form. The SimTools plugin then interprets them in the English standard, where a comma is used to group digits, so is just ignored when determining the value of the number.

Is there a mismatch between the locale that the game is set to and the system locale? It might fix the problem if they were the same, or maybe they both have to be English. I could also post an update to the plugin that corrects for this, if that would be more convenient.

If it is possible to adjust the plugin it would be perfect, as I have already tried to change the location and it has not resolved.

Okay, I'll work on this later today.

Solved.
I made a mistake in the language settings.
Now it worked.

You could make a plugin so you don't have to change the language.
It would be useful.

Tank you

Thanks, I changed the decimal separator in the region settings of windows and everything is working.

Icy7CE updated Microsoft Flight Simulator 2020 Plugin with a new update entry:

Fixed locale bug

Read the rest of this update entry...

This update should solve the problem. Try changing your language settings back to what they were, and let me know if it works.

Thanks again! What is the best way to install a new version vs the old one in Simtool?

Just drag the downloaded zip file over PluginUpdater, and then uninstall and reinstall the patch in GameManager.

@Icy7CE Thank you for the plug-in. It works very good.
I was wondering if it is possible to have a "wind" flow output.
I have a fan setup which I really enjoy in DCS and NoLimits2.
It is uses game dash but its a simple PWM / Arduino serial sketch.
I realize you should not get wind effects inside a Cessna 150 but it adds very much to the immersion
and gives a great sense of speed. I always fly with a HP reverb VR head mounted display and some air blowing on me is welcome.

Glad to hear it's working well. I'm planning to look into adding GameDash and GameVibe support at some point soon, which I think will be pretty easy.

Well, i just read all comments. Plugin works fine, and i use simshake aviator soft, made by andre, for vibes on my 8 transducers. the one thing its weird. at launch, pop up says me 100hz its blowed time connections. this is because 100hz maybe reachs high refresh than the system software support... change to 20hz could it possible fix this.