Andydigital

I didn't realise that Neal, good to know. I doubt I would touch a Saitek Yoke again to be honest, I didn't think much of the build quality or smoothness of movement, plus I just prefer joysticks especially my Thrustmaster Warthog, its smooth as silk (after doing the spring mod) and has Hall Effect sensors, so its likely to last longer than I will.

Windows update automatically installs stuff like this so I don't know what you think this will achieve.

I'm using two USB Saitek Quadrants without issue, I don't own the Yoke as I was one of the early adopters who sent mine back for a refund because of the phantom button press issues.

How are those screenshots supposed to prove your theory?

If its buttons can be seen in Windows game controllers interface and in FSX without needing any special drivers then yes.

If you are talking about the deadzone in the centre where it does nothing even though you are moving the mouse, then you need to look in the FSX controls menu, specifically in the calibration tab, select the mouse look option from the controls/device drop down menu (cant remember the name exactly) then move the Null Zone sliders all the way to the left.

I think this might be a bug and its state isn't saved, I can't get this option to save no matter what I do with the panel states or startup states. It is rather irritating if you are trying to use a hardware radio stack with the aircraft as it wont work until you change this option to NEVER.

What PMDG startup panel state are you using though, that is the question.

Because of the thread started in the last 24 hours detailing it elsewhere in the forum.

I'm sorry but this is utter poppycock, I've been using the supposed wrong version (6.0.6001.18000) for 6 weeks in a new build and not had a single freeze. I've just tried this other version today and sure enough had my first freeze.

Well I just changed to this supposed correct version of this file and I've had my first lockup since rebuilding this PC over 6 weeks ago, it froze with the faded white screen, THANKS FOR NOTHING. Back to using the version Nick suggested 6.0.6001.18000.

Well we can't help you anymore, as I said already some sounds will still mute when using the NGX or 777, but without you trying it for yourself and listening to the result you cannot possibly come to a conclusion whether its suitable for YOU or not. If PMDG implement an option to not mute their extra sounds then if will not sound any different regardless of whether FS has focus or not, IF you have Soundstream of course.

No because as Guenter said above FSX itself does not model such a feature. The quickest way to see what the list of FSX controls is is to use the document provided with FSUIPC, named as highlighted, its located somewhere similar to below. *:\FSX\Modules\FSUIPC Documents

Yes but only 1% of sounds will be heard (going by what Ryan just said) if you was using the NGX or 777 with it and FS lost focus. To be honest I don't think it's quite that extreme, but like I said buy it and try it and make your own mind up. I've never had a crash in FSX due to Sounstream, so you are in a tiny minority, it's certainly not something I have read on their support forum. As far as I am aware, making a program play sounds when it has lost focus is a trivial thing to fix if you have the source code of course.

I suggest you just buy it and try it, Flight1 has a 30 day no quibble money back guarantee and the price of the app isn't going to break the bank. I find it works great even with PMDG aircraft, you only lose some of the sounds when switching away from FS, and certainly not enough sounds to blemish the experience too much.

No not at all, I'd not even bothered looking, I went straight into FSUIPC and cleaned up the profiles I thought might conflict due to similar names and the FSUIPC profile option "substring" (or something like that) and the problem was gone. I also deleted the general assignments for aircraft with no profile set so it may have been a conflict there too. Parts of the VC not working when clicked with a mouse in my experience have one of two causes, EZDok having a camera inside the cockpit geometry (headrest for example), or a conflict somewhere in FSUIPC and one of its profiles as stated above.

If you have FSUIPC and you are using profiles try making a copy of the FSUIPC4.ini and keep it somewhere safe as a backup, then go into the working file and delete any other profiles you might have, leave your 777 profile intact (unless it was based on another profile when you created it, if it was you should probably clear that too and start again) and that includes deleting the general profile for aircraft you don't have specific profiles for. I had a similar problem when I first installed the 777 and it was a conflict of some kind in one of the other profiles that somehow caused problems. If you get it working then add the other profiles back a few at a time and test again. If the problem comes back you should be able to work out which other profile may be causing an issue.

You need "SoundStream" from Flight1, that will stop any sounds from FS itself from muting when FS loses focus, but it won't stop any externally generated sound modules going quiet, PMDG would have to make a change to their module for them to continue to be heard when FS doesn't have focus.

You're welcome Andrew.

Are you sure it's not the auto brakes turning on, double tap the pedals and see if they release next time it happens.

Your brakes need calibrating, it sounds like they are binding when your feet are off the pedals, either that or you haven't reversed the axis and they are releasing when you press them instead of vice versa.

Yup sure is, if it was windowed the background wouldn't be black it would show the desktop background image, plus you would see other running program's besides FS gauges.

It's already setup and working on the MCP2 are you sure you haven't just missed its assignment. I'm not near my FS PC so I cannot look for it, but I have used Speed Intervention many times with the 777.

Mark this thread has moved on from the question asked in the opening post, please read the thread properly and you will see that landing and take-off distances are not going to be effected by the DynamicFrictions.lua which is what this thread is mostly discussing now. This thread is no longer talking about the hacks made directly to the Sim1.dll which you will find discussed elsewhere, and yes those hacks will that will negatively effect the 777. Please read the thread its only 2 pages long. THIS IS THE LAST TIME I WILL SAY IT, LANDING AND TAKEOFF DISTANCES ARE NOT EFFECTED BY THE DYNAMICFRICTION.LUA no matter what aircraft you are using.

You can assign the Spoilers to an axis and they work exactly the same as default aircraft, just do not calibrate the axis or it won't work. To reverse the axis if you need to add ",*-1" (without the quotes) to the end of the line where your spoiler axis is defined in the FSUIPC4.ini, the control code for the spoiler axis is 66382, look through your 777 Axes section for that number and add it there. As an example here is what mine looks like; 3=QY,256,F,66382,0,0,0,*-1