No, I read your post several times. You have proven that the fault goes away with no Community content. The Sim is most likely the problem (because it’s so extensible), but the only thing you can fix in the short term is the 3rd party stuff. If you want to help the sim fix their code, you’ll need to be specific about what Community folder content triggers this. At the moment you’ve said you aren’t helping Asobo fix their code by doing that next level of identification. Not much point coming here moaning about the problem without actually offering to do a little more diagnosis to get to an actionable bug report…
1 Like
So, you tell me to do exactly what I did and explain in my initial post. THANKS SO MUCH 
I already did A LOT OF DIAGNOSIS so please stop trying to help, re-re-read my initial post (you still have missed parts apparently !). Also, proposing that I would carry on diagnosis on demand is not saying "At the moment you’ve said you aren’t helping Asobo "…
Many posts have been helpful here to understand further on my problem, you’re just hanging around proposing things that have already been proposed / that I have already made !
I get the same issue with an empty community folder in the beta.
Please don’t make assumptions about bugs, it doesn’t help anyone.
You need to be open minded about resolving issues like this, not assume a previous solution is automatically the same way to solve this.
The fact that the wing holder is visible indicates this is a different bug, manifesting itself further along the asset loading chain but still distrupting the detection of the aileron code.
An empty commuinty folder for me also confirms its a sim issue, possibly a loading order of some asset.
As to why @DreadMetis confirms it works with empty community I don’t know.
Confirmed it’s not FS Realistic related.
@Sonicviz the post was not in response to your post. I know your situation is different, when you have a clean Community it is still broken. That’s not the case for Dreadmetis.
This is the crux of the problem. You (and only you) can tell us which one of the things in your community folder is the one that causes this issue. None of us are aware what you have installed. None of us are able to repro this without knowing what item in your commmunity folder is the one that is causing the problem. Yet you’ve said you will not identify what community content is causing the problem… so again, I ask, what are you proposing anyone does here to help the situation??? I’m not suggesting you scan them for the same old pattern that you say you’ve addressed before, I’m taking you at your word that you’ve done that. But there’s a clear causation for your current issue, somewhere in your community folder, because we all know that when you clean it out it works fine.
If we knew which item was causing this, anyone could repro it and then Asobo and/or that dev could look and identify what (new) pattern or problem there is that needs to be addressed. There’s clearly something else wrong here, but getting to the bottom of it needs more data, and only you hold that key… Obi-wan, you’re our only hope…
It’s the same bug. You’re not actually helping here.
I’m taking you at your word that you’ve done that. But there’s a clear causation for your current issue, somewhere in your community folder, because we all know that when you clean it out it works fine.
You didn’t even read. I have the bug whether my community folder is empty or not.
You’re passive aggressive accusations are not conducive to solving this, especially if you don’t bother to read what people write.
can’t be the same bug if by removing Community it works for one and not for you. Similar, for sure, certainly the observed behaviour is identical, but when the problem disappears with a clear Community, there’s an influence there that can’t be ignored
1 Like
hey Sonic, I know your situation is different, I’m not replying to your thread post.
I like many here are just trying to get enough evidence to help Asobo make this sim even better. I’m not being passive agressive, sure you may sense my frustration, but that’s not agression.
That’s not true at all. You need to be open to all possibilities, and treat each bug independently even though there may be some overlap.
The visual signifier of wing holder being present and wing action not triggering indicate it’s the same issue, with a common cause somewhere that is independant of community folder.
It’s not FSR, I’ve tested and eliminated that.
Another cause could be packages or content from marketplace.
Again, your not helping with the chain of thought.
Every bug has a trigger (or triggers) and can eventually be found.
You need to be open in the process of elimination and testing.
if we don’t collect the extra info, then nobody can test the next hypothesis that there is a problem in the community content that Dreadmetis has… If we identify that, and someone else loads it and it breaks something, then there’s a direct relationship there. If someone else loads it and it does not break it, different line of thinking, but without testing that there’s no real answer…
And I’m telling you it IS likely the same bug with some common trigger, manifesting under different conditions. More evidence is what you look for when solving bugs to narrow down the common cause, especially if the signature is the same. Dismissing them isn’t the way to resolve issues.
You solve these issues by asking lots of questions, dumb ones, smart ones, obvious ones, then follow up leads to test. You don’t dismiss things because you assume something. Assume nothing. Start from scratch.
You are, with all due respect, getting in the way of us doing this.
It’s a matter of finding the pattern among the noise.
yes, you do. By eliminating and testing what is in someone’s Community folder, for example. 
I’m not saying you’re wrong. But finding what that trigger is that’s in Dreadmetis’ community folder will all add to the richness of the bug report. We don’t even know if they are using the beta version like you…
There you go again with the passive agressive putdown.
You are not helping.
Update: Issue resolved. Cause: Appeared to be a controller conflict.
Would still like a bindable key trigger to use as an alternate launch method.
@DreadMetis
Sorry to hear about your issue, it can be frustrating.
Mine appeared to be a controller conflict between my T16000M and Gamepad, so I crashed the sim and restarted in safe mode (which only loads base sim, no marketplace addons) and empty community (which would not load in safe mode anyway), reset a few things, tested on “official” glider strips, and suddenly the trigger started working again.
Double check your controller inputs, especially if you have multiple controllers connected - use them all to trigger it via rudders.
Apart from 100% eliminating the known airport services.spb issue, I don’t know what else could cause it atm.
FSR was the only third party app I was using, and that wasn’t the cause in this case either.
So work through the list of possible causes, eliminating them, testing in safe mode with MSFS gliders on an official glider airport (just to eliminate possible issues):
. Eliminate the known airport services.spb issue in community addons
. Eliminate third party apps for possible conflicts (eg: FSR etc)
. Eliminate Controller conflicts
. Eliminate Controller bind issues
. Eliminate glider assistance settings etc
. [insert here]
Good luck!
This is realy worthless, sorry to say with all respect. I tried all buttons on keyboard but nothing triggers the airtow or winch. Also in free flight when I choose glider and click in the aircraft the launch methos to air tow, nothing works. Very disappointing
achimvdg@ziggo.nl
I haven’t read the whole thread but have you tried the yellow handle? Is your marketplace content up to date?
And I will add that there are thousands of mods out there, I’m sure Asobo will look at the situation but no-one should expect anything from them when it comes to 3rd party dysfunction especially if that would mean added latency from extra code. The tail does not wag the dog.
We are evidently not waiting for Asobo (nor myself ! Even if I did try / diagnose a few hundreds among my about a thousand mods “useable”) to test all the 3PD mods, no one ever tried to say that. What we must do is report the environment at a specific moment with ats much accuracy as possible so that Asobo can have a better understanding at what can cause a working installation to become unstalble after ONE UPDATE FROM THEM.
I understand the SDK team is tiny compared to the millions of players that are advertised by Ms, BUT it is their choice to be only 3, not mine. So the lack of SDK documentation on gliders for example for developpers from Asobo is again, not my choice (nor the 3rd party’s one), when they have to get into Asobo’s files to get “examples” of documentation…
Anyone here can go on any forum and ask for example Jonxx if the new arguments for the glider has been shared in the SDK (it has not been : some of us in the community helped those devs to get their gliders right by sharing our discoveries/ common knowledge missing from Asobo’s documentation)
But all of this has nothing to do with a sudden bug that takes 3 different forms (as per posts here) since SUXI…
Oh and even if I do appreciate the rudder wagging being a “homage” to IRL gliding, I think a sim, on a chair in front of a (mostly) 2D screen need “translations” that would work. EVERYONE here asked for an option to rebind. Options are good 
I saw video on you tube and I see a guy holding the glider straight before air tow starts, for me that guy is not there, might that be the issue why airtow and winch will not start ?
Not only as tow release but if it works the yellow handle also starts the winch launch. I’m not certain the wing holder even makes an appearance.
when i release yellow handle the system goes back to restart, makes no difference sorry, it simply wont work
Then I suggest you find out which mod(s) are causing this and look or wait for an update. Asobo cannot test every addon out there so it’s down to the 3PDs to fix their own products … and of course their users to report problems to them.
If you’re missing the wing guy only on certain 3PD gliders, it is very possible your mod isn’t up to date/ not complete according to the (lacking) SDK documentation.
You might want to go into the “aircraft.cfg” and check you have those in the “Service” part :
WING_RUNNER = 1
WINCH = 1
And that in the “FLTSIM” part of the file (where you have description for all liveries) that the craft type role is correct :
ui_typerole=“Glider” and not ui_typerole=“Aircraft”
for each and every livery.
Or ask the dev to do it in his mod !
If the problem appears on the 2 default/ vanilla gliders (or on a modded MSFS, on all gliders, be vanilla or 3PD) it will be a bug… Which you should report here. Which is apparently caused by a change in something on Asobo’s / Ms’s side (on the scenery front) without warning (enought ?) 3PD.