Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

26th May 2021 Developer Q&A: Post Your Questions

Featured Replies

Generally the Asobo's airplanes need to be addressed, urgently. The team worked especially on the sceneries and fixing the graphic engine bugs, but their airplanes are not improved at all.

Missing the PMDG DC6 in MSFS 2024 (she's here, but...).

  • Replies 63
  • Views 6k
  • Created
  • Last Reply
On 5/13/2021 at 9:12 PM, Dillon said:

I posted about the tree draw distance.  Please vote on this if you agree.

Can you provide a link, please?

On 5/13/2021 at 7:43 PM, sd_flyer said:

Upvoted, but I would like to call your attention to what appears to be a typo, and a not precisely explained effect:

You wrote: " 1. Rudder to the wind side..."

It's actually rudder downwind / away from the wind, and...,  as you correctly wrote next, aileron into the wind...

And bellow that you wrote:

"Airplane weathervane (pointing nose toward wind side) while being on the ground and during ground roll (take off). This is incorrect !"

this is actually not incorrect... It's particularly true if it's a light aircraft, or if during the later phase of a takeoff roll when the lift is already doing it's job and releasing some weight and friction from the wheels... It's particularly true on aircraft like gliders with just a  central wheel, and even while being tugged ....

Also check this excellent examples involving a biggie and a not so but still bigger than a GA ... : 

 

 

Edited by jcomm

Flying gliders since 1980

Flightsimming since 1992

AMD Ryzen 5600x, 32GB RAM, GPU Nvidia RTX 3060 Ti 8 GB, 1 TB and 500 GB nvme2 SSD drives, HP 27" 60Hz LED monitor @ 1920x1080, T16000, Hotas from old X52 Pro, Saitek Combat Rudder Pro (2010 model)

It's unfortunate that we have to rely on asking Questions for Asobo to open their eyes ("What lightning bug?" !!), I've added a couple of questions about the hideous Horizon Line issue and the POI LOD blatant lack of knowledge bug.
I fully appreciate that these Q&As shouldn't be solely focused on the "bad" aspects of the Sim, each individual question deserves to be mentioned, but I just cringe every time they get asked something then they have that bemused look on their faces as though they don't know what they're being asked about - it's almost as if they don't play the same game we do.

Pico Neo3 Link VR - Windows 11 64bit, Gigabyte Z590 Aorus Elite Mobo, i7-10700KF CPU, Gigabyte RX 9070 XT OC 16gb (AMD GPU), 32gig Corsair 3600mhz RAM, SSD x2 + M.2 SSD 1tb x1

Saitek X45 HOTAS - Saitek Pro Rudder Pedals - Logitech Flight Yoke - Homemade 3 Button & 8-directional Joystick Box, SNES Controller (used as a Button Box - Additional USB Numpad (used as a Button Box)

18 minutes ago, Noooch said:

I posted about the sunken boats issue here, please vote if you want this to be taken care of 😉

https://forums.flightsimulator.com/t/could-blackshark-ai-identify-boats-in-marinas-and-create-3d-models-on-top-of-them/402196

Thanks, voted. Yes, they should tackle this. Aside a few hand-crafted areas, it's annoying all over the world close to the sea, rivers and lakes. Moreover, I have been told it's not trivial to remedy these "underwater worlds" for addon developers.

Kind regards, Michael

Intel i7-13700K / AsRock Z790 / Crucial 32 GB DDR 5 / ASUS RTX 4080OC 16GB / BeQuiet ATX 1000W / WD m.2 NVMe 2TB (System) / WD m.2 NVMe 4 TB (MSFS) / WD HDD 10 TB / XTOP+Saitek hardware panel /  LG 34UM95 3440 x 1440  / HP Reverb 1 (2160x2160 per eye) / Win 11

5 hours ago, jcomm said:

Upvoted, but I would like to call your attention to what appears to be a typo, and a not precisely explained effect:

You wrote: " 1. Rudder to the wind side..."

It's actually rudder downwind / away from the wind, and...,  as you correctly wrote next, aileron into the wind...

And bellow that you wrote:

"Airplane weathervane (pointing nose toward wind side) while being on the ground and during ground roll (take off). This is incorrect !"

this is actually not incorrect... It's particularly true if it's a light aircraft, or if during the later phase of a takeoff roll when the lift is already doing it's job and releasing some weight and friction from the wheels... It's particularly true on aircraft like gliders with just a  central wheel, and even while being tugged ....

Also check this excellent examples involving a biggie and a not so but still bigger than a GA ... : 

 

 

I have already replied to you on MSFS and I'm going to reply again. The display of heavy airplanes doesn't show they weathervane while on take off run but rather at the point of lift off. Also  it's not uncommon for pilot to over compensate with gusty wind and jerk nose to the either side.

My point is airplane do not weathervane when three wheel tightly plant on runway.And yes during snow or rain runway friction is a bit different and so when pilot ease controls aft friction reduces significantly faster than in dry condition. That what what we see in the video 

Life time flight sim enthusiast, current airplane owner 172P (past C182F). FAA CP/IR ASEL/AMEL, FI ASEL

My System: AMD Ryzen 9 9950X3D , MSI X870 GAMING PLUS, 64G RAM, ASUS RTX5090, 4T SSD

Put my hands on (pic/dual/given)

7GCAA, 8KCAB, BE24, BE76, BE35-C33, BE35, C150, C152, C172B/N/P/R/SP, 182F, M20E,M20C, M20J, AT6(SNJ4), PA28-140,PA28-151, PA28-161,PA28-181,PA28RT-201,PA28R-180/201T, PA24-250, PA32-300R, PA44, AC114, YAK-18T, YAK-52, SR22

 

4 hours ago, MarcG said:

but I just cringe every time they get asked something then they have that bemused look on their faces as though they don't know what they're being asked about - it's almost as if they don't play the same game we do.

I find myself having the exact same issue with these Q&A’s. Either they are not testing the game at all, or there’s a language barrier which prevents them from understanding the questions. 
 

I wanted to believe it’s the second issue, but there’s simply no way they could’ve acted clueless when they were asked about terrain spikes and the excessive lightning issues unless they didn’t test the build at all before giving it the green light to push to all users. 

There are doubtlessly several hundred separate concerns, needs and wants that could be formed into questions for ASOBO about when they will all be addressed. I have but one comment. Not really a question I guess and that is that it is my opinion that ASOBO should focus mostly on one thing only until it is "finished" and that is the SDK. Without a completed (or mostly) SDK, 3rd party developers are not going to be able to program the add-ons that we all clamber for. ASOBO is not going to perfect ATC, that will be left for a developer I think. Same with the native large aircraft. I don't believe ASOBO has even intended to develop those and would leave them to PMDG and others. Finish the SDK, the rest will follow I think.

United001

Windows 10 Pro, version: 10.0.18363 Build 18363 - Intel(R) Core(TM) i7-9700K CPU @ 3.60 Mhz, 8 Core(s), 8 Logical Processors; Mobo: Z390 Phatom Gaming 4S-IB: Physical Memory: 16Gigs; GPU: NVIDIA GeForce FTX 2080 Super, 8 Gigs; 500Gigs Hard-Drive; 1TB SSD; 1TB SSD; 50" Samsung 4K Flat-screen monitor; 26" LG side-car monitor. Saitek Yoke and Throttle. Saitek Rudder Pedals.
Screen Resolution: Full Screen: 1920X1080 Full and Windowed modes. 
 

 

4 hours ago, sd_flyer said:

I have already replied to you on MSFS and I'm going to reply again. The display of heavy airplanes doesn't show they weathervane while on take off run but rather at the point of lift off. Also  it's not uncommon for pilot to over compensate with gusty wind and jerk nose to the either side.

My point is airplane do not weathervane when three wheel tightly plant on runway.And yes during snow or rain runway friction is a bit different and so when pilot ease controls aft friction reduces significantly faster than in dry condition. That what what we see in the video 

Well,

again, I have to disagree... Sorry 😕

Not only is it wrong to say ( even from a purely physics / aerodynamics pov ) that there's no "weathervane" on ground, with all wheels or not, and at whatever speed ( other than standing still, unless the wind is blowing really strong... ) you travel, and that's why you're actually forced to use rudder AND aileron (*) even while taxiing under x-wind, but also when you write "rudder into the wind", and I assume you're talking about rudder "pedals"..., it really should be the opposite.

Curiously from a geometric pov, and although sign conventions play oposite on aerodynamics formulae, the rudder itself, as a surface, has it's chord oriented towards the wind when rudder opposite the wind is used to counter x-wind effects during taxi and takeoff.. so you could sort of say that "the rudder points to the wind", but I don't think that's what you meant 😉

(*) aileron use under x-wind, specially on taildraggers is even trickier depending on what quadrant the wind is blowing from realitive to the aircraft axis.

Again, if the videos I posted above can't convince you, watch this one, and there's no "aquaplaning"...

 

Edited by jcomm

Flying gliders since 1980

Flightsimming since 1992

AMD Ryzen 5600x, 32GB RAM, GPU Nvidia RTX 3060 Ti 8 GB, 1 TB and 500 GB nvme2 SSD drives, HP 27" 60Hz LED monitor @ 1920x1080, T16000, Hotas from old X52 Pro, Saitek Combat Rudder Pro (2010 model)

3 minutes ago, jcomm said:

Well,

again, I have to disagree... Sorry 😕

Not only is it wrong to say ( from a purely physics / aerodynamics pov ) that there's no "weathervane" on ground, with all wheels or not, and at whatever speed ( other than standing still, unless the wind is blowing really strong... ) you travel, and that's why you're actually forced to use rudder AND aileron (*) even while taxiing under x-wind, but also when you write "rudder into the wind", adn I assume you're talking about rudder "pedals"...

Curiously from a geometric pov, and although sign conventions play oposite on aerodynamics formulae, the rudder itself, as a surface, has it's chord oriented towards the wind when rudder opposite the wind is used to counter x-wind effects during taxi and takeoff.. so you could sort of say that "the rudder points to the wind", but I don't think that's what you meant 😉

(*) aileron use under x-wind, specially on taildraggers is even trickier depending on what quadrant the wind is blowing from realitive to the aircraft axis.

Yeah, not only does that happen.  When taking off in certain directions in piston aircraft you have to use left rudder; which is backwards.  I believe the entire issue is already known to ASOBO and is due to the XWind factor being reversed as well as the ground friction model being incorrect.  I can't remember how they described it, but I think it's actually 2 separate issues.

Jeff D. Nielsen (KMCI)

https://www.twitch.tv/pilotskcx

https://discord.io/MaxDutyDay

VENGEANCE a8200 Gaming PC: AMD Ryzen 9 9950X3D, GeForce RTX 5080, 64GB DDR5, 4TB (2TB/2TB) M.2 SSD, Win11 Pro

15 minutes ago, jcomm said:

Well,

again, I have to disagree... Sorry 😕

Not only is it wrong to say ( from a purely physics / aerodynamics pov ) that there's no "weathervane" on ground, with all wheels or not, and at whatever speed ( other than standing still, unless the wind is blowing really strong... ) you travel, and that's why you're actually forced to use rudder AND aileron (*) even while taxiing under x-wind, but also when you write "rudder into the wind", and I assume you're talking about rudder "pedals"..., it really should be the opposite.

Curiously from a geometric pov, and although sign conventions play oposite on aerodynamics formulae, the rudder itself, as a surface, has it's chord oriented towards the wind when rudder opposite the wind is used to counter x-wind effects during taxi and takeoff.. so you could sort of say that "the rudder points to the wind", but I don't think that's what you meant 😉

(*) aileron use under x-wind, specially on taildraggers is even trickier depending on what quadrant the wind is blowing from realitive to the aircraft axis.

Yes I should probably phrased it differently. You should say rudder to keep centerline. There indeed many variables here.

My point if airplane has proper aileron wind correction with three wheel touching the ground it shouldn't not yaw to the wind (wethervane). Of course we are not talking about hurricane kind winds here 🙂 

What I see in MSFS is lack of proper ground friction as I understand it. Especially during  taxi or initial take off roll. For example if I keep proper aileron deflection to compensate for sideloading airplane on my initial run. Lets abstractgate and say whichever rudder is necessary to keep centerline. Airplane  should not weathervane until I bring controls aft and unload front wheel 

Life time flight sim enthusiast, current airplane owner 172P (past C182F). FAA CP/IR ASEL/AMEL, FI ASEL

My System: AMD Ryzen 9 9950X3D , MSI X870 GAMING PLUS, 64G RAM, ASUS RTX5090, 4T SSD

Put my hands on (pic/dual/given)

7GCAA, 8KCAB, BE24, BE76, BE35-C33, BE35, C150, C152, C172B/N/P/R/SP, 182F, M20E,M20C, M20J, AT6(SNJ4), PA28-140,PA28-151, PA28-161,PA28-181,PA28RT-201,PA28R-180/201T, PA24-250, PA32-300R, PA44, AC114, YAK-18T, YAK-52, SR22

 

21 minutes ago, sd_flyer said:

What I see in MSFS is lack of proper ground friction as I understand it. 

I fully agree with you on that, at least from what I can recall since I last played it months ago....

Edited by jcomm

Flying gliders since 1980

Flightsimming since 1992

AMD Ryzen 5600x, 32GB RAM, GPU Nvidia RTX 3060 Ti 8 GB, 1 TB and 500 GB nvme2 SSD drives, HP 27" 60Hz LED monitor @ 1920x1080, T16000, Hotas from old X52 Pro, Saitek Combat Rudder Pro (2010 model)

3 hours ago, FAZZ3 said:

I wanted to believe it’s the second issue, but there’s simply no way they could’ve acted clueless when they were asked about terrain spikes and the excessive lightning issues unless they didn’t test the build at all before giving it the green light to push to all users.

As a longtime developer now, one thing that is one of the most difficult things to communicate to end users is how bugs can manifest. Users generally end up in repeated scenarios in really complex software where their specific combination of personal traits (tendency to do things in X order), use case, and specific hardware cause them to see a certain bug more than once. And because they see that bug more than once, they (justifiably) assume the bug is so obvious it should smack a tester in the face.

But, the unfortunately reality is that oftentimes this stuff is way less than obvious. On those two issues specifically (recalling the Q&A), I had never seen a terrain spike until much later (and I had been in the sim coding for hours and hours most days) and I only had just seen the lightning issue the day before. These kinds of problems are super insidious because they depend on so many factors that you, as a developer, cannot set up because you don't have enough super exact information. If I recall, the on the lightning issue Martial said the devs couldn't even repro the lightning issue locally. So sometimes this stuff is just not as glaring as an end user with their own pet list of annoyances feels they should be.

This isn't exclusively a dev -> end user problem, either. I've lost count of the number of times another dev said to me "hey man, this thing is super busted, it breaks for me every time I press this button" and I have the same code and it's totally working for me and I spend a day smacking that button in every strange way I can think of. Usually this is a good thing, because it means some unlikely combination of factors have conspired to make the bug show itself and now you get the opportunity to debug it while it is breaking.

But those aren't even the worst ones. The worst ones are when you are running things side by side in multiple threads and the breakage comes about because the order of things finishing (race conditions). They're usually (but not always) incredibly subtle, and because it only breaks on certain timing, oftentimes attaching the debugger or building the software in a debug config changes that timing just enough that the bug totally disappears and so you can't actually debug it. Those can take days or weeks to track down, and sometimes you just have to bail because you've already spent $4500 worth of dev time chasing this Heisenbug down with nothing to show for it, and it only affects a limited subset of users.

Anyway, said all that not so much to say that I think bugs are OK (they aren't) so much as to say that all three dudes you see on that Q&A haven't a bone of malice in their body.

-Matt

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.