avrbifly

works great otherwise!

No doubt a conflict on my system...  and not on the other fs2crew versions.  I ran track IR after pulling into the gate yesterday and the FO would no longer run tasks.  I did see a brief message flash - something about voice recognition...  I'll see if I can read it in a next experiment.

Agreed.  And it always worked well in the past, so I hope this conflict can be fixed.

Flew a lot today.  Without track Ir running I had no issues.  This has always worked fine in the past with other version for Airbus and PMDG 737, so I wonder what the conflict is now?  I think it would be easy for you to see the issue if you have track ir to test with.

I believe I am , yes...i see the appropriate commands in the green bar.  The FO responds,but doesn't perform any of the tasks (switches). Im running p3d4.4 with track ir and ezdok.  I noticed as i loaded track ir during an engine start, that the FO hasn't thrown any switches since.

I'm unable to get fs2Crew to work with the latest Maddogx.  Have tried reinstalling maddog and fs2crew as well as updating fsuipc to the latest.  The failure mode doesn't seem consistent, but the FO eventually stops performing tasks.  I can move or reset using the control panel and get the FO to respond but he won't perform any of the tasks. P3D v4.4

As far as the install goes, that seems to work.  But using the Start Center to activate doesn't.  It doesn't detect the MD11 presence.  Any suggestions for that?

I think the problem with that approach is that I've only been able to install the MD11 in one or the other, so chose to uninstall from fsx and move the md11 to steam...  So all the panel files are in steam..  Can I copy those to fsx to satisfy the installer,and then copy back to steam?

So, I do have steam and boxed fsx side by side.  I was able to install the MD11 by using the registry tool to change the path to the steam path.  However I can't get fscrew to install because it's looking for panel files in the fsx path.  Is there a way to fake this out so I can get the md11 fs2crew working in steam?

I've also got brakes on my Saitek pedals set with a slope of 5. While I still try to mimimize brake usage on the C90 during taxi, I do find them quite useable with occasional gentle application.

 

This plane certainly does make me wish I could set up beta properly on my throttle quadrant, though. I don't like to use reverse too much during taxi, as the sound transition is pretty artificial. Not bad for landing, but going back and forth during taxi grates on my nerves. I've gotten pretty good at anticipating lag with throttles though, and as a consequence my taxi efforts have also improved with the Turbine Duke. About my only complaint is that I expect the techiques that I've developed don't much resemble what would be done IRL.

 

Scott

I configured fsuipc so that when I pull my Saitek throttle into reverse it hits F1 followed by F2 4 or 5 times. Does a better job of simulating BETA which is what is usually used rather than full reverse.

2 issues:

Want to limit the pushback distance before the 90 degree turn. When I decrease the distance number to what I want, it performs that, but then after the 90 degree turn keeps pushing for what seems like forever...

after pushing last night and setting the parking brake, I could not get it to show released even though it was in the released position. After starting the pmdg ngx pushback, it released.

Other than that, great so far.

I currently have reinstalled FSX & Acceleration UT2 GEX UTX REX PMDG the fsdt scenery, but have not added FSUIPC yet.

Anybody have any issues with long pauses just after departure at fsdt ( LAS DFW ) airports. I've been trying to trouble shoot an issue where this occurs, but only after flying for an extended period. I get anywhere from a 15 second to 1 minute pause just after takeoff while still over airport. Been flying the 737NGX and don't know if it is specific to that airplane or not.

Try the 257.15 set and your land textures will be crisp and sharp. You can even take your LOD to 6.5 Also, you might want to read this:http://forum.avsim.n...the-verdict-is/

No, 260.99 is working great on my GTX470, use it..

Currently I use the 197.45 drivers with my GT285. My GTX 480 is on the way. What driver version should I plan to install for this card? I hear the latest has some issues. Should I plan on 257.21?

Did you try a search?

ALLOW_SHADER_30 simply allows FSX to make use of SM3.0 for Water Effects, because they are the only shaders compiled using SM3.0 everything else is either 2.0 or 1.1 This was a 'compatibility' or design decision I suppose. so, DONT USE if you have old hardware. SM3.0 is DX9c only.AffinityMask=12 yes, reduces thread collisions and FSX scales well up to 3 CPU. after that, you are wasting CPU cycles. There is no performance impact here, so don't worry. And remember, even though affinity mask=12 only makes two cores active (core2 and core3) you'll STILL have activity in CORE0 because the fiber system is NOT bound to the Affinity mask vale, so, even AffinityMask=12 will make use of 3 CORES's for FSXIn the 'BufferPools' section, I included ALL values for all situations, so the ONLY value you want to change there is UsePools (which is an ON/OFF switch)so, that way, you have the choice to either run with no BufferPools OR run with BufferPools, but using the most efficient way of doing so.As for what is RejectThrelshold, you'll need to search the forum for that to see my previous posts. Think of it as the 'Alternative' Holy Grail to BP=0UsePools=0 will IGNORE PoolSize and RejectThresholdUsePools=1 will use a BufferPool with the size you specify in PoolSize

Hi Rich,I don't run them in SLI, but I do run the GTX260 on PhysX while the 295 runs normally. I have never seen a benefit running SLI or even my configuration with FS. The higher end video card sure does help but really only when cranking out higher resolutions, so not much noticed to most. There is very little (if any) difference when I run just my 260 or just my 295. But it does help when running my resolution in 5040x1050. Other than that I never seen a difference in running the 260.Edit: You wouldn't be able to run them in SLI anyway, not your mentioned configuration anyway. You can't run a 260 in SLI with a 9800 and both need to be the same GPU to run SLI.

Oh... re-reading Dan's post... i'd probably get the crash @ 100 ft with crash detection on.Rich

DanP,Do you see any advantage with your 285/260 in SLI?

Crash detection is disabled. would I get different resuts with crash detection enabled?

Andrew beat me to it but yes, this does sound like your realism settings are set to not detect crashes. Of course this doesn't fix the problem, but being shot up 500' in the air is exactly what is done in that case when a crash is detected. I still cannot find my completed KBOS file which is sad, but trying my posted one above produced a crash (not lock up) on my first attempt flying 33L. Harry may be on to something here, but I can't see where the issue is in ADE. It seems like there's an invisible mdl right before the runway and my MD-11 just crashes 100' above the runway threshold.

Dan, Rich,Seen this before.There's a common thing about these runways, approach over water and a threshold, right when making land.KJFK 04L qualifies for this scenario as well.IMHO, It's an elevated threshold too close to (underlaying) water that causes this problem.Have seen this in the Queen and MD11 as well.Adapting the default scenery with ADE helped solving this problem on my side for known airpot/rwy situations.Would be even better if the PMDG aircraft could cope with this.Regards,Harry@Dan: working on a signature.

No... It is definately not that. It leaps forward just past the 50 to 100 foot call and is down on the ground spoilers deployed. Wondering if some sort of pre rendering issue?Rich

Rich, I am afraid it sounds like you are touching down before you expect to due to a high pitch angle at touchdown and the wheels are way back there much lower than the cabin. Check your playback friend.