balus

And yet you missed the first part of my post, the part that answered one of your complaints by simply reading the manual, you're welcome. One of the problems with text based forums is that they are two dimensional and sometimes what one person considers friendly can come across as condescending and aggressive, especially when you demand " This bug (or"feature"?) should be removed asap. NOT YET TESTED " your words, not mine. Once again, you may want to consider your tone/approach. Just as a suggestion, use ChatGPT or similar to rephrase the post in a friendly and formal manner, you might be surprised at the small changes made that affect how it may be interpreted by others.

Page 43 in the manual, turn off the AUTO GPU DISCO option. I prefer it on, makes sense to me. You may want to adjust your tone a little, you are coming across as demanding and agressive. You may or may not have some flight time, although I don't know how many hours are in an A350, but it is obvious that you aren't a programmer. I've completed a dozen flights and I'm happy with the money spent, there are issues, yes, but I'm confident that they will be addressed. Oh and I get more WASM problems with aircraft from another supplier that begins with P!

probably the nose gear retracting directly beneath the flight deck - pretty sure you can turn this off in the options menus

so a GSX update and an inBuilds update and all seems to be working.

Thanks, but the tug doesn't turn up, if I turn off the parking brake I get a message to turn it on again so I doubt that it is bindings

Anyone having an issue with pushback? I am using remote GSX and when I remove chocks, GPU and turn the beacon on I select Pushback from the remote GSX menu in the EFP, I choose the operator, the wing walkers appear and that's it, nothing more. So I disabled the remote GSX and tried to use the pushback option in the EFB, says it's working, but the aircraft doesn't move. Now I tired the Shift P option and still nothing. If I turn the parking brake off when using GSX I get the GSX message to set brakes. Not sure if this is a GSX, iniBuilds or a me problem, most likely the latter 🙂

As the title says.

Have an A380 parked at gate 640, use GSX to operate the jetway, I get a message that the gate has a default jetway, and then an operating message, but the jetway doesn't move. GSX is fully updated and OMAA has been excluded in the config. What am I missing?

Can anyone using a Logitech yoke share their sensitivity settings, mine seems to be overly sensitive with the A300.

Reinstalled MSFS, unable to load inManager, uninstalled and removed appdata entries, reinstalled, get to the enter login details and it won't accept credentials. I can login via the web with no problems, reset the password, no change. Why can I not access the software that I have purchased?

ok, problem resolved, and it wasn't an inibuilds issue. Before purchasing I had another KDTW from flightsim.to installed and forgot all about it - it didn't show up in the Marketplace when I was checking for duplicates, it was just buried in the Community folder, why does everything have to go in the same folder? So while I was starting my troubleshooting process to work out if I had a conflicting addon causing the problem I found it, deleted it and now the issue is resolved. Thanks to all who assisted, you may now call me Richard Cranium!

ok so renaming the Community Folder and creating a new one then copying the scenery over, well zipping it up and unzipping it since MS doesn't like Community folders that aren't on C drive, the scenery is ok. So does this mean that I have another scenery package that is conflicting, not sure how that could happen, but then again I'm not a scenery designer.

No, that didn't work, and I have the rolling cache turned off. If anything it has made it worse, the taxiway's are all over the place.

just checked and Photogrammatery is on

pretty sure it is on, will check when I get home. yes the issue does persist as I get closer, in fact I hit it and couldn't taxi past, had to slew which just so much fun in MSFS no other DTW scenery installed - do I need to disable the default and how would I do that if I did?

Any idea what this is, next to 21R? It looks like John D Dingell drive has risen above the terrain - how do I fix it?

Just trying to confirm that the texture.ini_base that goes into the PMDG 777-200LR folder will work for 77F liveries as well or does it also need to be copied to the PMDG 777F folder as well?