oneill875

http://forum.avsim.net/topic/344926-fsx-head-movement/ Have you tried this? Worked for me Dan.

Hi, Love the sim so far. Just got in from work and purchased and took her up for a quick flight. I pressed the TERR button then on the lower display control panel pressed the NAV button and got a FSX fatal error. Can't reproduce yet so hopefully its a one off... Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: PMDG_777X.DLL, version: 1.0.0.0, time stamp: 0x52256029 Exception code: 0xc0000005 Fault offset: 0x00247710 Faulting process id: 0x994 Faulting application start time: 0x01cea99553819aab Faulting application path: C:\FSX\fsx.exe Faulting module path: C:\FSX\GAUGES\PMDG_777X.DLL Report Id: 221c70b6-158f-11e3-8597-10bf4875e7f5 Cheers, Dan.

What was the stop code? Blue screens are nearly always hardware related

Good choice... There is no "realistic way" in the sense that you can't realistically look over your shoulder and look at a monitor in real life. So I guess that you could say that it really come down to personal preference. I realise that this may not seem helpful at first, it will however help you realise that only you can tell what seems realistic when you look at things. It will help with a larger monitor so you can set a narrow FOV with some peripheral vision, also beware of sunlight/ reflections. Set FSX in windowed mode while you change TIR settings in real time, this will help. Dan

I use Linda to assign pmdg specific functions to my warthog like TOGA and auto throttle soft disconnect etc...... I have in the past used FSUIPC too but at the moment Linda is good.

Have you set sensitivity to 100% in the FSX controller setup? Does it respond correctly in windows or device properties etc...

Yes it was, thanks. I forgot all about force feedback in FSX.

It's absolutely a game changer, quite literally... It definitely enhances immersion, particularly with flight sims and more so combat flight sims when you need to be " heads up". I even use it for sim racing too. As stated you set up profiles for different games and it will start up with windows.

I've posted this over at the PMDG section but this is probably a more relevant forum. Been away from flight swimming for a while and I've just re-installed FSX and the 737. I use a thrustmaster warthog for flight controls and I have the thrustmaster T500 wheel and pedals for racing, the pedals are configured in simple mode for rudder control. My issue is that whenever I move the aircraft on the ground then my wheel will start slowly turning about 90 degrees left to right, slowly increasing in speed so that by V1 it's going hell for leather! I've checked through the control options and I can't seem to find this control? Anyone else have similar hardware/ issues? Cheers, Dan.

Been away from flight swimming for a while and I've just re-installed FSX and the 737. I use a thrustmaster warthog for flight controls and I have the thrustmaster T500 wheel and pedals for racing, the pedals are configured in simple mode for rudder control. My issue is that whenever I move the aircraft on the ground then my wheel will start slowly turning about 90 degrees left to right, slowly increasing in speed so that by V1 it's going hell for leather! I've checked through the control options and I can't seem to find this control? Anyone else have similar hardware/ issues? Cheers, Dan.

I too had this problem initially. What you need to do is assign the left throttle lever (disconnected from the right) to the LEFT Engine lever. This is not visable initially until you scroll down in the callibration window.

The best motto ever: check, check and check again! Lol

Have you tried closing up the discontinuities?Then cycle through the CDU legs page with the EFIS on plan mode to view your route.Dan.

Of course Simon, I was only joking around. I know you are a professional and would not do anything to risk safety. I really appreciate you being on this forum as you give a personal view to the flying of these things that we all wish we could. Dan.

Hey Simon, thanks but make sure you don't get fired or anything trying to get photos of the flight deck during critical flight regimes. lol Cheers, Dan.

Exactly, what I meant was the motherboard controller/hub, as each can only assign 500 mA, so if you use an external hub as well then with today's hardware throttles and yokes etc you will run into problems.Often the ports on the rear of the case are on a different bus from the ones at the front so a good way to split the load.I'm no expert but this is how I understand the USB architecture.Dan.

How many USB ports so you have?Try using a different USB controller hub for each piece of hardware ( ie; one at the front of the PC and one at the rear).Just a thought, perhaps one is on the way out?I occasionally have a problem with one of my USB ports on the front of my PC and this affects my Track IR.Dan.

Yeah hotfix 2 was the best for me too, no freezes or crashes at all but PMDG said they left something in it for de-bugging I think and that is why we should change to hotfix 3.I wonder what it was?Dan.

Is it anything to do with the NGX default start up panel config?When you install a livery you also accept changes in the livery ini file for that livery.Perhaps changing the panel state in the ini or something may help?Just a thought,Dan.

Either you don't have enough fuel for the route or you are low on reserve fuel.Try loading more fuel and keeping the reserve you have or lower the reserve figure in the FMC.Dan.

I don't know if this will help but here are a few things to try.Try starting from a different panel state, after that try deleting your default flight to get back to the Trike at Friday harbour. This solved my engines not starting correctly and it has helped others too.At what stage in the preflight programming of the FMC do you access the Take off page? Have you already executed a route? Have you completed the Performance initialisation?I sometimes have a CTD when on climb out and thrust reduction is selected, I have to manually input these during preflight to stop that happening.Dan.

What about a FAQ? I'm not bloody writing it though! LOL. A fair bit of work but will save countless repetitive posts and together with the above, this would make finding things on here a bit easier. Actually, so would a search function..........Hmmmmm Dan.

Its also in the failures menu, I just tried it out. Go to engines then scroll through the pages until you find V1 failure or VR failure, click to arm in say 5 seconds. Enjoy. Also it normally takes between 30 -45 seconds to get to V1 depending on thrust used and weight, altitude etc.......... Dan.

I've had this on one saved flight I use and also a couple of other times now on the 800 (non WL). For me the ONLY way to stop the crash is to "Hard Code" the thrust reduction altitude into the CDU and not accept the default value. So when on page 2 of the Take Off pages, re-input the value so that it comes up in large font. Try that and get back to me as I think you are the only other person I've seen with this problem. Dan.

Some STARs are for a specific runway direction.For example LEPA has a STAR for runways 24 L/R and a different one for runways 06 L/R.Dan.